Privacy Policy

RankEcho is operated by Nexus Decision Systems LLC. This policy explains what information RankEcho may collect, how it is used, what the initial public-domain audit does not require, and how an optional Google Search Console connection handles your data.

Information we collect

• Public domain names submitted for audits.
• Optional email addresses submitted for results, login, support, billing, or follow-up.
• Audit metadata such as audit ID, target domain, status, and timestamps.
• Prompt outputs, cited URLs, source domains, competitor mentions, source classifications, and scorecard data.
• Fix package and proof-loop data when paid features are used.
• Account, plan, billing status, and entitlement data for paid plans.

Information we do not require for an initial audit

• No CMS admin access.
• No analytics access.
• No Google Search Console access.
• No CRM or customer database access.
• No private customer records.
• No website passwords.

Optional Google Search Console connection

Where this feature is available, a workspace owner can choose to authorize Google Search Console through Google's consent screen. RankEcho requests Search Console read-only access, not permission to change your Search Console properties. Google provides access and refresh credentials and the identifiers and permission levels of properties accessible through that authorization. RankEcho uses these to maintain the connection, show the owner available properties, and verify the property the owner explicitly selects for a website in the private workspace.

Search Console data RankEcho reads. RankEcho asks Google only for the read-only Search Console scope (webmasters.readonly). It cannot add, change, or delete anything in Search Console. When the owner saves a property for a website, RankEcho reads that property's Search Analytics reports: daily site totals, pages, and the searches that show each page, with clicks, impressions, click-through rate, and average position. It uses this data only to show your reports, rank Gaps & Actions, add search evidence to writer briefs you start, and measure changes you mark done.

How long synced data is kept. RankEcho stores the synced data in its server-side database, scoped to your workspace. Daily site totals and page rows cover up to 16 months, the history Search Console provides. Page-and-query rows are kept for the most recent 90 days, limited to the top 5,000 rows per day; older query rows are deleted automatically. Synced data is kept while the website stays connected, until the owner deletes it.

Never sold or used for advertising. RankEcho does not sell Google user data, use it for advertising, or use it to train AI models. It is shared only with the service providers that operate RankEcho (hosting, and the AI model that drafts a writer brief you start from an action) and, when you connect them, the AI assistants you authorize below. RankEcho's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting and deleting. Remove access from RankEcho stops future syncing for that connection. Delete my search data, in the Google Search Console section of the workspace, asks Google to revoke RankEcho's access, removes every saved Google credential and property link in the workspace, and deletes the synced daily totals, page rows, page-and-query rows, sync progress, and action decisions for all of its websites. Account, billing, and trial records are kept. Only the workspace owner can use either control. Deleted rows are removed from the active database at once; infrastructure backups and operational logs are not immediately erased.

What is saved and who can access it. RankEcho encrypts access and refresh credentials before storing them in its server-side database. They are used by the server to communicate with Google; this integration does not show them to workspace members or save them in browser storage. RankEcho also stores authorization-attempt records, connection status and timestamps, and the selected property's identifier, permission level, verification time, and links to the workspace website and connection. Only the workspace owner can authorize Google, discover the accessible property list, change a selection, or remove local access. Other authorized members can see selected-property and non-secret connection information for websites they are permitted to access; they do not receive the credentials or the list of unselected Google properties.

Current use and sharing. Connecting Google does not start search-data collection; saving a property for a website starts the sync described above. Separately, an approved workspace owner can start the closed Search Console pilot for the website, historical dates, and limits shown in its collection control. The pilot collects daily project totals and page/query results, including search queries, page URLs, clicks, impressions, click-through rates, average positions, and collection evidence. Google processes authorization and API requests. Cloudflare provides hosting, the control database, identifier-only processing queues, and a private archive. Only the approved workspace owner can start the pilot or download its retained partitions. Google connection credentials are never sent to AI platforms or model providers. Connecting Google alone does not authorize AI access. RankEcho does not use collected search data for model training or advertising, or include it in public audit benchmarks. An eligible owner may separately authorize the optional ChatGPT connection described below.

