Rankawy
Legal

Privacy Policy

Last updated: 2026-11-11

We collect the least data that lets us provide the service. This page explains plainly what we collect and why, and what you can ask of us at any time.

01AI question suggestions and brief summaries

OpenAI processes your site’s public page titles, descriptions and headings on our behalf to suggest questions when requested, and we ask the provider not to store the request. We also send the site type, country and a brand name evidenced on the public page. Search Console and GA4 data never go to any AI model. Suggestions and their facts remain in your account until the site is deleted; matching sets are reused for 30 days. This request does not prevent limited abuse-monitoring retention under the provider’s policy.

For content brief summaries we send only eligible competitors’ public page titles, descriptions and headings, with the target keyword, language and country. Your pages and connected-account data stay outside this request. Facts and summaries remain with the brief until it or the site is deleted; matching summaries are reused within your organization. We ask the provider not to store the request; limited abuse-monitoring retention may still apply.

02Who we are

Rankawy is a search engine optimization (SEO) platform with services delivered by our team. It is operated by Rankawy, Inc. ("we" or "us").

We are responsible for the personal data we collect through rankawy.com, the Rankawy app, our emails, and our free tools; in data protection terms, we are the "data controller."

03Scope of this policy

This policy covers visitors to our site, account holders and the members of their teams, users of our free tools, and anyone who writes to us.

If you add data about your own clients to the platform (such as their sites or their Search Console data), you are responsible for having a lawful basis to share it with us, and we process it on your behalf and only to provide the service to you. Managed-service contracts may add terms that complement this policy.

This policy does not cover sites we link to. If you place an agency check widget on your site, the widget section below explains how visitor data is handled; otherwise we install no code on your site, and we read its public pages only when you ask us to audit it.

04The data we collect

Account data

Your name, email address, and password (kept by our sign-in provider as a one-way hash that we never see), interface language, your photo if you upload one (stripped of location and camera data, and deleted as soon as you remove or replace it), the role you choose during onboarding, your SEO experience level, the AI assistant you use if you choose to answer, your organization name, each member's role, and the email address of anyone you invite to your team. If an agency uploads its logo for branded reports and client access, we store and serve that logo until the agency removes or replaces it.

Data about your sites

The domains you add, the markets you follow, the keywords, competitors, your brand names, your site's type and goals, audit and ranking results, a daily record of your site's health and score, the notes you write on the timeline, and the reports you create. The email DNS check stores the sender domain you check and the public DNS result for that domain. When we audit your site, we read its public pages as any visitor would, and we follow its robots.txt.

WordPress connector

When you explicitly connect the read-only WordPress connector, a device-authorization record stores, for up to 1 day, the site's home address, the normalized identifier of a detected SEO plugin, hashes of one-time codes and the PKCE challenge, the identity of the approver, the organization and project binding, and timestamps. An active connection stores the site address, the plugin identifier, one-way hashes of credentials and the ownership challenge, and the last-use time. Raw credentials and verification values remain in WordPress. Revoked or expired credential-hash rows are deleted after 30 days; connection and ownership-challenge metadata remains until the connected site or account is deleted.

Google data (only when you connect it)

When you connect Search Console or Google Analytics we ask for read-only access, plus the email address of the Google account to identify the connection. We keep the access token encrypted in a dedicated vault that only our server reads, and import performance data: queries, pages, clicks and impressions, and sessions by channel and landing page. We do not import revenue data.

Payments and billing

Stripe processes your card directly; its full number never reaches or stays on our servers. We keep your plan, subscription status and dates, your invoices, and the billing details you enter (legal name, country, address, tax number, commercial registration). To apply the "one free trial" rule we keep a one-way hash (SHA-256) of the card identifier Stripe gives us and of your email address, and whether the card is prepaid.

Free tools

For the free site checker we keep the domain you check, the result, and a keyed hash of your IP address to apply usage limits. For the AI-visibility snapshot we keep your email address to send you the result link, the brand and topic, and the engines' answers. AI glimpses store no email address or topic; we store your email and business topic when you request the full report.

If you ask for a reminder to re-check in 7 days, we keep your email address, the domain, the check's score, the language of the messages and a keyed hash of your IP address. We send a confirmation and send the reminder only after you click its button, then one reminder 7 days later. Resend delivers them, and we use your email for nothing else.

Agency site-check widgets

