Privacy Policy

Last updated: 21 October 2026 · Web, Android, iOS and macOS

Draft. Operator, hosting and retention details are still being finalised.

FlyAgain supports reporting bird rescue cases, cooperation between rescuers and keeping bird care records. This policy covers personal data processed in FlyAgain and login with Facebook.

1. Controller and contact

Controller: Barna Farago
Address: Nap u. 35. fszt. Budapest 1082.
Privacy enquiries: info@myndideal.com

2. What data do we process, and why?

Account and login: name, email address, user ID, permissions, preferences and sessions. For email registration, the server stores a hash used to verify the password. These data are necessary to create accounts, manage access and provide the service.
Facebook login: the Facebook ID provided to the application by Meta, name and, when permitted, email address and profile photo. Meta supplies these data at login. We import the photo as your profile picture if you do not already have one. We do not ask for or receive your Facebook password. We use the Facebook access token to verify login and do not store it persistently. This feature does not request access to your friends or Facebook posts and does not post on your behalf.
Profile: your chosen photo, biography, website and availability/work status. These help identify people involved in rescues and support cooperation.
Location: your configured default address and coordinates and, during field use, the permitted device location. We use these for maps, distance calculation and sorting nearby cases. You can revoke GPS access on your device; a default location can also be entered manually.
Cases and communication: reports, finding address and coordinates, photos and location/time information imported from them, journal entries, care data, participants and messages. These support rescue and care coordination. Medical records are for animals; do not upload human health data.
Operation and security: audit logs, identifiers used to limit login attempts and technical logs generated on the hosting service. Login rate limiting also uses hashes derived from email and IP addresses.

Camera and photos

FlyAgain uses the camera when you choose to take a photo of a bird or other animal in need and attach the selected picture to its case. Camera access requires permission from iOS or Android. The camera does not record in the background; this feature takes still photos, not audio or video recordings.

A photo may first be stored on your device with the local case or report. Selected photos attached to a case are uploaded to the FlyAgain server when the case is saved or synchronised. They are visible to people allowed to view the case; pictures attached to a public case may also appear on the guest website. Photo timestamps and, where available and permitted, location data may be used to document where and when the animal was found.

Camera permission is optional and can be revoked in your device’s system settings at any time. You can use FlyAgain without taking photos and can attach an existing image using the system photo picker. Do not photograph or upload people’s faces or other unnecessary personal information.

Support enquiries

We use the name, reply email address, request type and message provided in the contact form to handle your report or complaint and reply. Each enquiry receives a reference and is stored in the private admin report inbox; it may also be forwarded by email to the operator’s contact address. A hash of the IP address and submission times may be used to limit abuse. Do not include passwords or sign-in tokens in your message.

Bug reports and diagnostic attachments

When you open the bug report form, the app may capture a screenshot of the previously visible screen and a diagnostic snapshot of its operation. The screenshot may include case details, names, messages or other personal data displayed at that moment.

The diagnostic report may contain technical data needed to investigate the issue, such as app and system versions, connection type, operation names, times, durations, data volumes and error status.

The report and its attachments are sent to FlyAgain when you submit them. Reports from signed-in users are linked to their account; issues can also be reported without signing in. Reports are handled by authorised operators and may also be forwarded by email to the operator’s contact address. Diagnostic attachments may be stored and forwarded as compressed files.

Sign-in protection and password reset

For each account, we store the IP address and time of the last successful sign-in and counters of incorrect password attempts. We use these to detect and limit unauthorised access attempts. Three incorrect passwords lock password sign-in for five minutes; we show when you can try again. The IP address comes from the connection reaching the server; a shared network or network intermediary means it does not uniquely identify a person.

You can request a password reset email for the entered address on the sign-in page. For an active account, we send a single-use link valid for one hour; the database stores a hash of its secret token. The response does not disclose whether the address has an account. Requesting a reset alone does not change the password. Saving a new password invalidates previous sessions and reset links. Expired reset records are deleted when subsequent reset requests are processed.

3. Legal basis and providing data

Processing necessary to operate your account and the requested service is based on providing the service or taking preparatory steps at your request (GDPR Article 6(1)(b)). Security and abuse-prevention processing is based on the legitimate interest in protecting the system and its users (Article 6(1)(f)). You authorise optional Facebook data sharing and device location access; you may withdraw your consent (Article 6(1)(a)). Withdrawal does not affect the lawfulness of earlier processing.

Facebook login is optional; email registration is also available. A new FlyAgain account started with Facebook also requires a name, email address and your own password. If Meta does not supply an email address, you can enter it manually. You can link or unlink an existing account in Settings while signed in. Optional profile and location data may be omitted, but the features relying on them may be limited.

4. Who can see the data?

The guest list and map display some case data without signing in. Anyone who has a shared direct case link can also view detailed case information, photos and the journal. Share links only with appropriate recipients and avoid including unnecessary personal data in reports.

