Data handling
A detailed companion to the privacy policy: where data lives, who processes it, how long we keep it and how it's protected.
Where data is stored
Accounts, lists, items, memberships, invitations and notification tokens are stored in a Supabase database in the EU (AWS, Ireland). Notifications pass through Expo's push service in the USA on their way to Apple and Google.
Processors
| Provider | Purpose | Data location | Transfer safeguard |
|---|---|---|---|
| Supabase, Inc. | Database, sign-in, server functions | EU (Ireland) | DPA, standard contractual clauses |
| Functional Software, Inc. (Sentry) | Crash and error reports | EU (Germany) | DPA, standard contractual clauses |
| 650 Industries, Inc. (Expo) | Push notification delivery | USA | DPA, Data Privacy Framework, standard contractual clauses |
| Vercel, Inc. | Website hosting | Global edge network | DPA, Data Privacy Framework, standard contractual clauses |
| Namecheap, Inc. | USA/EU | DPA, standard contractual clauses |
Apple and Google are independent controllers for signing in with their accounts. Lappen receives your name, email address and profile picture link from them.
Retention
| Data | Deleted |
|---|---|
| Account and profile | When you delete your account |
| Lists and items | When deleted in the app, or with the owner's account |
| Memberships | When you leave or are removed, or with your account |
| Invitations | Automatically, 30 days after use or expiry |
| Join attempts (for rate limiting) | Automatically, after 1 day |
| Push notification tokens | When you sign out on that phone, with your account, or automatically 90 days after the phone last opened the app |
| Notification cooldown records | Automatically, after 1 day |
| Crash reports | Automatically, within 90 days |
| Support email | Within 24 months |
Security measures
- Encrypted connections (TLS) for all traffic.
- Row-level security in the database: every read and write is checked against list membership on the server.
- Invitation codes are stored only as keyed hashes (HMAC-SHA-256), and each works once.
- Rate limits on joining, inviting and creating lists and items.
- Live updates are delivered only to people allowed to see them.
- Sign-in only through Apple or Google; Lappen stores no passwords.
Personal data breaches
If a breach puts your rights at risk, we report it to IMY within 72 hours and tell those affected without undue delay.
Contact
RIEN Network AB, lappen@riennetwork.com.
Last updated: