Privacy Policy
Effective 2026-04-22 · Last updated 2026-10-06
This Privacy Policy describes how the DroneInfo mobile application and the DroneInfo weather API(collectively, “the service”, “we”, “us”) handle information when you use them. The service is published by Deeploy Tech, a sole trader (enskild firma) registered in Sweden, which is responsible for your data (the data controller). Contact: [email protected].
DroneInfo is designed to collect the minimum amount of data required to provide its functionality. We do not sell your data, we do not use it for advertising, and the mobile app does not require you to create an account.
Part A - Mobile App
1. Location data
The app requests access to your device location (coarse and fine) so it can show weather and flight conditions for your current position. Location data is used only to query weather and airspace information for your coordinates. It is processed in real time and is not stored on our servers after the request is served. To prepare notifications, the app may also check the forecast for your last known location in the background. That location is not stored. You can deny location permission at any time in your device settings; without it, the app falls back to manually selected coordinates or shows a prompt explaining what is unavailable.
2. Request metadata
When the app queries our backend API, standard technical information is received by the server, including approximate coordinates (rounded to 3 decimal places, ~110 m precision), the request timestamp, the response cache key, and the IP address (processed transiently by the server and standard logging/CDN layer). This information is used to operate the service, cache weather responses, and diagnose errors. It is not linked to a persistent user identifier.
3. Purchases
If the app offers in-app purchases or subscriptions, billing is processed by Apple App Store or Google Play Billing and managed through RevenueCat. We receive only the anonymous subscription status (active / inactive) and an anonymous subscriber ID generated by RevenueCat. We do not receive your payment details, credit card number, or full Apple/Google account email. We may also use this ID to confirm that your subscription is active for notifications.
4. Diagnostics and analytics
The app does not currently use third-party analytics or crash reporting SDKs. Standard App Store / Google Play crash metrics may be collected by Apple or Google under their own policies. Website and API analytics are described in Part B, section 8 - they do not apply to the mobile app.
5. Notifications (optional, Pro)
Pro users may receive notifications about upcoming flying conditions. To deliver them and to confirm that the Pro subscription is active, we may store a notification identifier for your device, your anonymous subscriber ID, your time zone and basic app details such as platform and version. We do not store your location for this purpose; the forecast is evaluated on your device.
Notifications can be turned off at any time in Settings, which deletes this information from our server. It is also deleted when the subscription ends, when the app is uninstalled, or after 30 days without use.
6. Data we do NOT collect (mobile app)
- We do not collect your name, email, phone number, or contacts.
- We do not track you across other apps or websites.
- We do not use advertising identifiers.
- We do not sell, rent, or share personal data with advertisers or data brokers.
Part B - Weather API & Web Account
7. API requests
The DroneInfo API receives latitude/longitude coordinates and endpoint paths in order to return weather data. Coordinates are cached internally rounded to three decimal places (~110 m precision) and used for performance only - they are never sold, shared with marketing partners, or correlated to identifiable end users.
8. Web accounts and billing
Account holders provide an email address and (when subscribing) billing details processed by Stripeunder Stripe’s privacy policy. We retain usage analytics (request counts, endpoint, status, latency) for 90 days for billing and abuse prevention.
The droneinfo.app website and weather API also use a first-party product analytics system that we operate ourselves. There is no third-party analytics vendor, and no script is loaded from an external analytics provider.
What is collected. Page views on the website, usage of the public API demo, and account milestones such as starting a signup, completing a signup, creating an API key, and starting a subscription. Each event records the page or endpoint path, the event type, and a small number of non-identifying technical details (for example, the HTTP status and response time of a demo request). If you arrive through a campaign link, the campaign tags in that link (utm_source and utm_campaign) are recorded when present, so we can tell which channel you came from.
The identifier. A single first-party cookie, set only after you actively grant consent through the consent banner, valid for 12 months. Until you grant consent, or if you decline, events are still recorded, but without this cookie and without any other identifier attached: those rows are aggregate counts, not a record tied to you. Declining, or not yet deciding, does not reduce how much traffic we count; it removes our ability to link your visit to a person or an account.
What we never collect. We do not store your raw IP address, your full browser user-agent string, the full URL of the page that referred you, or precise coordinates. Where a referring page or a device location matters, we keep only a coarse version (referring host name, or coordinates rounded to roughly 11 km) that is not enough to identify you or your exact location.
Lawful basis. Identified analytics, meaning any row carrying the cookie described above, rely on your consent. Aggregate counts that carry no identifier rely on our legitimate interest in knowing how many people use the site and the demo, without that data being tied to any individual.
Retention.Analytics records are kept for 12 months and then deleted automatically by a nightly housekeeping job. That job deletes both the event records themselves and the link between a consenting visitor’s cookie and their account. We do not keep this data indefinitely.
No third parties. This data is not sent to, sold to, or shared with any third party. It stays on our own infrastructure and is used only to understand and improve the product.
Withdrawing consent. You can withdraw consent at any time by clearing the di_consent and di_anoncookies in your browser (for example, via your browser’s site-data settings). Once cleared, later visits are treated as not yet decided until you make a new choice in the banner.
Part C - Common
9. Third-party data sources
To provide weather and aviation information, the service queries the following third-party providers. Approximate coordinates are sent to these providers when a forecast is requested:
- MET Norway - forecast and radar nowcast
- SMHI - meteorological data, used inside its national coverage
- AviationWeather.gov - METAR / TAF aviation weather
Baseline forecast data is computed in-house against open national weather-agency model outputs that we sync to our infrastructure directly; no coordinates are forwarded to a third party for that path.
Each of these providers has its own privacy practices. We send only the coordinates required to retrieve public weather information; no personal identifiers are transmitted.
Notifications may be delivered through Expo and the Apple and Google push services, and RevenueCat may confirm subscription status.
10. Data retention
- Location queries are processed transiently and not retained on our servers beyond cache TTLs (up to 24 hours for static airspace, typically 5-30 minutes for weather).
- Standard server access logs are retained for up to 30 days for security and diagnostics, then deleted or rotated.
- API usage analytics (request counts, endpoint, status, latency) are retained for 90 days for billing and abuse prevention.
- Website and demo product-analytics records, and the link between a consenting visitor and their account, are retained for 12 months (see Part B, section 8).
- Notification data is kept while notifications are on; see section 5.
- Purchase status records are retained by RevenueCat, Apple, Google, or Stripe according to their own retention policies.
11. Your rights
The mobile app does not ask for your name or email. Section 5 explains how notification data is deleted. For web accounts, you may request access to or deletion of your account data at any time. Contact [email protected] for any data-subject access request, deletion, or privacy question. We will respond within 30 days.
12. Children’s privacy
The service is not directed to children under 13. We do not knowingly collect information from children under 13.
13. Security
We use HTTPS for all communication between clients and our servers. Third-party providers we rely on also use encrypted transport. No method of electronic transmission or storage is 100% secure, but we apply commonly accepted industry practices to protect data in transit.
14. Changes to this policy
We may update this policy from time to time. The “Last updated” date at the top reflects the latest version. Significant changes will be announced in the app or on the listing page.
15. Contact
Privacy requests and general support: [email protected].
Mobile app: DroneInfo (package com.deeploy.droneinfo).
Legal disclaimer
DroneInfo provides advisory information only. It does not grant permission to fly in any airspace. Always verify airspace restrictions through official sources before every flight - the appropriate national drone-airspace authority for your location (for example the EASA drone-zones map within the EU, the FAA B4UFLY service in the United States, or your local civil aviation authority).