Dazr Identity privacy notice
Last updated 17 November 2026 · For your Dazr Identity account, organisations, organisation and business verification, personal identity verification and Sign in with Dazr Identity.
If a translation of this page differs from the English version, the English version applies.
Who is responsible
Dazr, Viale Cesare Poggi 1, 15061 Arquata Scrivia (AL), Italy, VAT IT 02801250065, is the controller for the personal data described in this notice. For anything about your data, write to privacy@dazr.eu.
What we keep for your account
- Your profile. Email address, name, language, and optionally a profile picture and a personal address. When you first sign in, we suggest a name based on your email address; you can change it.
- How you sign in. The one-time codes we email you (each valid for 10 minutes), the passkeys you add (the public key, the name you give it, and when it was added and last used), and whether you use Google or Microsoft sign-in.
- Your sessions. For each device you are signed in on: the browser and operating system, the country derived from your IP address, and when the session started and was last used. A session ends after 30 days or when you sign out. You can see and end sessions under Security.
- Sign-in times. The times of your last 50 sign-ins, kept for 100 days. Admins of organisations you belong to can see these times from the day you joined, but not your devices or the apps you use.
- Security counters. To stop abuse, we count requests per IP address and per email address. These counters are deleted automatically within 24 hours.
- Abuse protection. When you sign in or create an account, we keep the network address you used as a keyed hash (never the address itself; for IPv6 only its first half) for your last 10 sign-ins, and the random device ID from the
dz_devcookie for your last 5 devices. We use them only to stop people Dazr has banned for abuse from creating new accounts, and keep them for up to 400 days after your last sign-in. A ban on a network ends after at most one year. Legal basis: our legitimate interest in protecting Dazr and its customers against abuse (Article 6(1)(f) GDPR). A device or network that fills in a form field people never see, uses a trap record or scans Dazr for weak spots is marked as a bot for 24 hours to 7 days; in the last two cases it is also banned automatically. - Security log. When a request to Dazr looks like an attack or is refused for security reasons (for example a wrong sign-in code, a request from another website, code typed into a form field or a limit reached), or a browser reports that one of our pages blocked something, we record what happened and when, the address requested, the network address it came from and its country, the random device ID from the
dz_devcookie and, when known, the account. We look up which network the address belongs to (IP to ASN data by DB-IP, CC BY 4.0) and may report an attack to that network’s provider, with the times, the address and what was attempted. We never record passwords or what you write in documents and emails; of a suspicious field we keep at most 200 characters, without email addresses and long numbers. Only Dazr’s administrators see it, to find and stop attacks and abuse, and it is deleted after 30 days. Legal basis: our legitimate interest in protecting Dazr and its customers against attacks (Article 6(1)(f) GDPR). - Extra abuse checks. If an account shows signs of abuse, we may place it under extra abuse checks for a limited time. These use only the security records described here, never the content of your mail, documents or files.
Legal basis: we need this data to provide your account (Article 6(1)(b) GDPR). Sessions, sign-in times and security counters also serve our legitimate interest in protecting accounts against misuse (Article 6(1)(f) GDPR). Showing sign-in times to organisation admins serves the organisation’s legitimate interest in knowing that its members’ accounts are in use (Article 6(1)(f) GDPR).
Signing in with Google or Microsoft
If you choose Google or Microsoft, you sign in on their page and they send us your email address, confirmed as verified, and your name. We receive nothing else from your Google or Microsoft account, and never your password. Google and Microsoft handle your sign-in under their own privacy policies.
Organisations
You can create an organisation or join one when you are invited. An organisation holds its name, country, company number, VAT number, registered address and, optionally, a logo and an email domain, plus its members with their names, email addresses and roles. All members can see the member list. The owner and admins manage the organisation and can see when members signed in.
- When a VAT number is entered, we check it with the European Commission’s VIES service.
- To confirm an email domain, we look up a DNS record of that domain through Cloudflare’s public DNS service.
- Invitations are sent by email and expire after 14 days; invitation links after 7 days.
Legal basis: we keep organisations to provide the service to their members (Article 6(1)(b) GDPR). An organisation stays until its owner deletes it. Deleting your own account does not delete organisations, because other members use them: leave them first, and transfer or delete the ones you own.
Verifying an organisation
An owner or admin of an organisation can ask us to verify it. They name the director or another person who can sign for the organisation, with that person’s name and email address; we email that person a link (and reminders) and tell the requester and the organisation’s admins how the request stands.
- With a qualified electronic signature. The representative signs a declaration we generate. We check the signature and the certificate against the EU trusted lists and the certificate provider’s revocation service. We keep the signer’s name, country and, if present, the organisation identifier from the certificate, and the signed file, encrypted, as evidence for as long as the organisation is verified and 5 years after the verification ends or the organisation is deleted, because regulated businesses that rely on the verification must be able to show it to their auditors.
- With documents. Without a qualified signature, the representative can upload a company register extract and a copy of their passport or ID card. We tell them they may cover the document number and national ID or tax numbers. The files are stored encrypted, are never sent by email, and only Dazr staff who review verifications can open them. We use the ID copy only to verify that organisation and delete it automatically 30 days after the decision; we then keep only the decision, who made it, the date and a fingerprint (hash) of each file. The extract is kept like the signed file above.
- With the organisation’s seal, a sealed register extract or a PEC code. A declaration sealed with the organisation’s qualified electronic seal is checked like a signature. A company register extract that is digitally sealed by the business register (for example an Italian visura camerale or a Dutch KVK extract) is checked automatically: we read its text to find the company number, the representative’s name and, in Italy, the PEC address, and keep the extract encrypted as evidence. For a PEC code we send a one-time code to the organisation’s PEC address and keep that address with the verification.
- Paid: letter by post or video call. For a letter we use the organisation’s registered address to print and post a letter with a code; for a video call we keep the booked time, the meeting link and the reviewer’s note on the outcome. We do not record calls. Payments are processed by Mollie B.V. (Amsterdam), which receives the amount, a description and a reference to the request, not the documents; we keep payment and invoice records for as long as tax law requires (10 years in Italy). Refunds are also handled through Mollie.
- Legal basis. The organisation’s request (Article 6(1)(b) GDPR) and our legitimate interest in preventing fraud and impersonation of organisations (Article 6(1)(f) GDPR).
- Verification reports. For the apps’ audits we keep the facts of each verification (organisation details, dates, method, the certificate details of the signature or seal, the register extract check, the VIES result, the checks a reviewer made, file fingerprints) for as long as the signed file above. Never in a report: ID copies or ID numbers, one-time codes, email addresses or addresses other than the registered office; reviewers appear only as an internal ID. ID copies keep their 30-day retention.
- What apps see. Apps the organisation was shared with see its verification status, method and date. Apps that at least one member shared the organisation with can also download its verification report, the signed declaration (for a qualified signature or seal) and the company register extract, a public register document, as evidence for their audits. They never receive ID copies or the representative’s email address. Every download shows in the organisation’s activity for its admins.
Business verification
An owner or admin of an organisation can start a business verification. It checks the company register and the person acting for the organisation, so that apps can rely on knowing which company they deal with and who acts for it. Beneficial owners are not part of it, and we ask for no details about them.
- What the organisation gives us. The legal form and the register details, and the name and email address of the person acting for it (the representative), who declares that the details are correct.
- Your identity check. If you act for the organisation, you take one photo of your passport, ID card or residence permit and one selfie, live with the camera on the page; nothing can be uploaded from your gallery. On a computer, a QR code or an emailed link moves the photos to your phone. If someone else at the organisation started the verification, we email you a link and a one-time code; you confirm that you are a director or legal representative, and you may add a power of attorney, which only a reviewer sees and which is deleted with the other evidence. Before you take any photo we explain the check and ask for your explicit consent, because the face comparison uses biometric data (Article 9(2)(a) GDPR).
- How the photos are checked. An AI model reads the document photo to extract its details (name, date of birth, nationality, document type and number, dates and, for a passport, the machine-readable zone) and to look for signs of tampering. It sees only the document, never the selfie, and does not compare faces; it does not keep the images or use them to train models. A Dazr reviewer compares the selfie with the photo on the document. We then check the dates, the name and, for a passport, the machine-readable zone ourselves.
- Register and screening. We look up the organisation in the official business register (or check an extract the organisation uploads) and check whether it lists you. We check the organisation and you against the EU, UN and US (OFAC) sanctions lists, which we download and match ourselves. We also look for politically exposed persons (PEP): through OpenSanctions, which receives your name and, when known, your date of birth and nationality (for the organisation, its name and country), or, where it is not available, by looking up the name (and nothing else) in Wikidata, a public database, to see whether someone holds a public position. The PEP result is recorded for the apps and does not stop the verification. Approved organisations are checked against the sanctions lists again every day and for PEP status every 30 days.
- Decisions. A Dazr reviewer compares your selfie with the photo on your document and decides on the verification, with the results of the other checks; for high-risk cases two reviewers decide. No one is rejected by an automated decision. Reviewers can open the photos only for this purpose, and every opening is logged.
- Legal basis. The organisation’s request (Article 6(1)(b) GDPR); the legitimate interest of the organisation, of the apps that rely on it and of Dazr in knowing which company it is and who acts for it, and in preventing fraud (Article 6(1)(f) GDPR); compliance with EU sanctions law (Article 6(1)(c) GDPR); and your explicit consent for the biometric comparison (Article 9(2)(a) GDPR). You can withdraw your consent at any time by writing to privacy@dazr.eu; we then delete your photos, and your identity check can no longer be completed this way.
- How long we keep it. The photos of your document and your selfie: 30 days after the decision, then deleted automatically, also from the services above. The results (which checks passed, the screening results, your name, date of birth and nationality, but not your document number or the machine-readable zone) and the decision: for as long as the organisation’s business verification is valid and 5 years after it ends, as anti-money laundering rules expect from the businesses that rely on it.
- What apps see. Apps the organisation was shared with see the status, the risk level and the screening result, never names, photos or document details. Apps can download the audit report, which lists the representative and the results of each check, with fingerprints of the evidence, but never images or document numbers.
- Payment. €25 excl. VAT, paid by the organisation through Mollie, as for the paid options above, or by the app that asked for the verification from its prepaid credit. If the verification stops before any identity document has been checked, we refund it in full.
- Without a phone camera. You can ask for your ID to be checked in a video call with a Dazr consultant instead (€200 excl. VAT). You show your ID document on camera; the consultant notes the result and nothing is recorded. If Dazr cancels the call or offers no time that suits you, you get the full amount back.
Personal identity verification
An app can ask you to verify your identity when you sign in to it. You verify once; the verification stays valid for 12 months, and you decide which other apps receive it.
- What we process. One live photo of your passport, ID card or residence permit and one front-facing selfie, both taken with the camera on the page; nothing can be uploaded from your gallery. From the document we read your name, date of birth, nationality, the issuing country, the document type and number, its dates and, for a passport, the machine-readable zone. We check your name against the EU, UN and US (OFAC) sanctions lists, which we download and match ourselves, and keep the result.
- Your consent. Comparing your selfie with the photo on your document uses biometric data. Before the camera opens we explain the check and ask for your explicit consent (Article 9(2)(a) GDPR). You can withdraw it at any time by writing to privacy@dazr.eu; we then delete your photos, and the verification can no longer be completed this way.
- How the photos are checked. OpenAI reads the document photo through its European data residency endpoint, with zero data retention; it sees only the document, never the selfie. A person at Dazr compares the selfie with the photo on the document. We then check the dates and, for a passport, the machine-readable zone ourselves.
- Decisions. A person at Dazr reviews every verification, with the results of the checks, and approves or rejects it. No one is rejected by an automated decision.
- Sharing with apps. The app that asked receives your verification. Any other app receives it only when you agree on a share screen, which shows the app and what it will receive.
- What an app receives. The kyc claim: that you are verified, when and until when, your name, date of birth and nationality as on the document, the country that issued it, and the sanctions result. Never the photos or the document number.
- Who pays. The app pays for each verification and each sharing, from its organisation’s balance. You never pay.
- How long we keep it. The photos: 30 days after the decision, then deleted automatically. The record (the results, the decision and the apps that received it): 12 months while the verification is valid, or 90 days if it was not approved. Once a verification is approved, we keep no document number or machine-readable zone.
- Legal basis. Your request to verify your identity for the app (Article 6(1)(b) GDPR), compliance with EU sanctions law (Article 6(1)(c) GDPR) and your explicit consent for the face comparison (Article 9(2)(a) GDPR).
Signing in to other apps with Dazr Identity
Other organisations can let you sign in to their website or app with your Dazr Identity account (“Sign in with Dazr Identity”). Nothing is shared until you approve it on the Dazr consent screen, which shows the app, the organisation behind it (legal name, country and company number), its privacy policy and the actual values it will receive.
- What can be shared and only what you approve: a random ID; your name and language; your email address; your personal address, if you saved one; the organisations you tick, with their name, country, company number, VAT number, verification status and your role; and permission for the app to stay connected while you’re away. Dazr never shares your files, your contacts or any compliance data, and there is no password to share.
- A different ID per organisation. Each organisation receives its own random ID for you (a “pairwise” identifier), so unrelated organisations cannot link your accounts with each other.
- Legal basis. We disclose the data because you ask us to sign you in (Article 6(1)(b) GDPR). Once the app has received it, the organisation behind the app is an independent controller for that data, under its own privacy policy. Requests about that data, including deletion, go to that organisation; Dazr shows you its support email.
- What Dazr keeps. Your consent for each app (which data and which organisations you approved, when you first connected and when the app last used it), for as long as the connection exists. An activity log of sign-ins and token refreshes per app, kept for 90 days and deleted when you remove the app. Tokens expire on their own: access tokens after 10 minutes, refresh tokens after 30 days without use.
- Updates to apps. When the verification of an organisation you shared with an app changes, the app is told, with your ID for that app. For each app we keep daily counts of sign-ins and consent decisions, and an estimate of how many people signed in that cannot be turned back into a list of people; these are kept for 400 days.
- Your control. Dazr Identity → Connected apps lists every app with exactly what it received. “Remove access” ends the connection at once: the app’s tokens stop working and your consent and activity log are deleted. Connected apps are part of your data download, and deleting your Dazr account removes all connections.
The rules for the organisations that use Sign in with Dazr Identity are in the Dazr Identity Developer Terms.
Registering an app
If you register an app for your organisation, we keep its details (name, homepage, privacy policy, support email, purpose, logo and redirect addresses), who accepted the Developer Terms and when, its settings, and a log of its webhook deliveries, kept for 30 days. The organisation’s admins see the app’s daily sign-in counts.
Emails we send
We send the emails the service needs: sign-in codes, invitations, updates about organisations and verifications, and notices about your apps. Dazr Identity sends no marketing email.
When something goes wrong
If something seems wrong with your account or service, for example sign-in codes that do not arrive, a payment that failed or a mail domain that stopped working, a person at Dazr may call or email you to help. For this we use your name, email address, language, the phone number you or your organisation gave us, and what went wrong. Legal basis: our legitimate interest in keeping the service working for you (Article 6(1)(f) GDPR). You can turn this off at any time in Dazr Identity under Privacy & data; we then only contact you when you ask us to, or when the law or your contract requires it. Our team keeps a record of each contact (who, when, how and the outcome) with internal notes, which are never sent to you.
How long we keep it
- Your account and profile: until you delete your account.
- Sign-in codes: 10 minutes. Sessions: 30 days. Sign-in times: 100 days. Security counters: up to 24 hours. Abuse protection (hashed network addresses and device IDs): up to 400 days after your last sign-in. Security log: 30 days.
- Connected apps: as long as the connection exists; their activity log 90 days.
- Organisations: until the owner deletes them. Verification evidence and payment records: as described above.
- Business verification: photos of ID documents and selfies 30 days after the decision; results 5 years after the verification ends.
- Personal identity verification: photos 30 days after the decision; the record 12 months, or 90 days if the verification was not approved.
- Contacts by our customer care team, with their notes: 24 months.
Visiting our websites
- Server logs. Our hosting provider records each request: IP address, browser (user agent), the address requested, status and time. We use these logs to run our services and keep them secure, and keep them for up to 30 days. Legal basis: our legitimate interest in operating secure websites (Article 6(1)(f) GDPR).
- Page statistics. We count page views with Vercel Web Analytics. It sets no cookies and does not store IP addresses; we only see totals, such as how often a page was viewed. Legal basis: our legitimate interest in knowing which pages people use (Article 6(1)(f) GDPR).
- No advertising or tracking. Our websites show no advertising and contain no third-party trackers, pixels or social media widgets. Fonts and scripts come from our own servers.
- Spam protection. Before a public form is sent, your browser solves a small calculation (proof of work). It runs on your device and sets no cookie.
When you contact us
If you use the contact form or write to one of our addresses, we receive your name, email address, company (optional), the topic, your message and the page you sent it from. The form emails your message to our inbox and a copy to you. We use it only to answer you and follow up on your request, and keep it for up to 24 months after our last contact. Legal basis: steps you ask for before a possible contract (Article 6(1)(b) GDPR) and our legitimate interest in answering questions (Article 6(1)(f) GDPR).
Cookies and storage on your device
We use no advertising or analytics cookies, so there is no cookie banner. What we store is needed for the service or remembers a choice you made, so it needs no consent:
__Secure-dazr_id(cookie): keeps you signed in to Dazr Identity on the dazr.eu sites. It cannot be read by scripts and ends after 30 days, or when you sign out.dz_dev(cookie): a random ID for this browser, set when you sign in. It holds nothing about you or your device, cannot be read by scripts, is shared by the dazr.eu sites and lasts two years. It is used only to keep people banned for abuse from coming back.__Host-dazr_sso(cookie): connects a Google or Microsoft sign-in to your browser while it runs, for at most 10 minutes.dazr_id_hint,dazr_id_ping(local storage): your name, email address and picture, so the page header can show who is signed in straight away, and a signal that keeps your open tabs in step when you sign in or out.dazr_lang(cookie and local storage): the language you picked, so every Dazr site and app opens in it. The cookie holds only the language code, is shared by the dazr.eu sites and lasts one year.
Service providers
These companies process personal data for us, only on our instructions and under written contracts that oblige them to protect it:
- Hetzner Online (Germany, Nuremberg) runs our own servers: the file storage and the backups of our database, both encrypted, and our mail server.
- Vercel hosts our websites and server functions and counts page views.
- Upstash runs the database (a key-value store) that holds accounts and records.
- Mollie (Amsterdam) processes payments for verification by letter or video call and for business verification.
- OpenAI (our contract is with OpenAI Ireland Ltd, Dublin) reads the document photo in a business or personal identity verification, never the selfie, and does not compare faces. We use OpenAI’s European data residency endpoint: requests are processed in the European Union with zero data retention.
- OpenSanctions (Berlin) checks names against its database of politically exposed persons in a business verification.
- Namecheap Private Email hosts our mailboxes, such as hello@dazr.eu and support@dazr.eu, where the messages you send us arrive.
For some checks we contact public services that answer for themselves, not for us: the European Commission’s VIES service for VAT numbers, official business registers for company details and directors, the EU trusted lists and certificate providers for signatures and seals, the Wikimedia Foundation’s Wikidata query service for a name-only indication of public positions, and Cloudflare’s public DNS service for domain checks. Google and Microsoft are involved only if you choose to sign in with them.
Where your data is stored
We store personal data on servers in the European Union. Vercel, Upstash, OpenAI and Namecheap belong to companies based in the United States. Where one of them can access personal data from outside the European Economic Area, the transfer is covered by the European Commission’s Standard Contractual Clauses or, for companies certified under it, by the EU-US Data Privacy Framework.
How we protect your data
All traffic to our services is encrypted (HTTPS). Accounts, documents and files are encrypted with AES-256-GCM at the application layer, on top of our providers’ own encryption, with keys held on our servers. This is not end-to-end encryption: our systems can decrypt the data in order to provide the service, and only the few people at Dazr who run it can access them.
Your rights
You can ask us for access to your personal data, a copy in a portable format, correction, deletion or restriction, and you can object to processing based on our legitimate interests. Where we rely on your consent, you can withdraw it at any time.
Much of this you can do yourself. Your profile shows and lets you correct your data. Under Privacy & data you can download your data as a file (your profile, sign-in devices, organisations, connected apps and the list of your files) and delete your account. Deleting your account at once removes your profile, sign-in methods, sessions, files, the documents you sent with Dazr Sign and your connections to other apps. A Dazr Compliance workspace is separate and has its own settings.
Write to privacy@dazr.eu for anything you cannot do yourself. We reply within 30 days.
You can also complain to a data protection authority: in Italy the Garante per la protezione dei dati personali (garanteprivacy.it), or the authority where you live or work.
Changes to this notice
If we change this notice, we update the date at the top. Earlier versions are available on request.
Contact
- Privacy and data requests: privacy@dazr.eu
- Security: security@dazr.eu
- General: hello@dazr.eu
- Post: Dazr, Viale Cesare Poggi 1, 15061 Arquata Scrivia (AL), Italy