Skip to content

Privacy Policy

Last updated: 22 November 2026

WhoSaw ("WhoSaw", "we", "us") is operated by Ahmed Mustafa, an individual based in the Kingdom of Saudi Arabia. This policy explains what information WhoSaw collects, how we use it, and the choices you have. If you have questions, contact us at hello@whosaw.app.

Summary

  • If you connect Google Analytics, WhoSaw reads its data read-only to show you simplified reports. We never change anything in your Google account. Google Analytics is optional: checking how AI assistants see your website only needs its address.
  • We do not sell your data, use it for advertising, or use Google user data to train AI models.
  • WhoSaw itself never sends your Analytics data to an AI provider. It only reaches an AI assistant you connect yourself, such as Claude, when you ask it something.
  • You can disconnect Google or delete your account at any time.

1. Information we collect

1.1 From your Google account

When you sign in with Google, we receive:

  • Basic profile: your name, email address, profile picture and Google account ID (scopes openid, email, profile). We store your name, email address and account ID, not your picture.

  • Google Analytics data (read-only), if you grant it: through the https://www.googleapis.com/auth/analytics.readonly scope, we read:

    • the list of Google Analytics accounts and properties you can access, and their settings (such as time zone and website URL);
    • aggregated reporting data for the property you choose, such as visitor counts, visits, traffic sources, pages, devices, countries, cities and key events.

    Google Analytics reports are aggregated. We do not receive or store data that identifies individual visitors to your website.

    Granting this is optional. If you don't, or if you add a website without Google Analytics, we read none of this data for it; you can connect Google Analytics later.

  • An OAuth refresh token, which lets WhoSaw fetch updated reports without asking you to sign in each time.

1.2 Information you give us

  • Your website's address and, if you connect one, its Google Analytics property; your time zone (from the property, or from your browser for a website without Google Analytics) and your email settings.
  • Your brand name and the customer questions you choose to ask AI assistants.
  • On Growth and Studio, if you choose to, and on a lifetime plan, which requires them: the OpenAI or Perplexity API keys you add.
  • Messages you send to us.

1.3 Information from your public website

To check whether AI assistants can read your site, we fetch your robots.txt file and publicly available pages of the website you connect: your homepage, your pricing page and up to 5 more pages from your sitemap or your most visited pages. We fetch them as our own bot (WhoSawBot), and fetch your homepage again with the user agents of the AI assistants' search and answer bots. We store your robots.txt file, the text, title and descriptions found on each page, the results of the checks, and a screenshot of how each page looks.

To suggest customer questions you might track, we send the title, description and some of the text of up to 3 of these pages to an AI provider (see section 4).

1.4 The free AI check

Anyone can use the free AI check on our website without an account. It reads the robots.txt file and homepage of the domain entered. We keep the answer for that domain for 24 hours. To stop abuse, the check uses Cloudflare Turnstile, and we count checks per visitor using a hashed (not stored in clear) IP address.

1.5 Billing information

Payments are handled by Paddle.com, our reseller and Merchant of Record. Paddle collects your payment details, billing name, email address and country (and, where tax rules need it, your address or tax ID) under its own privacy policy. We receive your plan, billing status, and customer and subscription references from Paddle. We never receive or store your card number.

1.6 Technical information

We use cookies only to keep you signed in and to secure the sign-in process. We do not use advertising or third-party tracking cookies. The how-to videos in Settings load nothing from YouTube until you press play; once you do, YouTube may store information on your device under Google's policy (see section 4). Our application logs record events and errors with account and website IDs, not IP addresses; our hosting provider's request logs include IP addresses. To enforce request limits we keep counters keyed by a hashed IP address or your user ID.

2. How we use information

We use your information only to provide and improve the features you use:

  • to show your analytics dashboard, weekly brief and email summary;
  • to detect changes and write plain-language insights about your site's performance;
  • to check whether AI crawlers can access your site and what they can read;
  • to ask AI assistants your customer questions and report whether your brand is mentioned, and to suggest questions from your site's pages;
  • to send you service emails, including your weekly brief, which you can unsubscribe from;
  • to manage your plan and billing;
  • to keep the service secure, prevent abuse and fix problems.

