Privacy Policy

This policy explains what Seenary collects, why, who it is shared with, and what you can do about it. It describes the product as it actually works — if something here does not match what you see, tell us and we will fix one or the other.

1. Using Seenary without an account

You can browse the site, read about a destination, talk to the companion and generate one itinerary without signing in. For that one plan we do not ask for your name, email or phone number.

So that one free plan stays one, your browser or app creates a random identifier and keeps it on your device. We never store that identifier: we store only an irreversible fingerprint of it (an HMAC-SHA256 digest, which cannot be turned back into the original). It is used for nothing except recognising that this device has already had its free plan. If you sign in afterwards, that plan and anything attached to it moves to your account.

2. What we collect when you have an account

• Your identity. If you sign in with a phone number we store that number. If you sign in with Google or Apple we store the email address, name and profile picture URL they give us, and an identifier that links your account to theirs. You can optionally add a first and last name, a date of birth and an avatar.
• Your profile. A display name (what people you plan with, and anyone who reads a trip you share, see instead of your full name), your home city, and the currency, units and language you prefer.
• A profile photo, if you upload one: it is re-encoded on our server without the camera details or location a phone photo carries, stored privately on Seenary’s own storage, and deleted when you remove it or delete your account.
• Your trips. Destinations, dates, who is travelling, children’s ages if you give them, how you are getting there, dietary needs, where you are staying, the notes and messages you write to the companion, the itineraries Seenary generates and every earlier version of them.
• Your preferences. The travel styles, interests, pace, dietary choices, walking and driving limits, budget tier and favourite places you save, and the patterns Seenary learns from your trips. All of it is listed on the Personalization page, and anything there can be removed. A single trip can be planned without them (“Don’t use my saved preferences for this trip”).
• Trips you plan with other people. Who you invited, the role you gave them, their suggestions, comments and the trip’s activity history.
• What you publish. Stories, routes, tips, comments, “helpful” votes, saved places and reports, as described in section 5.
• Notifications. If you turn them on, the push endpoint or token for that device and the label you gave it; and, for stories, the notifications shown on the bell.
• Photos you add to a trip recap or a story.
• Plans and payments. Which plan your account is on and, where you buy one, the records in section 7.
• Messages you send us through Talk to us, and your conversations with the support assistant (section 6).
• A calendar link, if you turn “Calendar subscribe link” on in your profile: a private token that lists your upcoming trips to the calendar app you paste it into. Turning it off stops the link working at once; turning it on again makes a new one.

3. What we record about how Seenary is used

Seenary records product events against your account — a trip was created, an itinerary was generated, a plan was shared, the toolkit was opened — with the event type, the trip it belongs to and the time. We use these to see whether the product works, not to build a profile of you for anyone else.

The mobile app can send additional usage events. Those are off unless you turn on “Usage analytics” in Settings, and turning it off stops them and clears what is queued on the device.

For every AI call we keep an accounting record: what it was for, which provider and model, how many tokens it used, what it cost and whether it succeeded. The content of the prompt and the reply is not kept in that record. The same operations — a plan, a change by chat, a translator turn, an import — are also written to a usage ledger for your account, which is how your plan’s allowances are counted.

Our application database does not store IP addresses or browser fingerprints. Like any website, the servers that deliver Seenary keep short-lived technical logs, and those are used only to keep the service running and secure.

4. Where your information goes

We do not sell your personal information, we do not share it with data brokers, and we do not use it to target advertising. We share only what a particular feature needs, with the companies that provide it:

