Privacy Policy
We respect your privacy. This policy explains what we collect, why we collect it, how we use it, and the choices you have. It covers both organizers and participants.
Table of Contents
1. Data We Collect
Organizers
- Account data: name, email, Google account identifier (via Google sign-in with Supabase).
- Event data: title, description, date/time, location, visibility settings (link-only, passcode), custom questions.
- Invitee lists (optional): names/emails you upload or enter for invitations.
- Support & billing (if applicable): correspondence, subscription status (we do not store card numbers).
Participants
- RSVP details: name or nickname, RSVP status (yes/no/maybe), guests count, optional comments/answers to organizer questions.
- Technical data: IP address, user-agent, and basic logs for fraud/spam prevention and service operation.
- Optional account: if you create an account, we associate RSVP history with it.
All Users
- Usage analytics (if enabled): page views, feature usage, aggregated funnels (via PostHog).
- Device/diagnostics: coarse location inferred from IP, error logs, performance metrics.
- Avoid sensitive data: we do not request special-category data (health, religion, etc.). Don’t include it in events or RSVP notes.
2. How We Use Data
- Provide and improve the Service (create/manage events, collect/show RSVPs, send transactional emails).
- Prevent abuse and ensure security (rate limiting, spam detection, troubleshooting).
- Communicate with you (service notices, account security; marketing only with consent).
- Comply with law (e.g., legal requests, tax or accounting if applicable).
3. GDPR Legal Bases
| Activity | Legal Basis |
|---|---|
| Operating accounts & events | Performance of a contract |
| RSVP collection & display to organizer | Performance of a contract |
| Security, abuse prevention, diagnostics | Legitimate interests |
| Analytics & non-essential cookies | Consent |
| Legal compliance requests | Legal obligation |
6. Data Retention
- Events & RSVPs: kept until the organizer deletes them; inactive/ended events may be archived and auto-deleted after 18 months.
- Account data: retained while your account is active; deleted upon request or after 24 months of inactivity.
- Logs: typically 12 months for security/diagnostics.
- Backups: rolling backups typically 30–35 days before purge.
- Cookie consent records: stored for up to 13 months.
After these periods, data is deleted or irreversibly anonymized unless a longer period is required by law.
7. Security
We implement appropriate technical and organizational measures, including encryption at rest/in transit via our providers, access controls, and monitoring. No method is 100% secure, but we work to protect your information. If a breach poses a high risk to you, we will notify you without undue delay and inform the relevant authority where required.
8. International Transfers
Our primary hosting is in the EU (Hetzner Cloud). Some providers (e.g., email or analytics) may process data outside your country depending on configuration. Where data is transferred outside the EEA/UK, we rely on safeguards such as Standard Contractual Clauses (SCCs) or equivalent. If PostHog is self-hosted on our Hetzner infrastructure, analytics data remains in the EU; if using PostHog Cloud, PostHog’s regional settings and terms apply. Google, as your sign-in provider, may process limited account information per its own policies.
9. Your Rights (GDPR & CCPA)
Access & Portability
Get a copy of your data.
Rectification
Fix inaccurate or incomplete data.
Erasure
Request deletion where applicable.
Restriction & Objection
Limit or object to certain processing.
Withdraw Consent
For analytics/marketing, anytime.
CCPA Requests
Right to know, delete, and non-discrimination.
We do not sell or “share” personal information as defined by the CCPA. To exercise rights or appeal a decision, contact us.
You may also lodge a complaint with your local Data Protection Authority.
10. Controller vs Processor
- We are a Controller for platform-level data (accounts, security logs, analytics if enabled).
- We act as a Processor for participant RSVP data we handle on behalf of organizers. Organizers are independent Controllers for the invitee data they collect and must meet their own obligations (e.g., provide notices, respect deletion requests).
- A Data Processing Addendum (DPA) is available for organizers upon request.
11. Children’s Privacy
The Service is not intended for children under 16. Organizers must be 18+. If you believe a child provided us personal data, contact us to delete it.
12. Changes to This Policy
We may update this Privacy Policy as our Service evolves or laws change. Material changes will be communicated via e-mail or in-app notice.
13. Contact Us
Have a privacy question or request? Reach out: