01 — LegalLast updated: 2026-09-24

Privacy policy

How FollowerX GmbH processes personal data on chatteo.de — for users, Google OAuth verification, and GDPR transparency.

02 — 1. Controller

1. Controller

The controller for personal data processed via chatteo.de is:

FollowerX GmbH
Bei St. Annen 2
20457 Hamburg
Deutschland
Register court Hamburg, HRB 166452
Managing directors: Robin Trepte & Lukas Tumpak
VAT ID: DE343792884

Privacy and legal contact: business@chatteo.de. Product support: support@chatteo.de. We have not appointed a data protection officer. Please write to business@chatteo.de for access, erasure, or other GDPR requests.

03 — 2. Scope

2. Scope

chatteo is a SaaS AI chat workspace. Google OAuth is published for production sign-in. Paid Stripe checkout is not live. Features described on marketing pages as roadmap (for example SSO, SCIM, extra model hosts) are not treated as live processing in this policy until they are actually enabled.

This policy applies to the website, accounts, chat, and related emails. It does not apply to third-party sites we link to.

04 — 3. Categories of personal data

3. Categories of personal data

Account data
Email address, display name, password hash (if you register with email/password), email verification status, and account identifiers.
OAuth profile data
If you sign in with Google, we receive the profile Google shares for sign-in — typically email, name, and profile image — and an OAuth account link. We use this to create or recognise your chatteo account.
Chat content
Prompts, replies, model choice, and any files or images you attach when signed in. Guest (signed-out) chats are processed to generate a reply and are not saved as an account history.
Usage and security data
Timestamps, approximate usage/token counters for limits, IP address and user-agent used for rate limits and abuse prevention, workspace membership, and audit events for account actions (for example deletion requests).
Email delivery data
Address and message metadata for transactional mail (verification, password reset, similar notices) sent from support@chatteo.de via Amazon SES.
Cookie / session data
Authentication session, CSRF token, OAuth state/PKCE, and workspace preference cookies. See the Cookie policy.

We do not ask for special-category data (Art. 9 GDPR) as part of sign-up. If you paste such data into a chat, it is processed as chat content under the same rules.

05 — 4. Purposes and legal bases (GDPR)

4. Purposes and legal bases (GDPR)

PurposeLegal basis
Create and maintain your account; sign-in with email/password or GoogleArt. 6(1)(b) GDPR — contract (Terms of service)
Provide AI chat, save history when you are signed in, apply plan limitsArt. 6(1)(b) GDPR
Send transactional email (verify address, reset password)Art. 6(1)(b) GDPR
Security, rate limits, fraud and abuse preventionArt. 6(1)(f) GDPR — legitimate interests in a secure service
Respond to support and legal/business requestsArt. 6(1)(b) or 6(1)(f) GDPR, as applicable
Meet legal duties (for example commercial record-keeping, responding to supervisory requests)Art. 6(1)(c) GDPR
Measure which Google Ads campaigns lead to sign-ups, first use and purchases (conversion measurement), only if you accept marketing cookiesArt. 6(1)(a) GDPR and § 25(1) TDDDG — consent, withdrawable via “Cookie settings”
Count sign-ups, email confirmations, first chats and purchases as anonymous product statistics in our own systemsArt. 6(1)(f) GDPR — legitimate interest in understanding how the service is used

Google Ads conversion measurement: with your consent, the Google tag (Google Ireland Limited) receives the ad click identifier, the conversion event and, if enhanced conversions are on, a SHA-256 hash of your sign-up email. If you arrived via an ad link and consented, we store the click ID and campaign tags (utm_*) with your account and may send the click ID with server-confirmed conversions (for example a purchase) to Google Ads. Google may process this data in the USA (EU-US Data Privacy Framework). We do not use remarketing or personalised advertising, do not run Google Analytics, and never share chats, files or prompts. We do not sell personal data or send promotional newsletters unless we obtain a separate lawful basis and say so here.

06 — 5. AI inference and training

5. AI inference and training

To generate replies we send the relevant conversation context to Amazon Bedrock on EU routes for the models that are enabled (for example Amazon Nova Lite, Claude Haiku, Pixtral, and Claude Sonnet when configured). Inference is required to provide the service.

Policy: we do not use customer chats to train our own models. For Amazon Bedrock, Amazon’s customer agreement excludes use of customer inputs and outputs to train Amazon’s foundation models. We do not claim the same contractual exclusion for every possible future provider until that route is enabled and reviewed.

