SiteScout
PrivacyTerms & AUPDPAData notice / opt-out

Privacy policy

Last updated 2026-11-05

Template, not legal advice. Bracketed items are filled from the server's settings. Have a privacy lawyer review this before EU, UK or Canada outreach goes live.

This policy explains how [SiteScout legal entity] ([Registered postal address]) ("SiteScout", "we") handles personal data. It covers two groups of people: our customers (agencies and freelancers who use SiteScout) and the businesses our customers research and contact ("leads").

1. Who is responsible

  • For customer accounts, signup and billing data, SiteScout is the controller.
  • For lead data and outreach, each customer is the controller and SiteScout is their processor under our Data Processing Agreement. The customer decides which businesses to contact and approves every email.

Contact: privacy@sitescout.example

2. What we process and where it comes from

DataSourcePurposeLegal basis
Customer name, email, password hash, company, team membersYou, at signup / inviteProvide the service, security, supportContract
Billing status, plan, Stripe customer id (no card numbers)StripeSubscriptions, invoices, dunningContract; legal obligation (tax records)
Business name, address, phone, website, rating, reviews (place_id)Google Places API (official API only, no scraping)Lead research, scoring, demo previewsCustomer's legitimate interest (B2B prospecting)
Business email address + where and when it was foundThe business's own public websiteOutreach approved by the customer; proof of publicationLegitimate interest / inferred or implied consent where the law requires it
Website speed and mobile test resultsGoogle PageSpeed Insights; our own browser testOpportunity scoreLegitimate interest
Sent emails, approvals, unsubscribes (audit log)The serviceProof of compliance, abuse preventionLegal obligation; legitimate interest
Suppression entries (a one-way hash of an email or domain)Unsubscribes, objections, takedownsNever contact that business againLegal obligation

We do not buy lists, scrape Google, sell data or use lead data to train AI models.

3. Retention

DataKept for
Google Places content (other than place_id)Cache TTL per the Maps terms, then re-fetched or dropped
Leads never contacted90 days, then deleted (place_id kept only to avoid duplicates)
Leads contacted with no reply30 days for EU/EEA, UK and Canada; 180 days elsewhere
Replied leads and won clientsWhile the deal or client is active, plus 24 months
Suppression entries (hashed email or domain + reason)Indefinitely, so the opt-out keeps working
Demo preview sites30 days after they are built, unless the deal is won
Send and approval logs3 years (proof of compliance)
Customer account data after cancellation30-day export window, then deleted (billing records per tax law, held by Stripe)

An automated job deletes data when its period ends.

4. Your rights

Depending on where you are (GDPR, UK GDPR, the Philippine Data Privacy Act, Australian Privacy Act, CCPA/state laws, PIPEDA), you can ask for access, correction, deletion, restriction, portability, and you can object to processing, including direct marketing, at any time.

  • Businesses contacted through SiteScout: use the data notice page to opt out of all SiteScout customers' outreach or to have your data deleted. Every email also has a one-click unsubscribe link.
  • Customers: email privacy@sitescout.example.

You can also complain to your data protection authority.

5. Sub-processors and transfers

  • Hosting: [VPS provider and region]
  • Stripe (billing)
  • Postmark (account emails only, never cold outreach)
  • Google (Places API, PageSpeed Insights; Gmail API when a customer connects Gmail)
  • Microsoft (Graph API when a customer connects Microsoft 365)
  • LLM provider for drafting emails (Anthropic or OpenAI, if enabled)

Transfers outside the EEA/UK use Standard Contractual Clauses / the UK IDTA where needed.

6. Security

Data is separated per customer with database row-level security. Passwords are hashed (scrypt). OAuth tokens and API keys are encrypted at rest (AES-256-GCM). Access is logged.

7. Changes

We will tell customers by email before material changes take effect.

PrivacyTerms & AUPDPAData notice / opt-out