Data transparency
Privacy and data processing
ReceiptJar does not require an account or build a receipt history. Receipt data is processed for the active extraction, payment, and download workflow.
Service providers and what they receive
| Provider | Purpose | Data involved |
|---|---|---|
| Google Cloud Vision | Optical character recognition | Receipt images, or rasterized PDF pages, when OCR is required |
| Stripe | Checkout and payment verification | Payment details handled by Stripe plus batch count, tier, and session references; receipt images are not sent to Stripe |
| Upstash Redis, when configured | Temporary sessions, rate limiting, and aggregate counters | Short-lived extracted session data; rate-limit keys; daily event totals without receipt contents or visitor profiles |
| Hosting infrastructure | Serve the site and API | Normal network and request metadata needed to operate and secure the service |
Third-party processing is also governed by each provider’s applicable terms and privacy practices.
In your browser
Original files may be kept temporarily in browser storage so the batch can survive the Stripe redirect. Active sessions schedule deletion after about 30 minutes, and expired browser files are purged when ReceiptJar is next used. Browser behavior can affect when physical storage is reclaimed.
On the server
The OCR API receives an encoded image and forwards it to Google Cloud Vision without intentionally saving the image as a server file. Extracted fields and filenames are held temporarily so checkout and CSV download can complete.
Retention and deletion
Temporary server sessions are assigned a 30-minute expiry. When Redis-backed storage is configured, this uses a native expiry; the service also checks and removes expired fallback records. Browser files are deleted during active sessions, after paid processing, or during the next cleanup check after expiry.
Practical implication: download promptly, retain your originals elsewhere, and clear site data in your browser if you want to remove local browser storage immediately.
Analytics
ReceiptJar counts a limited set of product events—such as starting a preview or completing checkout—as aggregate daily totals. These events do not include receipt contents, filenames, payment details, session IDs, cookies, or a cross-session visitor identifier. Uploaded data is not used for marketing or model training by ReceiptJar.
Contact
ReceiptJar is the name of the software service available at receipt-jar.com. Privacy, access, or billing questions can be sent to contact@receipt-jar.com.
Last updated: July 15, 2026