Contact
Talk to us
Every address on this page is a real mailbox that a person reads. Pick the closest one — if none of them fits, the first one is always right.
Where to write
| Address | For |
|---|---|
| [email protected] | Anything that does not fit a line below. This is the address the footer, the privacy policy and our contracts all point at, so it is never the wrong choice. |
| [email protected] | Pricing beyond the public tier, bulk delivery, per-country onboarding, and the paperwork a procurement team needs before an evaluation starts. |
| [email protected] | Integration problems, a response that looks wrong, a record that does not match its register, rate limits and API keys. |
| [email protected] | Vulnerability reports and anything else that should not sit in a general inbox. Also published in /.well-known/security.txt per RFC 9116. |
| [email protected] | Invoices, VAT details and purchase-order references. |
Your data, or a company record
Named in our data and want it changed?
Use the request form rather than email — it routes straight into the process that has to answer you within the statutory deadline, and it does not depend on someone spotting a message in an inbox.
- Data-subject request — access, correction, objection, erasure
- What we hold and why · Public-records privacy policy
- Report illegal content (DSA Art. 16 notice)
A company record that disagrees with its register is a data-quality bug, not a privacy request — send that to support and name the identifier and the country so we can trace it to the source.
Who you are writing to
Inger · Banská Bystrica, Slovakia (EU)
We are a small team, so replies come from a person rather than a queue. Expect an answer within two business days; a security report is read the day it arrives.
Infrastructure and data all sit inside the EU. What that means in practice, including what we do not have, is written down rather than summarised in a badge.