Rank tracker security for your team's data
SearchTracking handles the account information, project settings and search results needed to run your tracking workspace. Security controls cover encrypted data, access roles and the permissions used for connected services. This page explains those controls and the data lifecycle in plain language. Use it when reviewing a subscription, assigning team access or preparing questions about your organization's use of the service.
| roles | access |
|---|---|
| owner | person responsible for the account |
| editor | colleagues who maintain tracking work |
| viewer | people who read results |
| client viewer | projects shared with a client |
02
Rank tracking data handling and encryption
Your workspace contains account details, domains, keywords, tags, location and device settings, recorded rankings and AI check results. Reports use the tracking information selected for their blocks. Connecting Google Search Console adds the search performance metrics you import. These categories describe the service's work, so review what your team enters and shares as part of account administration.
Data is encrypted in transit and at rest. Encryption in transit protects data as it moves between your browser and the service. Encryption at rest protects stored data. Account permissions control which people use the workspace, while report sharing determines the information recipients receive. Consider these controls together when deciding how colleagues and clients should access tracking results.
in transit
browser
service
at rest
stored data
Encryption
03
Account access roles for teams and clients
SearchTracking supports owner, editor, viewer and client viewer roles. Assign ownership to the person responsible for the account, editing to colleagues who maintain tracking work and viewer access to people who read results. Agency and Enterprise include client viewer logins for access to the projects shared with a client.
Unlimited seats on every plan let you assign individual access according to responsibility. Review those assignments when colleagues leave a project or client work changes hands. Enterprise adds SSO through SAML and an audit log for organizations that need centralized identity access and an activity record. The enterprise rank tracker page lists those features alongside its service commitment and security questionnaire pack.
04
Google Search Console read only access
The Search Console connection uses read only access. SearchTracking imports metrics such as clicks, impressions and CTR to display beside tracked positions. The connection reads search performance information without changing the connected site's content or Search Console settings. Review the property you connect so that imported metrics belong to the domain your team intends to analyze.
Read only access still exposes information to the workspace members who can view the connected project. Apply the same care to project permissions and report content as you do to tracking data. The seo ranking report software page explains how imported search metrics appear in the ranking and reporting workflow.
05
Account data retention and deletion
SearchTracking retains account and tracking data to operate the service and provide the history used in rankings, charts and reports. Some records also support payment administration, security and legal obligations. Retention depends on the record's purpose. A ranking history, an account access record and a billing record serve different needs and do not necessarily follow the same lifecycle.
To request account data deletion or clarify retention for a particular record, email [email protected]. Include the account or project concerned and describe the request without sending passwords or payment card information. Records required for legal obligations can remain for that purpose. Deleting account data also requires considering copies your team exports or shares, since recipients may retain downloaded reports separately.
06
Subscription payment security and billing records
A payment operator processes subscription payments. SearchTracking never sees full card numbers. Account billing records support the subscription and its administration, while the payment operator handles the card details used for payment processing. Enterprise also includes invoice billing for organizations using that purchasing workflow.
Keep payment information out of keyword fields, project notes and support messages. If you need help identifying a billing issue, describe the account and the charge rather than sending full card details. Compare the published subscription features in rank tracking tools when deciding which billing and account options fit your organization.
07
Service provider categories and security issue reporting
The service uses provider categories for hosting and storage, payment processing, email delivery, search result data and AI answer processing. Those categories support different tasks. Keyword and domain inputs support search and AI checks, account email supports delivery of account messages, and payment details belong in the payment operator's workflow. Consider the inputs your team sends when assessing the service for its intended use.
Report a security issue to [email protected]. Describe the affected page or account function, what you observe and the steps needed to reproduce the issue. Share only the information necessary to explain it. Do not include another person's data, passwords or full payment card numbers. For client reporting controls, review white label rank tracking and the access workflow in the agency rank tracker.
08
Rank tracker security questions
Is account data encrypted?
Yes. SearchTracking encrypts data in transit and at rest. Account roles and report sharing settings govern how people access workspace information.
Can the Search Console connection change my site?
No. The connection uses read only access to import search performance metrics. It does not change site content or Search Console settings.
Does SearchTracking see full payment card numbers?
No. A payment operator processes payments, and SearchTracking never sees full card numbers. Keep card details out of project fields and support messages.
How do I request deletion or report a security issue?
Email [email protected]. Describe the account data request or affected function, and include only the information needed to investigate or handle the request.
09
Start rank tracking with clear access responsibilities
Review the data your team uses, choose the right project permissions and decide which information belongs in shared reports. Check rankings in the demo with no card required, or create an account to begin the signup process. Send security questions to [email protected] when you need clarification for your review.