Receipt Janitor

What Receipt Janitor accesses

Google sign-in gives Receipt Janitor your account identifier, name, and email. Your account identifier and email are kept with your account records so we can find your account when you need help or a plan change. With your authorization, the app creates property Sheets and receipt folders, reads and writes the files it creates or you select for use with the app, and opens the related rows and receipts. The Google connection uses the limited Drive file permission requested during sign-in. Receipt Janitor does not need access to every file in your Drive.

You provide a property choice, the expense date, amount, merchant, description and category, optional receipt images or PDFs, and support requests. A receipt may contain more personal information than the expense fields you intended to record; review it before uploading.

How processing works

Receipt Janitor uses your inputs to fill the expense details, write the matching Sheet row, and file the receipt. Cloud receipt scanning sends the prepared receipt bytes through the backend to the scanner. Saving sends the same prepared bytes through the backend to your Google Drive. The app also reads receipt bytes when verifying a saved receipt for preview.

On eligible iPhones, Apple's text recognition and Foundation Models scan the receipt on the device. The backend records scan quota and request metadata; it does not keep the local scan's expense suggestions before you save. If on-device scanning is unavailable or fails, the app shows the reason and uses the cloud scanner. The web app uses the cloud scanner.

Google Gemini receives receipt content when the cloud scanner pre-fills expense fields. Receipt Janitor currently uses a Gemini API service level under which Google may use submitted content and responses to improve its products, and trained reviewers may read them. If a receipt contains information you do not want processed this way, don’t add that receipt; enter the details yourself instead. On-device scanning keeps receipt content on the phone during scanning; saving still sends it to the backend and your Drive. Google Drive and Sheets hold the saved files and rows in your account. Firebase Firestore stores app records and usage metadata. Vercel hosts the web app and backend and may process operational request and error data. These providers process the information needed for their roles; Receipt Janitor does not send receipt contents to product analytics.

ChatGPT connection

If you connect Receipt Janitor in ChatGPT, OpenAI receives the property and expense information returned by the tools you use. When you ask to add a property, ChatGPT can create its Google Sheet and receipt folder within your existing plan’s property limit. ChatGPT extracts the expense details from receipts you attach. The original receipts pass to our backend for validation and saving to your Google Drive. This connection does not send receipts to Gemini or use your Receipt Janitor receipt scans. Pre-save suggestions appear in your ChatGPT conversation; OpenAI handles that conversation under its own terms and privacy settings. Receipt Janitor keeps encrypted connection credentials and expiring authorization metadata so ChatGPT can access the account you approved. Google credentials are never returned to ChatGPT. Disconnect the plugin in ChatGPT to stop using that connection; account closure blocks its access and account deletion includes connection records.

Subscriptions and payment records

When purchases are available, Stripe processes payments on the web. Payment entry happens with Stripe. Receipt Janitor keeps your plan and usage, your payment customer and subscription identifiers, and subscription status; it does not store card details. Receipt contents and expense fields are not sent to billing providers.

This browser and the iPhone app keep an unfinished property setup so a retry can continue it. An anonymous cancellation reminder can remain on either device until you dismiss it.

Where records stay

Saved receipts occupy your Google Drive storage. Files that fit the 4 MiB preparation limit are kept as chosen. Larger photos are optimized on your device; the same optimized copy is scanned and saved to Drive, and JPEG conversion removes embedded photo details such as location. Native document scans may optimize every scanned page to fit. Imported PDFs and GIFs are never shortened or flattened; if they cannot fit safely, choose a smaller file. Receipt Janitor uploads a receipt directly into the property's receipt folder when you save. It does not create a temporary upload folder for new captures or add public sharing permissions. A saved receipt can inherit access from its destination folder, so check the Sheet and folder sharing settings before sharing links.

