Data processing agreement (optional template)
This English version is provided for convenience; the German version is binding.
Piggly is free; this template creates no fee and no service commitment. It is meant only for companies using the apps on piggly-solutions.de: even with their own database their requests pass through our server functions, and we store workspaces kept in our database. Anyone running Piggly entirely on their own infrastructure needs no DPA with us.
Controller: [company, address]
Processor: [TODO: set LEGAL_OPERATOR_NAME], [TODO: set LEGAL_ADDRESS], support@piggly-solutions.de
1. Subject matter
Providing the Piggly apps the controller uses, for as long as it uses them: passing through, storing (only for workspaces in Piggly's database), displaying and deleting its data, sending email, real-time transmission of meetings. Data subjects are its staff, contacts, customers, people who book and meeting guests; data are names, contact details and the content it enters. Special categories (Art. 9 GDPR) are not intended.
2. The processor's obligations
- Processing only on documented instructions; settings in the apps count as instructions. Notice if an instruction seems unlawful.
- Confidentiality of everyone with access.
- Measures under Art. 32 GDPR as in annex 2.
- Subprocessors only as in annex 1; changes are announced beforehand in text form, and the controller may object or stop using the apps. The obligations of this agreement bind them too.
- Assistance with data-subject rights and Art. 32 to 36 GDPR; forwarding requests.
- Notice of personal-data breaches without undue delay after becoming aware.
- After use ends, deletion of the data stored at Piggly unless the law requires keeping it; the controller can export it first.
- Information demonstrating these obligations on request; audits by arrangement.
3. Final provisions
Liability under Art. 82 GDPR. Text form suffices. German law applies.
[place, date, name – controller]
[place, date, name – processor]
Annex 1: Subprocessors (hosted mode)
| Provider | Purpose | Data | Location | Third-country safeguard |
|---|---|---|---|---|
| Vercel Inc.USA | Hosting the Piggly apps and their server functions, also for workspaces with their own database (passed through, content not stored); technical logs | IP address, time, requested address, browser details and all content transmitted while using the apps | Server functions in the region chosen for the project; delivery through the provider's worldwide network | EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR), with standard contractual clauses in addition |
| Supabase, Inc.USA | Piggly's database (pigglyDB) and sign-in (Supabase Auth): Piggly accounts and workspaces kept in Piggly's database | Account and sign-in data; content only of workspaces in Piggly's database | Frankfurt am Main, Germany (AWS region eu-central-1) | Stored in the EU; for access from third countries (operations, support) EU Commission standard contractual clauses (Art. 46(2)(c) GDPR) in the provider's data processing agreement |
| STRATO GmbHGermany | Sending email: booking confirmations, reminders, invoices, meeting transcripts | Recipient name and email address, email content | Germany | No transfer to a third country |
| LiveKit, Inc.USA | Real-time transmission of audio, video, screen sharing and chat in pigglyMeet (LiveKit Cloud) | Display name, participant id, IP address, connection data, audio and video streams (no recording) | The provider's servers, usually near the participants, also outside the EU | EU Commission standard contractual clauses (Art. 46(2)(c) GDPR) in the provider's data processing agreement |
Services the controller or its users connect themselves (own database, own SMTP/CalDAV server, Google or Microsoft calendar, AI assistants) are not subprocessors of Piggly.
Annex 2: Technical and organisational measures
| Physical and system access | No own server rooms; the data centres of the providers in annex 1. Sign-in through Supabase Auth, a separate sign-in cookie per product; admin access only for the operator. |
|---|---|
| Authorisation and separation | Row-level security: every row belongs to a workspace, access only with a matching membership and role. Own databases are fully separate; Piggly holds no credentials for them. The service key stays server-side. Tests use synthetic data only. |
| Transfer and input control | TLS for every connection. Credentials for SMTP, CalDAV and calendar accounts encrypted; calendar import stores busy times only. Access through the AI interface (MCP) is logged and read-only. |
| Availability | Rate limits and bot protection on public forms. No guaranteed availability. Backups are not guaranteed on the free Supabase plan (daily backups and point-in-time recovery: paid). |
| Defaults and review | No tracking, self-hosted fonts, transcripts only with consent, AI access off by default. Security updates of dependencies; open-source code. |
Last updated: 27 October 2026