Sub-Processors

Last updated: November 11, 2026

This page lists the third-party services Attena 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@attena.app.

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).

Infrastructure and storage

IONOS

Cloud hosting, managed PostgreSQL database, object storage — Germany

Since 19 September 2026, Attena's application servers, primary database and file storage run on IONOS Cloud (IONOS SE, Montabaur, Germany), with the servers in IONOS's Berlin data centre. All data Attena caches from your Gmail, calendar, and contacts — including message bodies, subjects, senders, and Attena-generated artifacts like AI summaries and drafts — is stored in IONOS's managed PostgreSQL database. Attachments and encrypted database backups are kept in IONOS Object Storage in Germany. OAuth tokens are encrypted at the application layer before being written, and Attena encrypts each attachment before uploading it, so IONOS only ever stores attachments as ciphertext. IONOS does not access this data except as required to operate the underlying infrastructure. A signed Art. 28 GDPR data-processing agreement (Auftragsverarbeitungsvertrag) with IONOS SE is in place.

Terms: cloud.ionos.com/terms

AI and language models

IONOS

AI features and search indexing — Germany

Attena uses the IONOS AI Model Hub for two things, both processed in Germany (IONOS's Berlin region) on open-weight models.

AI features. Summaries of your conversations, suggested reply drafts, briefings, triage and related features send the message content they need — typically the body, subject, sender, recipient and surrounding thread context — to IONOS for processing.

Search indexing. To make your messages searchable by meaning rather than just keywords, Attena converts each message into a numeric representation called an embedding. For this it sends the message's subject, sender address, and roughly the first 750 characters of the body — not full bodies, attachments or thread context. The same applies to search terms you type, so they can be compared against the index.

IONOS states that it does not retain or train on this content. In its published data-handling policy, IONOS says the content of prompts and generated outputs “is never logged and is never accessed by IONOS Cloud personnel”, is “not written to any log or to persistent storage”, and is “not used to train, fine-tune or otherwise improve any model”. IONOS runs these open-weight models on its own infrastructure, so the organisations that originally built them — Meta and BAAI — receive no data and have no access to it.

AI chat runs here too.

Terms: cloud.ionos.com/terms

Scaleway

Backup for AI features — France

If IONOS's AI service is unavailable, Attena sends the AI-feature requests described in the IONOS entry above — the same message content — to Scaleway's Generative APIs in Paris instead, running the same open-weight model, until IONOS recovers. Search indexing (embeddings) is never sent to Scaleway.

Scaleway states that it applies zero data retention and does not train on this content. Its published policy says customer data “is not used for training, retraining, or improving the base models”. The one exception is a request that causes an error or is flagged for abuse, which Scaleway may keep for up to two weeks for debugging. Scaleway runs the model on its own infrastructure, so Meta receives no data.

Terms: scaleway.com — Generative APIs data privacy · Data processing: DPA

Push notifications

Apple Push Notification service (APNs)

iOS push delivery: United States

When Attena 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.

Privacy: apple.com/legal/privacy

Google: Firebase Cloud Messaging (FCM)

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.

Privacy: policies.google.com/privacy

Identity and source data

Google: OAuth 2.0, Gmail API, Calendar API, People API

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 Attena 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.

Privacy: policies.google.com/privacy

Product analytics

Plausible Analytics

Website and product usage analytics — European Union

Attena uses Plausible (Plausible Insights OÜ, Tartu, Estonia) to understand how the website and app are used. In the app, Plausible receives page views with the section only, the names of product events such as “message sent”, the referring site's domain, and browser, operating system and device type. It does not receive email content, subjects, sender addresses, contact information, thread or conversation identifiers, search terms, or your Attena user ID, and Attena removes these from page addresses before anything is sent. On our website it also receives the page address and any utm_ campaign parameters, and records clicks on links that lead elsewhere and form submissions, without what you typed.

Plausible uses no cookies. It combines your IP address and browser details with a salt that it deletes every 24 hours to count unique visitors, and stores neither the IP address nor the raw browser details. It keeps only the country, region and city derived from the IP address. Plausible states that this data stays in the EU, using Hetzner (hosting, Germany), Bunny (CDN and DNS, Slovenia) and UpCloud (database, Finland).

Data policy: plausible.io/data-policy · Data processing: DPA

Transactional email

Google: Gmail SMTP (Workspace)

Outbound transactional emails from hello@attena.app: Global

Account emails from Attena, including email-verification, password-reset, password-changed notifications, and (if you opt in) the daily briefing, are sent via the hello@attena.app 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.

Privacy: policies.google.com/privacy

Error tracking

Sentry (Functional Software, Inc.)

Application error reporting — EU data region (Germany)

Attena uses Sentry to capture backend and web-app errors so they can be diagnosed and fixed, and to record sampled performance traces (roughly one request in ten): how long a request or page load took and which database queries ran underneath it. Sentry is deliberately hardened to keep your mail out of every payload: request bodies, cookies, client IP, query parameters, and stack-frame local variables are not transmitted, so message bodies, subjects, and sender addresses do not leave Attena's servers in an error report or a trace. Only an opaque Attena user ID is attached, so we can tell which account hit a bug — never your email content. Data is stored in Sentry's EU region.

Privacy: sentry.io/privacy

Contact

Questions about how Attena handles your data, or about any Sub-Processor listed here, go to privacy@attena.app.