User profiles and users’ map positions are available to signed-in users. Editing cases and using care features depends on permissions; communication participants can access their messages through the app interface. Authorised operators have the access necessary to operate the service.

The application may share a user's current, precise location with other signed-in users. A recent GPS position from the device appears on the map only while “In the field” mode is enabled, location access is permitted and the user is on duty. Otherwise, a configured default location may appear instead; this does not confirm the user's current whereabouts. Users' map positions are not available on the signed-out guest interface.

In Settings, you can choose not to appear on the map. Dispatchers and administrators can view hidden users by enabling their privileged option to include them. Turning off field mode and revoking device location permission are separate options; use the map hiding setting to control whether your default location is shown.

Sites and a default location are optional. A street and house number are not required: you may provide a city name with a selected map point, or use an account without an address or default location. Select the map point at your intended level of precision: a city name does not make an accompanying precise coordinate approximate. An animal's finding location is separate case information, not the user's current location.

We also determine an approximate country code from the IP address using a local database, including for signed-out visitors. We do not send the IP address to an external GeoIP service for this lookup. Signed-in users may select a different country; we store this as a private account preference, which can be cleared by restoring automatic mode. The country center helps set the initial map view. It is not a precise location or GPS fix and is not displayed as a user location marker.

Timestamped field GPS history can be enabled separately in account settings and is collected only when enabled in the system as well. Collection is disabled by default. We retain points actually submitted by the app in field mode; this does not imply continuous or background location monitoring. Users may view their own route history; dispatchers/admins require authorization. It is not public. Retention defaults to 7 days, and the actual period is shown in settings; scheduled maintenance deletes data beyond this period. Disabling the setting stops further collection; earlier points may remain until their retention period ends. Backups follow the separately specified backup retention period. For operational monitoring, we store minute-level aggregate API request counts, client platform, operation type, response category and server time, plus the authenticated user’s latest API activity. These statistics do not contain message text, passwords, tokens or full request URLs.

5. External services

Hosting and processing location: Mynd-ideal kft

Facebook login also involves Meta’s own processing: Meta Privacy Policy. That policy explains Meta’s international processing and the safeguards used.

Map tiles are loaded from an OpenStreetMap service and some web libraries from unpkg.com; these providers may receive network information, including your IP address. Address searches send the searched address to the geocoding service configured on the server. Starting navigation sends the destination to your selected Google Maps or Apple Maps service. Those services’ own privacy terms also apply.

6. Retention and local storage

We process account-related data for as long as necessary to operate the account. When handling deletion requests, personal data in cases, journals and messages are also reviewed; depersonalised parts of the shared bird rescue records may remain. See the deletion instructions for details.

Technical and security log retention: The retention period is being finalised.
Backup retention: The retention period is being finalised.

Your browser may store sessions, display preferences, drafts and photos awaiting upload locally. We use a short-lived technical cookie needed for Facebook login. Native apps may keep local copies of data and login details. The ad hoc macOS test version may store a remembered password unencrypted in a local file protected by file permissions. Do not use password remembering on a shared device.

7. Your rights and requests

You may request information, access, rectification, erasure, restriction and, where applicable, data portability; you may object to processing based on legitimate interests. Send your request to the contact address above, without needing to sign in. We ask only for data necessary to identify you; do not send passwords.

Requests must be answered without undue delay and, as a rule, within one month. You will be informed of any lawful extension and its reason. You may complain to the Hungarian National Authority for Data Protection and Freedom of Information or the competent supervisory authority, and seek a judicial remedy.

Moderation and relationship settings

Content reports store the reporter identifier, content identifier, explanation and submission time. Moderator decisions, personal hiding, blocks, friend requests and acceptances, and profile and messaging preferences are processed to protect the service and provide the functions you request. Dispatchers and administrators may view the conversation between the reporter and the reported person to investigate a conversation report; this does not make messages public. A non-public profile hides personal information and the photo from other users, but does not erase author names in previous case entries or copies already downloaded by others. See the moderation principles in the Terms of Service.

For designated alpha and beta testers, screen identifiers, navigation times, platform and client version are retained for 30 days to investigate operation. This log does not contain entered text or passwords.

User-authorized travel location sharing

