How we handle your data

Everything runs in the European Union: the application, database and file storage in Google Cloud’s Belgium region (europe-west1), and document AI processing on Google Vertex AI’s EU endpoint in the same region. Email is sent through Mailgun’s EU infrastructure. Traffic passes through Cloudflare’s network for delivery and protection.

Data is encrypted in transit (TLS) and at rest — Google Cloud encrypts all stored data, including your documents and photos, by default. There is no plaintext copy of your files anywhere in the system.

You, and only the people you explicitly invite to a property (with the role you give them). We don’t browse your files. Operational access to production systems is limited to what running the service requires, and we will only look at your data where you ask us to (support) or the law requires.

When you photograph a document, it’s processed once by Google Vertex AI’s EU endpoint to extract the details (make, model, dates, amounts), then the result is cached — identical uploads aren’t reprocessed. Under Google Cloud’s data-governance terms, your content is not used to train AI models — ours or Google’s. Every extracted field links back to the photo it came from, so anything can be checked against the source. The full walkthrough is on the Journal.

There are no third-party analytics scripts, advertising pixels or social trackers on KeepUp — no Google Analytics, no Meta pixel, nothing. We record first-party product events (for example “a document was uploaded”) in our own infrastructure to fix problems and improve the product. Your data is never sold and never used for advertising.

Every account — free plans included — can export the entire vault as a plain zip (every document, every photo, a CSV of every appliance) at any time from the account page. Account deletion is self-serve and erases your personal data. Unreviewed forwarded-email captures are automatically deleted by a daily retention sweep rather than lingering. The ownership promise, in full.

No SOC 2 or ISO 27001 certification — those are audits that make sense at a scale we haven’t reached, and we’d rather tell you that plainly than imply otherwise. No bug-bounty programme, though we do publish a security.txt and take reports at [email protected] seriously. This section shrinks as the company grows; the honesty stays.

Privacy questions and data-subject requests: [email protected]. Vulnerability reports: the same address, per our security.txt. The legal detail lives in the privacy policy.