ElbeWare ElbeWare Legal
Impressum Privacy AGB / Terms AVV / DPA
DRAFT — DRAFT — Not for public paid use until German counsel review. Replace with approved text and bump LEGAL_DOC_VERSIONS. Set LEGAL_STATUS=counsel-approved only after a lawyer replaces this copy.

Version 2026-10-05-draft · Stand: 5 October 2026 · Not legal advice from ElbeWare engineering.

Datenschutzerklärung / Privacy Policy

This draft describes how [Legal name — set LEGAL_OPERATOR_NAME after Gewerbe / UG] (“ElbeWare”, “we”) processes personal data when you use ElbeWare AI Studio at https://elbewareai.cycroommedia.com . Have German counsel finalize this before public paid launch.

1. Controller

[Legal name — set LEGAL_OPERATOR_NAME after Gewerbe / UG]
[Street / number — set LEGAL_OPERATOR_ADDRESS]
[PLZ City — Germany]
E-Mail: legal@elbeware.com

2. What we process

  • Account data: email, password hash (or GitHub identity), plan, workspace membership.
  • Usage: generation prompts/briefs, pipeline run metadata, quotas, Trust Engine results.
  • Billing: Stripe customer / subscription identifiers (card data stays with Stripe).
  • Integrations: GitHub tokens (encrypted at rest), Shopware shop connection credentials (encrypted), optional Shopware Account producer credentials.
  • Technical: session cookie, IP/security logs as needed to operate the service.

3. Purposes & legal bases (GDPR)

  • Provide the SaaS (Art. 6 (1)(b) — contract).
  • Security, abuse prevention, billing (Art. 6 (1)(b)/(f)).
  • Legal obligations (tax/accounting) (Art. 6 (1)(c)).

When agencies connect merchant shops or upload briefs containing personal data of end customers, ElbeWare typically acts as processor under Art. 28 GDPR — see the Customer AVV / DPA.

4. Processors / subprocessors

We use the following categories of providers (execute their DPAs before production):

ProviderRoleTypical dataNotes
SupabasePostgres / platform DBAccount & app dataPrefer EU region (e.g. Frankfurt); sign Supabase DPA
StripePaymentsBilling identity, planPCI handled by Stripe
AnthropicLLM generation / GuardPrompts, code snippets, briefsNo customer secrets in prompts; org spend limits
E2BSandbox validationGenerated package filesEphemeral VMs
GitHubOAuth + optional PRsProfile, repo access tokenUser-authorized scopes
[Hosting provider — set LEGAL_HOSTING_PROVIDER, e.g. Vercel / Hetzner / Fly]Application hostingApp traffic / logsEU (prefer Frankfurt)
Email provider (when enabled)Transactional mailEmail addressOnly if/when configured

5. Cookies

We use an essential session cookie (elbeware.sid) to keep you signed in. It is required to provide the service (login/session). We do not currently use non-essential analytics or advertising cookies. If we add them later, we will update this policy and show a consent banner where required.

6. Retention

Account data is kept while your account is active. You may export or delete your account in the dashboard (GDPR portability / erasure). Billing records may be retained as required by tax law.

7. Your rights

Under GDPR you may have rights of access, rectification, erasure, restriction, portability, and objection, and the right to lodge a complaint with a supervisory authority (e.g. your local Landesbeauftragte für Datenschutz). Contact: legal@elbeware.com.

8. International transfers

Prefer EU hosting and EU Supabase regions. Where a provider processes data outside the EEA, counsel should document SCCs / transfer impact assessments for that vendor.

[Legal name — set LEGAL_OPERATOR_NAME after Gewerbe / UG] · Home Sign in Register · docs 2026-10-05-draft