TripPocket Privacy Policy
Effective date: 8 November 2026
TripPocket: Split Travel Costs is operated by LAKESIDE VILLAGE COMPANY LIMITED, Thailand. Contact: sales@lakesidevillageproduction.com.
Information we use
Account: Google sign-in supplies your name, email address, profile information and a Firebase account identifier. We use these to sign you in, secure your account and sync trips. The current version uses Google sign-in because trip files are stored in Google Drive. Existing linked account identifiers and purchases are preserved.
Trips: trip names, traveler names, invitations, expenses, currencies, amounts, repayment preferences, receipt photos, optional places/Maps links, and creation/edit history are stored to provide the service. Other accepted members can view shared trip data. Trip owners manage access; administrators can manage expenses; members can manage their own entries.
Location: you can optionally add a location or Maps link. Using your current location requires device permission. A saved location may include precise coordinates. We do not track your location in the background.
Receipts: in the Drive version, tapping Read receipt sends the selected, reduced photo to Cloudflare Workers AI to suggest its total and currency. Attaching a photo alone does not start AI reading. Earlier versions may start reading when you select a photo. Review a suggestion before applying it; manual entry remains available. Standard inference processes the image and response for the request, without our saving them in server logs or caches. Cloudflare’s Workers AI data policy describes its processing and limited exceptions. Saved receipt photos are available to accepted trip members.
Purchases: Google Play or the Apple App Store processes payment. RevenueCat and our server use your account identifier, purchase history and entitlement status to enable and restore Remove Ads. We do not receive full payment card or bank details.
Notifications: if enabled, Firebase Cloud Messaging and our server use an app/device identifier and push token to deliver trip updates, without including trip contents in the push payload. The signed-in app checks current access before opening an update. Notifications may appear on your lock screen; you can control them in phone settings.
Ads: the free Android and iOS apps uses Google AdMob. When ads are requested, Google's SDK may collect/share IP-derived approximate location, device/ad identifiers, app interactions and diagnostics for advertising, measurement and fraud prevention. Available consent/privacy choices depend on your region and Google's requirements. Remove Ads stops banner advertising for the signed-in account; account, purchase and security processing still applies.
The current website provides app downloads, policies and support; it does not offer the trip editor or display AdSense ads. Earlier browser sessions may retain old cached pages.
Website statistics: direct website visits use a random first-party browser identifier, country and device type for visitor counts. These statistics are not linked to your Google identity, trips or receipts. You can turn visitor counting off on the website. This custom visitor counter is disabled in the native app. Infrastructure providers and ad/payment SDKs may separately process technical information to deliver and protect their services.
Safety and moderation
Safety: we store Community Rules acceptance, blocked-user settings, abuse reports and moderation decisions. Reports include the reporter’s account identifier, relevant trip/user references, reason and explanation and, for a Drive expense report, scoped references that allow the safety administrator to read the reported text and available receipt from Drive. These evidence files are relayed without our persisting their bodies. Older reports may contain a submitted copy of the text or photo. The TripPocket safety administrator can review these reports; they are not shown to the reported user. Blocking is private to your account. We use this information to prevent abuse, investigate reports, handle appeals and protect the service. Safety records are retained as needed for those purposes, subject to applicable deletion requests and legal obligations. Contact sales@lakesidevillageproduction.com for support or appeals.
Providers and sharing
We use Google Firebase/Firestore and Firebase Cloud Messaging, Cloudflare Workers/D1/Workers AI, RevenueCat, Google Play, the Apple App Store, Google AdMob and Google Drive. These providers process relevant information to deliver their services and may process it outside Thailand. Trip information is shared with people who accept an invitation to that trip. We do not provide expense contents or receipt images to AdMob for ad targeting. External Maps links open Google's service under its own policy. Necessary information may also be disclosed when required by law or to protect the service.
Storage and security
The Drive version stores trip details, expenses, rates, edit history and receipt files in participating customers’ Google Drive accounts. Files count toward their Google storage limits. Firebase retains account, purchase, access, membership and opaque file/update references. Private trips do not grant our sharing service folder access. The owner’s Create trip link or invitation action enables service access for that trip; joining contributors use their own TripPocket Drive folders. An authenticated Cloudflare relay reads shared files from these registered folders without persisting file bodies in our servers or CDN. Authentication and access rules restrict reads and updates.
Previously loaded trips and photos open from an account-scoped device cache, with access and version checks in the background. Pending edits and recovery copies are kept separately. A confirmed access removal hides the trip and removes display snapshots on an online device; it cannot remotely erase copies from an offline device or exports someone has already made. A temporary connection failure keeps the offline copy. Network requests use HTTPS/TLS. Sign out on shared devices.
Older versions use Firestore for trip content. Migration verifies Drive copies before switching to them, retains the original cloud data for owner review, and prevents old clients from changing the moved trip. Existing data is not silently deleted during migration.
Retention and deletion
Account and trip records remain while needed to provide the service, unless deletion is requested. Deleting an expense in the app may retain its edit/audit history; removing it from view is not an account/data deletion request. You may request deletion of your TripPocket account and associated data using Account → Delete account and data, or https://tptravelexpense.com/account-deletion. Email sales@lakesidevillageproduction.com from your sign-in email where possible. We verify account ownership before deleting data and aim to complete verified requests within 30 days.
Deletion covers the Firebase sign-in record, owned trips/expenses/receipts and related access records, membership/invitation references, device registrations and our purchase-entitlement records. Where your entries are in another person's shared trip, we will remove your personal identifiers and personal attachments; non-identifying amounts needed for the remaining members' accounting may remain. Store/provider transaction records may be retained as required for accounting, fraud prevention or law. Deletion does not automatically refund a purchase or delete your Google account. Provider retention and backup cycles may differ; any required retention or delay will be explained in our response.
Receipt-scan rate-limit records contain hashed account identifiers and timestamps, not the receipt itself; old entries are pruned during subsequent scans. Purchase-webhook deduplication records older than 30 days are pruned during subsequent events. Website visitor statistics may be retained for all-time reporting.
Your choices
You can edit your trip data within your role, remove optional receipts/locations, manage shared access as owner, disable notifications, manage available ad privacy choices, and request access, correction or deletion by email. You can reset/delete your advertising ID in Android settings. Google Play and Apple handle purchase/refund requests under their policies.
Adults and updates
This release is intended for adults aged 18 and older and is not directed at children. Contact us if a child's data has been submitted. We may update this policy and will display the updated date and notify users of material changes where required.
Privacy Policy · Delete account and data