When you use an agency's embedded check widget, the agency is the controller and Rankawy processes the data on its behalf. Before consent, we keep the website address and check result for up to 30 days, and reveal only the score, issue counts by severity, and the number of pages checked. If you explicitly consent, we also keep your email, optional name, consent version, the agency name shown to you, the time, locale, lead status, and repeat-submission count for up to 12 months after the last submission. We reveal the issue details and PageSpeed result inside the widget, notify the agency's selected verified members, and do not email you.

The widget uses a service to check abuse, sends the checked website URL to PageSpeed to measure its performance, and uses our email delivery service for agency notifications. We do not use an AI model for these checks, do not sell widget data, and do not expose one agency's leads to another. Ask the named agency to exercise your rights; it can update or delete the lead in its workspace, and Rankawy will assist it.

Rankawy newsletter

The weekly newsletter carries what is new in Rankawy, picks from the SEO Guide, Google updates and the Arabic Search Index numbers. If you subscribe, we keep your email address, the language of the emails, your subscription status (awaiting confirmation, confirmed or ended), and the page you subscribed from; a keyed hash of your IP address is kept for two days only, to apply usage limits. Nothing is sent until you press the confirmation link in your inbox, and every email lets you unsubscribe in one click. Resend delivers the emails; we use your address for the newsletter only and never share it.

Contact and support

What you write in the contact form or a support ticket: name, email, company, phone, website, message and attachments. When you request a Custom plan, we keep the plan configuration, name, email, company, site and optional phone number in the quote-request record for up to 12 months so we can answer the request and prepare the appropriate quote. A copy goes to our support inbox and follows support-ticket retention: as long as needed to follow up your request and protect legal rights; deleted on request unless a legal obligation prevents it.

Sign-up source

When you create your account we record how you reached us: the campaign parameters in the link (utm), the referring site's domain without the full link, the first page you visited, a partner code if any, your approximate country and city as Cloudflare's network determines them (we do not keep the IP address), device type and interface language. We also keep your optional answer to "How did you hear about Rankawy?" and your cancellation reason if you choose to give one.

If you reached us through one of our partners' links, we link your account to that partner to compute their commission on your paid subscriptions. We never give the partner your email or your site's data; they only see the number of accounts and the amounts.

Partner program

A partner application contains the applicant's name, legal name, email, country, partner type, primary audience URL, promotion method, proposal, preferred payout method, and the accepted terms version. For an approved partner, we keep program membership, aggregate daily link visits without cookies, referrals, commission adjustments, immutable payout statements, and transfer references. At the first payout, we compare one-way normalized email hashes to prevent self-referrals. For tax forms, we keep only the type, status, and validity date—not the document itself.

We may ask you an optional in-app question about Rankawy and its main benefit to you. We keep your answer with your account and read the answers in aggregate to decide what to build.

Usage data

We use PostHog to understand how the product is used: the pages you visit, clicks, session length, browser, device and operating system, and approximate location. We may record sessions in masked form, with every text and field hidden, and links stripped of tokens and identifiers before they are sent. Inside the app we link this data to an internal identifier of your account and organization, never to your email address. Visitors in Europe are measured without any cookie.

Emails

We record the delivery of our emails, as well as opens and clicks on their links. For opens and clicks, we record only the class of email client, without the IP address.

Technical and security logs

Our servers and infrastructure providers log technical data such as IP address, browser type and request time, to protect the service, prevent abuse and diagnose faults. Our public forms use Cloudflare Turnstile to tell people from automated programs.

When enabled, monthly rank updates go to paid-account owners and admins. They contain tracked keywords, accepted readings and comparisons, ranking pages, stored search volume and result features, and Search Console click and impression totals when connected. We keep the figures shown in the email log for 13 months, with delivery, open, click and unsubscribe events. You can stop this kind alone using its email link or My account email settings. A hard bounce or complaint suppresses digests, alerts, monthly rank updates, tips and scheduled reports.

05Why we use your data and on what basis

PurposeDataLegal basis
Providing the service and running your account and teamAccount, sites, and Google dataPerformance of our contract with you
Subscriptions, invoices and taxesPayments and billingContract, and legal obligation
Protecting the free tools and the free trial from abuseIP hash, trial hashes, logsLegitimate interest
Answering your requests and providing supportContact and supportContract, or your request
Service emails: alerts, invoices, renewal reminders, the weekly summary, and first-steps tipsEmail and site dataContract, and legitimate interest
Improving the product and learning what helps usersUsage data, sign-up source, cancellation reasonsLegitimate interest, and consent where the law requires it
Complying with the law and answering competent authoritiesOnly what that requiresLegal obligation

