Privacy Policy

Nimbent - Last Updated: July 20, 2026

FR — Version française

1. Overview

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.

2. Information We Collect

2.1 Account And Authentication Information

• Email address, display name, Firebase user ID, authentication provider, and account settings.
• Sign-in metadata needed to keep your account secure and restore access across devices.

2.2 Operational Information You Enter

• Jobs, clients, sites, landmarks, scheduled dates, job notes, and related attachments.
• Flight records, including dates, times, aircraft, batteries, crew notes, locations, weather context, altitude/distance fields, incidents, and compliance notes.
• Aircraft, battery, propeller, maintenance, checklist, incident, and insurance-claim records where you use those app features.
• Settings and preferences such as units, theme, notifications, sync preferences, and language.

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.

2.3 Files And Reports

• Files you upload or import, where supported by the app, operating system, and source app.
• Generated exports you create through the app, which may include CSV, PDF, ZIP, JSON, or similar files where supported by the feature used.

2.4 Device, Diagnostic, And Usage Information

• Device type, operating system, app version, language, platform, and technical diagnostics.
• Crash reports, error logs, performance information, and limited user identifiers where needed to debug authenticated issues.
• Feature usage and support interactions needed to provide, secure, and improve the service.

2.5 Website, Forms, And Support Information

• Information you submit through contact forms, support email, support feedback, or support chat.
• Email marketing preferences, including whether you consented to receive promotional messages.

3. How We Use Information

• Provide flight logging, job management, equipment tracking, maintenance records, exports, support, and account functionality.
• Authenticate users, prevent abuse, sync data, restore purchases, and enforce subscription entitlements.
• Provide weather, map, traffic, geocoding, and aviation-weather features when requested.
• Respond to support requests, troubleshoot errors, and improve reliability.
• Send transactional messages such as support responses, account notices, deletion confirmations, billing notices, trial notices, and important service updates.
• Send promotional communications only where you have opted in or where otherwise permitted by law.
• Comply with legal, tax, fraud-prevention, security, store, and regulatory obligations.

4. Storage And Security

4.1 Local Storage

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.

4.2 Cloud Storage And Sync

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 Montreal, Canada, for supported Firebase backend functions and storage where configured.

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.

4.3 Security Measures

• Firebase Authentication for account access.
• Encrypted network connections for app/backend communication.
• Firebase security rules, App Check monitoring/enforcement where configured, and rate limits on selected callable functions.
• Provider secrets stored outside the mobile app bundle where server-side functions are used.

No service can be guaranteed completely secure. If you believe your account or data has been compromised, contact us at privacy@nimbent.com.

5. Service Providers

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, App Check, crash/error reporting	Email, user ID, app data, files, device/app diagnostics, crash logs
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
Brevo	Transactional email, contact management, optional marketing where enabled	Email address, name, consent status, message type, and message metadata
Anthropic	In-app support chat assistance	Support prompts, recent chat context, generated responses, and limited account/support 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

6. Location, Maps, Weather, And Traffic

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.

• We do not use background location tracking for continuous monitoring.
• Location is used when you actively use location-based features or save location data in records.
• Coordinates or map bounds may be sent to weather, geocoding, map, aviation-weather, or live-traffic providers when you use those features.
• Location saved inside jobs, flight records, incidents, or reports may sync to Firebase if cloud sync or cloud-backed records are enabled.
• You can disable location permission in device settings, but some features may require manual entry or may not work.

7. Support Chat And AI Assistance

Nimbent may provide support chat or support assistance powered by Anthropic. When you use support chat, the text you enter and relevant support context may be sent to Anthropic and processed to generate a response.

• Do not submit sensitive information that is not needed for support, such as full payment card details, passwords, government ID numbers, or unrelated personal information.
• Support chat may be rate-limited, logged for abuse prevention, and reviewed to troubleshoot issues or improve support quality.
• AI responses are informational support assistance only and should not be treated as legal, regulatory, aviation, weather, insurance, or safety advice.

8. Subscriptions And Payments

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.

• Subscription records may include product ID, entitlement status, renewal/expiration status, store platform, and general transaction identifiers.
• Deleting your Nimbent account does not automatically cancel Apple or Google billing. You must cancel subscriptions through the store where you purchased them.
• Apple, Google, and RevenueCat may retain billing and subscription records according to their legal, tax, refund, fraud-prevention, and store-policy obligations.

9. Email And Marketing Communications

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.

• Transactional messages may be sent for account, support, deletion, billing, trial, or service purposes.
• Promotional messages are sent only where you have opted in or where permitted by law.
• You can unsubscribe from marketing messages using the unsubscribe link or by contacting us.

10. Cookies And Local Storage

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.

11. Flight Logs And Manufacturer Files

Nimbent may support manual flight records and supported imports where files are available to the user through normal operating-system workflows. Nimbent does not silently access private Android app folders used by DJI Fly or other manufacturer apps when the operating system does not allow third-party access.

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.

12. Sharing And Disclosure

We do not sell your personal information. We may disclose information:

• To service providers listed in this policy so they can operate the services we use.
• When you choose to export, download, share, email, or otherwise send a report or file.
• To comply with law, legal process, tax, security, fraud-prevention, or store obligations.
• To protect the rights, property, safety, and security of Nimbent, users, service providers, or others.
• In connection with a corporate transaction involving Cedar Orbit Labs Inc. or the Nimbent product, with appropriate notice or safeguards where required.

13. Retention, Export, And Deletion

13.1 Retention

• Local app data remains on your device until you delete it, clear app data, uninstall the app, or delete your account from within the app.
• Cloud account and operational records are retained while your account is active, unless deleted sooner through the app or a verified request.
• Support, email, diagnostic, security, and billing-related records may be retained as needed for support, legal, tax, audit, security, fraud-prevention, dispute, and operational purposes.
• Provider logs and app-store billing records are retained according to the relevant provider's policies.

13.2 Export

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.

13.3 Account Deletion

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, subject to limited retention for legal, billing, security, abuse-prevention, dispute, or provider-policy reasons.

14. Your Rights And Choices

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.

• Access, edit, export, or delete many records directly in the app.
• Use device settings to control permissions such as location and notifications.
• Use store subscription settings to manage or cancel billing.
• Use unsubscribe links or contact us to manage promotional email.
• Contact privacy@nimbent.com for access, correction, deletion, or privacy questions.

We may need to verify your identity before fulfilling certain requests.

15. Children's Privacy

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.

16. International Processing

Nimbent is operated from Canada and uses service providers that may process information in Canada, the United States, the European Union, or other jurisdictions. These jurisdictions may have different privacy laws than where you live. We use service providers and safeguards appropriate for the service being provided.

17. Changes

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.

© 2026 Cedar Orbit Labs Inc. All rights reserved.