Sub-processors — Moat8
Last updated: October 8, 2026
Moat8 LLC engages the third parties listed below to process personal data in connection with the Moat8 Data Vault service, whether on behalf of our customers or for the purposes for which Moat8 itself is the controller, such as billing and product analytics. Each is engaged under contractual confidentiality and data protection obligations consistent with our Privacy Policy.
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Google Cloud Platform (Google LLC) | Application hosting, databases, and object storage for the delivery buffer | Account data, encrypted connector credentials, vault file index, prepared file content in the delivery buffer, messages received from Telegram groups that a customer's connected bot is in (stored encrypted), help assistant conversations with the status summaries the assistant looked up, and the record linking an account to its help-desk customer record | United States (us-east1) |
| Google Workspace (Google LLC) | Sending the Service's emails: one-time sign-in links, where email sign-in is offered, and links to confirm it is you before a sensitive action | The email address a link is sent to, and the message containing the link | United States and other locations of Google's infrastructure |
| Paddle.com Market Ltd. | Payment processing; merchant of record | Billing contact data. Payment card numbers are collected by Paddle directly and are never received by Moat8 | United Kingdom / United States |
| PostHog, Inc. (PostHog Cloud EU) | Product analytics: understanding how the Service and the public website are used, in order to improve them | Events recorded by our servers, linked to the account's internal identifier (a random identifier, not a name or email address): account created or signed in and with which sign-in method; type of source connected, disconnected, first read, needing reconnection, or failed, with the error code; setup code created and its kind of access; device paired, first seen and first files delivered, with its platform and application version; source clicked in the source catalogue; and the name and optional note a user types when asking for a missing source. Timestamps. For public website visitors who accept analytics: an analytics cookie identifier, page views, clicks, scrolling, heatmaps and session recordings of the public pages with typed input masked, the referring website or campaign, and browser and device type. IP addresses are discarded and no location is recorded. No Customer Data; no content, names, paths or volumes from connected sources; no data received from Google APIs; no names, email addresses or credentials | European Union (Frankfurt, Germany). PostHog, Inc. is a U.S. company; access from the United States is covered by the EU-U.S. Data Privacy Framework (with its UK and Swiss extensions) and the EU Standard Contractual Clauses |
| OpenRouter, Inc. | In-app help assistant: passing a user's question to the language model and returning its answer | The question a user types into the help assistant and that day's earlier turns of the same conversation, with text that looks like a credential masked; Moat8's product documentation; and, when the question is about the user's own sources or devices, a status summary: each source's type and connection state, how long ago it was last read, each device's name as shown in the Service (by default the name the computer reports, unless the user renamed it), which sources it receives and when it last checked in. No account name or email address; no content, file names or counts from connected sources; no data received from Google APIs | United States |
| Google LLC (Gemini models), reached through OpenRouter | In-app help assistant: the language model that writes the answer | The same as for OpenRouter | United States |
| Atlassian (Jira Service Management) | Help desk: receiving, storing and answering support requests, and emailing customers our answers | For each support request: the account's email address and internal identifier, the request type, subject, message and replies, the page of the Service it was sent from and the browser's user-agent string, and, if the user chose to share it, that day's conversation with the help assistant (credential-like text masked; no status summaries). Messages sent to our support email address. No content from connected sources unless a user writes it into a request | United States and other locations of Atlassian's infrastructure |
| DigitalOcean, LLC | Hosting our monitoring server: metrics, service logs, dashboards and alerts on how the Service is operating | Operational metrics of the Service for each vault: the state and timing of connections, synchronizations and deliveries, and the state and version of devices. Service logs, from which secrets and credentials are removed; they may contain IP addresses and the internal identifiers of accounts, connections and devices. No content from connected sources; no data received from Google APIs; no credentials | European Union (Amsterdam, the Netherlands). DigitalOcean, LLC is a U.S. company |
We do not use external error-monitoring or advertising services. Application monitoring runs on a server we operate, hosted by DigitalOcean, listed above. For analytics we use PostHog, listed above. PostHog receives only pseudonymous usage events recorded by our servers and, from visitors who accept analytics, analytics from the public website. It never receives Customer Data, data received from Google APIs, or credentials. The in-app help assistant uses OpenRouter and Google's Gemini model, listed above; they receive what users type into the assistant and, when a user asks about their own sources or devices, the status summary described above, never the content of connected sources or data received from Google APIs. Support requests are handled in Atlassian's Jira Service Management, listed above; it receives what a user writes in a request, the account's email address so that our answer can reach them, and, if the user chooses to share it, that day's conversation with the help assistant.
The separate public Plays workflow catalog uses its own hosting and model providers, described in the Plays Privacy Notice. The table above covers the Data Vault service.
Changes to this list. We update this page before engaging a new sub-processor. Customers who wish to be notified of changes may subscribe by writing to legal@moat8.ai.
Questions. legal@moat8.ai — Moat8 LLC, 30 N. Gould St, Ste R, Sheridan, WY 82801, USA.