Privacy policy

The roles we act in

Who is responsible for personal data here depends on whose instruction the processing happens on. Four cases cover everything this product does:

• Your account, billing, support and our security and operational records (sessions, audit log, rate limits, server logs) - ADMI ENTERPRISES s.r.o. is the controller.
• The content of scans you run as a customer - pages, findings, screenshots of the sites you told us to scan - you are the controller and we process it on your instructions; for business customers the data processing agreement at /legal/dpa governs this.
• Anonymous free scans from our homepage - we are the controller, processing under our legitimate interest in offering and protecting the public scanner.
• Personal data of other people that appears on scanned pages - who answers for it depends on who ordered the scan: the customer where a customer did, and we ourselves for the anonymous scanner. The section for people who appeared in a scan, below, is written for exactly this case.

Data we collect

• Account data: name, email, hashed password or Google account identifier, workspace membership
• Billing data: your plan and subscription state, and payment metadata held by our payment processor. Cards are entered on Stripe's pages and never touch our servers; invoices and receipts are issued and held by Stripe/Link as merchant of record
• Scan data: target URLs, response headers, metadata, findings, scores and screenshots
• Security and operational records: sign-in sessions (IP address and browser), the workspace audit log (who did what, with the actor's e-mail and IP), short-lived rate-limit counters keyed by IP, and server logs kept as process output at our hosting provider
• Error reports: Sentry (EU region) receives an error message and stack trace when something breaks, with browser and operating-system details, the page address without its query string, and preceding page addresses in the same tab. Sign-in and reset tokens are scrubbed; console messages, form contents, clicks and network-request breadcrumbs are not sent. No IP address or account identity is stored with the report. Server errors are also reported. This runs without consent as necessary for operation and security; see /legal/cookies
• Website analytics, only if you allow it on the cookie banner: Google Analytics 4 records which public pages you view and, through Google's enhanced measurement, what you do on them (scrolling to the end, clicks on links to other sites, file downloads, starting and submitting a form without its contents, embedded video plays, a search term carried in the page address) and three steps you start on a public page (that a free scan was started, never the address entered; that you followed a link to sign-up or to checkout, with the plan and billing period the link carries, but not whether you finished), with a pseudonymous browser identifier from the _ga cookies, approximate location and device type derived by Google, and how you arrived. App pages, sign-in, checkout and token links are never measured. The page address is sent without its query string, Google signals and ad personalisation are off, and nothing is collected before you allow it
• Visit counts without cookies: when you open one of our public pages from another site or by typing the address, our server adds one to a daily counter for that page, kept by the referring website's name (without the rest of its address), the campaign tags in the link (utm_source, utm_medium, utm_campaign) and whether the browser is a mobile or a desktop one. Nothing is stored on your device, and no IP address, browser identifier or time of the visit is recorded with the count, so it cannot be linked to you. App pages, sign-in, checkout and token links are not counted, and neither are known bots

Legal bases

Each purpose has its own basis under Art. 6(1) GDPR, and marketing e-mail and website analytics are deliberately the only consents on the list - everything the product needs to function rests on the contract or on law:

• Providing the service - accounts, workspaces, the scans you run: performance of the contract (Art. 6(1)(b))
• Billing and plan state: performance of the contract, and afterwards compliance with legal obligations, since tax and accounting law require payment records to be kept (Art. 6(1)(c))
• Security, abuse prevention and the establishment or defence of legal claims - sessions, audit log, rate limits, acceptance records, error reports: our legitimate interest (Art. 6(1)(f))
• Checking that each workspace, e-mail address and IP address gets one free trial: our legitimate interest in offering the trial once and not repeatedly (Art. 6(1)(f))
• The anonymous free scan, including the recorded authorisation confirmation: our legitimate interest in offering and protecting the public scanner (Art. 6(1)(f))
• Marketing e-mail: consent only (Art. 6(1)(a)), withdrawable from any message - we send none without it
• Website analytics: consent only (Art. 6(1)(a), and §89(3) of Act No. 127/2005 Sb. for the cookies), withdrawable at any time under Cookie settings in the footer - nothing is measured without it
• Visit counts without cookies: our legitimate interest in knowing how people find the website (Art. 6(1)(f)); the request is used only to add to an anonymous counter and nothing is read from or stored on your device

Whether you have to provide data, and automated decisions

Account data and payment details are a contractual requirement in the plain sense: without an e-mail address we cannot create an account, and without payment we cannot provide a paid plan. Nothing else - not your name on the account, not a Google login - is required, and the free scan needs no personal data beyond the IP address any web request carries.

Scans are scored automatically - that is the product - but no decision with legal or similarly significant effect for you is made by automated means, so Art. 22 GDPR is not engaged.

How long we keep things

• Scan history: your plan's window, from 30 days on the free plan to 24 months on Agency; on Enterprise, scans are kept until the workspace is deleted. Deleting a project or workspace deletes its scans at once, screenshots and reports included
• The newest scan of each of your own projects is kept even when it is older than your plan's window, so your dashboard and comparison baseline never go blank - it is deleted when the project or the workspace is. Competitors you benchmark against get no such exception: their scans go when they fall outside the window, newest included
• Anonymous free scans: seven days, result link and scan together. The recorded authorisation confirmation is kept for twelve months
• Report unlocks (withdrawn): the one-off report unlock is no longer sold. Where one was bought before it was withdrawn, the record of it - the buyer's e-mail address, the payment identifiers and which report it unlocked - is kept while that entitlement stands, as proof of what was sold, and it pins that scan and its link past the seven days above until it is refunded
• Account data: until you delete your account, which you can do yourself in Settings, under the You tab. Deleting a workspace ends your membership of it and deletes that workspace's data, but not your account
• Workspace deletion evidence: a record with the workspace name and the deleting user's e-mail address, kept twelve months after the deletion, then removed. For those twelve months it also records whether the workspace had a subscription and how many scans it had used that month, and we use it, on the basis of our legitimate interest, to stop a deleted workspace from being replaced with a fresh free trial (by a new workspace, or by a new account with the same address) or with a refilled free scan allowance (by a new workspace of the same account)
• Account deletion evidence: a one-way hash of the deleted account's e-mail address - not the address itself - kept twelve months, then removed
• Sign-in sessions: removed seven days after they expire, together with the IP address and browser details they carry
• The workspace audit log: kept for the life of the workspace and deleted with it. The IP address recorded with each entry is removed after twelve months; the entry itself stays
• Record of accepting the terms of service: the version you accepted, when, your e-mail address and the IP address you accepted from. It is kept separately from any workspace and is not deleted when you delete your account, because it is the evidence of the contract. An acceptance recorded before 25 September 2026 is kept in your workspace's audit log until you next use the app, when it is copied into this separate record; until then it is deleted with the workspace. We keep it for as long as your account exists and for at least 3 years from the day you accepted, and delete it once the account has been deleted and those 3 years have passed. The IP address is removed from it after twelve months, as from every audit log entry. Basis: our legitimate interest (Art. 6(1)(f))
• Free-trial eligibility: when you open a checkout that includes the free trial, we record a keyed one-way hash of your e-mail address and a keyed one-way hash of the IP address it was opened from (for IPv6, the whole /64 block the address belongs to), together with the plan and the workspace. We use this record only to check that each workspace, e-mail address and IP address gets one trial, on the basis of our legitimate interest (Art. 6(1)(f)). A checkout you abandon stops counting after 24 hours. Because it exists to stop a trial being claimed again after a deletion, the record is not deleted when you delete the workspace or your account; it is kept for 24 months from when it was made, then removed
• Backups: encrypted nightly copies with a 8-day window, so a deletion has fully left the backups within 8 days
• Website analytics: Google Analytics keeps the event data for 14 months, then deletes it; the _ga cookies expire after two years, and withdrawing consent deletes them at once
• Visit counts without cookies: anonymous daily totals with nothing that identifies a visitor, kept for as long as the website runs
• Invoices, receipts and payment records: held by Stripe/Link as merchant of record under their own retention duties; the payment-processor customer record is not deleted when a workspace is

The public free scan

A scan started from our homepage produces a result page at a link containing an unguessable token. Anyone who has the link can open it while it lives; it shows the overall score, the page count, one finding, the homepage's Core Web Vitals and a screenshot of the homepage. The link and the scan are both deleted after seven days. The one exception is historical: where a report was bought outright before that was withdrawn, the scan and the link stay while that entitlement stands, and the seven-day window applies again from a refund.

For the person who started it we store the authorisation confirmation described in the terms (with IP address and time) for twelve months, and a salted hash of the requesting IP - not the address itself - with the scan. A repeated request for the same domain within 24 hours is served the same result rather than crawling the site again.

If your personal data appeared in a scan

We scan publicly reachable web pages on our customers' instructions and for anonymous visitors. If your name, photo, contact details or anything else about you is visible on a scanned page, it can appear in the scan's findings and screenshots. The source is always the public web page itself - scanning collects nothing about you from anywhere else, and the full HTML of pages is discarded after analysis; what persists is findings, metadata and screenshots.

Where a customer ordered the scan, that customer is the controller of the scan's content and our processing rests on our contract with them; the retention is their plan's window, above. Where the scan was anonymous, we are the controller under our legitimate interest, and the scan lives seven days, or until the refund of a report bought before that was withdrawn. Either way, the route below erases it on request.

If you operate the site, you can block all future scanning of your domain and erase what earlier scans stored at /opt-out - verified with one DNS record, no account needed. If you do not, write to [email protected] and we will handle your objection or erasure request directly where we are the controller, and pass it to the responsible customer without delay where we are not.

Sharing and sub-processors

We do not sell personal data. The vendors that process personal data for us - hosting, database, object storage, e-mail, error monitoring and backup automation - are each named, with locations and safeguards, on the sub-processor list at /legal/subprocessors, and each is bound by a data processing agreement.

Two parties process personal data as independent controllers rather than for us: Stripe (with Link as merchant of record) for payments, invoicing and refunds, and Google where you choose to sign in with a Google account. Their own privacy notices apply to that processing.

If you allow analytics, Google Ireland Limited processes it for us as a processor under Google's data processing terms, which we have accepted; Google may transfer it to the United States under the EU-US Data Privacy Framework. It concerns visitors to our public pages, not the data in your account, so /legal/subprocessors lists it only as the processor for our own website analytics, not as a sub-processor of customer data.

We disclose personal data to public authorities only on a lawful, binding request, and we tell the affected customer unless the law forbids it. If our business is transferred or reorganised, personal data may pass to the successor under this same policy - we would tell you before that happens.

How our crawler behaves - and how to report a security issue - is described at /security, and the small set of cookies and browser storage this site uses is listed at /legal/cookies.

Where data is processed, and international transfers

Our application, database, scan screenshots and reports, backups and e-mail sending run in the EU. Several of our vendors are US-incorporated companies, so transfers of personal data to the United States can occur; where they do, they rely on the EU–US Data Privacy Framework for vendors certified under it and on Standard Contractual Clauses otherwise. The per-vendor detail is on /legal/subprocessors.

Your rights

Requests are free of charge and answered without undue delay and within one month; for complex or numerous requests that can extend by two further months, and we tell you within the first month if it does, and why. The practical how-to - verification, the site-owner flow, what survives erasure - is at /legal/gdpr.

You can complain to the Czech supervisory authority - Úřad pro ochranu osobních údajů (ÚOOÚ), Pplk. Sochora 27, 170 00 Praha 7, uoou.gov.cz - or to the supervisory authority of the country where you live or work.

• Access - a copy of the personal data we hold about you, with the purposes, categories, recipients, retention and source
• Rectification - correction of inaccurate account or billing data
• Erasure - delete your account yourself in Settings under the You tab, or ask us; the GDPR page lists the little that survives an erasure, and for how long
• Portability - the data you provided to us, in a machine-readable format
• Restriction of and objection to processing - objection to marketing is absolute
• Withdrawal of consent at any time, without affecting what happened before

Contact

The controller is ADMI ENTERPRISES s.r.o., IČO 29581010, Nové sady 988/2, Staré Brno, 602 00 Brno. We have not designated a data protection officer; data-protection requests go to [email protected], or by post to the registered seat.