Receepo Privacy Policy

Receipt information

When you upload or scan receipts, we collect:

• Receipt text extracted via OCR (Optical Character Recognition), including merchant names, dates, amounts, and line items
• Receipt images, stored in Amazon Web Services S3 (eu-west-1, Ireland) for your records
• Forwarded email receipts: the emails you forward to your Receepo address, with their attachments
• Receipt metadata: dates, transaction amounts, categories, subcategories, and custom tags
• Manual annotations: notes, corrections, or classifications you add

Account information

• Email address (from authentication provider)
• User ID (unique identifier)
• Profile information (name, profile picture if provided)
• Account creation date and last login time
• User preferences and settings

Device and usage information

• Device model and iOS version (for compatibility)
• App version and build number
• Device language and timezone settings
• Usage analytics (features used, session duration)
• Error logs and crash reports (for debugging)

Camera and photo library access

We request access to your camera and photo library to enable receipt scanning functionality. This access is only used to capture or select receipt images. Each image is cropped to the receipt when the app can find its edges (otherwise the whole photo is kept) and read on your device before it is uploaded; with your consent, a reduced copy is also sent to TypeSafe.

TypeSafe integration (Jev AI models)

What is sent to TypeSafe:

• A reduced copy of the receipt photo: cropped to the receipt when the app can find its edges, otherwise the whole photo, and at most 1568 pixels on each side; a very long receipt is sent in a few parts, and an area that is hard to read may also be sent as a close-up
• The text your phone reads from the receipt: its printed lines, such as the merchant, address, items, amounts, and dates
• Email receipts you forward to Receepo: their subject, sender, and text, and the text of their attachments
• Your category names, so a category can be suggested, and the text of any category list you import

What is not sent to TypeSafe:

• Your login email, user ID, or password (a receipt or a forwarded email can still contain your name or email address)
• Any other photo from your camera or photo library
• Your device information
• Historical purchase patterns or aggregate data

Purpose of AI processing:

• Finding the total, date, merchant, and address on a receipt
• Checking the values your phone has read
• Suggesting a category and subcategory for each expense
• Picking out the details of a forwarded email receipt, such as the total, the date, or a flight number
• Sorting the lines of an imported category list into expense categories

TypeSafe only finds, checks, and chooses; it does not write text. Every amount, date, and merchant Receepo fills in for you is read from the receipt or email itself.

TypeSafe’s data handling. TypeSafe processes this data only on our behalf, under a data processing agreement covering retention and international transfers (EU Standard Contractual Clauses). TypeSafe states that it does not train its models on customer data. Read TypeSafe’s Privacy Policy.

Your control over AI processing

• Your permission first: nothing is sent to TypeSafe until you allow AI processing, and you can turn it off at any time in Settings
• Manual mode: enter or correct receipts by hand
• Data minimization: each feature sends only the data it works on: the receipt image (reduced, plus a close-up of an area that is hard to read), the receipt’s text, the email receipts you forward, and your category names and imported category lists; never your account details

Other third-party services

• Hetzner Online GmbH: hosting of the server in Germany where we run our database and sign-in (Supabase software), data sync, and backend (see data storage)
• Amazon Web Services: storage of receipt images and files in S3 (eu-west-1, Ireland), and receiving and sending email
• RevenueCat: management of app subscriptions: your user ID and your App Store purchase and subscription status
• Authentication providers: Google, Apple Sign In (only email and basic profile information)

Where your data is stored

• Cloud database: your receipt data and account information are stored in a PostgreSQL database with its sign-in service (Supabase software), which we run on a server rented from Hetzner Online GmbH in Germany
• Local device storage: temporary cache for offline access and performance optimization
• File storage: receipt images and their files are stored in a private Amazon Web Services S3 bucket in eu-west-1 (Ireland); the app opens them only through signed links that expire after 5 minutes

Security measures

• Encryption in transit: all data transmitted between your device and our servers uses TLS/SSL encryption (HTTPS)
• Encryption at rest: database and file storage are encrypted using AES-256 encryption
• Access control: row-level security policies ensure users can only access their own data
• Authentication: secure OAuth 2.0 authentication with industry-standard providers
• Regular backups: automated daily backups with point-in-time recovery
• Security monitoring: continuous monitoring for unusual activity and potential security threats

Data retention

We retain your data for as long as your account is active or as needed to provide you services:

• Active accounts: all receipt and account data is retained indefinitely while your account is active
• Deleted receipts: removed from your reports at once. Their files are erased from our cloud storage within 3 days of the deletion reaching our servers (a copy inside a report export you made is erased when that export expires, about 7 days after it was made); the rest of the receipt’s record (such as merchant, date, and amount) stays in our database, marked as deleted, until you delete your account
• Account deletion: deleting your account in Settings erases at once your receipts (deleted ones included), your reports and the emails sent from them, your categories, and the files of your receipts and reports in our cloud storage. Your sign-in login is shared with other Repleto apps and is not deleted. Account deletion does not erase forwarded email receipts not yet filed, your forwarding address, push notification tokens, your company membership, trips and receipt photos saved by earlier versions of the app, or your subscription record at RevenueCat; write to dev@repleto.io and we will erase them
• Inactive accounts: accounts inactive for 3+ years may be flagged for deletion with prior notice
• Legal requirements: some data may be retained longer if required by law

Service providers

• TypeSafe: AI processing of receipt images, receipt text, email receipts, and category names, only with your consent (see AI and third-party services)
• Amazon Web Services: receipt file storage (S3, eu-west-1, Ireland), and receiving the email receipts you forward and sending the reports you email
• Hetzner Online GmbH: hosting of the server in Germany where we run our database, sign-in, data sync, and backend
• RevenueCat: app subscriptions (your user ID and your App Store purchase and subscription status)
• Authentication providers: Google, Apple (only for identity verification)

Legal requirements

We may disclose your information if required by law, court order, or government request, or to protect our rights, property, or safety.

Business transfers

In the event of a merger, acquisition, or sale of assets, your information may be transferred. We will notify you before your data is transferred and becomes subject to a different privacy policy.

What we don't do

• Sell your data to advertisers or marketing companies
• Share your data with social networks
• Use your data for advertising purposes
• Track your location unless necessary for app functionality

How to exercise your rights

• In the app: go to Settings → Privacy & Data to manage your preferences
• Email us: send requests to dev@repleto.io
• Response time: we will respond to your request within 30 days