Privacy policy
Rankvisit gives your AI assistant read-only access to your search and analytics data. We collect as little as possible and we do not keep copies of your search or analytics data.
Last updated: 30 October 2026
1. Who is responsible
The controller for the processing described here is Halfmage, Gerrit Halfmann, Barbary Kostrzewskiej 39, 52-131 Wrocław, Poland (NIP 8993022263). Contact: support@rankvisit.com. See also the imprint.
2. What we process
Your account
When you sign in with Google, we receive your name, email address and profile picture. We use them to identify your account and to show who is signed in.
Google Search Console access
When you connect Search Console, Google gives us an access token and a refresh token with the read-only scope webmasters.readonly. We store these tokens encrypted (AES-256-GCM). We use them only to read Search Console data when your assistant asks for it. We do not store the Search Console data itself.
Google Analytics access
If you connect Google Analytics, Google gives us an access token and a refresh token with the read-only scope analytics.readonly, and the email address of the Google account you chose. We store the tokens encrypted (AES-256-GCM). We use them only to list your GA4 properties and to read the reports your assistant asks for. We do not store the Google Analytics data itself. When you remove the connection, we delete the tokens.
Bing Webmaster Tools access
If you connect Bing Webmaster Tools, Microsoft gives us an access token and a refresh token with the read-only scope webmaster.read. We store these tokens encrypted (AES-256-GCM). We use them only to read Bing search data when your assistant asks for it. We do not store the Bing data itself. When you remove the connection, we delete the tokens.
Analytics API keys
If you connect Fathom Analytics or Simple Analytics, we store your API key (and, for Simple Analytics, your User ID) encrypted. We keep the last four characters of the key in plain text, so that you can recognise it. We use the key only to read statistics when your assistant asks for them. We do not store the statistics.
AI assistants you connect
When you allow an assistant (for example Claude, ChatGPT, Claude Code or Codex), we store that permission and the OAuth tokens for that assistant. Access tokens are short-lived. When your assistant calls a Rankvisit tool, we read the requested data from Google or your analytics tool and send it to that assistant. From then on, the assistant provider processes the data under its own terms and privacy policy.
Tool requests
When your assistant calls a tool, we pass the request parameters (for example the property, date range and dimensions) to Google or your analytics tool and return the answer to the assistant. We do not store the request parameters or the answers.
To keep the service running well, we keep an anonymous call log: the time, the tool name, the type of assistant (for example Claude or ChatGPT), the duration and whether the call worked. It contains no user or account identifier, no parameters and no results, and it is deleted after 30 days.
Your assistant can send us feedback about Rankvisit (the tool rankvisit_submit_feedback), after it asks you. We store the text, the time, the tool name and the type of assistant, without any user or account identifier. Email addresses, URLs and domain names are removed before storing. Feedback is deleted after 90 days.
Billing
Payments are handled by Stripe, which acts as the seller of record (Stripe Managed Payments). Stripe processes your payment details and invoices as an independent controller; we never see your card number. We store the Stripe customer and subscription IDs, your plan and the subscription status.
Technical data
Like every website, our servers and our network provider receive your IP address, the time of the request, the requested address and your browser information. We use them to deliver the service, to protect it against abuse and to find errors.
- Web server logs (with IP address) are kept for 14 days and then deleted.
- Application error logs contain no IP addresses.
- Rate limits: to block abuse, we store a counter per IP address and route. Counters are deleted 24 hours after the last request.
Cloudflare, which delivers and protects rankvisit.com, processes the same request data under its own privacy policy.
3. Why we process it (legal bases)
- To provide the service you signed up for (Art. 6(1)(b) GDPR): account, connections, tool requests and billing.
- Legitimate interests (Art. 6(1)(f) GDPR): security, abuse prevention and error analysis.
- Legal obligations (Art. 6(1)(c) GDPR): for example tax records for invoices.
4. Google user data
Rankvisit's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- We request read-only access only.
- We use Google data only to answer the requests you make through your connected assistant.
- We do not sell Google data, do not use it for advertising, and do not use it to train AI models.
- No person at Rankvisit reads your Google data, except with your permission for support or where the law requires it.
With whom we share Google user data
"Google user data" means the data we receive from Google APIs: your Google profile (name, email address, profile picture), your Search Console data and, if you connect it, your Google Analytics data. We share, transfer or disclose it only in these cases:
- The AI assistant you connect (for example Anthropic for Claude or OpenAI for ChatGPT): when you ask a question, we send the requested Search Console or Analytics data to that assistant, and only to that assistant. This is the purpose of the service, and it happens only at your request and with your explicit permission for that assistant.
- Stripe (payments): when you subscribe, we give Stripe your name and email address from your Google profile to create your customer record. Stripe receives no Search Console or Analytics data.
- Service providers that only transmit or host data for us: Cloudflare (network delivery) passes the encrypted traffic, and our hosting provider in Frankfurt, Germany, stores the database with your profile and the encrypted tokens. They act on our instructions and do not use the data for their own purposes. We do not store your Search Console or Analytics data, so it is not in that database.
- Legal requirements: if the law, a court order or a public authority requires it, or to protect the security of the service and its users.
- Change of ownership: if Rankvisit is sold or merged, the account data can go to the new owner, under this policy. We will inform you by email before that happens.
We do not share, sell or disclose Google user data to anyone else. We do not give it to advertisers, data brokers or information resellers, and we do not use it or give it to others to train AI or machine learning models.
5. Who receives data
- Google: sign-in, the Search Console API and, if you connect it, the Google Analytics Data and Admin APIs.
- Microsoft (Bing Webmaster Tools): only if you connect it; we call the Bing Webmaster API with your token.
- Fathom Analytics or Simple Analytics: only if you connect them; we call their API with your key.
- The AI assistants you connect: they receive the data your questions ask for.
- Stripe: payments, invoices and tax handling.
- Cloudflare: network delivery and protection of rankvisit.com.
- Simple Analytics (Netherlands, EU): privacy-friendly visitor statistics for our website, see section 6.
- Our hosting provider: hosting of the application and database on servers in Frankfurt am Main, Germany (EU).
Some of these providers are located outside the EU (for example in the USA). Where this is the case, the transfer is based on an adequacy decision (such as the EU-US Data Privacy Framework) or on standard contractual clauses.
6. Cookies and analytics
We use one necessary cookie to keep you signed in. We do not use advertising or tracking cookies.
To understand how our website is used, we use Simple Analytics, a privacy-first analytics tool based in the EU. It sets no cookies, does not collect personal data such as IP addresses, and does not track you across websites. It only counts page views, referrers, device types and countries in aggregate. The legal basis is our legitimate interest in improving the website (Art. 6(1)(f) GDPR). Because no cookies or personal data are involved, we do not show a cookie banner.
7. How long we keep data
- Account: until you delete it.
- After your subscription ends: we delete your analytics keys, your assistant permissions and your Google tokens after 14 days. Your account stays, so that you can subscribe again.
- When you delete your account: we cancel your subscription, revoke Google access and delete your account and all connected data at once.
- Invoices: Stripe keeps them as long as tax law requires.
8. Your rights
You can request access to your data, correction, deletion, restriction of processing and a copy of your data (portability), and you can object to processing based on legitimate interests. You can delete your account yourself in the dashboard, or email support@rankvisit.com. You also have the right to complain to a data protection supervisory authority, in particular in the EU country where you live or work. Our lead authority is the President of the Personal Data Protection Office in Poland (Prezes Urzędu Ochrony Danych Osobowych, uodo.gov.pl).
You can remove Rankvisit's access to Google at any time in your Google account.
9. Security
Connections use TLS. Tokens and API keys are encrypted at rest. Access is read-only, and every assistant needs your explicit permission. You can remove an assistant or a connection at any time in the dashboard. No online service can guarantee complete security. To report a possible security problem, see the support page.
10. Children
Rankvisit is a business tool and is not intended for people under 16.
11. Changes
When we change this policy, we update the date at the top. For important changes, we inform account holders by email.