Privacy Policy
Last updated 16 August 2026
Tour-Trip Expense Manager ("the service") is operated by Ornova Labs, based in Malda, West Bengal, India. This page explains what the service stores about you, why, and what you can do about it. It is written to be read, not to be skimmed past.
Ornova Labs is the data controller (data fiduciary) for the information described below, and privacy@ornovalabs.com is the contact point for any question, request or grievance about it.
What we collect
| Data | Why |
|---|---|
| Name, username, email address | To create your account, sign you in, and let you reset your password. |
| Password | Stored only as a bcrypt hash. We cannot read it, and neither can anyone who obtains the database. |
| Trip details you enter | Names, destinations, dates, driver and vehicle details, and any description you write. |
| Expense records | Amounts, categories, dates, notes, and who each expense is split between. |
| Names and phone numbers of trip members and emergency contacts | So the group can identify each other and call for help. These are often other people's details — see below. |
| Photographs of bills you upload | To evidence an expense. Note that a bill photo may itself contain a card number or an address. |
| GPS coordinates, when you tap "tag location" | To record where an expense happened. This is always an explicit action; nothing is captured in the background. |
| IP address and sign-in attempts | To rate-limit password guessing. Failed attempts are deleted after 7 days. |
| An activity log | Records who changed what, so a group can resolve disputes about their own trip data. |
| A visitor count | The number in the footer. We store only daily totals — how many page views and how many distinct visitors. To avoid counting the same person twice in a day we store a one-way hash of your IP address and browser, salted with a secret and with the date, kept for three days and then deleted. No IP address is written anywhere, the hash changes every day so it cannot follow you between days, and it cannot be reversed to identify you. |
Data about other people
This service is unusual in one important way: most of what you enter is about other people — the friends and family you travel with. When you add someone as a trip member, or record their phone number as an emergency contact, you are supplying their personal data to us.
Please only add details you have their agreement to share, tell them the trip is being tracked here, and remove anyone who asks to be removed. If someone contacts us directly about details you entered, we will ask you to resolve it, and will act ourselves if you do not.
What we do not do
- We do not sell your data, and we do not share it with advertisers or data brokers.
- We do not use it to train machine-learning models.
- We do not track you across other websites. The visitor counter described above runs entirely on our own server, sets no cookie, and involves no third party.
- We do not use Google Analytics or any similar third-party analytics product.
- We do not read your trip data except where strictly necessary to fix a fault you have reported to us.
Advertising
There are currently no adverts anywhere on this service, and no advertising or ad-measurement code is loaded on any page. If that changes, this policy will be updated before any advert appears, and adverts would in any case only ever appear on public pages — never on signed-in pages showing your trips and expenses.
Who can see your trips
A trip is visible only to accounts explicitly granted access to it — the person who created it, and anyone they invite. No other user of the service can see it, and administrators of the platform do not receive access to your trips by virtue of being administrators.
Cookies
We set exactly one cookie, named TTEM. It holds your sign-in session and nothing
else — no identifier that follows you elsewhere. It expires after 8 hours of inactivity, or when
you sign out. Because it is strictly necessary for a service you asked to use, no consent banner
is required for it, and we do not set any cookie that would need one.
Third parties
- Email delivery. Verification and password-reset emails are sent through an SMTP relay, which necessarily processes your email address in order to deliver the message.
- Fonts, stylesheets and chart scripts are loaded from the jsDelivr CDN, which will see your IP address as a normal consequence of serving those files.
- An AI assistant widget from
ai.ornovalabs.comis loaded on pages when you are signed in. Anything you type into that chat is sent to that service.
How long we keep things
Trip and expense data is kept until you delete it or close your account. Failed sign-in records are deleted after 7 days, expired verification and reset tokens after 30 days, and the visitor-counter hashes after 3 days. Encrypted backups are retained for 14 days, so deleted data can persist in a backup for up to that period before ageing out.
Your rights
Under the GDPR and India's Digital Personal Data Protection Act you may access, correct, export or erase your personal data, and withdraw consent at any time. Two of these are built in and need no request: from My Account you can export everything we hold about you as a JSON file, and delete your account permanently. For anything else, write to privacy@ornovalabs.com and we will respond within 30 days.
What deletion actually does
Deleting your account erases your account record, your uploaded bill photos, your session and token records, and every trip for which you are the only owner, including its expenses. Where a trip has other owners it survives, because it is their data too — but your account is detached from it, and expenses you entered are re-attributed to "a deleted user" rather than removed, so that other people's settlement figures do not silently change. This is irreversible.
Security
Traffic is encrypted with TLS. Passwords are bcrypt-hashed, and verification and reset tokens are stored only as SHA-256 hashes, so neither can be recovered from the database. Sign-in attempts are rate-limited. Uploaded files are type-checked and stored where they cannot be executed. No system is perfectly secure, and we do not claim otherwise; if we discover a breach affecting your data we will tell you and the relevant authority without undue delay.
Changes
If this policy changes materially we will note it here and update the date above. Continuing to use the service after a change means you accept the revised policy.
Questions? Write to privacy@ornovalabs.com. · About · Contact · Privacy · Terms