Privacy Policy

Who is responsible

The service is operated by Serhii Sachenok, a private entrepreneur (FOP) registered in Ukraine, who is the controller of the data described here. Questions and requests about your data go to support@polyntor.com.

What we collect

Your account. Your email address and, if you set one, a password — stored as a hash, never as the password itself. A name, company and role if you enter them, and a timezone if you choose one.

Google sign-in. If you continue with Google, Google gives us your Google account id, your email address, whether Google has confirmed it, and your name. We keep the id to recognise you next time and the email and name for the account. We do not receive your Google password and cannot see anything else in your Google account.

Your stores. The store addresses you add, the pages the scanner fetches from them, screenshots of those pages, and the findings, scores and action plans the scan produces.

Your product feeds. Feed files you upload, or the address of a feed you connect and the copy we fetch from it before each scan — product titles, prices, links, images and the other fields in it — and the issues found in them.

Usage and billing. Your plan, when it renews, how many scans you have used and bought, and a record of each scan and its charge. When you buy a plan or a pack, Paddle — the company that takes the payment — gives us your customer and subscription ids, the plan and its status, and the name and country you entered at checkout. Your card details go to Paddle only and never reach us.

Security. The IP address, the country derived from it and the browser identifier of each sign-in, sign-up and password change, kept as a log you and we can read if something looks wrong.

How you found us. If the link that brought you to our website carried an advertising click id or campaign tags (the gclid and utm_… parts of an address), or you came from another site, we store those with your account when you sign up — the tags, the referring site's host and the page you landed on, nothing else. We use it to see which of our ads and links bring customers; it is not shared with anyone.

Settings. Which alert emails you want, and which is the last thing you did on a page (a chosen tab, a theme) — the last of these stays in your browser only.

What it is used for

• Running the service: scanning your stores and feeds, showing you the results, sending the alerts you turned on, and keeping your session signed in.
• Keeping accounts safe: limiting sign-in attempts, spotting a sign-in from somewhere new, and letting you sign every device out.
• Billing: counting scans against your plan and the packs you bought.
• Support: answering you when you write to us.
• Understanding how the website and the app are used — which pages are read, where visitors come from — through Google Analytics. Until you answer the cookie banner it runs without cookies or identifiers and sends only anonymous, aggregated signals; it stores cookies only if you allow it, and if you decline it is not loaded at all.
• Seeing where the app is hard to use — which controls are clicked, how far a page is scrolled, where a visitor hesitates — through Microsoft Clarity, which records sessions and draws heatmaps. It is loaded only after you allow it on the cookie banner; what you type is masked before it leaves the browser.

We do not sell your information, use it for advertising, or build profiles of you for anyone else. We do not read your store pages or feeds for any purpose other than the scan you asked for.

Legal bases

Where a law asks us to name one: we process your account, your stores and your feeds because that is the contract you entered by creating an account and asking for scans. We keep the sign-in log and rate limits out of a legitimate interest in keeping accounts safe. Alert emails are sent because you turned them on, and you can turn them off in Settings at any time. Visit statistics with cookies run on the consent you give on the cookie banner and stop when you withdraw it there; the anonymous, cookieless signals before an answer rest on our legitimate interest in knowing whether the website works, and end the moment you decline. We do not make automated decisions with legal effect on you.

AI analysis

Part of each scan sends text from your store pages — and, on some plans, a sample of product images from your feed — to Anthropic's Claude API, which reads it against Google's merchant policies and returns an assessment. This happens under Anthropic's commercial API terms, which do not use the content to train their models. Nothing about you as a person is sent: no email, no name, no account id.

Merchant Center connection

On the Pro plan you can connect a store to your Google Merchant Center account. You do this through Google's own consent screen, where Google asks you to grant Polyntor the Manage your product listings and accounts for Google Shopping permission (the https://www.googleapis.com/auth/content scope). Nothing is read until you grant it, and you can use every other part of the service without it.

What we read. Through the Merchant API, and only for the account you picked: the list of Merchant Center accounts your Google account can see, so you can choose one; the account's own issues and its product statuses, so the store page can show why Google limits or disapproves items; the products in the account — titles, links, prices, images and the other listing attributes — when you choose to check them as the store's feed; and, when you press Fill from Merchant Center, the business information, shipping settings and return policies you already entered in Merchant Center, so you do not have to type them again.

