Google Play · Data Safety
Data Safety
Summary of Flyding's Data Safety declarations · Effective 18 July 2026
This mirrors the answers Flyding provides in the Google Play Data Safety form
and Apple's App Privacy labels. For the full detail, see our Privacy Policy.
📍
Location
Collected to find the closest open table. Not shared for advertising.
◆
Advertising ID
AD_ID / IDFA collected for advertising measurement.
⚡
Payment info
In-app buys via app stores; deposits & cooldown-skip via Stripe. We store transaction records only.
◆ AT A GLANCE ◆
- Does this app collect data? Yes.
- Does this app share data with third parties? Yes — limited, as described below.
- Is data encrypted in transit? Yes.
- Can you request that data be deleted? Yes — see Account Deletion.
- Is collection required? Some data is required to use core features; advertising identifiers can be limited via your device settings.
◆ DATA TYPES ◆
1. Location
Data typeCollected / SharedPurpose & notes
Precise location
CollectedNot shared
Find and rank the closest open table and nearby venues, while the app is in use. Not collected in the background.
Approximate location
CollectedNot shared
Alternative to precise location for finding nearby venues. Optional — you may enter a location manually.
Required: optional. Purpose: App functionality. You control this via device location permissions.
2. Device or other identifiers — Advertising ID / ads
Data typeCollected / SharedPurpose & notes
Advertising ID (AD_ID / IDFA)
CollectedShared
Advertising or marketing. Shared with ad/measurement partners to attribute installs and campaign performance.
Required: optional. Purpose: Advertising or marketing.
Controls: reset/delete your advertising ID and opt out of personalized ads in device settings; on iOS we
request App Tracking Transparency permission before cross-app tracking.
3. Financial info — Payment information
Data typeCollected / SharedPurpose & notes
Purchase history
CollectedNot shared
Item or service purchased, amount, currency, date, and processor transaction ID — to deliver purchases, provide receipts/refunds, and prevent fraud.
Payment card / account details
Processed by Stripe & app stores
In-app purchases (Sparks, Flyding+) are billed by the Apple App Store / Google Play. Booking deposits and the $5 cooldown-skip are processed by Stripe via its secure payment sheet. Card and account details go directly to these processors — Flyding never receives or stores full payment details.
Required: required for purchases (purchases are optional). Payment processors:
Apple, Google, Stripe. Purpose: App functionality, Fraud prevention.
◆ OTHER DATA WE HANDLE ◆
Data typeCollected / SharedPurpose
Name & email
CollectedShared
Account management; first name shared with the venue to hold your table.
User IDs
CollectedNot shared
Account management and sign-in (Apple / Google / Facebook / email link).
App activity & interactions
CollectedNot shared
Bookings, Sparks, streaks, and reward boxes — to run the service and rewards.
◆ SECURITY PRACTICES ◆
- Data is encrypted in transit.
- You can request deletion of your data in-app or by email — see Account Deletion.
- We follow the Play Families policy by not targeting children; Flyding is a 21+ app.
- We provide a way to review and manage permissions (location, notifications, tracking) at any time.
This page summarizes the declarations Flyding submits to Google Play and Apple. The authoritative,
binding description of our practices is the
Privacy Policy. Review with counsel before
submitting to the stores to ensure it matches your production build.