Privacy Policy

Effective 19 September 2026. This policy applies to the JustTrippin mobile app (com.justtrippin.app) on Google Play, the JustTrippin web app at justtrippin.app, and the JustTrippin API that serves them. Together, these are "JustTrippin" or "the Service".

Your use of JustTrippin is also governed by our Terms of Service.

1. Who we are

JustTrippin is operated by JustPanthering, a sole proprietorship at Plot No. 308, Mother Teresa Nagar, Tundul Math-Toli, Ranchi, Jharkhand 835303, India. For the purposes of India's Digital Personal Data Protection Act, 2023, we are the Data Fiduciary for the personal data described here.

For anything in this policy, including requests about your data, write to support@justtrippin.app. We aim to respond within 7 days and in all cases within 30 days.

2. The short version

JustTrippin is a trip planner. We collect the account details needed to sign you in and the trip content you choose to create. We do not run advertising, we do not use analytics or tracking SDKs, we do not collect an advertising ID, we do not request access to your location, contacts, photos, or camera, and we do not sell or rent personal data to anyone.

Two things are worth knowing before you read the rest:

• A trip you share is visible to the people you share it with. Your comments, and the itinerary you build, are readable by every member of that trip. Nothing in JustTrippin is public, and no trip is visible to anyone who was not invited to it.
• If you let the app notify you, we store a token identifying your phone, and the text of a notification — which can include a short extract of somebody's comment — passes through Google to reach it. Section 3.5.

3. What we collect

3.1 Account information

Sign-in is handled by Google Firebase Authentication. You can sign in with Google, with Apple, or with an email address and password.

We receive and store:

• your email address (where your sign-in provider supplies one);
• your display name and profile picture URL, where your provider supplies them;
• a Firebase user identifier that links your sign-in to your JustTrippin account.

We never receive or store your password. If you sign in with an email and password, that credential is held by Firebase Authentication and is never sent to our servers. If you use Apple's "Hide My Email", we only ever see the relay address Apple gives us.

3.2 Profile and preferences

Information you give us when setting up your account or in settings:

• your display name;
• your home base — the place label you pick and its coordinates;
• your home time zone, language, and preferred display currency.

3.3 Trip content

Everything you create in the app. This is the substance of the Service and it is stored on our servers so it is available across your devices:

• trips: title, destination, start and end dates, time zone, base currency, status, and cover image;
• days: titles and your notes;
• itinerary items: title, description, type, times and durations, ordering, cost amounts and currency, booking references, and booking links;
• timestamps for when each of these was created and last changed.

Please treat trip notes and booking references as you would any note stored in a cloud service. Do not put payment card numbers, passport numbers, or similar identifiers into free-text fields.

3.4 Trips you share, and comments

A trip can have more than one person on it. If you invite somebody, or accept an invitation to somebody else's trip, we also store:

• membership: which trips you are on, the role you hold on each (viewer, commenter, admin, or owner), who invited you, and when you joined;
• invitations you create: the role offered, when the link expires, and who accepted it. The link's token is stored only as a hash, so we cannot reconstruct a link from our database;
• comments you write on a trip, a day, or an item: the text, who you mentioned in it, and when it was written or last edited;
• when you last read a trip's comments, which is how the unread count works.

Everyone on a trip can read that trip. Your comments, your name, and your profile picture are visible to the other members, and the itinerary is something you are all editing together. An admin or the owner can see the members list and remove people from it. This is what sharing a trip means, and it is the only circumstance in which another person sees your content — no trip is public, none is discoverable, and an invitation is something a member deliberately sends.

Comments are not private messages. There is no direct messaging in JustTrippin: a comment belongs to the trip it is on, and it stays readable by the trip's members until it or the trip is deleted.

3.5 Notifications

When something happens on a trip you are on — somebody comments, mentions you, joins, leaves, or deletes the trip — we write a notification record for each person who needs to know. You can read these under the bell in the web app and in the mobile app.

A record holds a copy of what it needs to stay readable: the trip's title, the name and profile picture of the person who did the thing, and, for a comment, an extract of up to 140 characters. It is a copy on purpose, so that a notification telling you a trip was deleted still makes sense after the trip is gone.

A record belongs to the person it was written for. When you comment on a shared trip, an extract of that comment is stored against each of the other members, under your name. Deleting your comment deletes those records too.

We keep notification records for 90 days, after which they are deleted automatically. Nothing you do is required to make that happen, and the lists you can read never show anything older.

Push notifications on your phone. If you allow notifications on Android, the app registers with Google Firebase Cloud Messaging (FCM) and sends us the registration token that identifies your phone, which we store against your account together with your phone's model name — "Pixel 8" — so you can see on the settings page which phones are receiving your notifications.

