Privacy policy
Last updated: 2026-10-14.
Controller: Pandus, sole proprietor (ФОП), Ukraine, tax number 3699800070, Ukraine, Krolevets, Zelinskogo, 107. Contact for privacy questions: vadym.queensoft@gmail.com.
This policy describes what Pandus (the "Service": the website, the customer area and the reports) does with personal data. It is written from what the Service actually does, not from a template.
1. What we collect and why
| Data | Where it comes from | Purpose | Legal basis (GDPR) |
|---|---|---|---|
| Account: name, e-mail, password hash, language, theme; the ID of the account you sign in with if you use a “Continue with …” button (Google, Microsoft, GitHub, GitLab, LinkedIn, Facebook or Apple); passkey public keys and the two-factor secret if you turn them on | you | providing the Service, security of sign-in | contract (Art. 6(1)(b)) |
| Acceptance of the terms and this policy (date and version), confirmation that you are 18 or older and use the Service for business | you | proving the contract and your eligibility | contract, legal obligation (Art. 6(1)(b), (c)) |
| Teams: team name and type, members and their roles, invitations (the invited person's e-mail), brand settings and logo | you and your team | team work, reports under your brand | contract |
| Sites you add and the results of checking their public pages: URLs, screenshots, the HTML of elements with problems, reports and PDF files, links to reports for your clients and how often they were opened | you; public pages of your sites | the checks and reports you ordered | contract |
| Billing: company name and address, VAT number, invoices, orders, the Paddle subscription ID | you; Paddle | payments, accounting, tax duties | contract, legal obligation (Art. 6(1)(c)) |
| API tokens and webhook settings with their delivery log | you | integrations you set up | contract |
| Support requests: your messages and our replies | you | answering you | contract, legitimate interest (Art. 6(1)(f)) |
| Free one-page check: the address checked, your e-mail if you want the result by e-mail, a hashed IP address for rate limits | you | showing and sending the result, preventing abuse | your request (Art. 6(1)(b)), legitimate interest |
| Contact and order forms: name, e-mail, company, message | you | answering you | your request (Art. 6(1)(b)) |
| Tips about accessibility by e-mail — only if you ticked the box; we keep the text you agreed to and the time | you | sending the tips | consent (Art. 6(1)(a)), withdraw at any time |
| Business contacts of companies that may need the Service (company name, website, public business contacts) | public sources: company websites and registers | offering the Service to businesses, only where the law of the company's country allows | legitimate interest (Art. 6(1)(f)); objection honoured at once and for good |
| Security logs: sign-ins (shortened IP address, browser), outgoing e-mail (recipient and subject only, never the text), actions in the admin | the Service | security, abuse prevention, accountability | legitimate interest |
| Error reports without personal data (Sentry, EU region) | the Service | fixing errors | legitimate interest |
| Your cookie choice: a random browser ID, what you allowed, when, the shortened IP address and the version of the banner and of the cookie policy | you | proving consent (Art. 7(1)) | legal obligation |
| Statistics (Google Analytics 4) — with your consent in the EEA, UK and Switzerland; elsewhere until you switch it off (section 3): pages you open, the events listed in section 3, a random browser ID, a pseudonymous user ID (never your e-mail), approximate location derived from the IP address, device and browser | your browser | understanding how the Service is used | consent (Art. 6(1)(a); Art. 5(3) ePrivacy Directive) |
| Session recordings and heatmaps (Microsoft Clarity) — with your consent in the EEA, UK and Switzerland; elsewhere until you switch it off (section 3): mouse movements, clicks, scrolling and the page layout, recorded to find places that are hard to use; text in the customer area, in sign-in forms and in form fields is hidden; a pseudonymous user ID | your browser | improving usability | consent |
We check only publicly available pages that you ask us to check. We do not identify the visitors of those pages.
Some data we process on behalf of our customers, who are its controllers: personal data that appears on the pages they ask us to check (in screenshots and code fragments), and barrier reports that visitors send through the form a customer placed on their own site (the message, the page address and, if the visitor gives them, a name and an e-mail). This is governed by our Data processing agreement; questions about such data are best sent to the site owner.
We do not use automated decision-making or profiling with legal or similarly significant effects. We do not sell personal data and do not use it for advertising: advertising features of Google Analytics and Clarity are off.
2. Who receives the data
- Hosting provider in the European Union — servers, database and backups, as our processor.
- Paddle.com Market Ltd (United Kingdom) — card payments as Merchant of Record. For card payments Paddle is a separate controller under its own privacy notice.
- Google Ireland Ltd — sign-in with Google (if you use it); Google Analytics 4 (see section 3).
- Microsoft Ireland Operations Ltd — Microsoft Clarity (see section 3).
- Cloudflare, Inc. — every request to the website passes through Cloudflare's network (protection against attacks, delivery, the country of the connection); Turnstile, a check that a form is sent by a person and not a bot.
- Functional Software, Inc. (Sentry) — error tracking in the EU region, without personal data.
- E-mail — sent through our own mail server.
- Sign-in providers — only the one whose “Continue with …” button you use; it confirms who you are and is a separate controller under its own privacy notice.
- Telegram — only if you connect our Telegram bot: alerts about your sites go to the chat you chose. Telegram is a separate controller under its own privacy notice.
- Accountant and authorities — invoices and payment records when the law requires.
Country detection uses the IP geolocation database by DB-IP.com (CC BY 4.0) on our own server; the IP address is not sent anywhere for this.
The full list with locations and transfer safeguards is on the Sub-processors page. When you add personal data of other people to the Service (team members, contacts of your clients), we process it on your behalf under the Data processing agreement.
3. Analytics in detail
In the European Economic Area, the United Kingdom and Switzerland statistics and recordings load only after you allow them in the cookie banner; until then neither Google nor Microsoft receives anything from your visit. In other countries they run from the first page and the banner lets you switch them off; if your browser sends the Global Privacy Control signal, we treat it as “switched off”. We decide the region from your connection (Cloudflare's country header or our own IP database), without storing it. You can change your choice at any time with “Cookie settings” at the bottom of every page; when you withdraw it, we delete their cookies in your browser.
With consent we measure, for example: page views, sign-up and sign-in (with the method, not your details), steps of the first setup, the start and the result of a check, opening and downloading a report, sharing a report link, forms started, sent or failed, the steps of a checkout and its result, cancellations and errors shown to you. We never send your e-mail, name, phone, address or the contents of form fields. Payment events are sent from our server only if you allowed statistics before paying.
The staff of Pandus and the admin area are never measured.
The full list of cookies is in the Cookie policy.
Where visitors come from, without cookies. When you sign up, start a free check or order, we also store how you first and last reached the site: the campaign tags of the link (utm_*), the website that sent you (domain only, for example an AI assistant), the first page you opened and whether the link came from an ad. It is saved with your account, check or order and used only to count which channels bring customers; reports show totals. To tell visits apart we keep a one-way code made from the day, your IP address and browser in our cache for at most 2 days. No cookie is set for this. Legal basis: our legitimate interest in knowing which channels work (Art. 6(1)(f) GDPR).
4. Transfers outside the EU
Our servers are in the European Union. The controller is established in Ukraine, and our staff access the servers from Ukraine. The European Commission has not adopted an adequacy decision for Ukraine. Because we offer the Service to people in the EU, the GDPR applies to us directly (Art. 3(2)), wherever we are; access from Ukraine is protected by the measures in section 8: encrypted connections, two-factor authentication and access for named staff only.
Google, Microsoft, Cloudflare, Sentry and Paddle may process data in the United States or the United Kingdom. They rely on the EU–US Data Privacy Framework, the UK adequacy decision and standard contractual clauses; copies are available from them or from us on request.
5. How long we keep data
| Data | Kept |
|---|---|
| Account, teams, sites | while the account exists; deleted when you delete the account |
| Check history | as long as your plan allows (3 to 24 months); the latest report while the site exists |
| Free one-page checks and their screenshots | 30 days; a record of your marketing consent while it stands |
| Invoices and payment records | at least 1,095 days from the filing of the tax return they were used for (Tax Code of Ukraine, Art. 44.3), longer while a tax audit or dispute requires |
| Sign-in and e-mail logs | 90 days |
| Admin action log | 1 year |
| Support requests and form messages | up to 12 months after the last message |
| Business contacts of companies | up to 1 year without a reply; an objection is kept for good so we never write again |
| Cookie consent records | 3 years after the choice |
| Google Analytics data | 14 months (the setting in Google Analytics) |
| Microsoft Clarity recordings | 30 days; heatmaps up to 13 months (Clarity's limits) |
| Backups | overwritten within 14 days |
6. Your rights
Under the GDPR you may ask for access to your data (Art. 15), its correction (Art. 16), deletion (Art. 17), restriction (Art. 18), a copy in a portable format (Art. 20), and object to processing based on legitimate interest, including any marketing (Art. 21). You may withdraw consent at any time without affecting earlier processing.
- Delete your account yourself: Settings → Profile → Delete account. This deletes your teams with their sites, checks, reports, files and keys and stops card payments; invoices stay as tax law requires. We then delete your pseudonymous ID in Google Analytics and Clarity within one month.
- Everything else: write to vadym.queensoft@gmail.com. We answer within one month.
- Complaints: to the data protection authority of your country in the EU, or in Ukraine to the Ukrainian Parliament Commissioner for Human Rights (Закон України «Про захист персональних даних»).
California residents (CCPA/CPRA)
In the last 12 months we collected the categories listed in section 1 (identifiers, commercial information, internet activity, and — only with consent — analytics data) for the purposes stated there. We do not sell personal information and do not share it for cross-context behavioural advertising. You may ask to know, delete and correct your personal information and will not be treated differently for doing so. You can switch analytics off in the cookie banner at any time (“Cookie settings” at the bottom of every page); we honour the Global Privacy Control signal as such a request.
7. Children
The Service is for businesses and for people aged 18 or older. We do not knowingly collect data of children; if we learn that we have, we delete it.
8. Security
Encrypted connections, hashed passwords, two-factor authentication required for staff, a scanner isolated from the database and secrets, tests that customers cannot see each other's data, limited staff access, logs with shortened IP addresses, and tested backups.
9. Changes
When we change this policy we update the version and date at the top. Material changes are announced in the customer area or by e-mail before they take effect.