Privacy Policy
Version: November 3, 2026
How Path Ranker, a product of Alcateia Digital, handles personal data, under the Brazilian General Data Protection Law (LGPD, Law 13,709/2018) and, for people in the European Union, the GDPR. In short: we read the public pages of the sites you ask us to analyze; your Google data (Search Console and Google Analytics) is read only with your authorization, read-only, and is never sold or used for advertising; your keys and passwords are stored encrypted; and pathranker.com counts visits by itself, with no cookies and without keeping your IP, and uses Google Analytics only if you allow it in the cookie notice.
1Who is responsible for the data
Controller: Alcateia Digital Ltda (CNPJ 69.903.358/0001-20), headquartered at Rua Francisco Sardinha, 773, Engenhoca, Niterói - RJ, CEP 24110-645, which runs Path Ranker (pathranker.com and dash.pathranker.com).
Data protection officer (art. 41 of the LGPD): Alcateia Digital Ltda, at dpo@pathranker.com.
2What data we process and why
| Who | Data | Purpose | Legal basis (LGPD art. 7; GDPR art. 6) |
|---|---|---|---|
| People who visit pathranker.com | The site is static and sets no cookies; your browser keeps the language you chose and your choice in the cookie notice, which never leave your device. Only if you allow the Analytics category in the cookie notice does the site load Google Analytics 4 (Google), which receives the pages viewed, the clicks on the sign-up and plan buttons, that the contact form was sent (never what you wrote), where the visit came from, the type of device and browser, the language and the approximate location (country and city, inferred from the IP address, which Google Analytics does not store), tied to a random identifier in two cookies (_ga and _ga_SB7QCNTH4E, up to 2 years); we use it to count visits and the most-read pages. Google processes the data, including in the United States, and keeps it for the period set in our Google Analytics property (14 months at most). We do not use Google’s advertising features, and switching the Analytics category off stops the measuring and deletes those cookies. In addition, the site counts by itself the visits, the clicks on the sign-up and plan buttons, the contact form being sent and where the visit came from (UTM, ad or referring site), with no cookies and without keeping your IP address: we keep the event, the page (without what comes after “?”), a random id of the visit that disappears when you close the tab, the type of device and the country Cloudflare reports, for up to 13 months. This does not run for anyone who sends “Do Not Track” or the Global Privacy Control. The origin of your first and your last visit stays in your browser and goes in the sign-up link; when the account is created we keep that origin with it, to know which channel brought the sign-up. The typefaces (Inter and IBM Plex Mono) are hosted on the site itself: no data goes to Google because of them. If you use the AI crawler test, the address you type goes to our server, which asks your site for its home page, robots.txt and llms.txt; the result stays only in memory for 10 minutes and we count each IP address’s tests over the last hour to limit abuse. The structured data generator runs in your browser and sends nothing. If you write by e-mail or WhatsApp, we receive what you send. | Show the site, offer the free tools, answer messages and understand how the site is used (its own measurement, with no cookies; Google Analytics, with your permission) | Legitimate interest, for the own measurement; pre-contractual steps; consent, for Google Analytics |
| People who create an account | Name (optional), e-mail and password, stored only as a hash by the sign-in service (Neon Auth), or the identity of Google sign-in (name and e-mail); language, time zone and e-mail preferences; and, if you came from our site, where you came from (UTM, ad or referring site). | Create and protect access, send account notices and know which channel brought the sign-up | Performance of a contract; legitimate interest, for the origin of the sign-up |
| Team and invitations | E-mail and role (admin or member) of the people invited. | Give the company’s team access | Performance of a contract |
| Domains and analyses | The addresses of the sites you add and the result of each analysis: what the public pages contain (titles, text, links, structured data), technical measurements, scores and findings. If a public page contains personal data, excerpts of text may appear in the result. | Deliver the diagnosis, the history, the alerts and the reports | Performance of a contract |
| Keys and logins you add | Third-party API keys (for example OpenAI, Anthropic, Gemini, Perplexity), a domain’s collection key and, if you set it up, the user name and password of a staging site. They are stored encrypted (AES-256-GCM) and the password never comes back to the screen. | Run the measurements with your accounts and reach your staging site | Performance of a contract |
| People who connect Google | See section 3. | See section 3 | Consent |
| People who install the behavior collector | See section 4: the site owner is the controller of the data of the site’s visitors; Path Ranker is the processor. | Show how visitors use the customer’s pages | Set by the customer (controller) |
| People who receive a shared report | The person’s e-mail, a hash of the PIN, when and how many times the report was opened; a session cookie that is valid only for that report. | Show the report only to the people invited | Legitimate interest |
| System e-mails | E-mail, domain name and the scores in the alert or summary; the send log (type, domain, result and date), without the text of the e-mail. | Alerts when a site gets worse, weekly summary and monthly report (you can switch them off in Preferences); e-mail confirmation and forgotten password, through the sign-in service | Performance of a contract; legitimate interest |
| Subscription and payment | Plan, period, subscription status and Stripe identifiers. Name, e-mail, billing address and card are handled by Stripe: the card number never goes through Path Ranker. | Charge and enable the plan | Performance of a contract; legal obligation |
| Account event log | Date and time, the account and the person involved, the type of event and minimal technical data: for example the domain and the number of the analysis, and payment amounts and status reported by Stripe. Never passwords, keys, the content of analyzed pages or card numbers. | Protect the account, give support and prove facts, in particular the use of the standalone diagnosis and the status of charges | Performance of a contract; legitimate interest |
| Support tickets | Name and e-mail of who opened it, the subject and messages of the ticket, its type and what is affected, the attachments you send, the screen you were on, your language, browser and plan, and the internal notes of the team (which you do not see). Attachments may hold personal data if you include it: send only what is needed. | Answer your support request, fix problems and improve the product | Performance of a contract; legitimate interest |
| Server logs | IP address, browser, date and time and the address requested, in the hosting logs, and counts to limit abuse. | Security and operation of the service | Legitimate interest |
3Google data (Search Console and Google Analytics)
If you click Connect with Google (Integrations), Path Ranker asks for your authorization, read-only, to:
openidandemail: know which Google account is connected and show its e-mail on screen;https://www.googleapis.com/auth/webmasters.readonly: read Search Console data;https://www.googleapis.com/auth/analytics.readonly: read Google Analytics 4 data.
You can allow just one of the two and you choose which sites and properties Path Ranker may read.
What we read: from Search Console, for the site you choose, clicks, impressions, CTR and position, and the top queries, pages, countries and devices; from Google Analytics 4, for the property you choose, sessions, users, engaged sessions, conversions, average session duration and traffic sources (including visits from AI assistants). We do not read e-mails, files or any other data in your Google account.
What we use it for: to show the trend and the opportunities of your domain in the dashboard, the analyses, the alerts and the weekly summary. Nothing else.
What we store: the access token (encrypted), the e-mail of the Google account and the numbers read, inside the domain’s history.
Limited Use. Path Ranker’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- We do not sell this data and we do not use it for advertising or to train artificial intelligence models.
- We do not transfer it to third parties, except to the providers needed to run the service (hosting and database, section 5), where the law requires it, or in a merger or sale of the business, with notice to you.
- Our people read this data only if you ask for support, for security, or where the law requires it.
How to revoke: in Integrations, click Disconnect: access is revoked at Google and the token, the e-mail and the permissions are deleted from Path Ranker. You can also revoke at myaccount.google.com/permissions. The numbers already read stay in the domain’s history until you remove the domain or ask for deletion (section 8).
4Visitors of our customers’ sites (optional collector)
Customers can install a small script (pr-collect.js) on their own site that shows how visitors use the pages. It sends: the page path (without anything after the ?), the window size and device type, the domain the person came from (without the path), where clicks happened (as a share of the page) and the name and text of the button or link clicked (up to 40 characters), how far the page was scrolled, the time on the page, forms started, sent or abandoned, repeated clicks with no response, the number of browser errors, and a random code that stays only in the tab (it is not a cookie).
Together with the measurements we do not store name, e-mail or IP address, and never what the person types in fields (the IP address appears only in the server logs, section 2). The script does not run if the browser sends “Do Not Track” or the Global Privacy Control.
In that case the site owner is the controller of the data of the site’s visitors and must inform them in their own policy; Path Ranker handles it on the owner’s behalf (as processor), only to show the results in the owner’s account, never mixed with other accounts.
5Who we share data with
| Who | Purpose | Data |
|---|---|---|
| Neon (United States; database in the São Paulo region) | Database and sign-in service | Accounts, domains, analyses and the encrypted keys |
| Fly.io (São Paulo region) | Hosting of the dashboard and the analyses | Everything that goes through the dashboard |
| Cloudflare (United States) | Delivery of pathranker.com and DNS | IP address of people visiting the site |
| Google (United States) | PageSpeed Insights, Chrome UX Report, Knowledge Graph, Web Risk, Places and Cloud Natural Language APIs; and the Search Console and Analytics you connect; and the Google Analytics of the pathranker.com site, if you allow the Analytics category | The address of the analyzed site; the public text of pages (in Natural Language, on the Pro and Enterprise plans, up to 4,000 characters per page); the business name, in the Business Profile lookup; your Google data, only as in section 3 |
| OpenAI, Anthropic, Google (Gemini) and Perplexity | AI visibility: only when you turn it on, with your own key | Questions about your brand and your domain; the answers come back to your report. Your contract with each provider applies |
| Stripe (United States) | Subscription payments | Name, e-mail, billing data and card, directly at Stripe |
| Postmark (United States) | System e-mails | E-mail and the content of the e-mail |
| Open PageRank (Keywords Everywhere) | Domain authority score | The analyzed domain (no data about people) |
| Wikipedia and Wikidata, Hacker News and Common Crawl | Find public mentions of the domain | The analyzed domain |
| Accountant and authorities | Tax obligations and what the law requires | What each obligation needs |
We do not sell personal data.
6International transfers
The database and the hosting are in the São Paulo region, but the providers in section 5 are companies that also process data in the United States (Neon, Fly.io, Cloudflare, Google, Stripe, Postmark and the AI providers you turn on). When personal data leaves Brazil or the European Economic Area, the transfer rests on one of the safeguards the law provides: standard contractual clauses (those approved by the ANPD, Resolution CD/ANPD no. 19/2024, and those of the European Commission) or the provider’s certification under the EU–US Data Privacy Framework (an adequacy decision of the European Commission), depending on each provider’s contract (art. 33 of the LGPD; chapter V of the GDPR). To receive a copy of the safeguards that apply, write todpo@pathranker.com.
7How long we keep data
- Account, team, domains, analyses and history: while the account exists. When you remove a domain, its history is archived for 30 days (so you can restore it) and then deleted.
- Keys and logins you added: until you remove them. Google connection: until you disconnect; the numbers already read stay in the domain’s history, as above.
- Collector measurements: for 13 months; then they are deleted automatically.
- Shared reports and the log of e-mails sent: while the account exists.
- Tax and payment data: for the legal period of 5 years.
- Account event log: for 24 months; events about purchases, refunds and charges, for 5 years, also after the account is deleted, without identifying the person.
- Support tickets: for 12 months after they are closed, with their attachments; deleted earlier if the account is deleted.
- Server logs: for as long as the hosting provider keeps them.
- Answers of public services kept to avoid repeating lookups (data about domains, not people): 1 to 30 days, depending on the service.
- Deletion request: we delete the account and the data within 30 days, except what the law requires us to keep.
8Your rights
Under art. 18 of the LGPD you can ask for: confirmation that we process data about you, access, correction, anonymization, blocking or deletion of unnecessary data or data processed in breach of the law, portability, deletion of data processed with your consent, information about who we share data with, information about the possibility of not consenting and its consequences, and withdrawal of consent. Under the GDPR, people in the European Union have the rights of access (art. 15), rectification (art. 16), erasure (art. 17), restriction (art. 18), portability (art. 20) and objection (art. 21), including to processing based on legitimate interest.
How to ask: write to dpo@pathranker.com. We may ask you to confirm that the request is yours (for example, by replying from the account’s e-mail) so that we do not hand over or delete the wrong person’s data. We answer within 15 days (LGPD, art. 19) and, for people in the European Union, within one month. Access and portability come as a structured file (JSON). Deletion removes the account, its people, the analyses, the stored reports and the collector measurements, and we tell you when it is done. Data we must keep by law, such as tax data, is kept for the period the law sets.
Consent: where processing depends on your consent (the Google connection), you can withdraw it at any time, in Integrations, without affecting what was done before.
Complaint: you can also complain to Brazil’s National Data Protection Authority (ANPD) or, in the European Union, to the data protection authority of your country.
9Security
Connections use HTTPS. Keys, tokens and staging-site passwords are stored encrypted (AES-256-GCM) and sign-in passwords only as a hash. Each account sees only its own data. A staging-site password is sent only to that site, and Lighthouse does not run in those analyses so the password is never passed to third parties. No system is infallible: in case of a security incident that may cause relevant risk or harm, we notify the ANPD and the people affected within the period the regulation sets (3 business days) and, for people in the European Union, the competent authority within 72 hours of becoming aware, as the law requires.
11Where the data comes from, sensitive data and automated decisions
Where the data comes from. Most of it is provided by you (account, domains, keys). We also receive: the e-mail of the people your company invites to the team or to view a report, provided by whoever invites; the public content of the pages of the sites analyzed, which we read; visitor measurements sent by the collector, when the site owner installs it; and the Google data you authorize (section 3). We do not buy data from third parties.
Sensitive personal data. We do not ask for or deliberately process sensitive data (health, racial or ethnic origin, religious belief, political opinion, biometrics and the rest of art. 11 of the LGPD and art. 9 of the GDPR). If an analyzed public page contains it, the text read may appear in the result of that analysis, which stays only in the account of whoever asked for it.
Automated decisions. We make no automated decisions that have legal effects on you or significantly affect you, and we do not profile people. Path Ranker’s scores rate sites, not people.
Is providing the data mandatory? To have an account, the e-mail and password (or Google sign-in) are necessary: without them we cannot create or protect the account. The rest is optional (name, photo, Google connection, AI keys, staging site, collector) and, without it, only the features that depend on it stop working.
12Changes
We may update this policy. Relevant changes are announced by e-mail to people with an account, and the version in force is always on this page, with its date.