Last updated: 14 October 2026
SpeedReceipt ("the app") scans receipts and logs them into a spreadsheet in your own Google Drive. This policy explains exactly what the app accesses and stores, and — just as importantly — what it does not. See the Terms of Service for your responsibilities around backing up and sharing your own data.
When you sign in with Google, the app requests one Drive/Sheets scope:
https://www.googleapis.com/auth/drive.file — limited to
files and folders the app creates, or that you explicitly select via
Google's own folder picker. The app cannot see, read, or write any
other file in your Drive — including spreadsheets you created
yourself or with any other app.All of your receipt images, spreadsheet data, merchant lists, and categories are stored only in your own Google Drive and Google Sheets — under your Google account, subject to Google's own privacy policy and your own account controls. The developer does not routinely access, export, or keep a copy of this data. The exceptions are: a receipt photo briefly passing through a third-party OCR service for scanning (see "Receipt scanning" below), snippets of it appearing automatically in crash reports (see "Crash reporting and diagnostics" below), and the opt-in email-forwarding feature — all described in full in their own sections below.
Every connection the app makes — to Google Drive and Sheets, to the developer's own servers, and to every third-party service listed below — is encrypted in transit (HTTPS/TLS). The app itself never operates its own copy of your receipt or spreadsheet data: it reads and writes directly to your own Google Drive and Sheets, under Google's own access controls and encryption-at-rest, exactly as if you'd edited those files yourself. The few narrow exceptions where something briefly passes through the developer's own infrastructure (an OCR request, a crash report, an emailed-in receipt) are each described in their own section below, including what's encrypted, how long it's kept, and when it's deleted. Access to the developer's own Firebase project is restricted to the developer alone.
How your receipt photo is read depends on the platform you're using:
If you use the app's WiFi scanner feature, your device talks directly to your scanner over your own local network using the standard AirScan/ eSCL protocol. Scanned pages are transferred straight from the scanner to your device — never through the developer's servers or any third-party service.
If you turn on email-forwarded receipts in Settings, you're given a unique address to forward receipt emails to. A forwarded receipt briefly passes through the developer's servers — just long enough to be matched to your account and copied into your own Google Drive, the same way any other receipt you add gets filed. It's automatically and permanently deleted from the developer's servers the moment that copy succeeds — normally within seconds, and always the next time you open the app if you were offline when it arrived. While briefly stored, it's encrypted at rest like everything else in the developer's Firebase project, and is never read, exported, or used for anything other than filing it into your Drive.
The app keeps a rolling technical log on your device to help diagnose problems. This log deliberately includes some receipt detail relevant to troubleshooting — merchant names, dates, and dollar amounts — alongside technical information (app actions, network requests, error messages).
Automatically, on every crash: the app uses Sentry, a third-party crash-reporting service, to capture what went wrong. Every crash report automatically includes recent entries from the on-device log described above (so it may contain receipt merchant names, dates, and dollar amounts from what you were doing right before the crash), your signed-in account's email address and account ID, and standard technical details (device/OS version, app version). This happens whether or not "Diagnostic reporting" below is turned on — it's how crashes reach the developer to get fixed at all.
"Diagnostic reporting" in Settings (off by default, offered once during setup, changeable anytime): when turned on, the app additionally sends your complete on-device log — not just the recent entries above — to Sentry automatically whenever the app crashes, giving the developer the full picture rather than a snapshot. You can also send the complete log manually at any time via "Send Diagnostics now" in Settings, regardless of this toggle, since doing so is itself your consent for that one report.
Diagnostic and crash data is used solely to diagnose and fix problems with the app — never sold, shared with third parties for marketing, or used for any other purpose.
A small amount of licensing data is stored in a Firebase project operated by the developer, solely to determine whether your account has an active subscription:
None of your receipt content, spreadsheet data, or images are included in this — it is purely "is this account's subscription active" bookkeeping. This data is never sold or shared with third parties, and is only used to unlock the app for your account across every platform it runs on (Android, iOS, Web, Windows, and macOS).
Since your receipt data lives in your own Google Drive, you can delete it at any time the same way you'd delete any other file or folder in Drive. To have the developer's licensing record for your account deleted, contact support@speedreceipt.app.
If this policy changes, the updated version will be published at this same URL with a new "last updated" date.