AI output can be wrong. See the Terms of service. Do not treat model output as legal, medical, or financial advice.

07 — 6. Processors

6. Processors

We use processors to host the app, send mail, run inference, and (when you choose it) authenticate with Google. The live list is on Subprocessors.

  • Hetzner (Germany / EU) — application hosting and private PostgreSQL.
  • Amazon Web Services — Amazon SES in eu-central-1 for transactional email; Amazon Bedrock EU routes for inference.
  • Google — Google OAuth sign-in only if you use that button.

A signed Article 28 DPA for Business customers is in preparation and is available on request when ready — see DPA. We do not publish a finished signed DPA as a product download today.

08 — 7. International transfers

7. International transfers

Storage intent: application data and the database are hosted in the EU (Hetzner, Germany). Email sending is configured in AWS eu-central-1. Model inference is configured on Amazon Bedrock EU routes. We intend EU processing for these routes.

Google OAuth is different. If you sign in with Google, authentication and profile lookup are performed by Google. Google is a US-headquartered provider. That can involve a transfer of sign-in data (for example email, name, subject identifier) to Google in the United States or other countries. We rely on Google’s published transfer tools — typically the EU-US Data Privacy Framework where Google is certified, and/or Standard Contractual Clauses (SCCs) in Google’s customer terms — plus Art. 6(1)(b) for performing the sign-in you requested. You can avoid this transfer by creating an email/password account instead of Google.

AWS is a US-headquartered group. SES and Bedrock are used in EU regions. Residual access by the provider for support or operations may still raise transfer questions; we rely on AWS’s EU data-processing and transfer terms (including SCCs where they apply) rather than claiming that no US entity can ever see metadata.

We do not route inference through unapproved US-only model hosts. If we add a processor or region, we will update Subprocessors and this section.

09 — 8. Retention

8. Retention

  • Account data: kept while the account is active. You can request deletion in settings; we apply a 14-day cooling-off period, then close the account and remove or irreversibly anonymise personal content we control.
  • Saved chats and attachments: kept while the account/workspace is active. Workspaces have a retention setting (default 365 days) after which older threads are deleted by a scheduled job.
  • Guest chats: not stored as saved history. The prompt is processed to produce a reply and then discarded on our side.
  • Auth sessions: JWT session cookies last up to 14 days.
  • Marketing attribution (ad click ID and campaign tags, only with consent): kept with your account while it exists and deleted with it; the browser cookie expires after 90 days.
  • Transactional email logs: kept only as needed to deliver mail and diagnose delivery failures.
  • Legal holds: we may retain a minimal record if required to establish, exercise, or defend legal claims, or to meet tax/commercial duties.

Backups of EU-hosted systems may persist for a limited operational window after primary deletion. We do not claim a certified backup-erasure SLA.

10 — 9. Your rights

9. Your rights

If the GDPR applies to you, you may request access, rectification, erasure, restriction of processing, data portability, and — where processing is based on legitimate interests — objection. Where processing is based on consent, you may withdraw it for the future.

Write to business@chatteo.de or use in-product export/deletion where available. You also have the right to lodge a complaint with a supervisory authority. Our lead authority is the Hamburg data protection authority:

Der Hamburgische Beauftragte für Datenschutz und Informationsfreiheit
Ludwig-Erhard-Straße 22
20459 Hamburg
Germany
https://datenschutz-hamburg.de

11 — 10. Cookies

10. Cookies

We use strictly necessary cookies for sign-in, CSRF protection, OAuth, remembering the active workspace and your cookie choice. Google Ads marketing cookies are set only with your consent. Details: Cookie policy.

12 — 11. Children

11. Children

chatteo is not directed at children under 16. Do not create an account if you are under 16.

13 — 12. Security

12. Security

Transport uses TLS. Passwords are stored as hashes, not plaintext. Sessions use HttpOnly cookies with SameSite=Lax (Secure on HTTPS). We do not claim ISO 27001, C5, TISAX, or an HSM-backed key-management programme as completed. Those items, where planned, are in preparation.

14 — 13. Changes

13. Changes

We will update this page when processing changes in a material way and set a new “Last updated” date. Current version: 2026-09-24. Questions: business@chatteo.de.

Last updated: 2026-09-24