AI receipt scanning uses artificial intelligence (AI) to read the merchant, date, currency, amount and text in a receipt photo and suggest editable expense fields. Check the result before saving. These fields can be wrong. The result is not financial, tax or legal advice. You can enter an expense manually without using AI receipt scanning.
This page supplements the Privacy Policy with an explanation of the feature covered by the Terms of Service. You do not need to accept it as a separate agreement. Permission to send a receipt to a cloud AI provider is requested in the app.
Processing the receipt you select
Google cloud AI receipt scanning: when you request a scan and allow this route, we send the selected receipt image, processing instructions and requested output language to Gemini through Google Cloud's Vertex AI service to extract editable expense fields. The image may contain merchant details, transaction information and information about you or other people. Only submit information you are entitled to provide; avoid unnecessary sensitive details.
Receipts can contain information about family members, including children. Supply only information you have authority to provide, with parent or guardian involvement where applicable law requires it. Your own improvement choice does not replace another person's required permission. Google's current cloud route uses a global endpoint; it does not itself guarantee processing in one country or region. Apple Private Cloud Compute does not let us choose a processing location either. See the Privacy Policy's international-processing explanation.
Apple Private Cloud Compute receipt scanning: on supported iPhones, the scan first uses Apple Private Cloud Compute. The app reads the receipt's text on your device, then sends Apple the receipt image (at most 1,600 pixels on its longest side), up to 120 lines of that text, our instructions and, when the trip has them, its destination names and dates, with your device's current date and time zone. Apple states that this data is used only for the request, is not available to Apple staff and is not retained after the response. If the route is unavailable or fails, the same scan can continue with Google cloud processing. Extracted result fields and operational usage records are sent to our Firebase backend when a scan completes, even if you do not save an expense. Apple's on-device model, when we use it, analyses the receipt on your device without sending it to Apple.
Permission: before the first scan that can use Apple Private Cloud Compute or Google cloud processing, the app asks for your permission, naming the photo and the trip's destination and dates. Naming Apple here does not authorise every Apple service.
Which service reads a receipt: we decide which of the AI services listed here handles a scan based on your device, availability, reading quality and other operational considerations, and this can change over time. We may replace or add AI providers for this feature. We keep the list on this page current and update it before a new provider receives receipts. Your in-app permission covers sending the receipt to the AI services listed here to read the expense; you can withdraw it at any time as described in Your Privacy Choices.
Explicit permission to disclose a receipt to a cloud AI provider is separate from accepting Terms, acknowledging the Privacy Policy, camera/photo access, optional improvement and a purchase. Reading this page or continuing to use the app alone does not grant it. The app presents the applicable permission before the first disclosure. You can refuse cloud processing and use manual entry. To withdraw a previously recorded cloud-processing permission, contact legal@vibeeverything.co. Use manual expense entry and do not start another cloud scan while your request is being handled. Withdrawal does not erase a receipt saved with a trip or automatically delete operational records with a separate lawful retention basis.
We retain the request state, timing, extracted fields, model and settings used, and quota and cost records needed to operate the feature. Saved expense and receipt records follow the shared-trip lifecycle. Raw processing fields have a 90-day retention period from the original scan; limited operational metadata has a 730-day period. Minimum unresolved billing evidence can be retained longer when necessary. These periods do not mean a receipt saved with a trip is automatically deleted after 90 days, or that Google has zero retention. Google's managed-model training restrictions, applicable abuse monitoring, logging and other retention depend on the service terms and configuration. Our improvement permission does not authorise Google or Apple to train a provider's model. See the Privacy Policy for the full schedule, Google's data-governance information and Apple's on-device model documentation for provider information.
Voluntary improvement
The optional Help improve Travel Together choice records the device model, iOS version and app version used for each scan made while you take part. When you change something the AI filled in, it also covers eligible receipt references (records that locate receipt images) and available images, what AI suggested, what was placed into your editable expense form and the first changes you save, including amounts and text, for analysis and evaluation of extraction quality and app improvements. When you save without changing anything, we keep only a record that no change was needed. We may pause this collection at any time. Authorised reviewers may keep private analysis copies, including downloaded receipt images. These are separate copies with a limit of up to 730 days from the original collection, not the export date. Reusing a saved receipt can still result in a private copy, but it does not extend how long the receipt is kept with your trip.
For feedback comparing your first saved corrections, an eligible sample must come from a completed scan made under your valid improvement choice and still be covered by that choice when feedback is collected. It is matched to the first saved expense. An image is included only when it is available and can be matched to that sample.
This choice does not currently authorise training or fine-tuning a model. If we offer that use, we will explain the data, model/provider, purpose and safeguards separately and obtain any required permission before it begins. It is not automatically included in an ordinary content licence or a Google/Apple cloud-scan permission. Optional app-usage analytics (basic usage information and upgrade-screen outcomes sent to Google Firebase Analytics) is part of the disclosed app-improvement choice when enabled; crash reporting, necessary operational scan records and subscription analytics have distinct purposes and are not all switched off by withdrawing that choice.
You can use the app without participating. Turn participation off in Settings to stop new optional improvement collection and use, including further optional use of your identifiable earlier samples. Turning it off also stops app-usage analytics and clears analytics data still waiting on your phone; it does not delete analytics data already sent. We delete or irreversibly anonymise identifiable improvement samples and private copies without undue delay, unless a separate lawful retention obligation applies. Backend removal, private-copy cleanup and restricted backup expiry are separate processes; withdrawal is not instant deletion of every copy. A separate necessary retention basis does not permit continued optional improvement. Withdrawal does not remove your normal expense or receipt from a shared trip. The retention limit is not a waiting period after withdrawal and does not permit continued optional improvement. Contact us to ask about cleanup progress. Contact legal@vibeeverything.co for a deletion or access request.
Allowances and reliability
The app shows how many scans you can use and whether you meet the conditions to use them. A plan can have usage and service limits; buying a subscription does not guarantee unlimited or uninterrupted scans. A suggested result is not saved as an expense until you confirm it through the expense flow. Review your own edits and the final shared record.