Privacy policy
Last updated: 23 October 2026
TourSeat helps travelers book group tours and organizers manage bookings. For privacy, support, refund or deletion requests, contact [email protected].
Information you provide
Guest bookings do not require an account. We process the booking contact details, traveller details and receipts you provide, along with the private access code used to retrieve the booking. For account holders, we process your account name, email and optional profile details; booking contacts and answers; payment receipt images and claimed/verified amounts; chats, reviews, disputes and refund records. If you choose Google sign-in, we receive your Google account name, email, verification status and profile image to create or access your TourSeat account. We do not request access to Gmail, Drive or your contacts. Organizers provide business details, tour listings and payment instructions. A tour may request identity or passport details for travel arrangements. Provide only information required for that trip and only information you are authorized to share.
How information is used and shared
We use information to manage accounts, tours, seats, tickets, direct-payment confirmations, refunds and support. Your booking contact is available to its organizer. Sensitive form answers are withheld from the organizer until payment has been confirmed. Authorized support/admin staff may access relevant records to investigate a case. Public tour listings and organizer information are visible without sign-in. Group chats show display names and messages to trip members and the organizer; reviews are public. Do not post private documents in chats or reviews.
Service providers and payments
Oyrial operates TourSeat and runs its application server and private receipt storage on its VPS. Google Firebase provides account authentication, the database and phone alerts; our configured database region is Mumbai, India. Google may process service/security information under its own terms. Wallet top-ups are no longer offered. We retain identifiers for earlier Google Play wallet purchases so we can verify those transactions and handle related support. Existing eligible balances are converted to Starter plan time. Paid subscription checkout is being prepared; no payment is taken by the marketing website. When subscriptions are available, the checkout provider processes the purchase and we retain the identifiers and subscription status needed to verify access. To give each organizer business one free period, we keep one-way hashes of the organizer phone number, the payment account shown to travelers and the organizer app installation; these stay after account deletion for fraud prevention. Payments for tours go directly to the organizer through the stated payment method. TourSeat does not hold or automatically refund those tour payments. Exchange-rate estimates use a public rate feed without sending your account or booking contact to that provider.
Camera, photos and phone alerts
Camera access is used when you choose to scan a ticket. The system photo picker grants access to the payment receipt image you choose; broad photo-library access is not requested. Receipt images are uploaded for payment verification; camera permission does not provide continuous location tracking. If you enable Android phone alerts, Firebase Cloud Messaging processes a device token and installation identifier linked to your current account. Lock-screen alerts contain a generic update message; booking details remain in your private inbox. You can disable phone alerts in Android settings. Inbox updates and device identifiers expire after 90 days; using the app can renew a device registration. Account deletion cleanup removes them. Android Saved trips keeps explicit read-only copies for up to 24 hours, encrypted on the device with an account key in secure storage. A copy can include trip details, the organizer public phone number, a signed ticket and minimal confirmed passenger names/references/seats for the agency owner. Bank receipts, financial instructions, form answers, identity documents and traveler phone numbers are excluded. App copies and their encryption key are removed on sign-out or when account deletion is observed. PDFs you save outside the app stay under your control and cannot be removed by signing out. Offline copies may be outdated after a cancellation or transfer. We do not sell your personal information.
Retention and account deletion
Receipt images and notes are normally removed after 90 days. Active trips, unresolved confirmations, disputes and unacknowledged refunds can require longer retention. Reports store your explanation and a limited copy of the reported content for moderation. Your block list is private to your account. You can request account deletion in Account and privacy, including through the web version without reinstalling the app. Current and upcoming bookings/tours are canceled using their applicable refund terms. You have 30 days to restore account access; canceled bookings/tours remain canceled. After that period, automated cleanup removes the Auth account/profile, booking contacts and answers, authored chat messages, personal shopfront content and block preferences. Financial amounts and dispute/refund history remain without the removed profile identity. Report identities are removed; evidence needed for an unresolved moderation, payment or refund case may remain until it is settled. A receipt already removed cannot be restored for a later case. A short security marker prevents old sessions reopening a deleted account for up to 24 hours after cleanup.
Your choices and contact
You may request access, corrections, deletion or assistance with remaining case evidence at [email protected]. Include your booking reference when relevant, and do not email a password or full identity document. We may need to verify that the request concerns your own account. Other travelers or third-party services may keep their own copies of material you shared with them. Contact us if you need help with a refund after your account is closed.