When we send you a notification, its title and body — including the comment extract described above — are passed to Google, which delivers them to your phone. Google carries the message on our instruction; it does not use it for anything of its own.

We delete the token when you sign out of the app, when you delete your account, and automatically if a phone has not registered for 270 days. Turning every notification off in the app's settings stops us sending anything, and turning notifications off in Android's own settings stops your phone showing them.

Trip reminders do not involve us or Google at all. The reminder you get the evening before a trip, each morning while you are on it, and before something with a time on it, is worked out and scheduled by your own phone from the trips it has already downloaded. No request is sent to schedule one, nothing about them leaves your device, and they keep working with no connection.

3.6 Place searches

When you search for a place, the text of your search and the map area it relates to are sent to a place-search provider so it can return results. Which provider depends on what you are searching for:

• Searching for somewhere to add to a trip — a restaurant, a museum, a station — sends your search to Google.
• Searching for a home city, or using "use my current location", sends your search to LocationIQ. When you use your current location, the coordinates your device reports are sent so the city can be identified; we do not store those coordinates.

We cache the results we get back (place names, addresses, coordinates, categories) so that repeated searches do not need to be sent again. The cache is not linked to you. Results from Google are deleted from that cache after 30 days, which is what Google's terms require.

When you add a place to one of your trips, we keep that place's name, address and coordinates on the trip item itself, so your itinerary stays complete and readable after the cache entry above has been deleted. That copy is part of your trip, and it is deleted when you delete the item, the trip, or your account.

Trip cover images, and any picture shown for a place on your itinerary, are fetched by your device directly from Wikimedia Commons. That means Wikimedia receives your device's IP address when an image loads.

3.7 The AI assistant

Where the assistant is available in your version of the app, using it sends the question you type, together with the relevant details of the trip you are asking about, to Anthropic PBC so a model can answer it. We store the conversation — your messages and the assistant's replies — against your account, along with technical records of each run (which model was used, how many tokens it consumed, how long it took, and how many questions you have asked that day, so we can apply usage limits).

Anthropic processes this content to return an answer and does not use it to train its models. If you would rather nothing about a trip reached a model, do not use the assistant for that trip; the rest of the app works without it.

3.8 Technical and log data

Our API records standard server logs for each request: IP address, the time, the endpoint called, the response status, and your account identifier once you are signed in. We use these to keep the Service running, to apply rate limits, and to investigate faults and abuse. Logs are retained for a short period and are not used to build a profile of you.

3.9 Data stored on your device

The mobile app stores the following on your phone, not on our servers:

• an offline copy of your trips, in a local database, so you can read an itinerary with no connection;
• cached trip cover images;
• small flags recording that you have seen the introduction screens, that you have been asked about notifications, and when you were last asked;
• the trip reminders your phone has scheduled for itself, held by Android until they fire;
• your sign-in token, held by the Firebase SDK in the Android Keystore or iOS Keychain.

Uninstalling the app removes all of this from your device. It does not delete your account — see section 8.

4. What we do not collect

• No advertising identifier, and no advertising or marketing SDKs.
• No analytics, attribution, or crash-reporting SDKs.
• No device location. The Android app requests no location permission; a "home base" is a place you type, not a position we read.
• No contacts, photos, camera, microphone, calendar, or file access.
• No payment information. JustTrippin is free and has no in-app purchases.
• No data about children — see section 11.

5. Why we use your data

We process this data on the basis of your consent, given when you create an account and use these features, and to provide the service you have asked for. You can withdraw consent at any time by deleting your account (section 8).

We do not use your data for advertising, profiling, or automated decisions that produce legal or similarly significant effects.

6. Who we share it with

We do not sell personal data. We share it only with the service providers below, each of which processes it on our instructions and for the purposes shown.

Other people on your trips are not in this table, because they are not service providers. A trip you share is readable by its members, and that is described in section 3.4 rather than here.

We may also disclose personal data where we are legally required to do so, or where it is necessary to establish or defend a legal claim — and, if the Service is ever transferred to another operator, to that operator, with notice to you beforehand.

7. Where your data is stored, and transfers out of India

Our servers and database are located in Singapore. Some of the providers listed above operate in the United States and other countries. This means your personal data is stored and processed outside India, and outside your own country if you are elsewhere. By using JustTrippin you consent to this transfer. We choose established providers and rely on their contractual data-protection commitments.

8. Keeping, and deleting, your data

We keep your account and trip data for as long as your account exists, so that your trips are there when you come back. There is no automatic expiry, with four exceptions, all of them deletions we make without being asked:

• trips and itinerary items you delete are kept for 30 days and then permanently erased. They cannot be restored by you or by us during that time. Our nightly backup keeps a copy for up to a further 30 days before it is overwritten;
• notification records are deleted after 90 days;
• a phone's notification token is deleted when you sign out, and automatically if the phone has not registered for 270 days;
• cached place results (section 3.6) expire on the schedule described there, and identify nobody.

