Privacy Policy
OdisTrip
Version 1.4 — October 6, 2026
This policy explains what data OdisTrip processes, why, who it is shared with, and how you can exercise your rights under Brazil’s General Data Protection Law (LGPD, Law No. 13,709/2018).
Controller: the independent operator of the OdisTrip app in Brazil.
Contact: Profile → Help and support in the app. Published email: [email protected].
We do not sell personal data.
1. Data we process
| Source | Data | Purpose |
|---|---|---|
| Google or Apple account | Account identifier, email, name, and photo if provided by the provider | Authenticate you and display your profile |
| Information you add in the app | Trips, stops, times, notes, checklist, budget, and custom places (address or map pin) | Provide the itinerary service |
| Smart mode assistant | Destination, dates, lodging, travel companions (including children’s ages), interests, pace, budget, must-see places, dietary restrictions, allergies, and free-text information you provide | Create, optimize, and adjust a smart itinerary (Premium) |
| Trip documents | Files and photos you attach to a trip (such as receipts and reservations), visible only to you | Store and open your documents, including offline |
| Support | Messages you send through Profile → Help and support and the team’s replies | Respond to your request |
| App usage | Product events before sign-in linked to an anonymous installation identifier, associated with your account ID after you sign in | Understand whether the app is useful and improve the product |
| Store / subscription | App identifier in RevenueCat and subscription status (the store processes payment) | Provide Premium access |
We do not ask for your Brazilian tax ID (CPF), home address, or card details. Payments are handled by Apple or Google.
2. Legal bases under the LGPD
- Performance of a contract: account, itineraries, place search, maps, and account deletion.
- Legitimate interests: product analytics (PostHog) and diagnostics (Sentry), using only what is needed and without selling data.
- Consent / store rules: subscription purchase and restoration (RevenueCat + App Store / Google Play).
- When you use Smart mode, sending the assistant preferences to DeepSeek is necessary for that itinerary request. If you do not want this processing, use Manual mode.
3. Who receives the data
We operate the app with the following service providers / processors, each with its own privacy policy:
- Supabase — authentication, database, and product files.
- Our server (API) — Places, itinerary generation, account deletion, and subscription webhooks.
- Google (Places, Maps, and Google sign-in) — place search and details, maps, and authentication if you sign in with Google.
- DeepSeek — itinerary generation and optimization using assistant preferences and places in the city’s catalog.
- Apple — authentication if you sign in with Apple; billing if you subscribe through the App Store.
- Google Play — billing for subscriptions purchased through Google Play.
- RevenueCat — subscription status between the app and the stores. It does not receive your card number.
- PostHog — usage events linked to an anonymous identifier before sign-in and to your account ID afterward, without your name or email in the analytics profile. It also receives server-sent subscription events (start, renewal, cancellation, and expiration, with product, currency, and revenue when available).
- Sentry — errors in the app and server.
We record screens only during trip-creation onboarding, sign-in, and subscription offers, including welcome and completion screens. Text shown on screen and text you enter are masked. We do not capture console logs or network traffic in these recordings. Analytics events do not include destinations, exact dates, coordinates, or free text.
Some of these services are located outside Brazil, especially in the United States; DeepSeek says it stores data in China. We use them because the product depends on these tools. Contact support with questions about international data transfers.
DeepSeek: receives the assistant data listed in Section 1 and names / details of places already listed in the catalog, so it can select, order, and explain the itinerary. It does not receive your name, email, or Google Places key, and it must not invent businesses. Data is sent only when you request an action in Smart mode (create an itinerary, optimize it, adjust a day, or replace a stop).
Places / Maps: place searches, details, and map tiles are sent to Google to show real places.
4. Retention
We keep your account and trips while your account exists. The server’s place cache supports the catalog for anyone searching the same city; it is not your personal itinerary.
PostHog events and Sentry errors follow each service’s standard retention periods, limited to what is needed for the product and diagnostics.
5. Account deletion (in the app)
In Profile → Delete account, after you confirm, the app calls DELETE /account. This deletes your authentication user and, in cascade, the trips, stops, checklist, and expenses linked to that account. This cannot be undone.
If you signed in with Apple, the app asks Apple to confirm the deletion and revokes OdisTrip’s authorization in your Apple account.
Deleting your account does not automatically cancel an App Store or Google Play subscription. Cancel renewal in the store.
Backups and error logs may take a short time to disappear completely. Requests to Google, Apple, PostHog, Sentry, or RevenueCat follow each provider’s own process. Contact support if you need help making one of those requests.
6. Your rights under the LGPD
You may request confirmation of processing, access, correction, anonymization, portability, information about data sharing, and withdrawal of consent when applicable. You may also object to processing based on legitimate interests.
Practical options:
- correct your name or email with Google or Apple (the app reads the information the provider sends);
- edit or delete trips and stops in the app;
- delete your entire account through the in-app process above;
- send other requests to [email protected].
You may file a complaint with Brazil’s National Data Protection Authority (ANPD).
7. Children
The app is not directed to children under 13. We do not knowingly collect children’s data. If we learn that an account belongs to a child under 13, we delete it.
8. Changes
The current version is the one at this URL, with its date shown above. We will reflect significant changes here. The app continues to point to PRIVACY_URL.
Questions: [email protected].
This English translation is provided for convenience. The Portuguese version prevails in the event of any discrepancy.