Last updated: May 27, 2026
This page lists the third-party services Nebula uses to deliver the product. In line with the GDPR Art. 28 transparency requirement and the Google API Services User Data Policy, every Sub-Processor that may receive content from your Gmail account, your email, or data derived from them is named here, along with what it does, where it operates, what data it sees, and a link to its data-processing terms.
When we add or change a Sub-Processor that handles user content, we update this page. If you'd like advance notice of material changes, write to privacy@getnebula.tech.
For the data-handling rules these Sub-Processors operate under — including Limited Use, no-train-on-user-data, and the four restricted exceptions to human access — see our Privacy Policy, especially §2 (Google API Services — Limited Use Disclosure) and §4 (Data Sharing and Disclosure).
VPS hosting, PostgreSQL backups — Germany / France
Nebula's application servers and primary database run on Strato (STRATO GmbH, Berlin — a German hosting provider in the United Internet group) within the European Union. All data Nebula caches from your Gmail, calendar, and contacts — including message bodies, subjects, senders, and Nebula-generated artifacts like AI summaries and drafts — is stored on these servers. OAuth tokens are encrypted at the application layer before being written. Database backups are kept on Strato-managed storage in the same region. Strato does not access this data except as required to operate the underlying infrastructure. A signed Art. 28 GDPR data-processing agreement (Auftragsverarbeitungsvertrag) is in place; Strato is ISO 27001 certified.
Strato uses Ionos SE (Montabaur, Germany — a sister United Internet company) as its underlying infrastructure provider for dedicated and virtual servers. Anyone running a WHOIS lookup on Nebula's production IP will see Ionos SE as the network registrant; STRATO GmbH remains our direct sub-processor under the AVV. Strato's other infrastructure sub-processors used in the VPS path are Hewlett-Packard GmbH (server hardware support, Germany), Virtuozzo International GmbH (virtualisation, Switzerland), and Plesk International GmbH (server admin software, Switzerland); the Swiss processors operate under EU Standard Contractual Clauses.
LLM inference for AI features — United States
When you use Nebula's AI chat, AI triage (when opted in), or features powered by Claude, Nebula sends the minimum necessary content — typically the message body, subject, sender, recipient, and surrounding thread context — to Anthropic's API for inference. Anthropic does not use API inputs or outputs to train its models. Anthropic retains API content for up to 30 days for abuse-monitoring purposes only, after which it is deleted.
LLM inference for AI features — United States
For AI features powered by open-weight models (briefings, dashboard summaries, channel summaries, draft suggestions, AI sentiment, triage, voice-profile learning, AI chat when configured), Nebula sends content to Together AI's hosted inference API using OpenAI-compatible endpoints. The content sent is the same as for Anthropic — body, subject, sender, recipient, surrounding context.
Nebula has opted out of Together AI's account-level data retention and product-improvement programs (effective 2026-05-29). On our account, Together AI is not permitted to retain prompts and responses for product improvement, and is not permitted to route our requests through passthrough models that would send data to other third-party providers. This is on top of Together AI's standard paid-API terms, which already exclude inference inputs and outputs from training data.
Nebula's mid-term roadmap replaces Together AI with self-hosted open-weight inference; this page will be updated when that transition is complete.
iOS push delivery — United States
When Nebula sends an iOS push notification (new message, important sender, etc.), Apple receives a small payload containing the sender's display name and the message subject (or the first 100 characters of a preview when no subject exists). Apple delivers the notification to your device and does not retain payload content beyond delivery.
Android push delivery — Global
The Android equivalent of APNs. Google receives the same payload (sender + subject/preview) plus structural metadata (thread ID, normalized subject) needed to route you to the right thread when you tap the notification. Google does not retain FCM payload content beyond delivery.
Identity provider and source of your Google data — Global
Google authenticates you when you sign in with your Google account and is the origin of every piece of Gmail, calendar event, and contact data Nebula processes on your behalf. We access this data via the scopes you grant on the consent screen (gmail.modify, calendar.events, contacts.readonly, plus openid email profile for sign-in); revoke at any time via myaccount.google.com/permissions.
If you sign in with a non-Google address — Varies
If you connect a Fastmail, Outlook, Yahoo, or self-hosted mailbox to Nebula, that provider is the source of your email — Nebula reads it via IMAP and sends through SMTP. Each user's IMAP/SMTP provider is determined by the user, not selected by Nebula. Credentials are stored encrypted at rest on Nebula's servers.
Product usage analytics — Global
Nebula uses Google Analytics 4 to understand how features are used — which pages users visit, which buttons get clicked, which onboarding steps stall. GA4 receives page views, custom product events (such as opening the briefing or sending a chat message), and after you sign in your Nebula user ID, so a session's events are linkable to your account. GA4 does not receive any Gmail content, message bodies, subjects, sender addresses, or contact information. You can opt out of GA4 collection site-wide by enabling your browser's "Do Not Track" signal or by installing the official Google Analytics Opt-out Browser Add-on.
Outbound transactional emails from hello@getnebula.tech — Global
Account emails from Nebula — email-verification, password-reset, password-changed notifications, and (if you opt in) the daily briefing — are sent via the hello@getnebula.tech mailbox on Google Workspace using Gmail SMTP. Google sees the recipient address (your account email) and the rendered email content. Inbound replies to support@ / privacy@ are also handled on Google Workspace.
For transparency, services Nebula does not use today (and which would require an update to this page before adoption):
Questions about how Nebula handles your data, or about any Sub-Processor listed here, go to privacy@getnebula.tech.