A comment you delete is different: its text, the people it mentioned and the items it pointed at are removed immediately, and the empty row is kept so that the replies underneath it keep their place in the conversation. It goes for good when the trip it is on does.

You can delete your account yourself, from You → Delete account in the mobile app, or from Settings → Account in the JustTrippin web app at justtrippin.app. You can also request deletion by emailing support@justtrippin.app from the address on your account; we act on it within 30 days.

Step-by-step instructions for all three routes, including what to do if you can no longer sign in, are at justtrippin.app/delete-account.

Deleting your account removes:

• your user record, and with it your profile and home base;
• every trip you own, with its days and itinerary items — including trips you share, which are deleted for the other members too;
• your membership of trips other people own, so you lose access to them;
• every assistant conversation and its message history;
• your notification records, your notification settings, and the token for every phone you had signed in to;
• your sign-in credentials, deleted from Firebase Authentication.

This is immediate and permanent. We cannot recover a deleted account.

If you own a trip other people are on, deleting your account deletes that trip for them as well. Ownership is not transferred to anybody and they are not asked first. Before you confirm, the app tells you which shared trips will go and how many people are on each, and the members are notified that the trip was deleted. If you want a trip to outlive your account, somebody else has to own it.

Three things survive a deletion, and none is used for any purpose other than the one stated:

• Comments you wrote on a trip somebody else owns, which stay readable to that trip's members with your name removed — they are shown as written by a removed account. This is deliberate: a conversation other people are still having should not have holes torn in it. Delete the comments first if you would rather they went.
• Notification records written for other people. Someone who was told that you commented, joined, left, or deleted a trip keeps that record, with your display name and any comment extract in it, until it ages out at 90 days. Those records belong to the people who were told, and one of the things they are told is that you are gone.
• Server logs, which may contain your IP address and account identifier, until they age out, and database backups, taken nightly and kept for 30 days on a rolling basis before being discarded. Backups are stored in our provider's encrypted storage and are readable only by us. We do not restore a deleted account from backup, and no backup containing your data survives more than 30 days.

The cached place data described in section 3.6 is not linked to you and is not deleted, because it identifies nobody.

9. Security

• All traffic between the apps and our API is encrypted with HTTPS/TLS.
• We store no passwords. Credentials are held by Firebase Authentication, and our API only ever verifies a short-lived signed token.
• Every request is authenticated, and the API checks on every read and write that the data belongs to the account asking for it.
• Authorisation tokens and cookies are stripped from our server logs before they are written.
• Database backups are held in encrypted storage, and access to production credentials and backups is limited to the operator named in section 1.
• JustTrippin staff can see your account details and usage counts, but not your itinerary content, for support and abuse prevention.

No service can promise perfect security. If a breach affects your personal data, we will notify you and the Data Protection Board of India as required by law.

10. Your rights

Under the Digital Personal Data Protection Act, 2023, you have the right to:

• access a summary of the personal data we hold about you and how it is processed;
• correct or complete inaccurate or incomplete data — most of it you can edit directly in the app;
• erase your data, by deleting your account or asking us to;
• nominate another person to exercise these rights on your behalf if you die or become incapacitated;
• complain to us and, if we do not resolve it, to the Data Protection Board of India.

If you are in the European Economic Area or the United Kingdom, you also have the rights to data portability, restriction of processing, and objection, and you may complain to your local supervisory authority.

To exercise any of these, email support@justtrippin.app. We may ask you to confirm you control the account's email address before acting on a request.

Grievance officer. Complaints about how we handle personal data go to our grievance officer at support@justtrippin.app. We acknowledge within 7 days and resolve within 30.

11. Children

JustTrippin is not intended for children. You must be 18 or older to create an account. We do not knowingly collect personal data from anyone under 18. If you believe a child has created an account, write to us and we will delete it.

12. Changes to this policy

If we change how we handle personal data, we will update this page and change the effective date at the top. Where a change is significant — a new category of data, a new provider receiving your data, a new purpose — we will tell you in the app or by email before it takes effect. Continuing to use JustTrippin after a change means you accept the updated policy.

Updated 11 October 2026. Planning a trip with other people, and notifications, both reached the app, so this policy now describes them: membership, invitations and comments (section 3.4), notification records and push tokens (section 3.5), Firebase Cloud Messaging as a provider (section 6), and what happens to a shared trip and to other people's notifications when you delete your account (section 8).

13. Contact

JustPanthering
Plot No. 308, Mother Teresa Nagar, Tundul Math-Toli
Ranchi, Jharkhand 835303, India
support@justtrippin.app