Early Black Friday access100k credits · $199→
RankParse

Privacy Policy

Last updated: October 1, 2026

This policy explains the information used by RankParse’s SEO tools, connected services, and automation features, who receives it, and how you can control it.

Who we are and what this policy covers

  • RankParse is operated by Autodeus Technologies Pvt Ltd. This policy covers our website, dashboard, SEO APIs, MCP connections, browser extension, and optional connected services. Contact support@rankparse.com with privacy questions or requests.
  • We handle account and service-operation data to run RankParse. When you submit contacts, campaigns, website data, or other personal information on behalf of a business, that business is responsible for its instructions and the lawful use of that information. We process it to provide the requested service.

Account, billing, and support data

  • We collect your email address, account identifier, account creation date, sign-in provider details, and any name, avatar, business role, or branding settings you provide. We also store onboarding preferences and connection status so the dashboard can show your setup and activity.
  • If you sign in with Google or GitHub, we receive the profile information and authorization information supplied by that provider. Email sign-in uses a time-limited verification link. Authentication cookies are necessary to keep you signed in.
  • Stripe processes payments. RankParse stores customer and transaction identifiers, purchases, credit balances, and billing settings. If you enable automatic recharge, we store its settings, a Stripe payment-method identifier, and the last four digits of the card. We do not store full card numbers or card security codes.
  • Referral features store attribution, commissions, withdrawals, and payout details you provide. Wix installation or purchase features store the installation and purchase identifiers needed to connect your entitlement.
  • When you contact us or submit a directory listing, we receive the information you send, which may include contact details and a website. We use it to respond, review the submission, and maintain the service.

SEO requests and service activity

  • We process the domains, public page URLs, keywords, filters, and other task-specific inputs you submit through the website, API, extension, or an MCP client. Results can include backlinks, anchor text, page metadata, website technologies, registration data, and search performance information.
  • Usage records can contain your account identifier, requested endpoint or tool, target domain or URL, timestamp, credits used, request source, and success or error information. We use these records for credit accounting, troubleshooting, security, abuse prevention, and product measurement.
  • Cloudflare and our application process IP addresses and request metadata for security, bot detection, and rate limiting. Some authentication and error logs can include an account identifier, email address, or IP address. We do not use these records for cross-site advertising profiles.
  • Public web data can contain personal information, including names or contact details in page text, URLs, or registration records. Being publicly accessible does not make information non-personal. Please avoid submitting private information in URLs or page content unless it is necessary for an authorized task.

MCP connections and AI clients

  • An MCP client sends the tool name and arguments selected for your request. RankParse processes those explicit inputs and returns the relevant results to that client. Our MCP server does not request or reconstruct your full conversation history.
  • The secure OpenAI directory connection exposes 23 read-only SEO and account tools. Its permissions are SEO data access, credit-balance access, and optional permission to stay connected. It does not grant access to Gmail, Google Ads, search-console integrations, or social outreach. Other RankParse API and MCP workflows can support additional actions under their own credentials and permissions.
  • For OAuth connections, we store authorization records binding your account to the client, permitted scopes, token expiry, and revocation state. Access tokens are valid for 15 minutes; refresh tokens are valid for up to 30 days and can be replaced during continued use. Authorization requests expire after 10 minutes and authorization codes after 60 seconds. Token validity is separate from the retention of connection and security records.
  • You can revoke secure MCP connections from the dashboard connection controls. For a client using a RankParse API key, revoke the key in RankParse and remove it from that client. The client provider, such as OpenAI or Anthropic, separately handles the conversations, inputs, and outputs you share with it under its own privacy policy.
  • Enter credentials only in the appropriate sign-in or integration settings. Do not place passwords, API keys, one-time codes, payment card details, government identifiers, or health records in SEO tool arguments or chat prompts.

