Skip to content
Legal

Privacy Policy

Draft, pending legal review. Version 2026-11-01.

This policy explains what personal data Anchr.ing processes and why. It covers two roles. For your dashboard account and the public site we are the controller. For the users who sign in to our customers' apps we are a processor: the customer is the controller and decides what happens with that data, as set out in the Data Processing Agreement.

Controller: Simon ApS, Gersonsvej 40, 1., 2900 Hellerup, Denmark, CVR 38213458. Contact: privacy@anchr.ing.

1. Dashboard accounts (we are the controller)

  • Account: your email address, optional name, passkeys and authenticator apps (public keys and encrypted secrets, never readable by staff), sign-in sessions with IP address and browser, and an audit log of what you do in the dashboard. Purpose: to provide the service and keep it secure (contract, GDPR Art. 6(1)(b); security, Art. 6(1)(f)).
  • Projects and members: the projects you own or belong to and their members' email addresses.
  • Billing, if you pay for a plan: your plan and subscription, your billing details (company name, address, country, VAT ID and the result of its check in the EU's VIES service, your purchase-order reference), the billing email addresses you add, invoices and credit notes, and payment records (amount, status, the payment processor's reference, card brand, last four digits and expiry, or the last four digits of a bank account and the SEPA mandate reference). You enter card and bank details on the payment page of our payment processor, Adyen N.V. (Amsterdam, the Netherlands); they never reach our servers, and Adyen gives us only a token to charge the stored method. Purpose: to bill you (contract, Art. 6(1)(b)) and to keep accounting records (legal obligation, Art. 6(1)(c)). Recipients: Adyen, and your card issuer or bank through it; for fraud prevention and its own legal duties (such as anti-money-laundering rules) Adyen acts as an independent controller under its own privacy statement. Our accountant and the tax authorities see invoices where the law requires.
  • VAT evidence, if you are a consumer in the EU: for each invoice we record the country of your billing address, the country of the card or bank account you pay with (from Adyen) and, where our network provides it, the country of the IP address you checked out from. Purpose: to show which country's VAT applies, as EU VAT rules require (legal obligation, Art. 6(1)(c)).
  • Fraud checks, when you check out or change your payment method: a keyed hash of your IP address range (never the address itself), your email domain, the token Adyen gives for your card (never the card number), the countries above, how often payments are tried and refused, and Adyen's own risk result. From these we calculate a risk score. A checkout may then ask for extra card verification (3-D Secure), be held for a person on our staff to review, or be refused. An existing subscription's renewal is never stopped by the score alone, and a held or refused payment can always be reviewed by a person: write to hello@anchr.ing. Purpose: to prevent payment fraud and card testing (legitimate interest, Art. 6(1)(f)).
  • Terms: which version of the terms you accepted and when.

2. Visitors to the public site

The public pages of Anchr.ing (not the dashboard, not any sign-in page) use a self-hosted analytics tool (Rybbit), which we run ourselves (Simon ApS) on our own server at Hetzner in the EU (Germany or Finland). For each page view it records the page address (with its query string), the referring site, browser, operating system, device type, screen size, language and an approximate location derived from the IP address, and it stores a random visitor ID in your browser's local storage so repeat visits can be counted. Purpose: to understand which pages are useful (legitimate interest, Art. 6(1)(f), or your consent where the law requires it for storing the ID; see the cookie statement). Session recording is switched off. We keep analytics data for 24 months.

The site's server keeps ordinary access logs (IP address, time, page, browser) for security, for at most 14 days.

3. Users of our customers' apps (we are a processor)

When you sign in to an app that uses Anchr.ing, the app's company is the controller of your data and you should read its privacy notice. On its behalf we store: your email address and whether it is verified, your name and picture if a sign-in provider gave them, data the app adds to your profile, your passkeys (public keys only), password (as an argon2id hash) and authenticator app (encrypted), linked sign-in accounts, sign-in sessions with IP address and browser, personal access tokens (hashed), and an audit log of sign-ins and account changes. If mail to your address bounces or is reported as spam, we note that so we stop sending to it.

You can download all of this, or delete your account, yourself on the account page of the app's sign-in host (Account, Your data). For anything else, contact the app's company; we help them answer you.

4. How long we keep data

  • Accounts and users: until they are deleted. Deleted users' entries in the audit and token logs keep only a pseudonym, without IP address or browser.
  • Audit and token logs: 365 days by default; each project can choose 30 to 730 days per environment.
  • Webhook and logout deliveries: 30 days after they finished. Test environments' mail log: 30 days.
  • Sign-in codes, links and challenges: minutes, until they expire. Backups: 30 days.
  • Billing: invoices, credit notes, the payment records behind them and their VAT evidence for 10 years after the end of the year they belong to. This covers both the Danish Bookkeeping Act (bogføringsloven, 5 years) and the EU VAT rules for sales declared through the One-Stop Shop (10 years). Billing details and billing email addresses are kept while the account exists, and after that only as part of those records.
  • Fraud-check records: 180 days. A staff decision on a held or refused payment is kept with the account's audit log.

5. Where the data is and who helps us

All service data is stored in the EU, with Hetzner in Germany and Finland. The companies that help us are on the sub-processor list. Where one of them is outside the EU/EEA, the transfer is covered by the EU-U.S. Data Privacy Framework or the EU standard contractual clauses.

6. Security

Each project has its own database namespace and database users; secrets we only compare are hashed, and secrets we must read back are encrypted with a key per project and environment, itself encrypted with a master key kept apart from the backups. Sign-in pages load no third-party scripts. The Data Processing Agreement lists the measures.

7. Your rights

You have the right to access, correct, delete and export your data, to object to processing based on legitimate interest and to restrict processing. Write to privacy@anchr.ing. You can complain to the Danish Data Protection Agency (Datatilsynet, datatilsynet.dk) or the authority where you live.