Privacy policy

Who runs it

RankPilot is operated by Hanzla Habib. For any question about this policy, your data or a request to delete it, write to hanzla.dev@gmail.com.

Google user data we access

You sign in with Google and connect your own Search Console and Google Analytics 4 properties so RankPilot can show you reports about your own sites. We ask for permissions one step at a time, and only when you press the matching Connect button.

• Sign in: openid, email and profile give us your name, email address and Google account identifier. Sign-in also asks for read-only Search Console access (webmasters.readonly), because Search Console is the first thing the product shows.
• Search Console, read-only: webmasters.readonly lets us read performance data (queries, pages, clicks, impressions, average position, country and device), sitemaps, and URL inspection results for the sites you can already see in Search Console.
• Search Console, manage: webmasters is requested only if you choose to let RankPilot submit a sitemap or add a site on your behalf. We do not use it for anything else.
• Google Analytics 4: analytics.readonly lets us read reports (sessions, key events, landing pages, and the channels and sources of traffic) for the GA4 properties you choose.
• Public data: Chrome UX Report and PageSpeed Insights are public Google services that we call with our own API key. They return public performance data about web pages and involve no data about you.

The product can offer further optional connections (AdSense, Google Business Profile, Merchant Center, and Google Docs or Sheets for exports). Each one asks for its own permission, only when you press its Connect button, and each is covered by this policy. Until you connect one, we hold no data from it.

What we store

• Your account: name, email address, Google account identifier, and the settings you choose.
• The Google connection: the access and refresh tokens Google gives us. They are encrypted at rest, and the web application cannot decrypt them; only the background worker that talks to Google can.
• Report data: the Search Console and GA4 figures listed above, copied into our database on a schedule so you can see history longer than Google keeps and compare periods. We store the aggregated figures Google returns. We do not read your Google Analytics visitors or Search Console users, and we do not store individual visitors.
• What you create: properties, goals, annotations, tasks and reports, and the results of crawls you run against your own sites.
• Technical records: request identifiers and error traces, with request bodies, cookies and query strings left out.

How we use Google data

We use Google data only to provide and improve the features you see in RankPilot: your reports, alerts, opportunities and exports. We do not use it for advertising, we do not sell it, and we do not use it to build profiles of people or to train general-purpose or generative AI models.

If you turn on a language-model feature, the report figures that feature needs are sent to the model provider you configured, using your own key, with personal data removed first. We do not send Google user data to any other third party except the service providers that run RankPilot for us (hosting and email), which process it only on our instructions.

RankPilot’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.

In line with those requirements, people at RankPilot do not read your Google data unless you ask us to look at it for support, it is needed to investigate abuse or a security problem, or the law requires it.

How long we keep it

• Report data is kept while your workspace exists. Daily detail is kept for a period that depends on your plan, after which it is rolled up into weekly or monthly totals; site-level totals are kept as long as the workspace exists.
• Tokens are kept until you disconnect the account or delete your account, then revoked.
• When you delete your account or a workspace it is locked and scheduled for removal. You can restore it for 30 days; after that its data is purged. A one-way hash of the email address of a deleted account is kept for 90 days so we can answer support questions.

Disconnecting and deleting

• Disconnect a Google account in your account settings at any time. We then stop reading from Google and revoke the token at Google.
• You can also revoke access from your Google Account permissions page.
• Export your data and delete your account from your account settings. To have data removed without using the settings, or to ask about any of it, write to hanzla.dev@gmail.com.

Sharing and security

We do not sell personal data or Google user data. Each row of data belongs to one workspace, and database row-level security stops one workspace reading another’s. More about our controls is on the security page; the companies that process data for us are on the subprocessors page.

Cookies

We use essential cookies for sign-in and security. Product analytics stays off unless you accept it. The list is on the cookie page.

Changes

When this policy changes we will change the date at the top and, for material changes, tell signed-in users. See also the terms of service.