• Our AI providers. Seenary is built to work with OpenAI, Anthropic and Google’s Gemini models; today’s calls go to OpenAI. The provider receives the trip details and the messages needed to write your itinerary or reply in the chat, the descriptions of the stops in a plan, the lines of a sign you point the app’s sign scanner at, what you say or type into the app’s voice translator, the text and photos of a story, tip or comment you publish (for review, section 5), and what you write to the support assistant (section 6). The camera picture stays on your phone, and Seenary never receives a recording of your voice: your phone’s own speech recognition (Google’s on Android, Apple’s on iOS) turns it into text first. With no connection, a language you download for the sign scanner (Google’s ML Kit, about 30 MB) translates the sign on your phone itself, and nothing is sent.
• Google Maps Platform receives place names and destinations so we can find real locations, distances, opening hours, place details and photographs. The coordinates it returns are cached for up to 30 days.
• Geoapify, a geocoding service built on OpenStreetMap, may receive a place name and the destination it belongs to (“Powered by Geoapify · © OpenStreetMap contributors”). Nothing about you is sent.
• OpenStreetMap data reaches Seenary as downloaded extracts (through Geofabrik) and through the Overpass service, which builds the places and roads in a plan, the offline map packs (map tiles from Protomaps) and the emergency places in the travel pack. Where OpenStreetMap cannot answer, Google Maps Platform is asked instead. These are requests for map data; nothing about you is in them.
• Viator provides the bookable experiences a plan may list. Seenary asks Viator about a destination, not about you, and keeps what it returns for seven days. A “Book” link is an affiliate link to Viator’s own site; once you open it, Viator’s policy applies.
• Wikipedia / Wikimedia Commons is used to fetch freely licensed destination photographs, each credited on the page and on Photo credits. This is a plain request for a picture; nothing about you is sent.
• Frankfurter (api.frankfurter.dev) gives our server the exchange rates the budget estimator converts with. Nothing about you is sent.
• Google and Apple, if you choose to sign in with them in the apps. On the website, “Continue with Google” is handled by Clerk, which receives what Google shares for that sign-in.
• Google Analytics (Google) receives the pages you open on the website and technical details of your browser and device, so we can see how the site is used. It sets cookies, which the Cookie Policy lists.
• Firebase Cloud Messaging (Google) delivers notifications to the app, if you turn them on.
• Razorpay handles payments on the website; Apple’s App Store and Google Play, through RevenueCat, handle them in the apps. See section 7.
• Resend sends the emails Seenary writes to you (it receives your address and the email). Zoho Mail carries the messages you send us through Talk to us, and our replies.
• Amazon Web Services hosts Seenary and stores its database. Photos you upload — your profile photo, recap and story photos — are kept in a private S3 bucket in the Mumbai region (ap-south-1).
• Official alert feeds — India’s NDMA Sachet and the global GDACS feed — are read by our server to check the places in upcoming trips. We also link to the government tourism and park websites for a destination. Nothing about you is sent until you open one of those links yourself.

We may also disclose information where the law requires it, or where it is necessary to protect Seenary or someone’s safety.

5. Stories and community routes

You can publish a story about a trip or a place, and a route (an itinerary Seenary planned) for other travellers to use. Both are public once published, under a community handle made from your first name — never your full name or email. A public story shows the month and year of the trip, not the exact dates, and never shows where you stayed. A public route shows the stops, not your stay.

Every public word — a story, a route, a tip, a comment — goes through an automated screen and then an AI review before it appears. Photos are re-encoded with the camera details and location removed, checked by an AI vision call, and stored on Seenary’s own storage; a photo the check is unsure about is shown only to you until a person has looked at it. Other travellers can comment, mark a story or route “helpful”, save a place from it, copy a route (“Use as template”) or start their own plan from a story (“Reuse this trip”), and report it. Three reports from different people hide an item until we have reviewed it. Stories written by us are labelled “From the Seenary team”.

Comments on your stories reach you on the bell and, once a day, in a digest email on the “stories” stream, which you can turn off in Settings. Contributor levels are earned from what your routes do for other people (copies, helpful votes); nobody rates a person.

6. The support assistant

A floating assistant on every page answers questions about Seenary. What you write to it is sent to our AI provider together with the context it needs to help — your account, your trips and their offline packs, what the app reports about your phone — and is stored as a support ticket so a person can take over, which they may do at any time. Anything that looks like a card number is removed before a message is stored. When the assistant escalates, the ticket is emailed to the team.

7. Plans and payments

