Approvalens scans public websites and sells reports about them, and monitors sites and Linux servers for the people who sign up for it. This policy explains what we collect while doing that. We collect as little as we can.
Who is responsible
The data controller (in Turkish law, the veri sorumlusu) is Kaan Tokalı, Kurtköy, Istanbul, Türkiye, who runs Approvalens. Write to kaantokali1@gmail.com about anything in this policy.
What we collect
The address you scan. We store the URL, the report we generate and a screenshot of the homepage as it appears on a phone. Reports are reachable only through their unguessable link.
Your IP address. We store it next to each scan request to limit how many scans one visitor can start, which protects the service and the sites being scanned. It is not used for anything else.
Your account (Google sign-in). You can sign in with Google. We ask Google only for the basic profile scopes (openid email profile) and accept only an e-mail address Google has verified. We store your e-mail address, your name, the address of your Google profile picture, Google's account id for you, your language, when you first and last signed in and how many times. Scans you start while signed in, your purchases, credits, plans, monitored sites and servers, alert settings and API keys are all linked to that e-mail address. We keep a short log of account events (such as sign-ins, purchases and plan changes) to run the service and answer support questions. We never see your Google password and get no access to your Gmail, Drive or anything else in your Google account.
Purchases. Payments are handled by Lemon Squeezy, which acts as the merchant of record. Lemon Squeezy collects your name, e-mail address, billing country and payment details under its own privacy policy. We receive the order number, the e-mail address, the amount and which site the purchase unlocked. We never see your card details. When we open a checkout we pass Lemon Squeezy your signed-in e-mail address, the site and report it is for, the page language and the traffic-source label described under "Cookies and browser storage".
Monitoring plans. For a monthly site or server monitoring plan we receive from Lemon Squeezy the subscription id, the plan and its size, its status (active, paused, cancelled or expired), the renewal or end date and a link to your Lemon Squeezy billing page, and keep them with your account.
Site monitoring. For each site you monitor we store its address, the result of the latest checks (robots.txt and ads.txt as they read, how the homepage answers Google's and AI crawlers, the TLS certificate, uptime and a few security checks), the changes and outages found, and which e-mails you want (per-site alerts, the weekly summary).
Alert destinations (optional). If you add places for alerts to go, we store each one with its rules (which alerts, minimum severity, tags, quiet hours, digest) and your time zone: an extra e-mail address, a Slack or Discord webhook address, a Telegram bot token and chat id, or a webhook address of your own and its signing secret. Webhook addresses, bot tokens and signing secrets are encrypted before they are stored and are never shown in full again. An extra e-mail recipient gets nothing until they confirm a link we e-mail them, and every message to them has a link that removes them. Alerts sent to Slack, Telegram, Discord or your webhook contain the site or server name and what changed, and are handled by that service under its own terms once delivered. We keep a log of deliveries (when, to which destination, whether it worked) to show you on the account page.
The server agent (optional). If you install our agent on a Linux server, it sends us information about that machine. The section "The server agent" below lists what it sends.
API keys (optional). When you make an API key we show it once and store only a one-way hash (SHA-256) of it, its first characters so you can recognise it, the name you give it, when it was made, when it was last used and whether you revoked it. Every API request is answered from your own account's data only.
AdSense outcome (optional). If you tell us on a report whether AdSense approved the site, we store your answer with that scan's score and issue counts, the names of the rejection reasons the page recognised in anything you pasted (never the pasted text itself), your optional short note, a random id your browser keeps so you can change the answer, and your e-mail address only if you are signed in; we use it, in totals and only internally, to check how well our scores match Google's decisions.
Report link by e-mail (optional). If you leave an e-mail address on the scan progress page, we store it with that scan, the page's language, the sentence you agreed to and the time, and send you one e-mail with the report link when the scan finishes. We never use the address for marketing unless you also tick the separate "send me tips" box, which is off by default; every e-mail has an unsubscribe link. The IP address of the request is kept for 30 days to stop abuse of the form. Delivery is handled by Resend.
Visit statistics. We count page views on our own server, without cookies and without storing your IP address. The section below explains exactly how.
Google Analytics. If it is switched on, we also use Google Analytics with IP anonymisation to count visits and see which pages are useful. You can block it with any content blocker; the site works the same.
We do not use advertising cookies and we do not sell or share personal data with advertisers. Our e-mails contain no tracking pixels and no tracked links.
Cookieless visit statistics
To know how many people visit, which pages and guides are read and how many visitors go on to scan a site, every page sends one small request to our own server when it opens. It contains:
- the page address, without its query string — except the campaign tags
utm_source,utm_medium,utm_campaignandref; report links are stored without their id; - the domain of the site that linked to us (for example
google.com), only if it is another site, never the full address; - your screen size as one of three groups: phone, tablet or desktop;
- the language of the page (English or Turkish).
To count each visitor once per day without a cookie, our server combines your IP address and your browser's user-agent string with a random value (a "salt") and keeps only a shortened one-way hash (SHA-256) of the result. A new random salt is created every day (UTC) and deleted after two days. After that, nobody, including us, can work out which IP address a code belonged to, and the same person gets an unrelated code each day, so visits on different days cannot be linked. Your IP address is used only for that calculation and, briefly and in memory, to stop abuse; it is never written to disk with the statistics. When you start a scan, the same daily code is stored with the request so that we can count how many visitors started a scan.
We set no cookies and store nothing in your browser for counting visits. One small first-party cookie, al_src, remembers, until you close your browser, where this visit came from (a source label such as google or reddit and the page you landed on, nothing that identifies you), so that a purchase can be traced to the channel that brought it; it is not written when your browser sends Global Privacy Control or Do Not Track. The site owner's own browser carries an al_internal cookie so that his visits are left out of the statistics. If your browser sends a Global Privacy Control or Do Not Track signal, nothing is sent and nothing is counted. Requests from known bots, crawlers and monitoring services are discarded. Your account and admin pages are never counted.
We use these statistics only as totals, to understand how the site is used and to improve it (our legitimate interest). They are not used for advertising or profiling, not combined with other data and not shared with anyone. Individual page-view records are deleted after 400 days.
Cookies and browser storage
All our cookies are first-party. None is used for advertising.
| Cookie | What it is for | How long |
|---|---|---|
al_sid |
keeps you signed in (signed, readable only by our server) | 30 days, or until you sign out |
al_oauth_state, al_oauth_verifier, al_oauth_next |
protect the Google sign-in step and bring you back to the page you came from | 10 minutes |
al_src |
the traffic-source label described above | until you close your browser |
al_internal |
marks the site owner's own browser so his visits are left out of the statistics | 1 year |
The page also keeps a few things in your browser's own storage, which is never sent to us: the boxes you ticked on the checklist, how many rows a table shows, some report view choices, a note that you have just left for a Lemon Squeezy checkout, and, for this tab only, text you paste into the rejection decoder. The random id for the AdSense outcome form is sent to us only when you submit an outcome. Google Analytics, when switched on, sets its own cookies.
The server agent
The agent is optional and open source (MIT); its full documentation and source code are at https://approvalens.com/agent. It runs only on servers where you install it. It never sends the contents of files, never runs commands it receives and opens no network port. Every 5 to 15 minutes, and at once when a rule trips, it sends us:
- machine health: CPU, memory, swap, load, disk and inode use, disk input/output, network traffic, connection counts, uptime, host name, operating system, kernel and hardware type;
- the busiest processes: process id, name, user, program path, systemd unit and command line, with passwords, tokens and keys in command lines and crontab lines replaced by
***before they leave the machine; - listening ports and the programs behind them, failed services (with their last ten log lines, redacted the same way), crontab lines, SSH key fingerprints and comments (never the keys), setuid files, and where disk space goes (folder and file names with sizes);
- security settings: SSH server settings, firewall rules, automatic updates, fail2ban, the accounts that can log in or use sudo (names, user ids, groups, last login);
- login records from the server's own logs: successful SSH logins and logins from the login history (time, account name, source IP address or host name), counts of failed attempts per source IP address with the names of accounts that exist on the server, and sudo use (time, account, allowed or refused, never the command);
- if you configure a web root, the names of PHP, JavaScript and HTML files that were added, changed or removed.
We also record the public IP address the agent reports from. At most once every 6 hours we try to open a TCP connection to that address on the ports the agent reports as listening on public addresses, to tell you which ones answer from the internet; we never connect to private addresses, and disable: [reachability] in the agent's configuration switches this off. Any other check can be switched off the same way.
Login records can contain the names and IP addresses of people who log in to your server. You decide whether to install the agent and which checks it runs.
The agent authenticates with a token that is shown to you once; we store only its hash.
What we do with the sites we scan
We fetch pages the way any visitor or search engine does: only public pages, at most 50 pages per free scan and up to 20,000 for a full (paid) report, plus a few files such as robots.txt, sitemaps and ads.txt. We identify ourselves with a standard browser user agent and, for a few requests, with Google's documented crawler user agents to test how your server answers them. We do not log in, submit forms or execute anything on your server.
The security check also requests, once each, a short fixed list of addresses that should never be public (such as /.env or /.git/HEAD), respecting robots.txt, and only records whether they are exposed, never what is in them. On WordPress sites it counts the public user list; the names are never stored.
To complete a report we look up the site's address with a few public services: Google PageSpeed Insights, Google's Safe Browsing status, domain registration data (RDAP), the Internet Archive's Wayback Machine and public DNS resolvers. Only the site's address goes to them, never anything about you.
Site monitoring requests the homepage of each monitored site every 5 minutes, and once a day its robots.txt, ads.txt and llms.txt, the homepage with Google's and AI crawlers' user agents, the TLS certificate and the same exposed-file checks.
Why we use it
- To provide what you ask for (performing our contract with you): scans and reports, your account, purchases, credits, monitoring plans, site and server monitoring, alerts and the API.
- Our legitimate interests: limiting abuse (IP addresses on scan and e-mail requests), keeping the service secure, the cookieless visit statistics, traffic-source attribution and checking our scores against the AdSense outcomes you share.
- Your consent: the optional report-link e-mail and tips, and the alert destinations you add. You can withdraw consent at any time (unsubscribe, or remove the destination); that does not affect what was done before.
- Legal obligations: order and invoice records that tax and accounting rules require.
How long we keep it
- Free scans: report and screenshot are deleted after 30 days.
- Paid reports: kept for 400 days so you can come back to them.
- Scan request records (the address scanned, when, your IP address and the daily visit code): the report and screenshot inside them are deleted as above, and the IP address is erased after 30 days. The rest of the record (address scanned, time) stays so that the site's scan history works; write to us to have yours removed.
- An e-mail address left for the report link: 30 days (until you unsubscribe if you also asked for tips); the IP address of that request: 30 days. An address that unsubscribed stays on a do-not-send list so that we never e-mail it anything optional again.
- Visit statistics (page-view records with a daily code, no IP address): 400 days. The daily salts behind the codes: 2 days.
- Your account, its event log, API keys and alert destinations: until you delete them or ask us to delete your account. Alert delivery records: 30 days.
- Site monitoring results and history: while the site is in your account. A site that was never covered by a payment is deleted, with its history, as soon as you remove it.
- Server agent data: per-minute figures 7 days, hourly figures 35 days, daily summaries and server alerts 90 days, availability 31 days, disk-usage history 31 days, failed login attempts by IP address 8 days; the latest login and sudo records (up to 200 each) and the addresses seen logging in (up to 1,000) are kept while the server is in your account. Deleting a server deletes all of its data at once. A server that no plan covers any more pauses (nothing it sends is stored; if no plan is left at all, servers first keep reporting for 7 days) and its stored data is deleted 30 days after it paused; the server's entry (its name, host name, system, last IP address and the lists it learned as normal) stays in your account until you delete it.
- Order records: as long as tax and accounting rules require.
Your rights
You can ask us to delete a report, to tell you what we hold about you, or to correct it. Write to kaantokali1@gmail.com from the e-mail address you used at checkout or sign in with, or include the report link. Residents of the EEA, the UK and Türkiye (KVKK) have the rights their laws grant, including the right to complain to a data protection authority.
Under the GDPR (EEA and UK) you can ask for access to your data, correction, deletion, restriction of processing, a copy in a portable format, and you can object to processing based on our legitimate interests.
Under Article 11 of the Turkish Personal Data Protection Law No. 6698 (KVKK), as a data subject you can learn whether your data is processed and request information about it, learn the purpose and whether it is used for that purpose, know the third parties in Türkiye or abroad it is transferred to, ask for it to be corrected, deleted or destroyed and for those third parties to be told, object to a result against you that comes solely from automated analysis, and claim compensation for damage caused by unlawful processing.
We answer within 30 days. If we may need to confirm that a request really comes from you, we will ask. You can complain to the data protection authority of the country where you live or work; in Türkiye that is the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu).
Deleting your account and data
There is no self-service button to delete a whole account yet. You can remove these yourself from your account page at any time:
- a server, which deletes all of its data at once (remove the agent from the machine too);
- an alert destination or extra e-mail recipient;
- an API key (revoked keys stop working at once);
- a site from your monitoring plan.
To delete your account and everything linked to it, write to kaantokali1@gmail.com from the Google address you sign in with. Cancel any active monitoring plan first in the Lemon Squeezy billing page linked from your account, so that it does not renew. We keep order records as long as tax and accounting rules require, and Lemon Squeezy keeps its own records as the merchant of record. Signing out does not delete anything.
Processors
- Lemon Squeezy — payments, subscriptions and invoices (merchant of record).
- Our hosting providers — the servers that run the website, the database, the scanner and the computers it fetches pages from.
- Google — sign-in with Google; PageSpeed Insights and Safe Browsing lookups for the sites we scan (the site's address only); Google Analytics, only if enabled.
- Resend — sending e-mail (the optional report link, confirmation e-mails for extra alert recipients, and monitoring alerts and summaries).
Slack, Telegram, Discord and your own webhook receive alerts only if you add them as destinations; they are services you choose, not our processors.
International transfers
Some of these providers, including Lemon Squeezy, Resend and Google, are based in the United States or store data in several countries. Using Approvalens therefore means your data is transferred outside Türkiye and outside the EEA. We send each provider only what it needs for its job, as listed above.
Changes
If we change this policy we update the date at the top. Material changes are announced on the homepage for 30 days.