Collected search data. Each pilot partition is available for 30 days from collection. Its private download checks that expiry; expired data is scheduled for archive deletion, with storage lifecycle expiry as a backstop. Physical deletion is asynchronous. Stop collection stops future pilot work and retains collected partitions until expiry. Delete collected data blocks access and starts archive removal; the pilot reports deletion complete only after a sweep verifies the archive is empty and the in-flight-write grace period has passed. Detailed pilot job, usage, and manifest records are purged 30 days after the pilot becomes terminal, once archive cleanup has been verified. Minimal aggregate quota counters remain until cleanup ends. Independent deletion journals expire 90 days after verified archive purge; a failed purge remains pending for cleanup. A minimal retired-pilot record is kept to prevent reactivation or budget resets. Removing a Google connection stops future authorized collection but does not delete already collected partitions; use the pilot's delete control for those records. Infrastructure backups and operational logs are not immediately erased by these controls.

Retention and removing local access. Saved credentials remain available to maintain the connection until the owner removes them or RankEcho detects an authorization failure that requires reconnection. The owner can use Remove access from RankEcho to clear that connection's saved credentials, outstanding authorization attempts, and selected-property links from every website using it in the workspace. This removes those records from the active application database. It does not delete RankEcho projects, locally configured property references, connection status/history metadata, or existing audit records. Retained connection metadata has no automatic deletion schedule. Local removal does not mean immediate deletion from infrastructure backups or operational logs. Contact hello@rankecho.io for broader privacy or deletion requests.

Removing access in Google. Local removal does not revoke RankEcho's authorization in your Google Account; Delete my search data does. You can also review or remove RankEcho's access in your Google Account settings. Google-side removal can affect other connections relying on the same Google grant; it does not delete records already retained by RankEcho.

How we use information

We use audit and account information to operate the product, generate reports, provide login and account access, process billing status, generate fix recommendations, support proof-loop tracking, improve reliability, prevent abuse, and produce aggregate benchmark patterns where appropriate.

Optional ChatGPT connection

An approved workspace owner can separately choose to connect ChatGPT to RankEcho. RankEcho asks you to select the sites the connection may read and authorize read-only access. When you use the connection, selected site names and domains, available reporting dates, search queries, page URLs, observed metrics, coverage limitations, and evidence links may be sent to ChatGPT. The connection cannot change your website, create tasks, start data collection, or change account settings. Google access and refresh credentials, RankEcho browser cookies, and billing data are not included in tool results.

Connection records and access. Cloudflare stores the separate OAuth client and authorization records and RankEcho stores the consenting account, selected sites, grant dates, and revocation status. Authorization lasts at most 30 days; access tokens last at most 15 minutes. Registered client records and expired or revoked grant metadata do not currently have an automatic deletion schedule. Only the selected sites and their currently authorized, retained reports remain available to the connection.

Disconnecting and recipient retention. Use Disconnect in ChatGPT & AI Connections to block future requests and token refresh for that connection. Disconnect remains available when the preview is disabled or your workspace is removed from it. This does not delete search data already sent to ChatGPT, remove collected data from RankEcho, or revoke your Google authorization. OpenAI processes data received by ChatGPT under the terms and privacy settings of your ChatGPT account or workspace; its retention and deletion controls apply to those copies. Contact hello@rankecho.io for broader deletion requests. Infrastructure backups and operational logs are not immediately erased by disconnecting.

Aggregate benchmark use

RankEcho may use audit data in aggregate reporting. Public reports use anonymized results, exclude customer-level details, and state the cohort, unit, configuration, time window, exclusions, and uncertainty. Unlike audits and repeat domains are not presented as a representative industry estimate merely because a record count is reached.

Service providers

RankEcho may use infrastructure, AI model, database, email, analytics, queue, and storage providers to operate the service. Paid checkout uses Stripe; RankEcho records account and billing status data and does not request raw card details in its own forms.

Data security

RankEcho limits initial audits to public-domain inputs and applies controls including public-host validation, request limiting, and signed payment-event verification. No online service can guarantee absolute security.

Your choices

You can choose not to provide an email for a basic public-domain audit when the product allows it. For account, billing, privacy, or deletion questions, contact RankEcho support.

Contact

Email hello@rankecho.io for privacy questions. Business address: 6545 Market Ave. North, STE 100, Canton, OH 44721, USA. Phone: (216) 483-6918.

Last updated 2026-10-19.