Privacy Policy
Last updated: 24 October 2026
What changed since our 1 October 2026 version:
- Product analytics: we now use PostHog (its EU Cloud) to see how the site is used and which errors people hit. Before you answer our analytics question, and if you reject, it counts page views, clicks and errors without cookies and makes no screen recording; if you accept, it keeps a random analytics ID, may record some visits with everything you type, all text and all images hidden, and records where on a page people click and move the pointer (heatmaps), clicks and swipes that do nothing, and, in a recording, the timing of the site's requests and its error messages, cleaned. You can change your answer on our cookie page.
- Who handles your data: we name the provider we use without a data processing agreement (Vercel), new processors (Hetzner, and Google for sign-in and our support mailbox) and the public registers we look things up in; Stripe uses some payment data as an independent controller, and so does Google Ads for the ad click id, not on our behalf; photos and screenshots you upload go to our AI provider, which reads any text in them; transfers outside the EU also rest on the EU–US Data Privacy Framework, and with Vercel on no clauses at all.
- What we keep: an IBAN is masked in pasted text too, but older reports can still hold one in full, and anything else in the text you paste is saved as part of it; the device ID is not anonymous: it singles out your browser; an owner check no longer holds an internal operator note and keeps the result we sent you, while any explanation our operator writes with it is emailed to you and not kept in our database, and by our own rule never names the registered owner; error reports can hold personal data, which we do not yet remove automatically.
- New topics: gifts, referral, share and partner codes, reading text in listing photos with Google Cloud Vision, the queue our emails wait in before they are sent, the ad click id, and that a person reviews a verdict you tell us is wrong.
- Keeping times: for withdrawal requests, contact-form messages, notices of changes to our Terms, error reports, backups, the reminder opt-out, unattached share codes and waitlist entries, for payment records (now deleted after the bookkeeping period) and the credit ledger (a deleted account's rows are now deleted after the same period), and for a staff action log, which is kept for 1 year and is not erased when you delete your account; an owner check whose late-result refund is still owed is kept, without its address and name, until 14 days after we have recorded that refund as paid (at most 5 years, see below).
- Deleting your account keeps some records, pseudonymised, does not reach the copies held outside our database (such as Stripe's payment records and our support mailbox), can leave an invite-programme anti-abuse note, and leaves for 30 days a scrambled code made from your email address, so that a late payment for an earlier purchase, or a sign-up link sent before the deletion, cannot re-create the account.
- The data download covers your account data, and the cookie list moved to our cookie page.
- Invites: the friend now gets 30% off their first purchase instead of a free owner check, and a referral no longer earns anyone a credit; the invite code is read at checkout to decide that discount, and the anti-abuse note now also stops the discount being given twice; the person who shared the link gets 30% off one of their own payments (their next Move-In Check or new Search Pass bought while logged in, or a coming renewal of their Search Pass) for each friend whose purchase counts, which we keep until 30 days after it is used or taken back (longer only while a discount taken back is still on their Search Pass, until we have removed it there).
- Owner checks and our emails: an owner check kept because its late-result refund is still owed is deleted 5 years after we recorded its result as delivered, even if that refund is never recorded as paid; and a refund confirmation already under way when you delete your account may still reach you once.
This policy explains what Dormetrics collects, why, and your rights. We are built on data minimisation: we collect as little as possible, we never build a database of property owners, and we never sell your data.
Who we are (data controller)
The controller is DoArt, a sole proprietorship (eenmanszaak) registered in the Netherlands under KVK 93987641, Helmond, Netherlands. Dormetrics (www.dormetrics.com) is a trade name of DoArt. For any privacy question or request, email hi@dormetrics.com.
What we collect and why
The listing you check — the pasted text, an optional listing URL, photos you add, and any hints (price, city, size, IBAN, contact name) — is processed to produce your risk verdict. Uploaded photos are never stored: they are checked within your request and discarded. Email — your account identifier (captured by Stripe at checkout, when you request a magic link, when you sign up with a password, or from Google when you use Sign in with Google). Owner-check credits, purchases & a credit ledger — to run your account and meet accounting obligations. Your saved checks — two records per check. The first is a non-identifying one (a listing reference, the graded band, and whether it was a free or paid check; the listing reference is the site and page of the listing link you gave, or of a rental listing link you typed into the text, and only the site when the page part looks like an email address, a phone number or a profile page). The second is the report itself, so you can re-open it later: what you gave us (your pasted text, the link, the price/city/size you typed, the contact name, and what your photos were classified as) alongside what came back. An IBAN is stored masked, whether you type it into the IBAN field or it appears in the text you paste, in the contact name or in a finding we write about it — the first four and last four characters only, enough for you to recognise it. We mask every IBAN we recognise there, in the forms banks and websites print them; an IBAN typed into the listing link, the city, or an owner check's address or owner name is kept as you typed it. Reports saved before we started masking pasted text and the contact name can still hold an IBAN from them in full until the report is deleted, at the latest 180 days after the check. The contact name you type in its own field names someone else, so it is removed from the saved report 30 days after the check, and every operator-check line that could name a person (such as the business-register lines) is replaced by a fixed sentence. Anything else inside the text you paste, such as a phone number or a name, is saved as part of that text. Photos themselves are still never stored. We keep your newest 20 reports; older ones drop off automatically, and you can remove any of them from your history yourself at any time. A random, signed device ID (it holds no name or email, but it does single out your browser) — to count free checks and limit abuse. Session data (a session ID and your browser's user-agent) — to keep you logged in and let you log out everywhere. Your IP address — used transiently for rate-limiting and bot protection, not stored in your account. If you use our browser extension: a random extension install ID, sent when you activate the extension and with each check, and stored only as a keyed hash in rate-limit counters for at most a day; the extension's activation token holds only that ID and when it was issued and expires. If you choose password login we store a salted, one-way hash of your password — never the password itself; magic-link and Google sign-in accounts have no password at all. With Sign in with Google we receive only your verified email and account identifier — never your Google password or contacts. Your language preference — we store a language setting (English or Dutch) on your account, taken from the page you signed up or bought on. It currently changes nothing: every email is sent in English. Referral data — if someone buys through your invite link (or you buy through someone else's), we record the referrer's and the referred buyer's account emails so each friend is counted once and our limits on how many friends one inviter can count, and how fast, hold (and, for invites from before our current programme, so the purchase-gated reward was granted exactly once, capped). A referral no longer earns anyone a credit. When a friend's purchase counts for your invites, we record one 30%-off discount for one of your own payments (your next Move-In Check or new Search Pass bought while logged in, or a coming renewal of your Search Pass): its state, the dates it was earned, used or taken back, the order number of the friend's purchase that earned it (not who the friend is), and the references of the checkout or payment of yours that held or used it; once it is put on your Search Pass renewal, the Stripe references of your subscription and of that discount on it, kept with the record unless it goes back to waiting for a payment; and, if it was taken back, the Stripe reference of the refund of the friend's purchase that took it back. We keep these so it is applied once, taken back if that purchase is fully refunded (or withdrawn and we take back what it earned), and normally given back if that refund fails. Your data download shows its state, its dates and the payment of yours that used it, not the other references. These records are kept as part of your account and credit ledger and are removed when the account is deleted, with three exceptions: the payment records we must retain by law, a small anti-abuse note, and, if your purchase earned the person who invited you a discount, their discount record, which keeps your purchase's order number (not your email), and, if your refund took it back, that refund's Stripe reference, until they use it or it is taken back, then 30 days (longer only while a discount taken back is still on their Search Pass, until we have removed it there). If you had bought through an invite (a purchase through a code no account had claimed yet leaves no note, unless it earned you a credit under our earlier invite programme), or a friend's purchase had counted for your invites (or was held for review in the 24 hours before), we keep a scrambled code made from your email address (we cannot read the address back from it), a note that you had already used an invite, a count of the friends whose purchases counted for your invites and when the last one counted, so the same email cannot get the invited-friend discount again, or restart those limits, after deleting the account and re-joining. If you deleted an account that had invited friends, we keep the same kind of scrambled code, and only the note that they used an invite, for each of those friends, because deleting your account also removes their only record. We do this for our legitimate interest in preventing abuse of the invite programme. We delete this note 24 months after the account is deleted; a note kept for a friend of a deleted account is deleted 24 months after the deletion of the account that invited them (or after their own deletion, if later). You can object by emailing hi@dormetrics.com: we will delete it unless we have a compelling reason to keep it, and we will tell you which. When we uphold your objection, we keep only the scrambled code, the date of your objection (even if no note was held yet) and your objection email, while the invite programme runs: the code and date so the note is not made again, the email so we can apply the objection again if the code ever has to be remade. A reward credit granted under our earlier invite programme stays in the credit ledger, which we keep as “How long we keep your data” below describes (after an account is deleted, its rows go once the bookkeeping period has run). If you go to checkout, the referral code (from the invite link you opened) is passed to our payment provider, Stripe, with that order, so the referral can be recorded when you pay. Whether the invited-friend discount applies is decided by our server, from the code and your account, before you pay, and Stripe receives only the discount itself, not who invited you. If you are not logged in, checkout tells you once how to get the discount; to remember that for 30 minutes we keep a scrambled code made from your browser's device ID (we cannot read the device ID back from it), and pressing buy again then pays the full price. After you pay for a purchase of your own that carried the code (not a gift), we usually remove the code from the browser you paid from when it comes back to our site from the payment, if it still holds that code. Share codes — when you share a check while logged in, the link carries your invite code. If you are not logged in, a shared link carries no invite code unless you choose “Add my invite code”: we then create a code and store it with a scrambled code made from your browser's device ID (we cannot read the device ID back from it), never your name or email; nothing is created unless you choose it. The first time someone logs in or creates an account on that browser, the code is attached to that account and the scrambled device code is removed. A code that has not been attached to an account is deleted when you delete your account, if that browser ran one of the checks we still keep for your account (one you removed from your history included), and otherwise 12 months and 30 days after it was created: 12 months is the longest your browser can still hand it out, and 30 days is how long an invite link someone opened keeps it. Partner codes — some organisations, such as student associations, share an invite code we issued to them for their own account. It works like a personal invite code: if you buy through it, we record that your first purchase came through that code, and, if you are logged in, your first purchase can get the invited friend's 30% off. Nothing we send the partner names you, and neither does a copy of the partner's own data: like anyone who invites people, they can ask us for that copy, and it lists the purchases made through their codes without the buyer's identity. In the same way, a copy of your own data lists the invite you bought through without the inviter's email address. Ad click id — only if you arrive from one of our ads and answer yes to the short question shown to those visitors, and only while we have ad-click measurement switched on, we keep Google's click id for that ad click (it identifies one ad click). If you go to checkout it is also passed to Stripe with that order. If you complete a one-off purchase we keep it on our purchase record for 90 days and then clear it; a Search Pass payment never adds it to our purchase record. If you are signed in when you answer no, we also clear it from your purchase records at once. The copy held in our Stripe account, on the order or the subscription, is not cleared by us. We use it for one thing: telling Google Ads which ad click led to a sale, by an export we run ourselves that contains the click id, the time, amount and currency of the sale and nothing else (no email, name, address or listing). With measurement off, no click id is collected, passed to Stripe or exported; ids stored earlier are still cleared at 90 days. The cookie behind it is described on our cookie page. Gifts — if you buy a check as a gift, the purchase is kept on your account like any other, and we email you once to confirm it (the email never contains the gift code). We do not ask for the recipient's name or email. We do not store the gift code itself: it is generated from a secret key, so we can show it to you again, and we keep only a keyed fingerprint to check it. You can see whether and when a gift was redeemed, but not by whom; the person who redeems it gets the credit in their own account and is not shown who bought it. If your payment is refunded or disputed, the gift is cancelled or put on hold as §4 of our Terms explains, and a credit that has not been used is taken back from whichever account holds it. Legacy waitlist entries — Dormetrics is now open to everyone; entries from the pre-launch waitlist are deleted automatically 12 months after sign-up.
Reports of illegal content — if you report something under §19 of our Terms, we use your name, your email address and your report (which may name someone else, such as a landlord) to decide on it and tell you our decision; if we remove or restrict something someone gave us, we tell them why. We do this because the EU Digital Services Act requires it (legal obligation), and we act only on the link you report.
The owner check — how we minimise owner data
When you buy an owner check, you give us the property address and the name the “landlord” gave you. We run a forward, address→owner lookup against the public Dutch Land Registry (Kadaster) and return only a match / no‑match / inconclusive result against the name you supplied. We do not splash the owner's full identity into the app, and we never offer a “type a name → see their properties” reverse search. Your owner-check request (the property address and the name the landlord gave you) is kept only to deliver and support that check: it sits in our fulfilment queue and is deleted automatically no later than 30 days after your result is delivered or refunded (if a late-result refund we owe you is not yet recorded as paid, or was recorded as paid less than 14 days before, only the address, the name and the result go then; see “How long we keep your data”). If we asked you for missing details and are still waiting, the address and the name are removed 30 days after we asked (we keep only a one-way keyed fingerprint of them, so buying the same check again is not charged twice); the request stays open, so you can send them again to continue, or ask us to return your credit. The result we emailed you is kept on that same request and deleted with it. Any explanation our operator writes with the result is emailed to you and not kept in our database (our email provider keeps its own copy of the email, see “Who we share data with”). Our rule is that it never names the registered owner or anyone else in the register: at most it says what kind of owner it is, such as a company or a public body. Nothing is ever added to any owner profile, database, or list. There is no owner database and no “worst-landlord” list. If the owner check was run on a saved report, the address and the name you gave us are also removed from that report by our daily clean-up once the report is 30 days old; the rest of the report (your own listing text and what came back) follows the saved-check rules below, alongside a non‑identifying record of your check: a listing reference, the graded band, and the kind of check.
If you are a property owner: we may, at a user's request, check a name against the public Kadaster record for a single address to help that user avoid rental fraud. We obtain that record from the Land Registry (not from you), use it only for that one check, and keep no lasting record of you — no profile, no list. The request itself (the address and the name the user was given), together with the result, is deleted no later than 30 days after the check is delivered or refunded; if the request is waiting on the user for missing details, the address and the name are removed 30 days after the user was asked. You have the right to object to this processing under Article 21 GDPR; email hi@dormetrics.com. (We rely on Article 14(5)(b) GDPR — disproportionate effort — and give this public notice instead of writing to each owner. We hold no contact details for you, and we deliberately keep no record of who owns what; to notify you individually we would have to build and retain exactly the owner records we refuse to keep, which would mean processing more of your data, not less. Set against that, what actually happened is that one person was told whether one name matches one entry in a public register — an answer they could lawfully have obtained themselves from the Land Registry for a few euros. Our full reasoning is written up in our Article 14(5)(b) assessment, available on request.)
Legal bases (GDPR)
We rely on our (and your) legitimate interests to run the address→owner check you request to protect yourself from rental fraud. Legitimate interests can include commercial interests, as the EU Court of Justice has confirmed (case C‑621/22). We process data to perform our contract with you (account, payments, saved checks); to meet a legal obligation (keeping tax and accounting records under Dutch law, and handling reports of illegal content under the EU Digital Services Act); and on your consent where we ask for it (e.g. the legacy launch waitlist, and PostHog’s analytics ID and screen recordings, heatmaps and records of clicks and swipes that do nothing). You can object to, or withdraw consent for, processing at any time.
Automated processing & AI
The free verdict is produced automatically, partly by an AI model: it reads the listing text for scam-script patterns, and other checks score price, image and IBAN signals. It grades the risk of a listing, not the character of any person. Some findings mention a name or business that appears in the listing (for example, whether it is in the Dutch business register), but the verdict is never a judgement about that person. It has no legal effect on you or on anyone named in the listing, and the decision whether to rent is always the renter's own. If you think a verdict about a listing that concerns you is wrong, email hi@dormetrics.com and a person will review it. You can also ask us about the logic involved.
AI & image processing
To grade a listing we send its text to a third-party AI / large-language-model provider for contract- and script-pattern analysis. Photos and screenshots you upload go to that provider too, which sorts them and reads any text in them (an ID document it sees only to recognise it, and transcribes nothing from it; please do not upload one). Listing images go to a reverse-image / web-detection provider to spot photos stolen from elsewhere; in the same request it also reads any text printed in those photos, such as a watermark, and we keep from that text only the web addresses it names, for that check, never the text itself. Under those providers' commercial / API terms, your inputs are not used to train their models. These calls return signals to us; they are not a stored profile of you.
Messages with the landlord. You can paste a conversation, import a WhatsApp “Export chat” file (read in your browser: only the newest messages are sent, as text, never the file or its photos) or upload screenshots of a chat. We use them for that one check and do not store them with your report, your history, our cache or our logs. A check of a chat alone still saves its result (the verdict and its findings, with a note that a chat was checked, never the chat's text) for the same 180 days as any saved report. Before any of that text goes to our AI provider we replace the personal details of the people in it that we recognise: phone numbers, email addresses, valid BSNs and bank account numbers (of an IBAN only the country and the first and last characters stay), and, in a conversation, the name in front of each message, which becomes a label such as “Renter” or “Person 1” (and, where we can tell, where that name appears in the messages themselves). Our own automatic checks read the text unchanged, on our server and only during your request, for example to see which country a phone number or an IBAN is from. A screenshot itself still goes to the AI provider, which has to see it to read it; we ask it to write the senders only as “Me” and “Them”. Identity documents: if an upload looks like a passport, ID card, driving licence or residence permit, the AI provider sees it once to sort it, but it is told not to write out anything from it, we drop anything it writes anyway, we do not send it to the reverse-image provider or keep it, and we ask you to leave it out.
Who we share data with (processors)
We use the service providers below to run Dormetrics. Each processes data on our behalf under a data processing agreement, except one:
- Vercel, our hosting provider: we are on its free plan, and we have not confirmed that its data processing agreement covers that plan, so we treat it as not covered.
Hetzner (Germany), which hosts the server for our emails to organisations (see “If we emailed your organisation” below), processes data under a data processing agreement we concluded in our account on 3 October 2026.
Stripe also uses some payment data as an independent controller, for fraud prevention and its own legal duties; its own privacy policy covers that use.
Google Ads is not one of our processors. Only while ad-click measurement is on, it receives the click id, sale time, amount and currency described under “Ad click id” above, and it uses them as an independent controller, under its own privacy policy, not on our behalf.
Our other processors, and what each does:
- Anthropic (United States) — AI analysis of listing text (contract & script red flags), and sorting and reading the photos and screenshots you upload.
- Google Cloud Vision (United States) — reverse-image / web detection and reading text (such as a watermark) in listing photos.
- Google (United States) — “Continue with Google” sign-in (your email address), and our hi@dormetrics.com mailbox, which receives what you send us through the contact form or by email and our internal owner-check job notices.
- Zyte (Ireland) — opens the listing page for us when you paste a link to a site that blocks us. It receives the listing address you pasted and returns the page; it does not receive your email, your account, or your IP address, and the page is read and discarded, never stored.
- Supabase — database & hosting for your account, credit ledger, and saved-check records.
- Upstash — caching, rate-limiting, short-lived tokens, and your choice to stop the unused-credit reminder and your “don't ask again” choice for removing checks (each stored as a one-way keyed code of your email address; a “don't ask again” choice made before we changed how it is stored stays under the address itself until you change it or it expires, one year after you made it; both are erased when you delete your account).
- Vercel — application hosting and serverless functions (no data processing agreement on our plan; see above).
- Stripe (PCI-DSS) — payment processing, billing details, your email. At checkout we also pass it the referral code from the invite link you opened, on a checkout that uses a discount you earned through your invites that discount's reference (a random id, not who your friend is), and, if you opted in to ad-click measurement, Google's ad click id, as metadata on that order.
- Resend — magic-link and transactional email delivery. It keeps the emails it sends for 30 days.
- Cloudflare — bot protection (Turnstile) and abuse prevention, and storage of our encrypted database backups (Cloudflare only ever receives an already-encrypted file and holds no key to it).
- GitHub (United States) — runs the nightly job that produces those backups. The backup is encrypted on GitHub's machine, so the job briefly handles the unencrypted database copy; nothing is kept after it finishes.
- Sentry (EU data region) — error & crash monitoring. Error reports can contain your IP address, your browser and the page you were on, plus technical details of what failed, which can include your email address or something you typed. We do not yet remove personal data from them automatically.
- Vercel Web Analytics — privacy-friendly, cookieless, aggregated page analytics (no cookies, no cross-site tracking, no advertising; not loaded on shared-check, report or sign-in pages).
- Vercel Speed Insights — anonymous, aggregated performance measurements of how fast pages load (no cookies, no cross-site tracking; not loaded on shared-check, report or sign-in pages).
- PostHog (its EU Cloud) — product analytics and error tracking, and, only if you accept, masked screen recordings of some visits, heatmaps and clicks and swipes that do nothing. It receives the pages you open (with secret parts of the address removed), clicks (without the text or link of what you clicked), from our servers a record of each free check (how it ended, the risk band, how long it took, whether it was served from our cache, whether the link could be read or steps were skipped to stay fast, and which of our checks flagged something or could not run, never what you entered or the link), for each request the free check makes to our AI provider the model, the amount of text in tokens, the time it took, why it stopped or how it failed and which step made it, grouped per check by a random ID (never the text sent or received), and records of the answers to our analytics question (accept or reject only; past 20 answers from one connection in an hour, no record is sent, though each answer still applies); these server records are sent whatever you answer, under one shared ID, and we never link them to you. It also receives technical details of errors (with emails, phone numbers, IBANs, BSNs, postcodes, addresses and map coordinates removed where we can recognise them (a name, or a detail written in an unusual way, cannot always be spotted), and, in an error from your browser, everything from the first quotation mark, square or curly bracket, backtick or < of its message on cut off), your browser and device type, and, as part of the connection, your IP address, which our PostHog project is set not to store and which is not used to work out where you are. Before you answer and if you reject, it sets no cookie (apart from a test cookie and a test entry in your browser's storage, both holding nothing, that it deletes at once) and PostHog's servers tell visits apart with a privacy-preserving hash; if you accept, it keeps a random ID in a cookie and your browser's storage. In recordings everything you type, all text and all images are hidden (each piece of text becomes a single *, so not even its length shows; the page's layout and colours do show), and none of the content or headers of what the site sends to or receives from our servers is included: a recording holds only the timing, size, status, method and address (secret parts removed) of each request the page makes, and the page's error and warning messages with secret parts of links and details such as emails, phone numbers, IBANs and BSNs removed (a name or a street name written inside an error message cannot always be spotted). Heatmaps hold the position of each click or pointer move, its kind and the page (secret parts of its address removed); a click or swipe that does nothing is recorded with the kind of element it landed on, never its text or link. It never receives your name, email or account, and it is not loaded on shared-check, report, sign-in or staff pages or the extension activation page. If your browser sends Do Not Track or Global Privacy Control, we treat it as a reject.
Public registers are not our processors. Each is responsible for its own register; we only look things up in it:
- The Dutch Land Registry (Kadaster) — the register an owner check is run against.
- PDOK, the Dutch government's address service — the postcode and house number of the address you give are checked against the official address register (BAG): whether the address exists and, for a listing's address, what the register records about it (its use, its floor area and whether the building is finished). Nothing else is sent with them; a house letter or suffix is only compared on our side.
- SIDN, the register of .nl domain names — when a check includes a .nl web address (the listing's site and the site its link leads to, or a link in text or a chat screenshot you give us), that domain name is looked up to see when it was registered. Nothing else is sent with it.
- KvK, the Dutch business register — when this check is switched on, the name of a letting agent or landlord found in the listing is looked up to see whether it is a registered business.
We do not sell or rent your personal data, and no third-party ad tracker runs on our pages; the ad click id above is the only advertising data that identifies a single ad click, and we set it only if you say yes; which channel or campaign brought a visit feeds daily totals only (see our cookie page).
International transfers
Some processors are based outside the EU/EEA. Where data leaves the EU/EEA, we rely on the European Commission's Standard Contractual Clauses (SCCs) and, where the provider is certified, the EU–US Data Privacy Framework. PostHog, a US company, stores our analytics in its EU region; any access from outside the EU/EEA rests on the SCCs in its data processing agreement. The exception is Vercel, a US company: our app's server functions run in its Frankfurt region, but without its data processing agreement we have no SCCs with Vercel either (see above). A copy of the clauses we do have is available on request.
How long we keep your data
- Owner-check requests — the property address and the name the landlord gave you are kept only to deliver and support your check, and are deleted automatically no later than 30 days after the result is delivered or refunded, together with the result we sent you. Any explanation our operator writes with the result is emailed to you and not kept in our database. If your result reached you more than 48 hours after your request and the refund we owe you for that is not yet recorded as paid, or was recorded as paid less than 14 days before, the address, the name and the result are removed after those 30 days, and the rest of the request (your email address, the request's dates and language, and how it was handled) is kept until 14 days after we have recorded that refund as paid, or at most until 5 years after we recorded the result as delivered; it is then deleted at our next clean-up. While a request waits on you for missing details, the address and the name are removed 30 days after we asked; the request stays open.
- Saved checks — your most recent 20 per account; anonymous device records are purged automatically after ~90 days. The contact name you typed is removed once the report is 30 days old, and every operator-check line that could name a person is replaced by a fixed sentence; a name inside your pasted text stays with that text. The report body (what you gave us and what came back) is removed by our daily clean-up once it is older than 180 days, even if the check itself is still listed, so an old report stops holding your words long before the record of it goes. Each share link you make is a small record of its own (when it was made, when it lapses, and whether you revoked it, never the link itself): it stops working after 90 days or when you revoke it, and goes with its report. Links made before revocable links were introduced are not records of their own: they stop working after 90 days, or when you delete your account, and cannot be revoked one by one.
- Reports you remove from your history — “remove from my history” takes the report out of your view immediately but does not erase it, because we may still have to answer a complaint or a chargeback about a report you were given. It is deleted on the same 180-day clock as any other report. If you want it gone now, delete your account — that erases your account and your reports, removed ones included. In our database we keep only the records we need to keep: your purchases and payments, the credit ledger, our records of your withdrawal (cancellation) requests, the record that you wrote to us (when and about what, not your words) and our answer, the notices we sent you about changes to our Terms and any cancellation you made because of one, a one-year log of what our staff did on your account, and, if you ever bought through an invite or a purchase by a friend you invited ever counted, a small anti-abuse note (a scrambled code made from your email address, which we cannot read back, with a note that you used an invite, a count of the friends whose purchases counted for your invites, including any held for review in the 24 hours before, and when the last one counted: no email, no name), so the same address cannot get the invited-friend discount again or restart the limits on invites, and we delete that note 24 months after your account is deleted; if we upheld your objection to that note, we keep instead only the scrambled code and the date of your objection (even if no note was held yet), while the invite programme runs, so the note is not made again; and, for 30 days after the deletion, a scrambled code made from your email address with the time of the deletion (no email, no name), so that a late payment for an earlier purchase cannot re-create your account. They are pseudonymised: your email address, and the name and words you typed into our forms, are removed; our answer to a message you sent us through our contact form is kept as we wrote it, and the notes our staff wrote on your withdrawal requests and on a cancellation you made because of a Terms change are kept as written; both may name you. Outside our database, our payment provider Stripe keeps its own payment records, our email provider keeps copies of the emails we sent you, error reports and encrypted backups roll off within 30 days, and copies of the emails you sent us stay in our support mailbox until we delete them by hand (email us to ask); an email in which you objected to the anti-abuse note is kept as long as the record of that objection.
- Sessions — about 90 days, or until you log out.
- Magic links — 15 minutes.
- Withdrawal requests — deleted automatically 2 years after the request is closed and you have been told the outcome. If money was refunded, the request is a payment record and is kept with the payment records below instead; it is not deleted on this schedule. If we ever have to refund you by bank transfer because Stripe cannot, we ask you by email for your name and IBAN, use them only to make that transfer, and keep them no longer than the bookkeeping rules require.
- Contact-form messages — deleted automatically 1 year after the last activity once we have answered; complaints and billing messages 2 years after they are closed. A message we have not answered yet is kept until we have. A copy of each message also reaches our support mailbox, which is cleared by hand.
- Reports of illegal content — your report, your name and email, our decision and the reasons we sent are kept for 2 years after we close the report, then deleted.
- Notices of changes to our Terms — the record that we emailed you a change is deleted automatically 2 years after the change takes effect or after we first announced it, whichever is later; if anyone who cancelled because of that change still has an open refund claim then, your record is kept until that claim is closed.
- Emails we owe you — receipts, the confirmation of a refund, notices about your Search Pass and about changes to our Terms, the confirmation of your withdrawal request and our decision on it, your contact-form acknowledgement and our answer, and the result of an owner check or its rejection wait in a sending queue (your email address and what the email needs to say) until they are sent. They are deleted automatically 30 days after sending; one that could not be delivered is deleted 30 days after our operator was alerted to it, and no later than 90 days after it was queued; one for an account deleted before it was sent is deleted unsent (a refund confirmation already under way may still reach you once); and one about an owner check is deleted no later than 30 days after it was queued, sent or not.
- Staff action log — a record of what our staff did on your account (for example a refund issued or a check delivered), naming you by a one-way code, never your email. It is kept for 1 year and is not erased when you delete your account, so a refund or a decision stays provable.
- Error reports (Sentry) — 30 days.
- Product analytics (PostHog) — events and error reports are kept for as long as PostHog keeps them on its free plan, which is at least 1 year (PostHog promises no date on which it deletes them); screen recordings for at most 30 days, after which PostHog deletes them. The analytics cookie in your browser lasts 180 days; it is deleted when you reject or change your answer to reject (at once, or, if PostHog has not loaded on that page yet, as soon as it does), and when your answer has expired. Your answer itself is kept in two small cookies for 180 days: sd_consent (accept or reject) and sd_consent_at (when you answered, so that if you answer in two open tabs the later answer wins); we never use them to recognise you.
- Database backups — 30 days, encrypted.
- Payment records (your purchases and the gifts you bought, withdrawal requests that moved money, and cancellations after a change to our Terms) — kept for the bookkeeping period the law requires (legal obligation): until the end of the seventh calendar year after the year of their last activity (for a gift, from its expiry date, even if it was redeemed or cancelled earlier), then deleted automatically. A purchase is not deleted while an account it added credits to (yours, or for a gift you bought, the recipient's) still exists and has credits, nor until that period has run from the last entry in that account's credit ledger (a credit added, used or taken back, or a refund noted on it), nor while an owner check you asked for is still open. A withdrawal request that is still open or whose outcome we have not told you, and a cancellation we have not answered, are never deleted, and neither is a purchase such a withdrawal request names; an open request that names no purchase keeps every purchase made with the same email address. The credit ledger (each credit added, used or taken back) is not deleted on this schedule while your account exists: it is the record of every change to your credits, and what we can still refund on a purchase is worked out from it. After you delete your account, its rows are pseudonymised, and each row is deleted automatically after the end of the seventh calendar year after the year it was written (a row about a purchase is kept while we keep that purchase, and until the same period has run from the last entry about it).
- Reminder opt-out — if you stop the unused-credit reminder, we keep a one-way keyed code of your email address and the date you stopped it, so the choice holds for every future purchase. It is kept for as long as your account exists and erased when you delete your account. If there is no account behind the address, it is deleted after 1 year.
- Unattached share codes — a code made for a share while you were not logged in, with the scrambled device code it is stored with, is deleted 12 months and 30 days after it was created, or earlier when you delete your account (see above), unless it was attached to an account by then (it then stays with the account, without the device code).
- Invite-programme anti-abuse note — if you had bought through an invite or a friend's purchase had counted for your invites, deleting your account leaves a scrambled code made from your email address (we cannot read the address back from it), a note that you had already used an invite, a count of the friends whose purchases counted for your invites and when the last one counted, so the same address cannot get the invited-friend discount twice or restart the limits on invites. If you invited friends and delete your account, the same kind of code and note is kept for each of them. We delete this note 24 months after the account is deleted; a note kept for a friend of a deleted account is deleted 24 months after the deletion of the account that invited them (or after their own deletion, if later). You can ask us to delete it by emailing us; we will, unless we have a compelling reason to keep it. When we uphold your objection, we keep only the scrambled code, the date of your objection (even if no note was held yet) and your objection email, while the invite programme runs: the code and date so the note is not made again, the email so we can apply the objection again if the code ever has to be remade.
- Your earned invite discounts — each 30%-off discount a friend's purchase earned you is kept until it is used or taken back, then deleted 30 days after that, with one exception: a discount taken back while it was on your Search Pass is kept for those 30 days or until we have removed it from your subscription, whichever is later (our daily check removes it, normally within a day; we are alerted if it is still there after the 30 days); all of them are deleted when you delete your account.
- Deleted-account marker — when you delete your account, we keep a one-way keyed code of your email address (never the address) and the time of the deletion for 30 days, so a payment for a purchase made before the deletion that reaches us late (some payment methods take up to about three weeks to settle) cannot re-create the account: we refuse it and refund it by hand. A new purchase after the deletion is not affected. We also check it before we queue a failed-payment, Search Pass ended or Terms-change email to an address with no account, so such an email is not stored or sent to the deleted address (unless it is about a charge or an ending after the deletion). And we check it when a sign-up confirmation link we sent before the deletion is opened, so that link cannot re-create the account. It is stored in our database and deleted by our daily clean-up once it is 30 days old.
- Other caches — expire automatically (seconds to days).
Your rights (GDPR)
You can request access, rectification, erasure, restriction, portability, and object to processing, and withdraw consent at any time. While logged in you can download your account data and permanently delete your account from the account panel (or via /api/account/export and DELETE /api/account). Deletion erases your account, your sessions and your saved checks, and also the checks run while logged out in a browser that ran one of the checks we still keep for your account, one you removed from your history included (on a shared browser that includes another person's logged-out checks); the download includes those checks too. In our database we keep only the records we need to keep: your purchases and payments, the credit ledger, our records of your withdrawal (cancellation) requests, the record that you wrote to us (when and about what, not your words) and our answer, the notices we sent you about changes to our Terms and any cancellation you made because of one, a one-year log of what our staff did on your account, and, if you ever bought through an invite or a purchase by a friend you invited ever counted, a small anti-abuse note (a scrambled code made from your email address, which we cannot read back, with a note that you used an invite, a count of the friends whose purchases counted for your invites, including any held for review in the 24 hours before, and when the last one counted: no email, no name), so the same address cannot get the invited-friend discount again or restart the limits on invites, and we delete that note 24 months after your account is deleted; if we upheld your objection to that note, we keep instead only the scrambled code and the date of your objection (even if no note was held yet), while the invite programme runs, so the note is not made again; and, for 30 days after the deletion, a scrambled code made from your email address with the time of the deletion (no email, no name), so that a late payment for an earlier purchase cannot re-create your account. They are pseudonymised: your email address, and the name and words you typed into our forms, are removed; our answer to a message you sent us through our contact form is kept as we wrote it, and the notes our staff wrote on your withdrawal requests and on a cancellation you made because of a Terms change are kept as written; both may name you. Outside our database, our payment provider Stripe keeps its own payment records, our email provider keeps copies of the emails we sent you, error reports and encrypted backups roll off within 30 days, and copies of the emails you sent us stay in our support mailbox until we delete them by hand (email us to ask); an email in which you objected to the anti-abuse note is kept as long as the record of that objection. To exercise any right, email hi@dormetrics.com. You may also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
Cookies
Every cookie we set, what it does and how long it lasts is listed on our cookie page, together with the few settings we keep in your browser's local storage. That page is the one list, so this policy and the list cannot disagree. Our page analytics (Vercel Web Analytics and Speed Insights) set no cookies; we use them on the basis of our legitimate interest in understanding how the site is used. PostHog's cookieless counting (before you answer, or after you reject) rests on the same legitimate interest, and so do the server records described above, which are sent whatever you answer; its analytics cookie, the screen recordings, the heatmaps and the records of clicks and swipes that do nothing rest only on your consent, which you can give or withdraw on the cookie page with one click.
If we emailed your organisation
This policy covers people who use Dormetrics. We also contact organisations — universities, student bodies, relocation and housing firms — at addresses they publish on their own websites, to offer them the free check for the people they serve. That is a different processing activity with its own source, purpose and retention, so it has its own notice: why you got an email from us. It explains where the address came from and how to stop it permanently — a reply is enough.
Security
We protect data with TLS encryption in transit, HMAC-signed tokens, access controls, and PCI-DSS-compliant payment handling via Stripe. If a data breach poses a risk to you, we will notify the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) within 72 hours and affected users where required.
Children
You must be at least 16 years old to use Dormetrics, and if you are under 18 you need permission from a parent or guardian before you buy anything (§18 of our Terms). We do not knowingly collect data from anyone under 16. If you believe someone under 16 has used the service, contact us and we will delete the data.
Changes
We may update this policy; we will post the new version with a revised date. Material changes take effect when posted.
Contact
DoArt (trading as Dormetrics), KVK 93987641, BTW NL005056384B70, Helmond, Netherlands. Privacy questions: hi@dormetrics.com. Supervisory authority: the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).