Leela Privacy Policy

Effective date: 6 October 2026 Version: 1.0 (beta)

Leela is a nightlife events app for Android and iOS. It shows parties on a map, lets you say you're going, share photos and videos from a night ("moments"), and follow friends. This policy explains what we collect, why, where it goes, and what you can do about it.

We wrote it in plain English on purpose. If anything is unclear, email us at support@itsonleela.com.

1. Who we are

Leela is run by Fayçale Jerdioui, 10 rue Abdelmjid Benjelloun, Maarif, Casablanca, Morocco ("Leela", "we", "us"). We are the "data controller" for the personal data described here under the UK GDPR, the Data Protection Act 2018 and the EU GDPR.

Contact for anything privacy-related: support@itsonleela.com.

2. The short version

3. What we collect, feature by feature

Everything below comes from reading how the app and server actually work. If a feature isn't listed, we don't collect data for it.

3.1 Browsing as a guest

When you choose "Continue without an account", the app creates a random guest ID on your phone (for example guest-abc123). This ID is sent with your requests so saved events work. Our server creates a minimal record for it: the guest ID, a placeholder name, your chosen city (defaults to "London") and the music genres you tapped during onboarding. No email, phone number or name is involved. "Start fresh" in Settings clears the guest session from your phone.

3.2 Creating an account

Accounts are handled by Auth0 (EU data centre). You can sign up with an email address and password, or with Google.

3.3 Your profile

Stored on our server and visible to other members: display name (max 50 characters), handle (@name), profile photo (optional), bio (max 160 characters), city (free text, defaults to "London"), up to six favourite genres, and counts of followers, following and nights attended. We also store when you last opened your activity inbox so we can show an unread badge.

3.4 Location

The app asks for "while using the app" location permission (Android: coarse and fine; iOS: when-in-use). We use it to:

What our server receives is the map area you are looking at (a rectangle of coordinates) and the dates you chose, so it can return the events inside it. It does not receive your exact position, and we do not store any position history. There is no background location tracking.

If you refuse permission, the map opens on London (Shoreditch) and everything still works; you can set a home city in Settings instead.

The map itself is drawn by the Mapbox SDK, which fetches map tiles directly from Mapbox's servers as you pan and zoom. Leela switches off the Mapbox SDK's own usage and location telemetry, so your location is not sent to Mapbox. Like any website, Mapbox's servers see the network requests for map tiles (including your IP address); Mapbox's privacy policy applies to those (mapbox.com/legal/privacy). See section 6.

When an organiser creates a party, the address search sends the text typed and the position of the map pin to Mapbox so it can suggest venues and addresses.

3.5 Events: going, interested, saved, reactions, views

When you tap "Going" or "Interested", save a night, or add a vibe reaction (fire / dance / chill / sleep), we store your account ID, the event ID, the status and the time. When you open an event page, we record a view (event ID, time, and your account ID if signed in) so organisers can see how many people looked at their party. Views are shown to organisers as totals only.

3.6 Social: follows, invites, activity inbox

We store who you follow and who follows you, invites you send ("Come to this") with the event and recipient, and we build your activity inbox (follows, likes, comments, invites, friends going out) from those records.

3.7 Moments (photos and videos)

To post a moment you must be marked "going" to that event (or be its organiser). We store: the event, your caption (max 500 characters), and the photos and videos (up to ten per moment; photos up to 20 MB, videos up to 50 MB and three minutes).

Media is uploaded from your phone directly to Supabase Storage (our storage provider) using a one-off signed upload link from our server. The file is stored under a path containing your account ID and a random ID. Media in the bucket is publicly readable by anyone who has the link, even if they are not signed in to Leela. Please only post what you're happy to have public.

We do not currently strip metadata (such as EXIF location tags) from photos before upload. If your camera saves location in photos and you don't want it shared, turn that off in your camera settings before posting.

Likes and comments (max 500 characters) on moments are stored with your account ID and the time.

When you delete a moment it disappears from the app immediately; the database row is marked deleted and kept for a short time for moderation history (see section 8).