06What we never do with your data

  • We do not sell or rent your personal data, or share it for targeted ads.
  • We do not send your Search Console or Google Analytics data to any AI model, or use it to train any model.
  • We do not show your site's data to other customers. We may temporarily cache public market data, such as a keyword's search volume or its search-result rankings, and use it for more than one customer; it contains none of your private data.
  • We do not write anything to your site. Every connection to your site or accounts is read-only.
  • We currently run no advertising-platform trackers on our site. If we add any later, they will run only with your consent, and we will update this policy first.

07Google API data

In using information received from Google APIs and transferring it to any other app, Rankawy follows the Google API Services User Data Policy, including the Limited Use requirements:

Rankawy's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
  • We use Google data only to show you your reports and analysis inside Rankawy.
  • We do not use it for advertising, sell it, or transfer it to others except as needed to provide the service or as the law requires.
  • No one on our team reads it except with your permission, for security, or under a legal obligation.
  • You can disconnect from inside Rankawy, or revoke access in your Google account settings, at any time.

08Who we share your data with

We rely on service providers who process data on our behalf, under contracts that require them to protect it and not to use it for their own purposes:

ProviderServiceDataWhere
SupabaseDatabase, sign-in and file storageMost of the data aboveEuropean Union (Ireland)
CloudwaysApplication hostingData while it is being processed, and technical logsThe hosting provider's data centers
BrowserlessCloud PDF printingThe report page requested for printing and a technical request logAccording to the service plan and terms
OpenAISuggesting questions when requested and preparing content brief summariesYour site's public page titles, descriptions and headings, site type and country for questions; competitors’ public page titles, descriptions and headings, target keyword, language and country for brief summariesUnited States
CloudflareContent delivery, protection, and Turnstile verification; customer-site analytics event ingestion and raw storage for 3 monthsIP address and request dataGlobal network
StripePayments, subscriptions, tax and invoicesPayment and billing data, emailUnited States
ResendEmail deliveryEmail address, message content, delivery eventsUnited States
PostHogProduct usage analyticsUsage data and an internal identifierEuropean Union (Germany)
GoogleSearch Console and Google Analytics integration, and page speed measurementThe data you authorize, your public page URLsUnited States
Search data providersSearch results, keyword volumes, backlinks, and AI engine answersKeywords, domains, markets, and templated questions; no personal dataVarious

When you download a PDF report, we send the report page requested for printing to a cloud-based PDF printing service (currently Browserless). The service uses the content to create the file and may keep technical request logs, such as the address of the page requested for printing and the request time, for a limited period according to its plan. We keep the generated PDF in private Supabase Storage for up to 31 days, as a daily job deletes files more than 30 days old.

We also share data in these cases:

  • With the members of your organization in Rankawy, according to their roles.
  • With anyone you send a report link to: whoever holds the link sees the report, and we record only the time of the view and the device type.
  • With the writer you send a content brief link to: whoever holds the link sees the writer's copy and your notes for them, and we record only how many times it was opened.
  • With an AI app that you connect to your account through the "MCP connect" page: with your permissions, it reads your sites, audit results, action plan, rankings, and alerts. It reads Search Console and Google Analytics data when your account plan includes them and you explicitly allow it. If your account plan includes paid research tools and you ask the app to use them, we deduct credits after you agree. Its processing is subject to the app provider's policy; we log every request it makes, and you can turn off permissions or disconnect at any time.
  • With competent authorities when the law requires it, or to protect our rights and our users' safety.
  • With a company that acquires or merges with Rankawy, which must honour this policy; we will tell you beforehand.

09Transfers outside your country

Rankawy is a US company, and our service providers are in the United States and the European Union, so your data may be processed outside your country, whether you are in Saudi Arabia, the UAE, Egypt, or elsewhere. We protect these transfers through data processing agreements with our providers, standard contractual clauses where applicable, encryption, and by transferring as little data as possible. Where the law of your country requires additional safeguards for a transfer, we apply them, and you can ask us about them.

10Cookies and similar technologies