3. Google user data: our commitments

WhoSaw's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

  • We use Google user data only to provide and improve the user-facing features described in this policy.
  • We do not sell Google user data, use it for advertising, or transfer it to data brokers or information resellers.
  • We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.
  • We do not allow humans to read your Google user data, except: with your explicit permission (for example when you ask for support), when necessary for security purposes such as investigating abuse, to comply with applicable law, or when the data is aggregated and anonymized for internal operations.
  • We transfer Google user data to third parties only as needed to provide the service (see section 4), to an AI assistant you connect yourself when you ask it something (see section 4), to comply with law, or as part of a merger or acquisition with notice to you.

4. Who we share data with

We use the following providers to run WhoSaw. They process data on our behalf and only for the purposes below, except Paddle, which acts as the seller of record for your purchase, and YouTube, which receives data directly from your browser, under its own policy, when you play a how-to video.

ProviderPurposeData involved
GoogleSign-in and Google Analytics accessProfile, Analytics data
VercelApplication hosting, and file storage (Vercel Blob)All data processed by the app; request logs with IP addresses; screenshots of your public pages; your data downloads, encrypted
NeonDatabase hosting (European Union, Frankfurt)Account data, encrypted tokens and keys
UpstashShort-lived cache and request limits (European Union, Frankfurt)Cached Analytics reports; request counters keyed by a hashed IP address or user ID; free-check answers
Trigger.devRunning scheduled background jobsAccount and website IDs needed to run each job, and each run's history
SentryError monitoring (European Union, Frankfurt)Technical details of errors. Email addresses, IP addresses, sign-in tokens and Analytics data are removed before anything is sent
ResendSending emails: the weekly brief, test emails and the account deletion confirmationEmail address, email content (for the brief, aggregated numbers and sentences from your reports)
PaddleReseller and Merchant of Record: checkout, payments, tax, invoices and refundsBilling details, purchase history
OpenAIAsking your customer questions; suggesting questionsYour questions; for suggestions, text from your public pages
PerplexityAsking your customer questions; suggesting questions when your own Perplexity key is the only one you addedYour questions; for suggestions, text from your public pages
CloudflareDomain name system, email forwarding, and Turnstile on the free AI checkEmails sent to our address; browser signals from free-check visitors
YouTube (Google)Playing a how-to video in Settings, only when you press play on itYour IP address and device and browser information, sent by your browser directly to YouTube. We use YouTube's privacy-enhanced mode (youtube-nocookie.com). YouTube handles this under Google's privacy policy

We only use AI providers whose API terms do not permit them to use this data to train their models. WhoSaw itself never sends your Analytics data to an AI provider: insight sentences in the dashboard and weekly brief are written by fixed rules in WhoSaw, not by AI. Your data only reaches an AI assistant you connect yourself, when you ask it something (below).

Your own AI keys. Solo and the free trial always use WhoSaw's API keys. Growth and Studio may use your own OpenAI or Perplexity API keys instead, and a lifetime plan must. When your own keys are used, your questions and question suggestions are processed by those providers under your own account, its settings and their terms, not ours. To check that a key works when you add it, we send one small request with that key.

Connecting WhoSaw to an AI assistant. If you connect WhoSaw to an AI assistant such as Claude, the assistant can read your WhoSaw data when you ask it something: your websites, weekly briefs, traffic summaries (which come from your Google Analytics) and AI visibility results. Only the data needed to answer your question is sent, and it goes to that assistant's provider (for Claude, Anthropic), which handles it under its own terms and privacy policy, not ours. The assistant can't change anything in WhoSaw or see your Google account. You can disconnect it at any time in Settings › Account, and deleting your account disconnects it too.

We do not sell personal information to anyone.

5. How we protect data

  • OAuth refresh tokens and your own API keys are encrypted at rest with AES-256-GCM, using a key stored separately from the database.
  • All connections to WhoSaw use HTTPS.
  • Access to production systems is limited to the operator of WhoSaw.

