What Data Does Rankato Store?# Link to this article
Rankato stores the crawl, ranking and backlink data it collects, the aggregate Google reporting data you authorise, and your account and workspace records. It does not store end-user-level analytics data.
Data Rankato collects itself# Link to this section
- Crawl data — pages fetched during audits: URLs, response codes, headers, rendered content used for checks, and the findings derived from them.
- Ranking data — tracked keyword positions with their collection timestamps and the SERP layout observed.
- Backlink data — links discovered in the open web corpus and the results of Rankato's own verification crawls.
- Indexing data — URLs submitted and their observed index status over time.
# Link to this section
With a connected integration, Rankato reads aggregate reporting data: impressions, clicks, queries and pages from Search Console; sessions, engagement and conversions by landing page from GA4.
Rankato does not read or store user-level or individual-visitor records from GA4, and never writes to your Google properties. Access is read-only and you can revoke it at any time from your Google account or from Rankato's integration settings.
Account and workspace data# Link to this section
Your account details, workspace membership and roles, project configuration, billing records, and support conversations.
What Rankato does not do# Link to this section
- It does not sell your data.
- It does not train models on your private workspace data or your support conversations.
- It does not place your private content into any publicly reachable index or assistant.
Retention and deletion# Link to this section
Collected data is retained for the historical range your plan provides, so trends remain comparable. You can delete a project and its data from project settings, and request account deletion from support.
The authoritative statement is the Privacy Policy; this article is a plain-language summary of it.
Written by Rankato