Privacy Policy

PixyScan is a continuous SEO monitoring service. You give us a website address; we crawl it on a schedule you control and report technical SEO problems we find.

The service is operated by {LEGAL_ENTITY_NAME}, registered at {REGISTERED_ADDRESS}. For anything in this policy, contact us at {PRIVACY_CONTACT_EMAIL}.

For the data you put into PixyScan, we act as a processor: you decide which sites are scanned and why. For your account and billing details we act as a controller.

Three categories, and nothing else.

2.1 Your account

Your name, email address, and a password stored only as a bcrypt hash — we cannot read your password, and a reset is the only way to recover access. If you sign in with Google, GitHub, GitLab or Bitbucket, we store that provider’s user ID instead of a password. We also keep session tokens so you stay signed in across devices, along with the time each session was last refreshed.

2.2 Your workspaces and sites

Workspace and site names, the addresses of the sites you have asked us to scan, your crawl settings (page limits, URL exclusions, which checks are enabled), your schedules, and who you have invited. We record a history of changes to a site’s configuration so you can see who changed a setting and when.

2.3 What our crawler reads from your site

This is the largest category and the one worth being precise about. When we scan a page we store the technical SEO signals on it:

• Page URLs, HTTP status codes, redirect chains and response timings
• Title tags, meta descriptions, canonical tags, robots directives and the heading structure
• Open Graph and Twitter card tags, including any author name and publish date declared in them
• Structured data (JSON-LD, microdata, RDFa) found on the page
• Image sources, dimensions and alt text; internal and external link targets and their anchor text
• HTTP security headers, hreflang tags, semantic HTML usage, and a readability grade for the page’s text

We do not store the full text or HTML of your pages, and we take no screenshots. Readability is computed during the crawl and only the resulting score is kept. That said, elements like a title, a meta description or an article author name are page content — if your pages contain personal data in those places, it reaches our database, which is why section 4 matters.

Our crawler identifies itself as pixyscan-lighthouse-bot and respects robots.txt by default. You can disable that for sites you control.

2.4 What we do not collect

No advertising or cross-site tracking cookies. No third-party analytics inside the product. No behavioural profiling. The only cookies the application sets are the two httpOnly session cookies that keep you signed in.

To run the service you asked for: to crawl your sites, produce reports, show you changes since your last scan, send scheduled scans, and let your teammates share a workspace. To secure your account — session tokens exist to detect and revoke a stolen session. To keep the platform running: we measure scan durations, failure rates and queue depth so we can find and fix problems, as described in section 5.

We do not sell your data. We do not share it with advertisers. We do not use the content of your sites to train machine-learning models.

PixyScan will crawl whatever address you give it, and our terms require you to have permission for the sites you scan. If you point PixyScan at a site that collects personal data — a forum with real names in page titles, say — that data lands in our database as a consequence of your instruction, and you are the one responsible for having a lawful basis for it.

Use your crawl exclusions for areas of a site that should not be indexed by us, and tell us if a scan has captured something it should not have. We will delete it.

Most privacy policies gesture at this with “authorised personnel may access your data.” Here is the specific version.

5.1 The administrative dashboard

We run an internal dashboard that shows the platform as a whole: how many accounts, workspaces and sites exist, how many scans ran and how many failed, how long scans take, which scans are running right now, and how deep the job queues are. It exists so we can tell whether the service is healthy, and so we can answer “why did my scan fail?” when you ask.

To do that, staff on this dashboard can see:

• Your name, email address, sign-in method, when you joined and when you were last active
• Your workspace names, who owns them, and how many members they have
• Your site names and their domain — for example example.com
• Scan status, duration, branch, page count, issue count and health score, plus the error message when a scan fails

5.2 What that dashboard deliberately cannot show

It does not display the contents of your scans. Not the page URLs we crawled, not your titles or meta descriptions, not your headings or link text, not individual issues found on individual pages. The dashboard shows that a scan found 41 issues; it does not show what they were. That is a property of how the software is built — the endpoints behind it do not return those fields at all.

There is no “view as customer” feature. No member of our team can open your workspace and browse your reports as you.

5.3 Every access is recorded

Each time a staff member opens any part of that dashboard, we write a record of who they are, what they looked at, when, and from what IP address. That record cannot be edited or deleted from within the application.

Where an action concerned your account specifically, you can see it yourself under Account → Privacy in the app. Platform-wide views — a count of all users, for instance — are recorded too, but they concern no single customer and so appear in our internal log rather than yours.

5.4 Direct database access

A small number of engineers can reach the production database directly, as is true of any hosted service — someone has to be able to restore a backup or fix corrupted data. That access is limited to those who need it, and we use it for operating the service, never for browsing customer reports. It is the one path this policy cannot make self-verifying, so we would rather name it than imply it does not exist.

We keep this list short deliberately. Our infrastructure runs on Amazon Web Services in {DATA_HOSTING_REGION}. Email — password resets and workspace invitations — is delivered through our transactional email provider. We do not use third-party analytics or advertising services inside the product.

We will disclose data if legally compelled to. Where we are permitted to tell you that has happened, we will.

• Scan data is kept while your account is open, because comparing a scan against the previous one is the core of the product. Deleting a site deletes its scans and every page record under them.
• Account data is kept until you close your account.
• Session tokens are removed when they expire or when you sign out.
• Administrative access records are retained even after the account they concern is closed. A log that disappears when the account does would be no log at all.

Depending on where you live you may have the right to access your data, correct it, delete it, export it, restrict how we process it, or object to processing. You can edit your profile and delete your workspaces and sites yourself from within the app at any time. For anything else, write to {PRIVACY_CONTACT_EMAIL} and we will respond within 30 days.

If you are unhappy with our response, you can complain to the data protection authority in {GOVERNING_JURISDICTION}.

Passwords are hashed with bcrypt. Sessions ride on httpOnly cookies that JavaScript cannot read, and refresh tokens rotate on every use — if a token is used twice, we treat the session as compromised and revoke every session on that account. Traffic is encrypted in transit. Access to the administrative dashboard requires a specific staff role that is checked against the database on every single request, so revoking it takes effect immediately rather than when a token happens to expire.

No system is perfectly secure. If we suffer a breach affecting your data, we will tell you and the relevant authority within the timeframes the law requires.

If we change what we collect or who can see it, we will update this page and change the date at the top. For material changes we will email account owners rather than relying on you to re-read this page.