Subprocessors
The services that handle data for Ark8, what each one receives, and where. Ark8's own records are in one place: Supabase, on Amazon Web Services in us-west-1 (Northern California, United States). There is no choice of region and no self-hosted option today. Most of what the app works with never reaches any of these services: it stays on your Mac, as the Privacy Policy explains.
Processors
They handle personal data on Ark8's behalf.
Supabase
- What it does
- Ark8's database, sign-in service, file storage (the app's downloads and updates) and server functions (the update feed and, once single sign-on is available, its setup).
- What it receives
- Your account (email address, name, picture, sign-in history), organization memberships, roles, groups and invitations, the details of hosts shared with an organization, the organization audit log, which version of the Terms you accepted, and the redacted crash and hang reports the Mac app sends if you turn that on. Its request logs include IP addresses.
- Where
- Amazon Web Services us-west-1 (Northern California, United States). Server functions run on Supabase's edge network and read and write that database.
Vercel
- What it does
- Hosts this website and the web admin console.
- What it receives
- Requests to the site: the IP address, browser and page asked for. Its request logs include IP addresses. For signed-in admins it renders the console's pages from the database above, which is where Ark8's records are kept.
- Where
- Vercel's global network.
Services under their own terms
Used only when you or your organization choose them. They act under your own agreement with them, not as Ark8's processors.
- What it does
- Sign-in, when you choose Continue with Google. A Google calendar, if you connect one to runbook schedules.
- What it receives
- For sign-in, Google tells Ark8 your email address, name and picture; you type your password only on Google's page. Calendar lookups go from your Mac to Google, read-only.
- Where
- Google's own infrastructure, under your agreement with Google.
Microsoft
- What it does
- Sign-in, when you choose Continue with Microsoft. A Microsoft 365 calendar, if you connect one to runbook schedules.
- What it receives
- For sign-in, Microsoft tells Ark8 your email address and name; you type your password only on Microsoft's page. Calendar lookups go from your Mac to Microsoft, read-only.
- Where
- Microsoft's own infrastructure, under your agreement with Microsoft.
Your organization's identity provider
- What it does
- Single sign-on over SAML 2.0 (Okta, Microsoft Entra ID and others), once it is available and your organization sets it up. Planned; not live yet.
- What it receives
- It tells Ark8 your email address and, if it sends one, your name. Your organization chooses and contracts with it.
- Where
- Wherever your organization runs it.
Anthropic
- What it does
- The assistant, only after you turn it on and agree to its consent screen.
- What it receives
- What you ask and the context it needs (see the Privacy Policy, section 3). Requests go straight from your Mac with your own API key, never through Ark8's servers, under your agreement with Anthropic.
- Where
- Anthropic's API.
GitHub
- What it does
- Only if you use it: pushing your runbook library to a GitHub repository, running a runbook on a GitHub runner, or installing metrics-server in a cluster. Ark8 also keeps a copy of each release on GitHub.
- What it receives
- What you push, such as a runner workflow Ark8 wrote with its step scripts, target hosts and the host keys you accepted, never secret values or private keys. Running on a runner calls GitHub's API with the token the gh command-line tool already holds; Ark8 stores no GitHub token. Installing metrics-server downloads its manifest from GitHub, which sees your IP address. All of it goes from your Mac, never through Ark8's servers.
- Where
- GitHub's own infrastructure, under your agreement with GitHub.
Lookups by Ark8's servers
Called by Ark8's servers, with no personal data.
Cloudflare DNS and Google Public DNS
- What it does
- Once single sign-on is available: when an organization verifies its email domain for it, Ark8 looks up the domain's DNS record through both resolvers, which must agree.
- What it receives
- The domain name being verified, and nothing about any person.
- Where
- Their public DNS resolvers.
Not Ark8's subprocessors
Nothing reaches them through Ark8's servers. What your Mac sends them, it sends directly, under your own account or agreement with them.
- Apple
- Apple notarizes each release before it is published: that is Ark8's own build, not your data. When you open the app, macOS may check its notarization with Apple, between your Mac and Apple. Ark8 sends Apple nothing about you, and updates come from Ark8's own feed.
- Services you connect
- Your servers and clusters, Vault, your SIEM, Slack, webhooks, Git remotes, calendars, and the Helm chart catalogues and Artifact Hub. The app reaches each of them directly from your Mac and sends them what you set it up to send; the Privacy Policy's section 4 says what that is. None of it passes through Ark8's servers.