Skip to content

Security

Facts about how ShipVitals is built and run, in short sections. Each links to where you can check it.

Last updated November 12, 2026

Hosting and region

ShipVitals runs on Google Cloud in europe-west1, in Belgium: the API and sync jobs on Cloud Run, the database on Cloud SQL for PostgreSQL with private networking only, daily backups and 7 days of point-in-time recovery, and files in private Cloud Storage buckets. These pages and the app are served by Firebase Hosting.

Evidence:Sub-processors

Encryption

Every connection to ShipVitals uses TLS, and browsers are told to use HTTPS only. Each workspace has its own data key, which encrypts that workspace's credentials and test accounts' passwords and is itself encrypted by a key held in Google Cloud KMS (envelope encryption). When a workspace is deleted for good, its data key is destroyed, which leaves its stored credentials unreadable.

Evidence:Deleting a workspace

Read-only access

ShipVitals asks for read-only access wherever a provider offers it: Stripe restricted keys, a GitHub App with read permissions, Google Cloud viewer roles, a read-only AWS role, GA4 Viewer. Some providers issue only keys that can also change things, among them OpenAI, Anthropic, OpenRouter, Neon, Vercel, Resend and App Store Connect. Those connections are labelled "Not read-only", and ShipVitals calls only the reporting endpoints it needs: usage, costs and sales. Every connector's scopes, and which aren't read-only, are on one page.

Evidence:Every connector's scopesIntegrations

What we store, and what we never store

We store your connections' credentials, encrypted; the figures we read (costs, usage, revenue totals and health results); and who did what in your workspace. We never store your customers' names, emails or card details (revenue is counted against a hashed customer id), your source code, your users' identities, or your own card number, which only Stripe sees.

Evidence:What the Privacy Policy says we collectWhat leaves your machine

Signing in

Sign in with Google, GitHub or a one-time email link; there are no ShipVitals passwords to leak or reset. Two-factor sign-in uses an authenticator app, never SMS, and comes with ten one-time recovery codes, shown once. A workspace can require it of its admins. Sensitive actions, such as deleting a workspace, need a sign-in within the last 10 minutes.

Evidence:Signing inTwo-factor sign-inWhen a workspace requires it

Who sees what

A workspace has four roles: owner, admin, editor and viewer, and editors and viewers can be limited to some projects. Amounts can be hidden from editors and viewers. The database enforces this as well: row-level security limits every query to the workspace and projects the person may see, and someone outside a workspace is told it doesn't exist.

Evidence:Changing someone's access

Audit log

Invitations, access changes, plan changes, API tokens made and revoked, deletions and every decryption of a credential are written to the workspace's audit log, which its admins can read and export. Security changes to your own account are listed in your account's security settings and emailed to you. Audit entries are kept for 13 months.

API tokens and the MCP server

Scripts and AI agents read a workspace through its API and MCP server with a workspace token, which starts with sv_api_ and works nowhere else in ShipVitals. A token can only read: each of its requests runs in a read-only database transaction. It never sees more than the person who made it can see now: it covers the projects they chose, shows amounts only if they can see them, narrows as soon as their access narrows, and stops working when they leave. A token lasts 30 days, 90 days, a year or until revoked, as its maker chooses, and makes at most 60 requests a minute. We store only a SHA-256 hash and show the token once. Owners and admins can see and revoke every token; editors make and revoke their own.

Evidence:Connect your agentThe API referenceAPI tokens in the Privacy Policy

Cloud browser checks and walks

Cloud browser checks run a fresh, sandboxed Chromium on our servers for each run, with no profile kept, none of our secrets in its environment and 30 seconds to finish. Every connection it makes goes through our egress proxy, which allows only HTTPS to public addresses: it looks up each host, refuses it if any address is private, loopback, link-local (such as the cloud metadata server) or reserved, and connects only to the address it checked, so a redirect or a changed DNS answer can't reach inside our network. Each run is capped at 64 connections at once, 256 in all and 50 MB. A check is data, never code: nothing you write runs in the browser. Cloud guide walks open only an HTTPS site whose address names it a test environment, such as staging.example.com, and everything else a page loads goes through the same proxy.

Evidence:Cloud browsers in the Privacy Policy

The invoice inbox

Each workspace has its own address to forward bills to. Every delivery must carry Mailgun's signature and is accepted once. ShipVitals reads a bill automatically only when its mail carries a DKIM signature from the domain in its From address, which ShipVitals verifies itself rather than trusting any header, and an owner or admin has confirmed that sender. Any other mail waits, unread: a new sender's until an owner or admin confirms the sender, and a mail that fails the DKIM check, marked "Sender not verified", until one of them chooses to read that bill. So mail that only pretends to come from a vendor adds no cost and spends nothing on AI unless someone reads it on purpose. Bills are read within daily limits per workspace and per sender.

Evidence:Forwarding invoicesThe invoice inbox in the Privacy PolicyAI features in the Privacy Policy

Payments

Paid plans are paid on Stripe's own checkout and billing pages, which ShipVitals sends you to, so card numbers never reach ShipVitals' pages or servers. Stripe's notices of payments are checked against their signature and handled once. Only a workspace's owner can start a paid plan.

Evidence:Plans and payment in the TermsPaying, in the Privacy Policy

No third-party scripts

These pages and the app load no script from anywhere else, and show no advertising and no third-party trackers. The Content Security Policy allows scripts only from ShipVitals itself and, to finish signing in, Google's sign-in script. We count page views with Umami, which we run ourselves: your browser sends them to ShipVitals' own address, and our servers shorten your IP address before Umami sees it. ShipVitals sets no cookies.

Evidence:Analytics in the Privacy PolicyCookies

Sub-processors

The companies that process data on our behalf, and what for, are listed on the Sub-processors page.

Reporting a vulnerability

If you find a security problem, email support@nannertech.com with what you found and how to reproduce it. Please don't access other people's data or disrupt the service while you look. We read every report and reply.

A lost authenticator

When signing in asks for your code, choose Use a recovery code instead and enter one of yours: it turns two-factor sign-in off, signs out every device and emails you, and you set it up again. If you have no codes left, write to support@nannertech.com from the address on your account, and we'll confirm it's you before removing the factor.

Evidence:Two-factor sign-in