Connected search, advertising, and indexing services

  • Optional connections to Google Search Console, Bing Webmaster Tools, and Yandex Webmaster provide account labels, website properties, permissions, and website performance data. We store selected properties, tracked queries, clicks, impressions, average positions, top pages, device and country breakdowns, sync status, and alerts where the provider supplies them.
  • Google Search Console requests read-only webmaster access. Google Ads uses the permissions shown by Google; its authorization scope has no read-only variant. The current RankParse Ads features retrieve advertising and keyword information. We store connection identifiers and encrypted integration tokens to make authorized requests.
  • When you request indexing or inspection, we send the relevant website or URL to the selected search provider. IndexNow submissions include the host, submitted URLs, and the site-verification key; we may fetch the public key file to verify the submission. We retain submitted URLs and status information for your dashboard.
  • Disconnecting a search provider removes its local credentials and stops future synchronization. Previously synchronized records are not necessarily erased by disconnecting or archiving a website. Use account deletion or contact support@rankparse.com to request removal of retained data. You can also revoke access in the provider’s own account settings.

Outreach and optional social automation

  • If you use outreach, we store the campaign information, instructions, contact names and email addresses, domains, message subjects and bodies, queue settings, and send status you or your agent provide. These may be personal information about other people. You are responsible for having the right to use these contacts and for complying with applicable messaging rules.
  • Gmail connection requests permission to send messages and identify the connected email address. It does not request mailbox-read or draft-management permission. When you enable sending and queue a campaign, recipients and message content are sent through Gmail to the intended recipients. We retain sending records to show status and help prevent duplicate outreach.
  • Archiving or pausing a campaign stops its queued activity but does not erase its contacts or history. Gmail disconnection clears locally stored tokens; connection settings and campaign records may remain so you can manage them. Messages already delivered remain with recipients and the email provider.
  • If you connect Zeekeo for social automation, your requested campaign information, profile URLs, recipients, templates, and message content are sent to Zeekeo to carry out the action. Zeekeo and the destination service handle that data under their own terms and privacy policies. Disconnect the integration to remove its locally stored credential.
  • RankParse’s OpenAI directory SEO connection cannot invoke these outreach or social actions. Connecting that plugin alone does not authorize them.

Recipients and external requests

  • Cloudflare provides hosting, database and object storage, caching, authentication email delivery, security, and bot protection. Stripe handles payments, and Wix receives or supplies installation and purchase information when you use our Wix integration.
  • Google, Microsoft/Bing, Yandex, Gmail, and Zeekeo receive the information needed for the particular integration or action you choose. An external website receives a request when you ask us to audit or fetch its public page.
  • Some SEO tools send the target domain or URL to external data providers: registration/RDAP services for domain enrichment, the Internet Archive for crawl history, and Google PageSpeed Insights for performance analysis. Tool descriptions identify live fetches or external enrichment. These providers can observe the requested target and our network request.
  • PostHog receives product and service events as described below. Google Analytics receives consented website analytics. Internal signup notifications may send an account email address and signup source to Slack for our team to operate the service.
  • Profile images may be loaded from your sign-in provider, your chosen avatar URL, or Gravatar. Gravatar requests use a hash of your email address rather than the plain address; the hash can still be a personal identifier. Image hosts receive normal browser request information.
  • Authorized personnel and service providers may access data to deliver support, administer the service, or investigate security and billing issues. We may disclose information where legally required or necessary to protect rights and investigate abuse. We do not sell personal information or share it with third parties for their own marketing.

Analytics

  • Optional browser analytics use Google Analytics 4 and PostHog to measure page views, interactions, navigation, browser/device information, and errors. Page addresses and interaction metadata may be included, so avoid placing sensitive information in URLs. PostHog can associate these events with your account identifier and email when you are signed in. Browser capture is opted out by default and enabled when you accept analytics.
  • Google Analytics uses browser cookies. PostHog uses localStorage for browser persistence, and we store your analytics choice locally. Necessary session and security storage is separate from optional analytics.
  • Our server also sends account signup, onboarding, API-key activity, and API-use events to PostHog when configured. These events can include an account identifier, signup email, endpoint, target domain, credits consumed, source, and success/error details. Server events are separate from optional browser analytics and currently do not depend on the cookie-banner choice.
  • Use Cookie preferences in the footer to reopen the analytics choice and decline future optional browser capture. Declining does not erase previously collected events or disable server events. Contact support@rankparse.com to request access, deletion, or object to account-linked measurement; we will assess the request and explain any records needed for service operation or legal obligations.

