This policy explains what personal data GeoVerdict processes, why, where it is stored, how long it is kept, and the rights you have under the General Data Protection Regulation (GDPR).
1. Who we are
GeoVerdict is operated by [LEGAL ENTITY], registered with the Dutch Chamber of Commerce (KvK) under number [KVK NUMBER], registered address [REGISTERED ADDRESS]. For anything privacy-related, contact support@geoverdict.com.
2. Two roles
We process personal data in two capacities:
- As controller for your account, the website, billing and support: everything in this policy.
- As processor for address data that our customers submit through the API or the embeddable widget. That data may relate to the customer's own end users; the customer is the controller and our Data Processing Agreement applies.
3. What we process and why
| Data | Details | Legal basis |
|---|---|---|
| Account data | Your email address, plan, account settings and creation date. Sign-in works with a one-time email link or code; we never store a password. | Performance of a contract |
| Credentials | Sign-in links and codes, session tokens and API keys are stored as cryptographic hashes. Recently created API keys are additionally stored encrypted so you can reveal them yourself in the console. | Performance of a contract; legitimate interest (security) |
| API usage logs | For every API request: the submitted address query, the returned result, which data sources answered, verdict, confidence, latency, timestamp, optional source tag and credits charged. These logs are the billing ledger and are visible to you in your own console. | Performance of a contract (billing); legitimate interest (troubleshooting, abuse prevention) |
| Homepage demo | Addresses typed into the demo on the homepage are validated and logged like API requests, without any link to an account. To enforce demo limits we store a salted hash of your IP address; the raw IP address is never stored. | Legitimate interest (abuse prevention) |
| Website analytics | On the public landing pages we use PostHog (EU cloud) with a randomly generated device ID to measure page views and events such as demo use and signup steps. Analytics is not linked to your account email and is disabled for crawlers. | Legitimate interest (improving the website) |
| Payment data | Checkout happens on Stripe-hosted pages. We receive the checkout email address, the product purchased, the amount and a Stripe customer reference. Card details go to Stripe directly and never reach our systems. | Performance of a contract; legal obligation (bookkeeping) |
| Support | Emails you send to support, and our replies. | Legitimate interest (support) |
4. Address data and geocoding providers
To answer a validation or autocomplete request, we forward the address query to one or more geocoding data sources, listed on the subprocessors page. Providers receive the address query itself and nothing else: no account identity, no end-user identity. Responses may be cached for up to one hour, and only when the terms of every data source involved permit caching.
5. Where your data lives
GeoVerdict runs on Cloudflare. The primary database and cache are stored in Cloudflare's Western Europe region (Amsterdam). Requests are executed on Cloudflare's edge network at the location nearest the caller. Analytics data is stored in PostHog's EU cloud, and transactional email is sent through Brevo (France). Payment data is held by Stripe. See the subprocessors page for the full list.
6. How long we keep data
| Data | Retention |
|---|---|
| Account data | While your account exists; deleted on account closure, except records we must keep by law |
| Sign-in links and codes | Valid for 15 minutes; removed from the database within about a day |
| Console sessions | 30 days |
| API usage logs (including queries) | While your account exists; they form the billing ledger. Removed on account closure on request, except where retention is legally required |
| Demo rate-limit IP hashes | Rolling 30 days, then deleted |
| Geocode cache | Up to 1 hour |
| Analytics cookies | 1 year (see section 9) |
| Billing records | As long as Dutch tax law requires (in general 7 years) |
7. Sharing
We do not sell personal data. We share data only with the service providers needed to run GeoVerdict (see subprocessors), and with authorities where we are legally required to.
8. International transfers
Data is stored in the EU. Some of our providers are part of groups headquartered outside the EEA or operate a global network. Where personal data is transferred outside the EEA, we rely on an adequacy decision (such as the EU-US Data Privacy Framework) or on standard contractual clauses.
9. Cookies
| Cookie | Purpose | Lifetime |
|---|---|---|
gv_session | Keeps you signed in to the console. Essential, HttpOnly. | 30 days |
gv_did | Random device ID for website analytics (PostHog EU). Not linked to your account. | 1 year |
gv_ab | Remembers which version of the homepage you were shown, so it stays consistent. | 1 year |
We use no third-party advertising cookies.
10. Your rights
Under the GDPR you can ask us for access to, correction of, deletion of, or a copy of your personal data, ask us to restrict processing, and object to processing based on legitimate interest. Email support@geoverdict.com and we will respond within the statutory period; we may need to verify that you control the account email address. You can also lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens.
11. Security
The measures we take to protect your data are summarized on the security page.
12. Changes
We will update this policy when our processing changes and revise the date at the top. For material changes we will notify account holders by email or through the service.