Nimbent - Last Updated: November 10, 2026
Nimbent is operated by Cedar Orbit Labs Inc. This Privacy Policy explains how we collect, use, disclose, and protect information when you use the Nimbent mobile app, website, support services, and related services.
Nimbent is designed for drone operations management. It is not an official regulator, air navigation service, weather authority, insurer, or aircraft manufacturer. You remain responsible for verifying operational, regulatory, weather, airspace, and safety information before flight.
Information about third parties. Some operational records you enter — for example client names, email addresses, phone numbers, and site addresses, or crew names — are personal information about other people. You provide this information, and you are responsible for having the authority or consent to enter it and for meeting your own privacy obligations toward those individuals. Nimbent stores and processes this information on your behalf, as a service provider, solely to provide the features you use.
Your choice about analytics. Product analytics is off unless you turn it on. Nimbent collects the product analytics events above, and the compliance-workflow usage records described in this policy, only if “Share usage analytics” is on. After you sign in, the app asks you once, and nothing is collected unless you choose “Share analytics”. You can change it at any time in Settings → Communications → Privacy, and turning it off stops collection. Crash reports are not covered by this switch.
Nimbent stores core app data locally on your device using IndexedDB and related local storage. Local data remains on your device unless you enable sync, use a cloud-connected feature, submit support information, or export/share it yourself. Deleting the app or clearing app data may remove local data from that device.
When cloud sync or cloud-backed features are used, app data may be stored in Firebase services, including Firestore and Firebase Storage. Nimbent uses the Google Cloud region configured for the project, currently northamerica-northeast2 in Toronto, Canada, for the production Firestore database, app Storage bucket and core app backend functions. Separate monitoring services also run in Montréal. Authentication and other Google services have different processing locations, described in Section 16.
With cloud sync enabled, the operational records you create — including jobs, clients, flight records, equipment, checklists, and incident and insurance records — are synchronized across your signed-in devices and stored in the Canadian region above until you delete them or delete your account. Deleting your account removes this data as described in Section 13.
No service can be guaranteed completely secure. If you believe your account or data has been compromised, contact us at privacy@nimbent.com.
We use service providers to operate Nimbent. They process information under their own terms and privacy policies and only for the purposes needed to provide the service.
| Provider | Purpose | Information Involved |
|---|---|---|
| Firebase / Google Cloud | Authentication, Firestore, Storage, functions, flight-log processing, App Check, crash/error reporting | Email, user ID, app data, files including imported flight logs, device/app diagnostics, crash logs |
| DJI | Decryption keys for encrypted DJI flight logs you import | Encrypted key data from the log, the log version, a department code and Nimbent's DJI developer key |
| RevenueCat | Subscription entitlement management | App user ID/Firebase UID mapping, subscription status, store product and purchase metadata, non-card transaction identifiers |
| Apple App Store / Google Play | App distribution, purchases, refunds, subscriptions | Store account and payment information handled by Apple/Google; Nimbent receives purchase/entitlement status, not full card details |
| Google Analytics for Firebase | In-app product analytics (which features are used and where sign-in, onboarding, or purchases fail) | Firebase user ID, app-instance identifier, event names and simple event details, app version, device type, operating system, language, and the approximate region Google derives from the network connection; no advertising identifier, email address, or record contents |
| Brevo | Transactional email, contact management, optional marketing where enabled, and delivery monitoring | Email address, name, Firebase user ID, language, consent status and when and how it was given, email content (including support content or secure action links where applicable), and delivery, bounce, open, and click metadata |
| WeatherAPI, OpenWeatherMap, aviation-weather sources | Weather forecasts, radar tiles, METAR/TAF or aviation-weather context | Coordinates, stations, dates/times, map tile coordinates, and weather query parameters |
| MapTiler, OpenStreetMap contributors, Nominatim fallback, and map tile providers | Maps, address search, reverse geocoding, and map display | Map viewport, search text, coordinates, tile coordinates, and device/network request metadata |
| Live traffic / ADS-B data providers | Optional traffic map layer | Map bounds/viewport coordinates and request metadata |
Nimbent requests location permission to support job/site setup, flight records, nearby map context, weather, airspace planning context, sunrise/sunset calculations, and other field workflow features.
The current app does not offer AI support chat. You can contact support@nimbent.com for help. Older support-chat or feedback records, if any, remain subject to the retention and rights described in this policy. We will assess and explain any future AI support feature before making it available.
Do not send passwords, full payment-card details, government ID numbers, or unrelated sensitive information to support.
Nimbent subscriptions are purchased through Apple App Store or Google Play. We do not collect or store full payment card numbers. RevenueCat helps us determine whether your account has an active entitlement.
If you contact us, create an account, request support, or opt in to updates, we may use Brevo to send transactional messages and manage your email preferences. When you create an account, your email address, Firebase user ID, and language are added to Brevo so we can send account and service messages.
The Nimbent website and app may use cookies, local storage, IndexedDB, or similar browser/device storage to remember preferences, support sign-in, keep the service secure, measure reliability, and understand basic website usage. You can control cookies and local storage through your browser or device settings, but some features may not work correctly if storage is blocked or cleared.
To understand how visitors find the website, each page sends an anonymous visit count to Nimbent: whether it is
the first page of a visit, the referring website's domain, campaign tags in the link (such as
utm_campaign), the page section, and clicks on App Store or Google Play buttons. This uses no
cookies and no identifiers; we keep only daily totals and do not store IP addresses, full URLs or
browsing histories. Your IP address is used briefly, in hashed form, only to limit abuse.
Nimbent supports manual flight records and, on iPhone, imports of supported DJI flight-log files that you choose through normal operating-system workflows, such as the Files picker or the share sheet. On Android, flights are recorded manually: the Android app does not import or upload flight-log files, and it does not access private app folders used by DJI Fly or other manufacturer apps. Flight records you enter manually do not involve uploading any file.
Manufacturer flight logs can contain detailed information, including: the aircraft's position, height, speed, and orientation throughout the flight; takeoff and home-point locations; aircraft, camera, remote-controller, and battery serial numbers and firmware versions; battery condition (charge, voltage, cell voltages, temperature, cycle count, and capacity); flight modes, automated actions such as return-to-home or landing, warnings, and system faults; camera activity, photo and video counts, and storage-card status; app and aircraft settings; and, depending on the aircraft and app, the location of the remote controller or mobile device (which can indicate where the pilot was standing) and small preview images.
Imported flight-log values may include source-app calculations or telemetry fields. You are responsible for reviewing records before relying on them for regulatory, insurance, client, or safety purposes.
We do not sell your personal information. We may disclose information:
Signed-in users can use Settings > Export My Data to create a ZIP export containing local app tables as CSV files, a full JSON backup, a manifest, and the Firebase profile document where available. Export before deleting your account if you want a copy of your records.
You can request account deletion in the app or review the public account deletion instructions. Deletion removes or queues removal of Nimbent-controlled account data according to our deletion workflow, including your cloud records, imported flight-log files, passkeys, the crash reports and usage records linked to your account, and your Brevo contact, subject to limited retention for legal, billing, security, abuse-prevention, dispute, or provider-policy reasons.
Depending on where you live, you may have rights to access, correct, export, delete, or object to certain uses of your personal information. Canadian users may also have rights under PIPEDA and applicable provincial privacy laws.
We may need to verify your identity before fulfilling certain requests. The in-app export may not include every record held by us or our providers; contact our privacy officer for a broader access request or to make a privacy complaint. We respond to access and correction requests within applicable legal deadlines, normally 30 days, and explain any lawful refusal or permitted extension.
Nimbent is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us and we will take appropriate steps to delete it.
Production records synced through Nimbent are stored with Google Cloud in Toronto, Ontario. Firebase Authentication processes information in the United States. Crash reporting and optional usage analytics use Google's global infrastructure, including the United States. RevenueCat stores subscription data in the United States. Brevo hosts its databases in the European Union and uses some infrastructure and support providers outside it. Map, weather and traffic services may also process location queries and request metadata internationally.
Before entrusting personal information outside Québec where Québec law applies, we assess the privacy risks and require applicable written safeguards. Information processed in another jurisdiction may be subject to its laws. Usage analytics is off by default and runs only if you choose to share it.
We may update this Privacy Policy from time to time. We will update the "Last Updated" date and provide additional notice where required by law or where changes materially affect how we process your information.
If you have questions, concerns, or requests about this Privacy Policy or Nimbent's data practices, contact us:
Privacy Officer / person in charge of personal information protection: Joshua Barrow — privacy@nimbent.com
Support: support@nimbent.com
Company: Cedar Orbit Labs Inc.
Mailing address: 3300 Highway 7, Suite 600, Concord, ON L4K 4M3, Canada
© 2026 Cedar Orbit Labs Inc. All rights reserved.