NamePurposeDuration
sb-…-auth-tokenKeeping you signed in and protecting your sessionUntil you sign out or the session ends
rk_ft and rk_ltThe source of your first and most recent visit, linked to your sign-up. Not set for visitors in the EU or the UK.90 days
rk_siteRemembers the last site selected in the app. Contains only the site UUID.90 days
rk_hintRemembers that you signed in on this browser so the header can show the dashboard button. It carries no identifier.90 days
rk_skip_<site>Remembers the optional steps you chose “Not now” for on your site's dashboard. It carries no identifier1 year
rk_onboarding_stage1 and rk_ai_quizRemember that you skipped an optional onboarding question in this browser. They carry neither your answer nor any identifier about you1 year
rk_gu_hideRemembers the Google update whose line you hid on your dashboard, so it does not show again. It carries no identifier60 days
rk_learn_progress_v1 (local storage)Stores each SEO roadmap node as done, learning or skipped. It stays in your browser and is not linked to your accountUntil you clear it in your browser
ph_…_posthog and its local-storage equivalentUsage analytics. Visitors in Europe are measured without any cookiesUp to 12 months
__stripe_mid and __stripe_sidFraud prevention on the payment page only, set by Stripe1 year / 30 minutes
__cf_bm and similarProtecting the site from automated programs, set by CloudflareUp to 30 minutes

You can delete or block these files in your browser settings. Blocking the sign-in cookies stops you from using your account; blocking the analytics files does not affect the service.

The customer-site analytics tag uses no cookies or browser storage. The site owner remains responsible for choosing a lawful basis and informing visitors.

11How long we keep your data

DataRetention
Account, site data and reportsWhile your account exists; deleted within 30 days of a deletion request
Search Console and Google Analytics archiveWhile your account exists; deleted on request, or when you connect another property in place of the previous one
WordPress device authorizations, connection metadata and credential hashesDevice authorizations: up to 1 day. Revoked or expired credential-hash rows: 30 days. Connection and ownership-challenge metadata: until the site or account is deleted
Free checker results30 days
Generated report PDF filesUp to 31 days
AI visibility snapshot and its associated email address90 days
Re-check reminder emailDeleted within 7 days if never confirmed, otherwise within 30 days of the reminder date
Newsletter subscriber emailWhile the subscription lasts; deleted within 7 days if never confirmed, and within 30 days after unsubscribing
IP hash for usage limits2 days, or with the check or snapshot it belongs to
Email log and shared report views13 months
The two visit-source cookies in the browser90 days; the sign-up source stays with your account
Usage data in PostHogUp to 12 months
Invoices, subscription and payment historyAs long as tax and accounting law requires
Hashes that prevent repeated free trialsAs long as needed to prevent trial abuse
Support ticketsAs long as needed to follow up your request and protect legal rights; deleted on request unless a legal obligation prevents it
Custom-plan requests and quotesRequests and unaccepted offers: up to 12 months from the request date. Accepted offers: as long as tax and accounting rules require, with the payment records
Rejected partner applications12 months from the decision
Approved partner membership, acceptances, statements and tax-form statusFor the duration of the program relationship, and then as long as tax, accounting, and legal record-keeping obligations require
Aggregated partner-link visit counts24 months; no IP address, browser type, or referring page is stored with a visit
Saved access-log summaries90 days from saving; an authorized member can delete them earlier, and they are deleted with the site or account
Daily save counters for access-log summaries (site, date and number of saves)Deleted by the daily cleanup once the UTC day after the save day has ended: at most 52 hours from the start of the save day, or 76 hours if one cleanup run is missed

12How we protect your data

  • Connections to the site and the app are encrypted (TLS), and the database is encrypted while stored.
  • Each organization's data is isolated at the database level, so no user can reach an organization they do not belong to.
  • Google tokens are kept in an encrypted vault, share and invitation links only as hashes, and IP addresses only as keyed hashes.
  • Access to personal data in production is limited to the fewest possible members of our team, and sensitive actions require two-step verification.
  • If a breach affects your data, we notify the competent authorities within the period set by law, and notify you without undue delay.

No system is perfectly secure, but we keep reviewing and improving our measures.

13Your rights

Depending on the law that applies to you, such as Saudi Arabia's Personal Data Protection Law, the UAE Personal Data Protection Law, Egypt's Personal Data Protection Law No. 151 of 2020 and the EU General Data Protection Regulation, you have the right to:

  • Access your data and receive a copy.
  • Correct inaccurate data or complete it.
  • Have your data deleted, unless the law requires us to keep it.
  • Port your data: you can export your sites' data as CSV from inside the app.
  • Object to, or ask us to restrict, processing based on legitimate interest, such as analytics.
  • Withdraw your consent at any time, without affecting processing done before you withdrew it.
  • Stop emails that are not necessary for the service.

