Security and data practices
Purchase data deserves careful handling.
Purchory separates public pages from private purchase data, keeps receipt storage private, and limits operational data to what the service needs.
Review privacy practicesCurrent technical boundary
Receipt access stays behind the account boundary.
- Private receipt storage
- Saved receipt images use private storage. Access is checked against the signed-in account and workspace before a receipt is returned.
- Protected transfer
- Purchory uses encrypted connections in production and keeps upload permissions short-lived instead of making receipt objects public.
- Privacy-safe operations
- Routine logs are designed to exclude receipt content, merchant names, items, totals, filenames, questions, tokens, signed URLs, and email addresses.
AI processing
Machine-extracted details are a draft for you to check.
Receipt processing may use the OpenAI API when the feature is enabled. Purchory does not opt receipt content, corrections, purchase data, or questions into generalized model training.
Public launch remains blocked until the production account, contract, and endpoint settings are verified. Until that evidence is complete, the working disclosure allows provider retention of processed content for up to 30 days.
Your controls
Review, correct, export, or ask to delete.
Purchory shows extracted receipt details for review. You can correct saved information, delete individual receipts where available, and use the published data-rights paths for broader requests.