Browser extension

  • On-page analysis reads page HTML to extract SEO metadata, headings, links, and images locally in your browser. The local analysis does not upload the page HTML to RankParse.
  • Domain lookups send the requested domain to RankParse. Optional toolbar badges, metrics bars, and search-result metrics can automatically request domain data when enabled. The toolbar badge can react to navigation on public websites; search-result features read domain names from Google results. You can disable these features or exclude domains in extension settings.
  • We do not receive your complete browsing history from the extension, but enabled lookups can produce account-linked records of the domains queried. Free lookups also send the domain and normal network request metadata.
  • Your API key, preferences, excluded domains, cached account email and credit balance, and domain results can be held in local extension storage. Cached domain results are reused while less than 24 hours old; that freshness period does not guarantee physical deletion of older entries. Clear extension storage or uninstall the extension to remove local data.

Retention and account deletion

  • Account profiles, settings, connection metadata, submitted URLs, and campaign/contact records are retained while needed for your active account or the feature you use, unless you delete them or request their removal. Archiving normally preserves records; it is not deletion.
  • Our retention policy for API usage logs is 90 days. Search daily metrics, device/country breakdowns, appearance data, and derived alert events have a 400-day retention window. Completed search synchronization runs have a 30-day window. Scheduled cleanup can take additional time to clear eligible records in bounded batches. Other search configuration and latest-state records remain until removed with the associated account or feature.
  • Account deletion includes a 14-day cancellation period. API keys are revoked when deletion is requested, and connected-service credentials are cleared during disconnection or account purging. Active account data is scheduled for deletion or removal of identifying profile fields within 30 days of the request. You can cancel during the grace period before purging begins.
  • A recovery snapshot may be kept for up to 30 days after the account purge to recover from operational errors. It is separate from your active account and is not used to restore normal access without an authorized recovery request.
  • We retain limited billing, tax, referral accounting, fraud-prevention, and reconciliation records where needed to meet legal obligations or resolve disputes. These can include payment-provider identifiers and records involving another customer; deleting an account does not erase records held independently by Stripe or other recipients.
  • Analytics, security logs, caches, and infrastructure recovery copies have separate provider-specific retention and deletion settings. Contact support@rankparse.com for the applicable period or a deletion request. Revoking an integration stops future access but does not recall data already delivered to a client, recipient, or external service.

Security and international processing

  • We use HTTPS for service connections, hashed RankParse API keys, encrypted product-integration credentials, and account access checks. These controls reduce risk but cannot guarantee that every transmission or storage system is completely secure.
  • RankParse uses Cloudflare’s global network and US-based storage and analytics services. Your information may be processed in India, the United States, and other countries where our providers operate. A request’s processing location and each provider’s storage location may differ.
  • Where applicable law requires a safeguard for an international transfer, the relevant service agreement and transfer mechanism must apply. Contact support@rankparse.com for information about our processing arrangements or a customer Data Processing Agreement.

Your choices and rights

  • You can update your profile and preferences, revoke API keys or secure MCP access, disconnect integrations, pause outreach, and request account deletion from the dashboard. Use the footer’s Cookie preferences to manage optional browser analytics and extension settings to manage automatic domain lookups.
  • You can request access, a copy, correction, or deletion of your personal information by emailing support@rankparse.com. People whose contact information or public-page information appears in RankParse can also contact us. We may verify your identity and the information involved before acting. We aim to respond initially within 5 business days and handle requests within the period required by applicable law.
  • Where applicable, you can withdraw consent, object to processing, request restrictions or portability, and complain to your local data-protection authority. Withdrawing consent does not affect processing that was lawful before withdrawal. Some information may need to remain for a legal obligation or to protect another person’s rights.
  • For EU/EEA users, we rely on contract necessity for account and requested service delivery; consent for optional browser analytics; legitimate interests for proportionate security, abuse prevention, support, and service measurement; and legal obligations for required accounting records. Customer-submitted personal data is processed under the customer’s lawful instructions and applicable agreements.
  • We use your account email for sign-in, billing, security, and requested service notifications. Promotional messages include an unsubscribe option; opting out of promotions does not stop necessary transactional messages.

Changes to this policy

  • We will update this page as the service and its data practices change. For material changes, we will notify affected account holders by email at least 14 days before the changes take effect. The date at the top identifies this version.