Rescuers, transporters and caregivers may start and stop sharing. It is disabled by default; manual or field sharing requires separate acknowledgment. On each new multi-device client, automatic participation can be enabled once: a foreground client may then join the same account’s trip started on another device. Installations have separate identifiers and revocable device keys. Spatially divergent sources remain separate and are not averaged into the shared track. Devices can be excluded or re-enabled for a trip. In the iOS and Android apps, a separate per-device setting, off by default, may enable location sharing already started by the user to continue while another app is in use or the screen is locked. This requires acknowledging a disclosure and granting system location permission. Android displays a recording notification with a stop action. Disabling location sharing stops recording and revokes background consent; route retention still follows the separate GPS-history setting. The browser interface does not provide continuous background recording. Operating-system termination or force-quitting the app may interrupt recording. New clients keep an account-scoped temporary queue of up to 20,000 samples, removing acknowledged samples after upload; permanently rejected samples remain locally with an error. Samples up to seven days old, measured within the recording period, may be uploaded for up to seven days after closure without restarting live tracking. Older clients may retain their previous limits. Precise live locations are visible only to dispatch-authorized users, including administrators, and are not public. Case viewers see participants, states, notes and arrival estimates. Retaining raw or shared route history requires both personal and system GPS-history permission. Users may view their own routes; dispatchers/admins require the corresponding authorization. Remote stop takes effect on the recorder’s next successful refresh; the server removes the live position immediately. Maintenance removes current fixes older than fifteen minutes. Coordinate-free upload receipts and empty closed recording metadata may remain for at least eight days for safe retries.

Voice messages and speech recognition

You may voluntarily record and send voice messages to your conversation partner. We use the microphone only for a recording you start, with your permission. An unsent voice draft may be stored on your device; sent audio may be stored in private storage on the FlyAgain server and in its backups.

Audio may be transcribed by an authorised AI worker of the FlyAgain operator or, depending on your settings, by Apple speech recognition. FlyAgain’s own worker operates in an environment provided by the operator, without an external cloud speech recognition service.

Apple speech recognition can be enabled separately. When supported by the device and selected language, the app requests on-device recognition; otherwise, Apple’s service may also process the audio. Apple’s own privacy terms and a system permission request may apply.

Machine-generated transcripts may contain errors and do not replace the original recording. The access and retention rules for messages apply to both audio and transcripts.

Personal summary and speech playback

FlyAgain may prepare a personal summary from the data available to you. This may include the number of new messages, the status of followed, nearby or cared-for cases, and care tasks.

The summary may be converted to audio by your device’s speech synthesiser or FlyAgain’s own AI worker. For server-side speech generation, the summary text is sent to the FlyAgain server, where it is processed as a task linked to your account and stored together with the generated audio.

Local copies of the text and generated audio may be stored on the iPhone and its paired Apple Watch. The iPhone may transfer the generated audio to the watch; the devices may also synchronise whether playback has been completed. Automatic background playback on the watch can be enabled with a separate setting.

Location sharing: enabling, disabling and background recording

Location sharing helps coordinate bird-rescue and transport tasks: an authorised dispatcher can see a participant’s recent location while the travelling user uses another app or locks their phone. This is not an emergency-location or guaranteed continuous-monitoring service; confirm essential coordination details directly when needed.

Location sharing, background measurement on this device and route-history retention are separate settings. Background recording is off by default. Under Settings → Field location sharing, users who have already enabled location sharing may enable “Record in the background on this device” after accepting a separate disclosure. System location permission is also required. Accepting the EULA, registering or consenting on another device does not enable it. Case management and manual journey-status updates remain available without location sharing.

Turning off the background switch stops background measurement locally on that device, including when offline; foreground location sharing may continue according to its separate setting. The Android notification’s Stop action disables the same background permission. To stop all location sharing, use “Never share my location”; stopping one journey stops recording for that journey. Once the server confirms that location sharing is disabled, background consent is cleared for every device. A stop requested from another device reaches the recording client on its next successful refresh. System location permission can also be revoked in the phone’s settings.

Recording processes coordinates, measurement timestamps, accuracy and identifiers associated with the account and recording device. Precise live location is visible only to authorised dispatchers and administrators; it is not public. Full route-history retention requires both the personal and system GPS-history settings. Users can view their own retained routes; dispatchers/admins need the corresponding authorisation. Disabling recording does not delete earlier data: existing routes follow the retention periods in the privacy policy and settings, and applicable deletion rights. The temporary local upload queue may contain previously measured points; a delayed upload does not restart recording. Location data is not sold or used for advertising tracking.

The iOS/iPadOS, macOS and Android apps can continue recording already started by the user. The browser version does not offer continuous background GPS recording through this switch. The system indicates location use; Android also offers a stop action in its service notification, whose display depends on system notification permission. GPS reception, connectivity, power saving, operating-system termination or force-quitting the app may interrupt recording. The feature may increase battery consumption.

The optional Apple Watch app is connected with separate approval on the iPhone and receives its own revocable access; your password is not copied to the watch. The watch is a separate GPS source with its own location permission and background recording setting. It stores points locally while offline and uploads them with server acknowledgement. Watch access can be revoked on the iPhone; a stop or revocation reaches another device at its next successful communication. The watch feature is under development and testing.

Detailed privacy policy · Data deletion and privacy requests

Status as of 21 October 2026: background location recording is under development and testing. This status note does not replace separate permission or limit your privacy rights.