Data Processing Addendum
Last updated November 11, 2026
This addendum is part of the Terms of Service. It applies when a workspace contains personal data that its owner (the "customer") is responsible for and Nanner Tech LLC ("we") processes it to provide ShipVitals. Where it and the Terms differ on personal data, this addendum wins.
1. Roles
The customer is the controller of personal data in its workspace, and we are its processor. We process that data only to provide ShipVitals as the customer configures it, and on the customer's documented instructions, which are these terms and the customer's use of the service. If we believe an instruction breaks data protection law, we'll say so.
2. What is processed
- Data subjects: the customer's members and invitees, and people who appear in data from connected services or in forwarded bills (for example, a provider account's owner).
- Personal data: names, email addresses, roles, audit records, and whatever personal data connected services return in the figures ShipVitals reads. ShipVitals is built not to store end customers' names, emails or card details.
- What the customer adds: bills forwarded to the workspace's invoice address, with whatever names and addresses they contain; the screenshots that cloud browser checks and guide walks take of the customer's own sites; the test accounts those walks sign in with; and the API tokens its members make, stored only as one-way hashes.
- Purpose and duration: providing ShipVitals, for as long as the workspace exists, then deletion as in section 8.
3. Confidentiality
Everyone at Nanner Tech who can access customer personal data is bound to keep it confidential and accesses it only when needed to run, support or secure the service.
4. Security
We keep the measures described on the Security page, including encryption in transit, per-workspace encryption keys held under Google Cloud KMS, row-level access control in the database, audit logging, two-factor sign-in, read-only API tokens that never exceed their maker's access, and cloud browsers that can reach only public addresses. We may improve them, but not reduce the overall level of protection.
5. Sub-processors
The customer authorises the sub-processors listed on the Sub-processors page. We hold each to data protection terms at least as protective as these. We'll announce a new sub-processor on that page and in the app at least 30 days before it starts processing customer personal data; the customer may object, and if we can't address the objection, may stop using ShipVitals and delete its workspace.
6. Helping the customer
We'll help the customer, as far as we reasonably can, to answer requests from data subjects (members can export and delete their own data in the app), and with security, breach notifications and data protection impact assessments relating to ShipVitals.
7. Personal data breaches
We'll notify the customer without undue delay after becoming aware of a personal data breach affecting its workspace, with what we know and what we're doing, and keep it updated.
8. Deletion and return
The customer can export its workspace at any time. When a workspace is deleted, it can be restored for 7 days; then we delete its data and destroy its encryption key. Backups roll over within 14 days.
9. International transfers
Workspace data is stored in Google Cloud's europe-west1 region (Belgium). Where a sub-processor processes it outside the European Economic Area, we rely on that sub-processor's transfer safeguards.
10. Audits
We'll make available the information reasonably needed to show compliance with this addendum. Write to support@nannertech.com.