What we keep. The Google account id and email address the connection was made with, the refresh token Google issues — encrypted at rest in our EU database and used only to read the data above — and a daily snapshot of the account issues and product statuses, of which the last ten are kept so the store page can show what changed. Products read as a feed are treated exactly like an uploaded feed. The settings that Fill from Merchant Center reads are shown to you and saved only if you press Save.

What we do not do. We do not write anything to your Merchant Center account: no products, settings or feeds are created, changed or deleted. We do not share Merchant Center data with anyone, do not use it for advertising or to build profiles, and do not send it to the AI analysis described above. It is used only to show you the state of your own account and to run the checks you ask for.

How to revoke. Disconnect the account from the store page or from Scan settings → Connections; ticking also revoke access at Google there invalidates the token with Google in the same step, and the stored token and snapshots are deleted. You can also remove Polyntor at any time from your Google account's third-party access page; the next daily read then fails and the connection is dropped on our side. Deleting your account deletes the connection with it.

Who else handles it

These companies process data on our behalf, only as far as running the service needs:

• Neon — the database, hosted in the EU (Frankfurt).
• DigitalOcean — the servers that run scans, in the EU (Frankfurt).
• Vercel — serves the web app.
• Cloudflare — DNS and the proxy in front of the servers.
• Google — sign-in with Google, and the Merchant Center connection, when you use them.
• Anthropic — the AI analysis described above.
• Resend — delivers the emails we send you.
• Microsoft Clarity — session recordings and heatmaps of the app, only after you allow it on the cookie banner; typed text is masked, and the recording is never tied to your account.
• Google Analytics — visit statistics: anonymous, cookieless signals until you answer the cookie banner, cookies only with your consent, nothing at all if you decline; never tied to your account.
• Paddle — takes payments as our merchant of record, holds your card details and issues invoices; it processes your data under its own privacy policy as the seller of record, not only on our behalf.

The scanner also visits your store the way a browser would, so your store's own hosting sees requests from our servers.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Where it is stored and moved

The database and the scanning servers are in the European Union. Some of the companies above operate from the United States or route traffic through it — Vercel, Cloudflare, Google and Anthropic — so pieces of your data cross borders when the service is used. Each of them is bound by a data processing agreement and, for transfers out of the EU and UK, by the standard contractual clauses those regions require.

If something goes wrong

If we learn that your data was accessed by someone who should not have had it, we will tell you by email without undue delay, say what was involved, and say what we did about it — and notify the authorities where the law requires it.

Cookies

One cookie keeps you signed in. A second, short-lived one exists only during a Google sign-in, to make sure the answer that comes back from Google is for the request that went out. Your theme choice, and — until you have an account — a store address you typed on our website and the campaign tags of the link you arrived by, are kept in the browser's local storage. When you open the checkout, Paddle's payment form sets its own cookies for fraud prevention. Google Analytics sets its own cookies only after you allow it on the cookie banner — before your answer it runs in Google's consent mode with every permission denied, which means no cookies and no identifiers, and if you decline it is not loaded at all. Microsoft Clarity sets its own cookies to tell one session from the next, and only after you allow it. Your answer is kept in a cookie for a year and can be changed from the Cookie settings link at the bottom of this page. There are no advertising cookies.

How long we keep it

As long as your account exists. Scan results and feed copies stay so you can compare runs over time. When you delete your account, everything it owns — stores, scans, screenshots, feeds, the sign-in log — is deleted in the same step, and it is not recoverable. Backups of the database are rotated out on the hosting provider's schedule. Invoices and payment records are kept by Paddle for as long as tax and accounting law requires, and we keep the record of what was paid for the same reason.

Your choices

• See and change your profile, timezone and alert emails in Settings.
• Export everything the account holds as one JSON file, from Settings → Data & account.
• Delete the account from the same place. It asks for your password, or for a fresh Google sign-in if the account has none.
• Sign out everywhere from Settings → Password & 2FA if a device is lost.

If you are in a place with a data protection law — the EU, the UK, Ukraine, California and others — the rights it gives you (access, correction, deletion, portability, objection) are met by the controls above, and anything they do not cover you can ask for by email.

Children

The service is for businesses and is not directed at anyone under 16. We do not knowingly keep an account for a child.

Changes

When this page changes, the date at the top changes with it. A change that affects what we collect or who handles it is announced in the app before it takes effect.

Contact

Questions about this document go to support@polyntor.com.