Help when you need it
FlightTrove Support
Help with your FlightTrove account, location, notifications, Spots, Favorites and subscriptions.
For product support or technical issues, tell us what happened, which app version and device you use, and the steps that led to the issue. Include the affected screen, approximate time, whether the problem is repeatable, and any visible error message. Use the separate privacy contact on the Legal page for data-subject requests or data-protection questions. Never send your password, Firebase token or purchase token.
Contact support
Start with the details that help us solve it.
How can we help?
Account access
For sign-in or password problems, tell us whether you use email/password or Google sign-in, which step fails, and the exact error text. Do not create a second account to work around the issue. If the app says the device is not active, include the device model and app version; never send a password, Firebase token or recovery code.
Notifications
Check the Android notification permission first, then the FlightTrove notification categories and quiet hours. If one alert is missing, include the saved alert location, category, approximate time and whether Radar showed the aircraft. Notification delivery can depend on device battery restrictions and current provider coverage.
Location permissions
Current Radar and physical Spot confirmation need a fresh permitted device location. Saved alert locations are separate remote contexts and do not prove where you are. If location is wrong or stale, check Android permission, precise-location mode, device settings and whether an Active Spotting Session is running; include the approximate area, never raw coordinates or screenshots containing private addresses.
Spotting
A Spot is created only after you manually confirm that you saw the aircraft from a safe, permitted location. Nearby data or an alert is not enough. For a failed submission, include the aircraft reference shown, observation time, whether the current location was fresh, and the visible error; do not claim a Spot you did not personally observe.
Favorites
Favorites control discovery and alert preferences; they do not create a Spot or prove presence. Tell us whether the issue affects one aircraft, a type, an operator or all Favorites, and whether it appears in the app after a refresh.
Subscriptions
Describe which Free or Plus capability is missing and whether Google Play shows an active purchase. Include the Play order date or product name only when support asks for it; never send a purchase token. FlightTrove account deletion does not cancel a Google Play subscription, which must be managed separately in Google Play.
Delete account
Use the secure Delete account page or the in-app deletion control. The flow requires owner authentication and an explicit confirmation; an email address alone cannot authorize deletion. If deletion stops, tell us which stage failed and the displayed message, but do not email credentials or identity tokens.
Security report
For a suspected account takeover, exposed personal data or security weakness, contact support promptly with a short reproduction and affected route. Do not publicly disclose exploit details or include passwords, tokens, payment data or precise personal location.
Common guidance
Account access
For sign-in or password problems, tell us whether you use email/password or Google sign-in, which step fails, and the exact error text. Do not create a second account to work around the issue. If the app says the device is not active, include the device model and app version; never send a password, Firebase token or recovery code.
Notifications
Check the Android notification permission first, then the FlightTrove notification categories and quiet hours. If one alert is missing, include the saved alert location, category, approximate time and whether Radar showed the aircraft. Notification delivery can depend on device battery restrictions and current provider coverage.
Location permissions
Current Radar and physical Spot confirmation need a fresh permitted device location. Saved alert locations are separate remote contexts and do not prove where you are. If location is wrong or stale, check Android permission, precise-location mode, device settings and whether an Active Spotting Session is running; include the approximate area, never raw coordinates or screenshots containing private addresses.
Spotting
A Spot is created only after you manually confirm that you saw the aircraft from a safe, permitted location. Nearby data or an alert is not enough. For a failed submission, include the aircraft reference shown, observation time, whether the current location was fresh, and the visible error; do not claim a Spot you did not personally observe.