Privacy Policy

Account information

You need an account to use Rotori. When you sign up we take:

• Email sign-up: your email and password. We never store the password in plain text — it's securely hashed (bcrypt).
• Sign in with Apple: Apple hands us an identity token on your behalf. If you chose "Hide My Email", we only see an Apple relay address ([email protected]) — never your real email.

In-app data

What you create while planning is sent to us so you can see it on your other devices:

• City picks, dates, flight details (departure/arrival times, airline names)
• Hotel names, addresses, check-in/check-out dates
• Your activity list, reminders, pre-departure checklist
• If you attach a ticket photo — that photo is stored with your plan only

Location data

Your location does not reach us. Rotori uses GPS locally on your device for "discovery badges" (like the one you earn when you arrive at Senso-ji Temple). This runs entirely on your device — your location isn't sent to our servers, logs, or any third party.

Photos and camera

If you want to capture a boarding pass, we ask for camera or photo library access. Selected photos stay only in your plan; they're not sent anywhere else.

Offline text translation

Text entered in the Premium Pocket Translator and its translation result are processed on your device. We do not send them to Rotori servers or advertising systems, store them, or log them. Required language models may be downloaded by Google ML Kit when you request them during setup; text translation then runs on the device. This feature does not use the microphone or speech recognition.

AI-assisted route review (Premium)

When you create a new plan with Premium and have allowed AI data sharing in the app, the route order is reviewed. For this, the days' stop list (title, time, duration, category, latitude/longitude), the weather code, and — if booked — your hotel's name + city + coarsely rounded location (roughly 1 km precision — the exact address is never sent) are sent to OpenAI to get a better ordering suggestion. This request never includes flights, tickets, personal notes, contact details, or your account identity. Under OpenAI's API usage policy, this data is not used to train their models.

Rotori Assistant (AI chat)

When you use the in-app assistant, the messages you write and your trip plan (cities, dates, each day's stops and times, hotel names and check-in/check-out dates) are sent to DeepSeek to generate an answer or a suggested change. Your email address and account details are not included. DeepSeek may process this data on servers outside your country, including in China. Rotori does not store the conversation on its servers; it stays on your device. Changes the assistant suggests are only applied after you confirm them.

Your permission for AI features

The assistant, route review and reservation reading send data to third-party AI services (DeepSeek and OpenAI). Before any of these send data for the first time, the app explains what is sent and to whom, and asks for your explicit permission. If you don't allow it, nothing is sent and these features stay off. You can withdraw permission at any time from "AI permission" in the app menu.

Pasting a reservation

When you use "paste confirmation email" on the hotel or flight form and send the text, the text you pasted is sent to OpenAI to fill in the form. It can contain whatever is in your confirmation email (e.g. your name, booking/PNR code, hotel or flight details) — you can delete any part you don't want to share before sending. Rotori does not store, cache, or log this text on its servers; only the extracted fields (dates, times, hotel/flight details) are written to your plan. Using this feature is optional; you can always fill in the form by hand.

Price-tag scanning

When you scan a store price tag, on-device OCR (Google ML Kit) reads the text; that text (e.g. product name and price) is sent to OpenAI for parsing. The photo itself is never uploaded — only the text extracted on your device. The result is cached briefly on our server to avoid re-processing the same tag; the cache key carries a one-way hash of the text, not the text itself.

Product analytics and technical diagnostics

To improve Rotori's reliability and route quality, we keep limited product events linked to your signed-in account: app/screen opens, route-generation success or failure, selected cities and dates, generated stop order, times, transport modes, and aggregate duration/count metrics.

The analytics route record excludes flights, hotels, tickets, free-form notes, contact details, photos, map links, precise GPS location, and the contents of dietary preferences. Dietary and budget fields record only whether a preference exists or its count.

For crashes and technical errors, Sentry may receive a stack trace, app version, device/OS information, safe screen name, and pseudonymous account ID. Email, screenshots, UI hierarchy, and route JSON are not sent to Sentry.