Data Safety and App Permissions
This page summarizes what data the Giddly mobile apps collect, what it is used for, and which device permissions the app requests. It mirrors the Data Safety section of our Google Play listing.
Data we collect
| Data | Why | Shared off-device? |
|---|---|---|
| Name, email, phone number, profile info | Account registration and personalization | With service providers that operate the app |
| Photos and videos you choose to share | Event media-sharing uploads you initiate | Uploaded to our backend so event members can view them |
| Event bookings and payment info | Processing bookings | With payment processors and event organizers |
| Location (only with your permission) | Showing nearby events | With event organizers only when you consent |
| Device info and app interactions | Analytics, performance, and security | With analytics providers |
We do not sell your personal information.
Data security
- Data is encrypted in transit (TLS 1.2+) and encrypted at rest (AES-256).
- Payment details are handled by PCI-compliant payment processors.
- You can request deletion of your data at any time — see How to delete your Giddly account.
Device permissions
The app requests these permissions only to power features you use:
- Notifications (Android 13+) — event updates, booking confirmations, and upload progress.
- Photos / media access — only the photos and videos you pick when sharing to an event.
- Location (optional) — only used, with your permission, to show nearby events.
Background media uploads (Android foreground service)
When you tap Upload to share photos or videos to an event, the Android app completes that upload using a foreground service of type data sync:
- It starts only from your tap and stops by itself when the upload finishes or you cancel it.
- Android shows a persistent “Uploading media” notification with progress while it runs. Tapping the notification returns you to the app.
- It processes only the media you selected (compressed on your device first), the event, and the recipients — then clears temporary files.
- It never starts on boot, on a schedule, or from location or push events. It does not track location, play media, or keep running afterwards.
- On iOS there is no foreground service; uploads use a short system background task instead.
Watch what it looks like while an upload runs:
For the full legal text, see our Privacy Policy.