Firestore stores your property mappings, preferences, final-save records and recovery details, usage counters, subscription records, support requests, and property-operation history. New captures do not create server drafts. Final-save and historical expense records have no automatic expiry at present. We store an encrypted Google connection, bound to your verified Google account, so shared-property work can finish independently of a browser or iPhone session. Signing out revokes that app session; the connection remains until account deletion or you revoke Google access. When you remove a property you choose whether to keep its files in Drive or move its Sheet and entire receipts folder, including files you added there yourself, to Drive Trash; Receipt Janitor never permanently deletes files or empties your Trash.

Shared properties

You can invite one person by their verified Google email. When you select Invite, Brevo receives the recipient’s email, your email, the property name and an invitation link to send the invitation. Brevo processes message and delivery records; invitation emails do not include receipts or expense details. Receipt Janitor keeps delivery status so retries do not send duplicate invitations. Acceptance gives that person Editor access to the property’s Sheet and receipts folder. Both people can save expenses, and shared rows record the contributor’s verified email in Added by. Each person uses their own receipt scan allowance. Activity shows your own submissions; the shared Sheet includes both people’s expenses.

Leaving or ending sharing may copy the complete supported workbook and original receipts into the other person’s Google account so their records remain usable independently. Original files are kept. Manual Sheet content is copied from the actual workbook. Unsupported structures, changed content or uncertain Google effects keep the handoff pending. Google access removed outside the app or deleted source files may prevent completion. Historical shared expenses and attribution remain with the other person after you leave or delete your account.

Before and after Save

Before you save, the selected receipt, scan suggestions, property choice and edits stay in the browser or iPhone app's memory. They are not autosaved or kept in an unfinished-expense recovery copy. Leaving Capture, refreshing or closing the app may lose them. Raw OCR text stays in memory. The iPhone app's session token remains in Keychain; billing and property setup keep their separate retry information.

Starting Save freezes the expense and prepared receipt for that request. It continues as you move between screens in the app, and the backend keeps final-save evidence for recovery. Closing the browser, terminating the app or a server interruption can stop processing. If the result is uncertain, use Check on the original expense before retrying. Routine temporary-receipt cleanup is no longer performed. Saved receipts, property files and old temporary folders remain in your Drive until you change them there or use the separately offered property Move to Trash action.

Usage analytics

We use PostHog to understand page and screen visits, property setup, receipt-scanning actions, save and recovery outcomes, and subscription actions so we can improve Receipt Janitor. Signed-in usage uses a hashed account identifier shared across web and iPhone; anonymous visits use an identifier kept only in memory. We do not send receipt contents, OCR text, expense amounts, merchants, descriptions, property names, email addresses, Google file identifiers, authentication tokens, or private URL parameters to analytics. Session replay and automatic form, console and error capture are off. PostHog receives network requests and may process connection metadata, including your IP address; event payloads disable IP geolocation and person profiles.

Analytics uses no additional cookies or persistent tracking identifier on your device. Browser Do Not Track and Global Privacy Control signals turn analytics off, as do previously saved analytics opt-outs in this browser or iPhone installation. Analytics failures do not interrupt capture or saving. For analytics access or deletion questions, email hello@receiptjanitor.com or use the Help form.

Account deletion and your choices

From Account, you can request account deletion. The request is handled manually. Your original Google Sheets and Drive files are kept. Shared-property handoffs finish before Google access is revoked or the account is closed. The request stays pending if the other person’s independent copy cannot be verified; you can reconnect Google and continue from Account. The pending request keeps your Google account identifier and reply email until the owner processes and answers it. Requesting deletion cancels a web subscription’s renewal. After handoffs and review, Receipt Janitor removes ordinary account records, offline connection credentials and finished invitation metadata while retaining shared expense history, historical Added by labels, and unresolved write and billing safeguards. A minimal hashed account reference remains to prevent replay and accidental account reopening. These records have no automatic expiry. Any additional required retention will be explained as part of the deletion response.

Use Subscription help to manage billing even after app access closes.

You can also revoke Receipt Janitor’s Google access in your Google Account. The app may still appear as Receipt Janitor in Google’s connection settings. Revoking access stops app actions but does not itself delete app records or Google files. For access or privacy questions, email hello@receiptjanitor.com or use the Help form.