Privacy Policy

1. What data we collect

Account. Email, name and photo (if you provide them), username, user ID and session data, managed by Clerk. You can sign in with your email or username, or with your Google account. We use your verified emails to redeem Pro invitations.

Plan and access. Plan (Free or Pro), subscription status, complimentary Pro grants (including the first 7 days) with their audit record, and in-app reminder preferences and dismissals.

Preferences. Language, theme, distance units and other planning preferences.

Your trips. Trips, destinations, activities, dates, routes, notes, accommodation and booking details (for example, confirmation numbers) and other data you add.

Documents. Files you upload (stored in Amazon S3) and their metadata (name, type, size, category and tags).

Public and community content. Creator profile (display name, username, bio, photo and cover, languages, travel style, external links and experience map), published guides, reviews, follows and followers, saves, and guide views and copies. Also profile reports you send (reason and details).

Purchases and sales.

• Buyers: orders (guide, amount, currency, status, refunds, disputes, refund policy version and Stripe identifiers).
• Creators: Stripe account ID, country, enablement status, commission credit ledger, and the version and date you accepted the Creator Terms.
• Card details are received and processed by Stripe (guides) or Clerk Billing (Pro). RideHop does not store them.

Searches and location. The text you search for, the visible map area and the coordinates of places in your trip, to find places and nearby points of interest. RideHop does not access your device’s GPS location.

Usage and technical data. Pages visited, referrer, device and browser type, approximate country, performance metrics and server logs (including IP address). Also product events: when a plan limit stops an action (limit_hit), when the upgrade window opens (upgrade_opened), when a Pro subscription activates (checkout_completed) and when complimentary Pro ends (grant_expired). These events include only the plan and the reason or grant type, never the content of your trips, your documents or your account details.

2. How we use it

• To provide the Service: accounts, planning, storage, maps, search and share links.
• To manage plans, grants, purchases, guide licenses, refunds and creator payouts.
• To show public content (profiles, guides, reviews) on RideHop and in our public views: the discovery API and the read-only MCP, which never expose private trips or paid or unlisted content.
• To moderate, prevent fraud and abuse, and keep the Service secure.
• To provide support and escalate cases to support@ridehop.ai.
• To measure and improve the product with aggregated analytics.
• To meet legal and tax obligations.

We do not sell your personal data or use it for third-party advertising.

3. Who we share it with

Providers that process data on our behalf:

• Clerk: authentication and Pro billing.
• Supabase: database, in the us-east-2 region (Ohio, USA).
• Amazon Web Services: document storage, in the us-east-1 region (Northern Virginia, USA).
• Vercel: hosting, web analytics and Speed Insights.
• Google: Google Analytics and Google Maps Platform/Places, which receive searches and coordinates.
• Mapbox and CARTO: map loading; they receive your IP address and the map area you view.

Stripe. Processes guide payments on the selling creator’s account. If you are a creator, we send Stripe your contact email, display name, country and RideHop ID to create your connected account. Stripe collects your verification and bank details directly.

Creators. If you buy a guide, the selling creator sees in their Stripe Dashboard the payment details needed to handle the sale, refund or dispute, such as your email, the cardholder name, country and amount.

The public. What you publish (profile, guides, reviews) is visible to anyone. A trip shared by link is visible to anyone with the link; it does not show your private notes.

Authorities. When the law requires it.

4. Cookies and similar technologies

We use cookies and local storage:

• To keep you signed in (Clerk) and remember preferences (language, theme).
• For analytics: Google Analytics uses cookies; Vercel Web Analytics and Speed Insights measure visits and performance.

We do not load third-party analytics on invitation acceptance or access administration pages, and we strip the URL fragment from events.

5. International transfers

DRESH LLC is in the United States and its providers process data mainly in the United States (for example, the app is hosted on Vercel in the iad1 region, Washington, D.C.). If you are outside the United States, your data is transferred there. We rely on our providers’ data processing agreements, which include standard contractual clauses where applicable.

6. Retention

We keep your data while your account is active. Moving from Pro to Free does not delete your trips or documents. When you delete a trip, it is permanently removed from the app.

If you ask us to delete your account, we delete your personal data within 30 days. We keep only what we must: order, refund, payment and tax records for up to 7 years, and access and moderation audit records for as long as needed to resolve disputes, also up to 7 years. Backups and our providers’ logs are deleted on their normal rotation cycle.

7. Your rights

Depending on your country, you can request access, correction, deletion, portability or objection, withdraw your consent and complain to your data protection authority (for example, in Argentina, the Agencia de Acceso a la Información Pública).

You can edit your profile, trips and preferences in the app. You can delete your sign-in account from your account settings; to also have us delete your trips, documents and the rest of your RideHop data, write to support@ridehop.ai. For any other request, write to the same address. We will verify your identity and respond within 30 days.

8. Security

We use per-user access controls in the database (RLS), server-side permission checks, signed webhooks and restricted-access storage for documents. No system is completely secure. Tell us about any incident at support@ridehop.ai.

9. Minors

RideHop is not intended for anyone under 18, and we do not knowingly collect their data. If you believe a minor has given us data, write to us and we will delete it.

10. Changes

If we change this Policy materially, we will notify you in the Service before the change takes effect.

11. Contact

DRESH LLC (RideHop AI) · 5830 E 2nd St, Ste 7000 #18280, Casper, WY 82609, USA · support@ridehop.ai · ridehop.ai