This policy explains what personal data Sextant Web (“Sextant”, “we”) collects, why, how we keep it safe, who we share it with, how long we keep it, and how you control it. Sextant is a service of Basil Design Company LLC, 148 Elcho Ave, Crested Butte, CO 81224, USA. It covers the app at app.sextantweb.com, the Sextant API and MCP server for AI agents, and the tracking script on your sites.
1. The data we collect
Your account: your name, email address and sign-in sessions. If you sign in with Google, also your Google account ID and profile picture (see section 2).
Your workspaces and sites: the sites you add (name, domain, time zone, country), the people you invite and their levels, your settings, notes, goals, saved keywords and the other items you create.
Billing: the billing profile you enter (name, email, address, tax ID) and a card label such as “VISA ···· 4242”. Stripe processes card payments. We never see or store full card numbers.
Your sites’ visitors: the tracking script records page views, events and, only when you turn them on, session replays and heatmaps. It does not set cookies to identify visitors. Replays hide form fields. You decide what your site collects, and we process this data on your behalf.
AI agents and API keys: the agents you connect (their name and the access you approved) and your API keys (stored only as hashes).
Activity records: a log of changes made in your sites (who, what, when) and basic technical logs (IP address, browser) to keep the service secure and to fix errors.
2. Google user data
Sextant asks Google for access only when you choose a feature that needs it, and only for the data that feature uses.
Sign in with Google
Data: your name, email address, profile picture and Google account ID (scopes: openid, email, profile). Use: to create your Sextant account and sign you in. Nothing else.
Google Search Console (read only)
Data: the list of your Search Console properties and their search performance data: search queries, pages, countries, devices, clicks, impressions, click-through rate, average position, and URL inspection results (scope: webmasters.readonly). Use: to show this data in Sextant (Google search, the site overview and SEO tools) for the site you connect it to, and to send it to an AI agent that you connected to Sextant when that agent asks for it on your behalf.
Verifying your site with Google (only when you choose it)
Data and actions: when you choose “Let Sextant verify it”, Sextant asks Google for a verification record for your domain, asks Google to check that record, and adds the verified domain to your own Search Console (scopes: siteverification.verify_only and webmasters). Use: only to verify the domain you own and to add it as a property. Sextant does not delete properties, change other Search Console settings, or verify domains you did not ask for.
Google Analytics (read only, history import)
Data: the list of your Google Analytics 4 accounts and properties, and daily report totals for the property and dates you choose: visitors, visits, page views and their breakdown by page, traffic source, country, device, browser and operating system (scope: analytics.readonly). Use: only to import your past analytics into the Sextant site you choose, so its charts start before you installed Sextant. Sextant never changes your Google Analytics account, properties or settings.
Who sees the Google data of a site
A Google connection belongs to the site it is connected to. Admins of that site see the email address of the Google account that connected it and the Search Console and Google Analytics properties that account can open, so they can choose the right one. Everyone you give access to the site, their AI agents and API keys, and the share links you publish see the site’s Search Console data and its imported analytics.
How we store Google user data
Google access and refresh tokens are encrypted before we store them, and only the Sextant service reads them. They are stored by the SEO service on Cloudflare.
We store which Search Console property, Google Analytics property and Google account each site uses.
Search Console reports may be cached on Cloudflare for up to 7 days so pages load quickly, and in the memory of the app server (Vercel) for up to 10 minutes. They are then deleted automatically.
Imported Google Analytics data is stored as daily totals in the site’s analytics database (Railway). While an import runs, its rows are kept in the app database (Neon) and deleted when it finishes or is undone.
All data travels over encrypted connections (HTTPS).
How we share Google user data
We do not sell Google user data.
We do not use Google user data for advertising, including personalized, re-targeted or interest-based ads.
We do not use Google user data to decide credit-worthiness or for lending.
We share it only to provide the features above: with you and the people you give access to that site, with an AI agent you connected to Sextant when it asks on your behalf, and with the providers that host it for us (Cloudflare, Vercel, Railway and Neon, listed in section 4). We also share it if the law requires it.
Sextant does not send Google user data to AI model providers on its own, and it does not use Google user data in its own AI features. When you connect your own AI agent (for example Claude, ChatGPT or Gemini) and ask it about your site, Sextant sends the Google data that the agent asks for to that agent, on your behalf. The agent’s provider then handles that data under its own terms.
No AI training
We do not use Google user data to develop, improve or train generalized artificial intelligence or machine learning models.
People at Sextant
No person at Sextant reads your Google user data, unless you ask us to (for example for support) and agree, unless we must do so for security reasons (for example to investigate abuse), or unless the law requires it.
Keeping and deleting Google user data
We keep a Google connection until you disconnect it, delete the site, or remove Sextant’s access in your Google Account.
When you disconnect Search Console (Settings › Integrations) or delete the site, we delete its token. We also revoke it at Google, unless another of your sites still uses that Google account (Google would end that connection too).
Google Analytics has no separate disconnect: its connection stays with the site until you delete the site or remove Sextant’s access in your Google Account. To remove imported analytics, undo the import in the site’s Import data page, or delete the site.
When you delete your account, we delete your personal sites and their Google connections. A site in a team workspace stays with that workspace until its owner deletes it or disconnects Search Console.
If you start to connect Google but do not choose a site, the connection stays unused until you remove it in your Google Account, or ask us to delete it.
Cached Search Console reports are deleted within 7 days.
Sextant’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
3. Why we use your data
To provide Sextant: to sign you in, show your analytics and SEO data, run the actions you or your agents ask for, and send sign-in links and invites.
To bill you for paid plans and extra use.
To keep the service secure, stop abuse, and fix problems.
To meet legal duties, such as tax records.
We use account and billing data because we need it to provide the service you asked for (contract), activity records because we have a legitimate interest in security, and your sites’ visitor data on your instructions as your processor.
4. Who we share data with
We use these service providers. Each one processes data only to provide its part of Sextant, under its own data protection terms:
Vercel (hosts the app) and Neon (the app database), in the USA.
Railway (hosts the analytics service and its database, including imported Google Analytics data), in the USA.
Cloudflare (hosts the SEO service, including Google tokens and cached Search Console reports).
Resend (sends email) and Stripe (payments and invoices).
DataForSEO and OpenRouter (paid SEO Research and AI Research lookups that you run: they receive the keywords, domains and questions of that lookup, never Google user data).
Google (sign-in, Search Console, site verification and Google Analytics import, when you use them).
We do not sell personal data. We share data with others only when the law requires it, to protect people from harm, or with your consent.
5. How long we keep data
Account and site data: while your account exists. When you delete a site or your account, we delete its data.
Session replays: 30 days, unless you save a replay. Saved replays stay until you delete them.
Billing records: as long as tax law requires (in the USA, up to 7 years).
Google user data: as described in section 2.
6. Your choices and rights
You can view and change your profile, disconnect Search Console, undo a Google Analytics import, delete sites and delete your account in the app.
You can ask for a copy of your data, for a correction, or for deletion, and you can object to a use, by email to hello@basildesign.co. We answer within 30 days.
Depending on where you live (for example the EU, the UK or California), the law gives you these rights. You can also complain to your data protection authority.
Visitors to a site that uses Sextant should contact that site’s owner, who controls their data. We help site owners answer such requests.
7. Security
We encrypt all traffic, encrypt Google tokens, store API keys and sign-in link tokens only as hashes, limit access to the people who need it, and log changes in your sites. No service can be perfectly secure. If a breach affects your data, we tell you as the law requires.
8. Cookies
The app uses only the cookies it needs to keep you signed in and secure. It does not use advertising or tracking cookies. The tracking script on your sites does not set cookies.
9. Children
Sextant is for businesses and is not for children under 16. We do not knowingly collect data from children.
10. International transfers
We store and process data in the USA. When we transfer data from the EU or the UK, we rely on our providers’ standard contractual clauses.
11. Changes
When we change this policy, we update the date above. When a change is important, we tell you by email or in the app before it takes effect.
12. Contact
Questions about privacy or your data: Basil Design Company LLC, 148 Elcho Ave, Crested Butte, CO 81224, USA, hello@basildesign.co.
Basil Design Company LLC · 148 Elcho Ave, Crested Butte, CO 81224, USA · hello@basildesign.co