FLYNORI / Privacy policy
FLYNORI Privacy Policy
Last updated November 11, 2026
FLYNORI is a flight game for iPhone and iPad by ARSENII DOROGIN. For privacy questions and support, email support@avsidev.com. Visits to this page are covered by the separate website privacy policy.
Data on your device
Drawings, 3D models, hangar, flight history, personal records and preferences are stored on your device. Your pilot name is saved in your profile on your device. The editor and flights work offline. Apple backups follow your device settings.
Optional world rankings
When you enable world rankings, Google Firebase Authentication creates a guest account with an identifier. No email address or password is required. Firestore stores your best distance and the duration of that same flight for each ranked map, along with the physics rules version. The identifier connects your results across maps and is part of the public record’s technical address. The release app displays an automatically generated callsign alongside distance and flight time. It keeps your pilot name on your device and does not send it to the rankings. A nickname previously sent by a test version may still be present in a public ranking entry. Deleting the associated guest account removes that entry.
A record report sends the reporter and record owner identifiers, map, distance, duration, selected reason and submission time to Firebase. Reports are stored privately. Firebase may also process network addresses and technical data to run and protect the service. Rankings are not a backup of your progress.
Optional analytics and crash diagnostics
If you enable Game analytics, Firebase Analytics receives game events such as screens opened, editor actions, map and model category, rounded flight distance and time, and result actions. Google also processes an installation identifier, app and device information, and may infer approximate location from the network address. FLYNORI does not request location access. The app does not attach player names, account identifiers, drawings or prompts to analytics events. Advertising consent signals are denied and vendor identifier collection is disabled for Analytics.
If you enable Crash reports, Firebase Crashlytics can receive crash traces, installation identifiers, app and device information, and recent game events if analytics is also enabled. The app may keep a crash report on the device and send it on a later launch while you allow reporting. Turning off analytics resets local Analytics data. Turning off crash reporting clears unsent crash reports. These choices do not recall data already sent.
Consent, retention and deletion
The three switches in Settings → Data & privacy are independent and off by default. Change them at any time. We use consent for each optional feature. We use support correspondence to respond to requests and comply with applicable obligations. This includes your email address, message and any attachments you choose to send.
Turning off rankings stops new submissions. Previously published entries remain visible in the rankings. Use Settings → Data & privacy → Delete guest account to remove the current Firebase account, its ranking entries and related server data, including any legacy profile and model records tied to it. Associated reports are removed. After deletion, Firestore retains a marker containing a hash of the account identifier to prevent submissions using old credentials. If deletion fails, keep the app installed and retry when online. Your local drawings, hangar and personal records remain on your device. Analytics and crash data are managed separately.
Ranking data stays in the service until account deletion or service closure. Reports are retained as needed to handle the associated records and maintain the service. Analytics retention follows the Google Analytics property settings. Google begins removing Crashlytics crash data and associated identifiers after 90 days. Support correspondence is retained as needed to answer the request and meet applicable obligations.
Providers and your rights
Google provides Firebase Authentication, Firestore, Analytics and Crashlytics under its Firebase privacy and data processing terms. The Firestore ranking database is located in a European region. Firebase Authentication processes data in the United States. Google describes applicable transfer safeguards in its terms. Apple handles distribution and device backups under Apple’s privacy policy.
Where applicable, you can ask for access, correction, deletion, restriction or portability of your data, object to certain processing, and complain to a competent data protection authority. Withdrawal of consent does not affect earlier lawful processing. Email support@avsidev.com to make a request. We may need to verify ownership or ask for information that identifies the relevant account or installation.