3.8 Push notifications

If you are a member and turn notifications on, the app asks the operating system for permission, then registers an Expo push token for your phone with our server (token, platform: Android or iOS, your account ID). We send pushes for: new followers, likes and comments on your moments, invites, people going to your party (organisers), and friends going to public upcoming nights (capped so one person can't trigger thousands of pushes).

Delivery goes through Expo's push service, then Firebase Cloud Messaging (Android) or Apple Push Notification service (iOS). Push content is a short line such as "Amara is going to Fabric" plus a link into the app. Turning the Settings toggle off or logging out removes the token from our server. Tokens the phone reports as dead are removed automatically. Guests are never asked for notification permission.

3.9 Leela Pro and organiser tools

If you upgrade to Pro we store your plan, its status, the renewal date, which store it came from and the store's reference. Today the upgrade is a free test purchase: no payment is taken and no card details are collected. When real in-app purchases launch, payment is handled by Google Play or the Apple App Store; we never see your card number. Promotion "boosts" are stored with the event, package, dates, price and a payment reference.

Parties you publish as an organiser are content you choose to make public (or members-only, followers-only or link-only), including the venue, address, cover photo, line-up, house rules and the fact that you are the organiser.

3.10 Technical data and logs

Our API logs each request (time, path, response code, a request ID and the connecting IP address) to detect abuse and fix bugs. We use IP addresses to rate-limit requests (300 per minute per address). We do not build profiles from logs. Logs are kept by our hosting provider, Render, for a limited period (see section 8).

Stored only on your phone (never sent to us): map style, distance unit, home city, prices-on-map toggle, notification toggle, onboarding answers, and your guest or sign-in session.

3.11 Crash reports and analytics (not yet active)

We plan to add:

We will update this policy and the app before either is switched on. Where the platform allows, you will be able to opt out in Settings (for example "Share crash reports" and "Share usage data" toggles). We do not intend any of this to count as cross-app tracking, so no App Tracking Transparency prompt is planned on iOS.

3.12 Public event data

Event listings on the map come from Ticketmaster, Skiddle and Eventbrite (and from organisers using Leela). These contain venue, artist and promoter information published by those services. They are not about you. If you buy a ticket, you do that on the provider's website under their privacy policy.

3.13 Safety: age confirmation, reports and blocks

Only the developer and any future moderators with an admin role can see reports and moderation records.

4. Why we use your data and our lawful basis

What Why Lawful basis (UK GDPR Art. 6)
Account ID, profile, guest record To run the app and show you and others who you are Contract (our Terms)
Map area and dates you search To return the events on screen Contract
Device location (on your phone) To centre the map and show distances Consent (the OS permission; withdraw any time)
Going / interested / saved / reactions / follows / invites The social features you use Contract
Moments, comments, likes To publish what you post Contract
Event views Organiser statistics (totals only) Legitimate interests (helping organisers understand reach)
Push token and notifications To send the notifications you turned on Consent (the toggle and OS permission)
Pro subscription records To provide what you bought and keep accounts Contract; legal obligation (tax and accounting records)
Request logs and IP addresses Security, abuse prevention, fixing bugs Legitimate interests (keeping the service safe)
Crash reports and analytics (when enabled) Making the app work better Consent where required; otherwise legitimate interests, with opt-out
Moderation and takedown records Enforcing our Community Rules and the law Legitimate interests; legal obligation

We don't use your data for advertising, don't sell it, and don't make automated decisions with legal effects about you.

5. Who can see what (sharing with other users)

Your email address is never shown to other users.

6. Who we share data with (processors)

We use these companies to run Leela. Each only gets what it needs, and each is bound by a contract or standard terms covering data protection.

Provider What they do What they get Where
Neon Database hosting (Postgres) Everything in section 3 that is stored on our server AWS eu-west-2 (London, UK)
Render Runs our API server and stores its logs All traffic to our API, IP addresses, logs Frankfurt, Germany
Supabase Stores photos and videos Your uploaded media and its path (contains your account ID) Supabase cloud (ask us for the region)
Auth0 (Okta) Sign-in, accounts, passwords Email, password hash, Google profile details, sign-in logs EU
Google (Sign in with Google) Optional sign-in Your Google account details you agree to share Google's global infrastructure
Mapbox Map tiles, address search Map requests from your phone, typed addresses and pin positions (SDK telemetry is switched off) USA and global (Mapbox's own privacy terms apply)
Expo (EAS) Push delivery, app builds, over-the-air updates Push token and notification text; app version checks USA
Google Firebase Cloud Messaging Push delivery on Android Push token and notification text Google's global infrastructure
Apple Push Notification service Push delivery on iOS Push token and notification text Apple's global infrastructure
Google Play / Apple App Store App distribution and (later) in-app purchases Purchase and subscription records Global
Sentry (planned) Crash reports See 3.11 EU (to be confirmed at activation)
PostHog (planned) Product analytics See 3.11 EU (to be confirmed at activation)
Ticketmaster, Skiddle, Eventbrite Provide public event listings to us Nothing about you; our server requests their public listings n/a

We will also share data if the law requires it (for example a court order or a lawful police request), to enforce our Terms, or to protect someone's safety.

International transfers. Most of your data stays in the UK and EU. Where a provider is in the USA (Mapbox, Expo, Google, Apple, Sentry/PostHog if US-hosted), the transfer is covered by the UK extension to the EU-US Data Privacy Framework where the provider is certified, or by the UK International Data Transfer Agreement / Addendum to the EU Standard Contractual Clauses.

7. Children

Leela is about nightlife and licensed venues. You must be 18 or over to use it. We don't knowingly collect data from anyone under 18. If you believe someone under 18 has an account, email support@itsonleela.com and we will remove it.

8. How long we keep things

Data Kept for
Account, profile, follows, going lists, saved events, reactions, invites Until you delete your account, then removed within 30 days
Moments, comments, likes Until you delete them or your account. Deleted moments are hidden immediately and the record is purged within 30 days; media files are removed from storage within the same window
Guest records Deleted after 12 months without use
Push tokens Until you turn notifications off, log out, or the phone reports the token dead
Event views Kept as totals; individual rows deleted after 12 months
API request logs (incl. IP) 30 days
Subscription and payment records While you have Pro, then 6 years (UK tax and accounting rules) once real payments start
Reports, takedown notices, blocks, suspensions and other moderation records 12 months after resolution, or longer if needed for a dispute or legal claim. Blocks last until you unblock
Age confirmation timestamp Life of the account
Backups Database backups roll over within 30 days

9. Your rights

Under UK data protection law you can ask us to:

Email support@itsonleela.com from the address you signed up with (or use the app's "Send feedback" link so we can match your account). We will reply within one month. We may ask you to confirm you own the account.

If you're unhappy with how we handle your data, you can complain to the UK regulator, the Information Commissioner's Office (ICO): ico.org.uk/make-a-complaint, or 0303 123 1113. We would appreciate the chance to sort it out first.

10. Deleting your account

Deletion completes within 30 days. We keep only what the law requires (payment records) and records of any moderation action, without your profile attached. Comments you left on other people's moments are removed with your account. Things other people posted that show you (for example a group photo) are their content; see our Content Takedown Policy if you want something removed.

Guests: "Start fresh" in Settings clears your guest session on the phone; the server-side guest record expires after 12 months.

11. Security

Traffic between the app and our servers is encrypted (HTTPS). Sign-in tokens are stored in the phone's secure keystore. Our server never stores passwords. Storage keys never leave the server; the phone uploads with short-lived signed links (10 minutes). Access to production systems is limited to the developer. No system is perfectly secure; if we discover a breach that puts you at risk we will tell you and the ICO as the law requires.

12. Changes to this policy

We'll update this page when the app changes (for example when crash reporting or real payments go live). For meaningful changes we'll show a notice in the app before they take effect. The effective date at the top always tells you the current version.

13. Contact

Fayçale Jerdioui 10 rue Abdelmjid Benjelloun, Maarif, Casablanca, Morocco support@itsonleela.com