Receipt Image Privacy & Storage
Receipt photos are handled with the same privacy-first approach as your bank statements.
Where images are stored
Receipt images are stored in Supabase Storage (AWS Canada ca-central-1), separate from the database. They are not publicly accessible — each image requires a time-limited signed URL to view.
What Claude Vision AI sees
When you scan a receipt, the compressed image is sent to Claude Vision AI for extraction. The AI reads the receipt and returns structured data (merchant, amount, date, etc.). The AI does not receive your name, account information, or any data beyond what's visible on the receipt itself.
Image retention by plan
- Free tier: Receipt images are automatically deleted from storage immediately after AI extraction. Only the extracted text data is kept.
- Pro plan: Images are retained for 6 years alongside your transaction data.
- Max plan: Images are retained for 6 years.
- Tax Season Pass: Images are retained for the duration of the pass.
Client-side compression
Before uploading, receipt images are compressed in your browser from up to 10MB down to approximately 300KB. This reduces storage costs and speeds up processing while preserving enough detail for accurate extraction.
Deletion
When you delete a receipt from the Receipts tab, both the database record and the stored image file are permanently removed. When you delete your account, all receipt images are destroyed along with the rest of your data.
Related articles
How Your Financial Data is Protected
GigBooks processes bank statements in your browser. Learn how client-side parsing, encryption, and minimal data collection protect your privacy.
What Information the AI Receives
Exactly what data GigBooks sends to Claude AI for categorization — only anonymized merchant names and amounts, nothing else.
PDF Statement Privacy & PII Redaction
How GigBooks redacts personal information from PDF statements before AI processing — names, account numbers, and addresses are removed.