Planning is free: a Free account can make three itineraries a month (at most three a day). Where paid plans are offered, a Trip Pass (₹149, one trip, 30 days from first use), Plus (₹199 a month or ₹1,499 a year) or Pro (₹399 a month or ₹2,999 a year) unlocks the in-trip toolkit: offline map packs, the voice translator, whole-board sign translation, more imports, shared editing and further trips.

Payments on the website go through Razorpay; in the apps through the App Store or Google Play, reported to us by RevenueCat. Seenary never sees or holds your card number. We store what the provider reports: the amount, tax, currency, country and invoice reference, and which plan it bought. A subscription cancelled with us runs to the end of the period you paid for; one bought in a store is cancelled in that store.

8. Trips you share

Sharing is something you switch on, per trip. Two things are worth knowing before you do:

• A view-only link can be opened by anyone who has it, without signing in. We store the link’s secret in a protected form rather than in plain text, and you can revoke it at any time, which stops the old link working.
• People you invite see the trip’s contents and your display name, and can act according to the role you gave them — edit, suggest, or read. Their comments and suggestions stay with the trip’s history. Removing someone ends their access but does not erase what they already saw.

9. Checks before a trip, and the emails we send

Before a trip, and about once a month for a trip further out, Seenary checks the stops in your plan again against the map data and the official alert feeds in section 4. Nothing in your plan is changed; you get an email only when something new was found.

The other emails are: a welcome (one per address, ever), a note when a trip is created, reminders two weeks, three days and the morning before a trip, an offline set-up checklist, a mid-trip note asking for photos and memories, the trip story afterwards, an invitation to share your route, a purchase confirmation, the stories digest, and the results of the checks above. Each carries an unsubscribe link for its stream (trip emails, recaps, plan-again nudges, stories); Settings lists them too. Accounts that belong to the app stores’ test devices are never emailed.

10. Devices, sessions and the offline copy

When you sign in on the website you choose whether to stay signed in on that device; untick “Keep me signed in on this device” on a shared computer and the session ends after 30 minutes of inactivity, taking the trips saved on that computer with it. “Sign out of all devices” in Settings ends every session, stops push notifications to every device, and takes effect on each device the next time it talks to us.

Your trips, travel packs and offline toolkit are kept on your device so they open with no signal. If you set an offline lock (a PIN or this device’s passkey, fingerprint or face), those copies are encrypted whenever you are signed out and unlocked only by you. Logging out removes them.

Offline navigation in the app uses your phone’s location only while the Directions screen is open. Your position is never stored and never sent to Seenary. The same is true of “Explore nearby”: your position goes to the map provider for that one search and is not kept.

11. How long we keep it

Trips, itineraries, preferences, stories and support tickets stay until you delete them or delete your account. Deleting your account from Settings (or from the delete-account page) removes your account and the trips, itineraries, preferences, photos, stories, routes and comments attached to it; this cannot be undone.

Two things deliberately outlive an account: the device fingerprint described in section 1, so the same device cannot take a second free plan, and a record that a welcome email was sent to your email address, so a new account on the same address does not get a second one. Coordinates from Google Maps Platform are kept for at most 30 days and Viator’s experiences for seven; neither contains anything about you.

12. Your choices

• Edit or delete any trip, at any time; publish or unpublish any story or route, at any time.
• See everything Seenary has learned about how you travel, and remove any of it, on the Personalization page.
• Turn usage analytics, notifications, the calendar link, automatic offline downloads and the stories digest on or off in Settings and your profile.
• Unsubscribe from any email we send, using the link in it.
• Cancel a paid plan, or sign out of every device, from Settings.
• Delete your account, and everything attached to it, from Settings.
• Ask us for a copy of your information, or ask us to correct or delete it, through Talk to us.

13. Children

Seenary is not intended for children under 16, and we do not knowingly collect their information. If you believe a child has given us information, tell us through Talk to us and we will remove it.

14. Changes to this policy

If we change this policy we will update the date at the top of this page, and we will tell you in the product if the change is a significant one.

15. Contact

Questions about your information, or any request under this policy, can be sent through Talk to us.

This policy is written and published in English. Where you read it in another language, that translation is provided for convenience and is produced automatically; the English text is the one that applies.