Privacy Policy
Notice of change (November 1, 2026) We corrected how long original receipt photos are kept (sections 3 and 6) to match how the app works. Originals saved with an expense have already been kept by the app. Photos not saved with an expense are still deleted automatically after one day. Deleting the expense or the photo deletes the original too. The updated policy applies from December 1, 2026. We also added the app’s usage statistics (Google Analytics for Firebase) to sections 2 and 4, and the website collects visit statistics (Google Analytics) from November 8, 2026.
Earlier notice of change (October 22, 2026) We added how the optional Android feature Payment alerts handles data (the table in section 2, section 3-1, OpenAI’s task in section 4, retention, and permissions). The updated policy applies from October 29, 2026; until then, the policy effective September 19, 2026 applies.
This is an English translation of the Korean Privacy Policy (개인정보처리방침). If the two versions differ, the Korean version prevails.
1. What this policy covers
TripClear (the “Service”) is a mobile app for recording and settling travel expenses together with other people. This policy applies to personal information processed by the app and by tripclear.site.
The Service collects only the information needed to keep the ledger and settle up, and does not provide the information it collects to third parties for building advertising profiles or for sale.
2. Information we collect and why
| Category | Details | Purpose |
|---|---|---|
| Account information | Your Google account's email address, display name and account identifier | Signing in, identifying trip members, showing who wrote an entry |
| Ledger data | Trip name, dates and destinations; members; expense amounts, currencies, dates, categories and notes; line items; settlement records; display currency setting | Keeping the ledger, sharing it with members, calculating settlements, exporting |
| Receipt images | Receipt photos you take or pick from your gallery | Reading receipts automatically (extracting the shop name, amount, currency, date and line items) |
| Location | Coordinates and place name when you save your ‘current location’ with an expense | Recording where an expense was made and showing it on a map |
| Device notification token | Firebase Cloud Messaging registration token | Sending push notifications such as trip join requests |
| Advertising identifiers | Advertising ID and the information collected by Google's ads SDK | Showing banner and rewarded ads in the app |
| Payment notifications (optional, Android) | When you turn on Payment alerts: the text of payment notifications from card, bank, pay and messages apps during a trip (processed on your device only) | Offering to add them as trip expenses |
| Crash diagnostics | Error details when the app crashes, device model, OS version and app version | Finding the cause of failures and improving stability |
| Usage statistics | App: use of features such as creating a trip, saving an expense and reading a receipt, device information, and an internal user identifier (not an e-mail or a name). Website: pages visited, referral source, device and browser information, store button clicks, cookies | Understanding usage and traffic sources, improving the service |
The Service has no separate sign-up form, and does not collect national identification numbers or payment method information. Card digits and names in payment notifications are masked on your device and are never sent to or stored on our server.
3. How receipt images are processed
Automatic receipt reading works in the following order.
- Text recognition (OCR) is performed on your device first. This step does not use the network.
- Only when the recognition result has low confidence are the photo and the recognition result sent to our server, where OpenAI's image recognition model reads the receipt once more.
- When reading is complete, the extracted amount, currency, date and line items are returned to the app, and you check and edit them before saving.
Uploaded original receipt photos are kept in private storage. An original saved with an expense stays with that expense so you can view it later, and is deleted when you delete the expense or the photo. A photo not saved with an expense is deleted automatically one day after upload.
3-1. How payment notifications are processed (Android)
Payment alerts work only after you turn them on in the app and allow Notification access in Android settings.
- Only notifications that arrive while a trip is running, from the day before it starts to the day after it ends, are looked at.
- Of the notifications from card, bank, pay and messages apps, only those that read like payments are kept on your device. Notifications from other apps, and anything that is not a payment, are dropped on the device and not kept.
- The kept text stays on your device and is not sent to our server. Only the expenses you add (shop, amount, currency, date, category) are saved to your ledger.
- Only for a notification whose shop name our rules cannot read, the notification text with names, card, account and phone numbers, running totals and links removed may be sent through our server to OpenAI to read the shop name and category. The result is returned to the app only and is not stored on our server. (Only where this reading is offered.)
- Turning the feature off deletes the kept notifications from your device right away.
4. Service providers that process data for us
We entrust processing to the following providers, to the extent needed to provide the Service.
| Provider | Task | Information shared |
|---|---|---|
| Supabase | Authentication, database, file storage, running server functions | Account information, ledger data, receipt images |
| OpenAI | Reading receipt images (only when confidence is low); reading payment notification text (only when our rules cannot read the shop name) | Receipt photos, on-device OCR results, payment notification text with names and numbers removed |
| Google (Firebase) | Sending push notifications, collecting crash diagnostics | Device notification token, crash diagnostics |
| Google (Analytics) | Usage statistics for the app and the website | The information listed under usage statistics |
| Google (AdMob) | Showing in-app ads and managing consent | Advertising identifiers, information collected by the ads SDK |
| Google (Maps) | Showing expense locations on a map | Coordinates to show on the map |
| Vercel | Hosting the website and invite links | Access logs, invite link tokens |
Exchange rates come from public data based on European Central Bank reference rates (Frankfurter); no personal information is sent when they are fetched.
5. Transfers outside Korea
The servers of the providers above may be located outside the Republic of Korea. Using the Service requires transfer to those countries; the information transferred and the purposes are as listed in the table in section 4. If you do not want your information transferred, you can stop using the Service and delete your account.
6. Retention and deletion
- Original receipt photos: originals saved with an expense are kept until you delete the expense, the photo or your account. Photos not saved with an expense are deleted automatically one day after upload.
- Payment notification records: kept on your device only (up to 300), and deleted right away when you turn Payment alerts off.
- Account and ledger data: kept until you delete your account.
- When you delete your account: the trips you created, with their expense and settlement records, stored receipt images and push notification tokens are deleted. Records left in shared trips that someone else created belong to that trip's owner, so they are not deleted; only the link to you as their author is anonymized.
You can delete your data yourself in the app under Settings › Delete account and data. If you have already removed the app or cannot sign in, make a request on the data deletion request page and we will process it after verifying your identity. Deleted data cannot be recovered.
7. Device permissions
Permissions are requested only when you use the feature that needs them, and you can keep using everything else if you decline.
- Camera — used only when you photograph a receipt. Not needed when you pick one from your gallery.
- Photos and videos — used when you pick a receipt from your gallery; only the photos you select are used for reading.
- Location — used only when you save your current location with an expense. Location is not collected in the background.
- Notifications — used to receive news you need to see even when the app is closed, such as trip join requests.
- Notification access (Android, optional) — used only when you turn on Payment alerts, to ask whether a payment notification should be added as an expense. Processed only as described in section 3-1.
You can turn off granted permissions at any time in your device settings.
8. Advertising
The Service shows banner ads and rewarded ads through Google AdMob. Rewarded ads play only when you start them yourself, and if you do not finish watching, the feature falls back to manual entry.
Users in the European Economic Area, the United Kingdom and Switzerland are asked, through Google's consent management tool, whether they consent to personalized ads. You can change your choice at any time in the app under Settings › Ad privacy options.
Information that Google collects for advertising is processed under Google's policies.
9. Children's personal information
The Service is not directed at children under the age of 14 and does not knowingly collect their personal information. If we learn that a child's information has been collected, we delete it without delay.
10. Your rights
You can request access to, correction, deletion or suspension of processing of your personal information at any time. You can do the following yourself in the app.
- Access and correction — view and edit directly on each trip and expense screen
- Download — save as CSV or PDF under Settings › Export
- Deletion — Settings › Delete account and data
Other requests are accepted at the contact below, and we will tell you the outcome within 10 days of receiving them.
11. Contact
Operator: TripClear Studio
Privacy officer: TripClear Studio operations team
Email: tripclearstudio@gmail.com
To report or seek advice about a privacy violation, you can contact the Korean authorities: the Personal Information Infringement Report Center (privacy.kisa.or.kr, call 118 in Korea), the Supreme Prosecutors' Office Cyber Investigation Department (1301) or the Korean National Police Agency Cyber Bureau (ecrm.police.go.kr, 182).
12. Changes to this policy
If this policy changes, we will post the change on this page at least 7 days before it takes effect. Changes that are unfavorable to users will be posted 30 days in advance and also announced in the app.