We do not make automated decisions about you with legal effect. Rankawy's scores and ratings measure sites only.

To exercise any of these rights, write to us through the contact form and choose the “Account and privacy” topic. We may ask you to verify your identity, and we will respond within 30 days, or sooner if your country's law sets a shorter period. You may also submit a complaint to the data protection authority in your country, such as the Saudi Data and AI Authority (SDAIA), the UAE Data Office, Egypt’s Personal Data Protection Center, or the data protection authority in your European country.

14Emails we send you

We send emails necessary to provide the service: account confirmation, invoices, renewal reminders, trial ending notices, cancellation confirmations, and replies to your tickets. We also send a weekly summary about your site, which you can stop at any time from a link at the bottom of the email or from your dashboard. We send marketing emails only with your consent.

15Minors

Rankawy is intended for businesses and may not be used by anyone under 18, or under the age of majority in their country. If we learn that we have collected a minor’s data, we delete it.

16Organizations and teams

An organization’s owner and admins can see members’ names, email addresses, and roles, and can invite and remove members. Data added to an organization stays there if a member leaves, and the member’s personal account remains active until they ask for it to be deleted.

17Custom plan

When you accept a Custom plan offer, we retain the plan's configuration, price, billing period, pricing version, the time you accepted, the terms version and a fingerprint of the renewal text we showed you, linked to your account and invoices, to administer the subscription and document the agreement.

Quote requests and unaccepted offers are kept for up to 12 months. Accepted offers and payment records are kept for as long as tax, accounting and legal record-keeping obligations require.

If you choose the monthly call, the booking link opens Cal.com to arrange a Zoom appointment. Those services receive what you enter there under their own privacy policies. We store only the booking link and do not import booking details or call recordings.

If you contact your account manager through WhatsApp, WhatsApp processes contact and conversation information under its privacy policy.

18Changes to this policy

We may update this policy when our services or applicable laws change. The date of the latest update is shown at the top of this page, and if a change is material, we will notify you by email or in the app at least 30 days before it takes effect.

19Contact us

For any question about your privacy or your data, write to us through the contact form and choose the “Account and privacy” topic.

20Customer site analytics

When you install site analytics, we process minimized and pseudonymous data on your behalf: host and redacted page path, redacted UTMs, channel and source, referrer hostname, country, device category, goal kind and outbound hostname only, and navigation response status. We use IP and user agent transiently to produce a project-specific daily pseudonymous identifier with a random salt; we do not store IP or user agent. No cookies, browser storage, fingerprinting, page content, form values, phone numbers or email addresses are collected. Raw events last 3 months, salts up to 48 hours, and daily aggregates follow plan retention. Pixel data never reaches AI models or MCP. The site key is visible in page source like every analytics tag, so counts may include forged or automated events. Rankawy filters known bots, requires browser request signals, applies rate limits and a daily cap of 300 retained pageview events and 60 retained goal events per source before sample weighting, and excludes detected events. Filtering may be incomplete within processing limits; a notice is shown when this happens. We cannot guarantee every event comes from a real visitor; counts are estimates. Rankawy's public pages use the same pixel under the same rules to measure their own visits; it does not run inside the app.

21Access-log analysis

When you select an access log or a Cloudflare log export, your browser processes the file on your device. Rankawy does not upload or retain the original file, client IP addresses, complete User-Agent strings, referring-page URLs, authenticated-user fields, cookies, request bodies or query strings. For requests naming a crawler, IP addresses are used temporarily in browser memory for comparison with IP ranges published by the crawler owner. A match alone does not prove the sender's identity.

If you choose to save the summary, Rankawy stores crawler names, daily request counts, counts by response status and IP comparison result, the URL paths you choose to keep without query strings, file-coverage indicators and counts of lines by parsing outcome, IP range list fetch dates, and the account/site identifiers needed to secure the summary. Paths can contain personal information; review them before saving and exclude sensitive paths.

Saved summaries are available to authorized members of your organization and authorized client viewers. They expire after 90 days and can be deleted earlier by an authorized member. Rankawy does not send these summaries to AI models, publish them, or expose them through MCP in this version.