Privacy policy
This English version is provided for convenience; the German version is binding.
Piggly is free and open source. This policy covers the Piggly apps on piggly-solutions.de (pigglyOS, Desk, Prod, Cal, Fin, Meet) and the public pigglyCal booking pages.
1. Controller
[TODO: set LEGAL_OPERATOR_NAME]
[TODO: set LEGAL_ADDRESS]
Email: support@piggly-solutions.de
2. Whose data lives where
- Own database: when a company uses Piggly with its own database, it is the controller of its data. Piggly does not store it; our servers only pass the requests through.
- Piggly's database: when a workspace lives in our database, we process its content on the company's behalf (Art. 28 GDPR); the company remains the controller. DPA template
- Self-hosted: anyone running Piggly entirely on their own infrastructure sends us no data.
We are the controller for sections 3 to 8 below. Please send questions about a company's data to that company; we forward what reaches us.
3. Visiting the pages
On every visit our host Vercel processes IP address, time, address and browser details to deliver the pages and fend off attacks (Art. 6(1)(f) GDPR). The logs are deleted automatically after a short time.
4. Piggly account and sign-in
For an account we store email address, name, user id, which workspaces you may open, and logs of security-relevant events. Sign-in codes and invitations arrive by email (Art. 6(1)(b) GDPR). The data stays until you delete the account.
5. Booking pages (pigglyCal)
When you book an appointment, name, email address, time and an optional note go to the company you book with; you receive a confirmation and reminder by email. That company is the controller. To prevent abuse we limit requests per IP address (Art. 6(1)(f) GDPR).
6. Meetings (pigglyMeet)
For a meeting we process display names, optionally your email address and, while you turn them on, audio and video. Transmission runs in real time through LiveKit; nothing is recorded. A transcript is made only with consent and emailed only to those who ask for it (Art. 6(1)(a) GDPR); consent can be withdrawn at any time. When joining with a code we limit failed attempts per IP address (point (f)).
7. Emails and connections
We send only emails that belong to using the apps, no marketing, through STRATO in Germany or an SMTP server a workspace has entered itself. Connections you switch on yourself are used only for that purpose:
- Google (Google Ireland Limited) · Microsoft (Microsoft Ireland Operations Limited): Calendar connection in pigglyCal, only when a person connects their account: Piggly reads busy times (start and end), no titles, attendees or notes.
- SMTP / CalDAV: Own email or CalDAV servers a workspace enters in pigglyCal. The credentials are stored encrypted.
- KI-Assistent / AI assistant (MCP): When a person connects an AI assistant (for example Claude by Anthropic) to Piggly over the MCP interface and a workspace admin has allowed it, the assistant reads report data from Fin, Desk and Prod with that person's permissions. The assistant's own provider terms apply.
8. Cookies and local storage
We set only each product's sign-in cookie (sb-piggly-<product>-auth) and keep settings such as light/dark, the selected workspace and camera/microphone choice in the browser. This is strictly necessary for the service (§ 25(2) no. 2 TDDDG) and needs no consent. No analytics, no advertising, no tracking; fonts come from our own servers, not from Google Fonts.
9. Service providers
| 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 |
10. Your rights
You have the right of access, rectification, erasure, restriction, portability and objection (Art. 15 to 21 GDPR) and can withdraw consent at any time (Art. 7(3)). Write to support@piggly-solutions.de. You can complain to a supervisory authority (Art. 77 GDPR); ours is Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach.
Without an email address we cannot create an account or confirm a booking. There are no automated decisions under Art. 22 GDPR.
Last updated: 27 October 2026