No system is perfectly secure, but we take reasonable measures to protect your information and will notify affected users of a breach as required by law.

6. How long we keep data

  • Account and settings: while your account is active.
  • Analytics reports: WhoSaw does not keep its own copy of your Analytics history. It asks Google Analytics for reports when you view them and keeps short-lived cached copies, for up to 7 days, to make the dashboard faster. Weekly briefs are kept while your account is active so past briefs can be viewed again.
  • AI readability checks: only the latest few checks. Older checks and their screenshots are deleted.
  • AI answers: 16 weeks, then deleted.
  • Data downloads: a file you ask for with "Download my data" is stored encrypted and deleted within an hour after its link expires, 24 hours after it's ready.
  • Connected AI assistants: a record of each connection (the app's name and when it connected and was last used) while it's connected, and for 30 days after you disconnect it. Its access codes are stored only as one-way hashes and expire within 30 days.
  • Request counters and free-check answers: request counters expire within 24 hours, and a free-check answer is kept for 24 hours.
  • Kept by our providers: Resend keeps sent emails (address and content) for 30 days. Trigger.dev keeps the history of background job runs, which holds account and website IDs, for up to 30 days. Sentry keeps error events, and Vercel keeps request logs, for up to 90 days.
  • After a free trial ends unpaid: when the 7-day trial ends without a plan, all scheduled work for your account stops: we stop reading your Analytics, sending the weekly brief, checking your site and asking AI assistants. We keep your data for 30 days in case you subscribe, then delete it as described for deleted accounts below.
  • After your plan ends: if you cancel, you keep access until the end of the month you paid for. When that month ends, we stop reading your Analytics and delete your data within 30 days.
  • After you delete your account: deletion starts as soon as you confirm. We revoke WhoSaw's access to your Google account and delete your account data, cached reports, screenshots and tokens within 30 days. Database backups are overwritten within a further 30 days. We keep a hashed (not readable) copy of your email address and the date of deletion for 2 years, to prevent abuse and for audit. Paddle keeps billing records, and we keep any we hold, for as long as tax law requires.
  • Free trial records: to allow one free trial per person and per website, we keep a one-way hash of your Google account ID, your Google Analytics property ID (if you connect one) and your website's domain, also after you delete your account, for 2 years.

7. Your choices and rights

  • Disconnect Google: you can revoke WhoSaw's access at any time at myaccount.google.com/connections. WhoSaw will then stop fetching new data.
  • Delete your account: use "Delete my account" in Settings, or email hello@whosaw.app from the address you signed up with. Deleting your account deletes your data as described above.
  • Access, correct or copy: use "Download my data" in Settings › Account to get a copy of everything WhoSaw keeps for your account and websites, as one ZIP file (JSON, and CSV for tables). We email you a link that works for 24 hours, only while you're signed in, up to twice a day. It leaves out your Google token and AI keys, and Google Analytics reports, which WhoSaw doesn't keep. You can also email us to ask for a copy or to correct your data.
  • Emails: every weekly brief email includes a one-click unsubscribe link.

Depending on where you live, including under the Saudi Personal Data Protection Law and the EU General Data Protection Regulation, you may have additional rights, such as objecting to processing or complaining to a data protection authority. To exercise any right, email hello@whosaw.app. We will respond within 30 days.

8. International transfers

WhoSaw is operated from Saudi Arabia. Our database is hosted in the European Union, and some providers listed above may process data in other countries, including the United States. We rely on our providers' contractual and security commitments to protect data when it is transferred.

9. Children

WhoSaw is a business tool and is not directed to anyone under 18. We do not knowingly collect personal information from children.

10. Plans

WhoSaw is offered on three paid plans, Solo, Growth and Studio, a 7-day free trial on Solo's limits, and a lifetime plan for some accounts. This policy applies the same way to every plan and to the trial. Which plans use your own AI keys is described in section 4.

11. Changes to this policy

If we make material changes, we will update the date above and notify you by email or in the app before the changes take effect.

12. Contact

Ahmed Mustafa, operator of WhoSaw Kingdom of Saudi Arabia Email: hello@whosaw.app