Last updated 28 October 2026. This is the short version; the service agreement governs where they differ.

What Anchor stores

For each Search Console property you connect: the Page Indexing exports Google produces (URL lists per reason and the chart totals), the history of those snapshots, crawl results for the URLs in them, and the steering your organisation writes for its own AI. For your organisation: member names and email addresses from your Google sign-in, the names of API keys, and the usage of those keys.

What we never hold

Your Google password or session. Signing in uses Google only to confirm who you are; we receive your name, email address and profile picture, nothing else. On the Local tier the Search Console capture runs in your own browser and only the exports reach us. On the Cloud tier a property Owner grants a dedicated Tight Ship address Restricted read access in Search Console, which that Owner can remove at any time. API keys are stored hashed; the secret is shown once at creation and cannot be recovered by us.

Who can see it

Only members of your organisation, and Tight Ship staff for support and operation of the service. Every API request is scoped to one organisation by its key. We do not sell or share your data, and we do not use it to train models.

Where it lives

Data is stored with Supabase and Google Cloud in the United States. The web app is served by Render. Each of these providers processes data only on our instructions.

The app sets only the cookies and local storage needed to keep you signed in and remember your last organisation. There is no advertising or cross-site tracking.

Leaving

Revoke your keys in Settings and, on Cloud, remove our address from Search Console. Ask and we delete your organisation’s data; otherwise it is retained for the life of your subscription and purged afterwards on the retention schedule in your agreement.

Contact: ben@tightship.consulting