What data Stareceipt stores

Stareceipt stores the following data on your behalf:

Data type	Backing system	Notes
Receipt images	Deployment-configured object storage	Provider and retention are environment dependent
Receipt fields, workspaces, memberships	Application databases	Lifecycle follows receipt deletion and account-deletion flows
Account profile and login state	Auth and application services	Lifecycle follows account settings and account-deletion flows
Connected Gmail authorization and sync state	Auth and application services	Refresh credentials are envelope-encrypted server-side; disconnect revokes the Google grant
Export files	Temporary export storage	Retention is environment-policy dependent
Server-side logs	Operational logs	Retention is deployment-policy dependent
Partner referral and commission ledger	Application databases	Portal identifiers are anonymized on account deletion; minimum financial and abuse-prevention records may be retained for legal, tax, accounting, and dispute obligations

Exporting data

Current shared code proves normal report and workspace export flows plus export quota tracking. This page does not assume a separate self-service "download everything about me" privacy export workflow unless your deployment documents one separately.

For regular workspace exports, see Export & CSV.

Accessing and correcting your data

Use the profile, account-binding, and other account settings that your current client exposes to update your details. If you need help with a privacy or support request, contact support@stareceipt.com.

Connected Gmail privacy

Connected Gmail is optional and independent from Stareceipt login. Stareceipt requests read-only access and filters for likely receipt or invoice messages before retrieving content for extraction. The app never stores the Google refresh credential; it is envelope-encrypted on the server, while retrieval workers receive only short-lived access credentials. Temporarily staged message content is deleted under the deployment retention policy.

Disconnecting a mailbox stops future synchronization and revokes the Google grant. Previously imported expenses remain until you delete them through the normal receipt lifecycle. Stareceipt does not use connected Gmail content for advertising, sale of personal data, or general-purpose model training.

Deleting individual receipts

Deleted receipts leave the active receipt list. Clients that expose recycle and restore controls can recover deleted receipts during the recycle-bin retention window. See Recycle Bin.

Deleting your account

Stareceipt includes an account-deletion request flow. Depending on deployment policy and owned-workspace actions, a deletion request may delete the account immediately or place it into a pending-deletion state first.

Before deleting:

Export your data if you need a copy (see above).
If you own shared workspaces, resolve the required owned-workspace actions before final deletion.
Account cleanup revokes connected Gmail grants and removes their stored credentials; export or review imported expenses first if needed.

Account-deletion flow

Open the current client settings and start Delete Account.
Review the warning and submit the deletion request.
If the account enters a pending-deletion state, the client can query deletion status and, where supported, cancel the deletion before final cleanup.
Final cleanup timing is deployment dependent.

If the account participated in the invited partner referral program, final cleanup removes or anonymizes portal profile and contact identifiers. Stareceipt may retain pseudonymized attribution, commission, payout, tax, accounting, and fraud-prevention facts where required by law or contract; these retained facts are not available as an active partner login.

If you need a privacy-specific request that is not exposed directly by your current client build, contact support@stareceipt.com.

Privacy policy

The full privacy policy is available at stareceipt.com/privacy. If you have questions not addressed here, email privacy@stareceipt.com.