Privacy Policy

Privacy Policy

Overview

NiteOcean is a premium Digital Flight Deck developed and operated by Fly Away Today Ltd, a UK registered company. This policy explains how we handle information when you visit niteocean.com, create or use a NiteOcean account, use Ask the Captain, the Digital Logbook and account-support routes, manage subscriptions or contact us about the product.

Data Controller

Fly Away Today Ltd is the data controller for personal data processed through NiteOcean. For privacy questions or requests, contact us at [email protected].

Information We Collect

We collect information you choose to provide, such as your name, email address, authentication information processed by Supabase, account profile details, pilot profile information, saved aircraft or airport preferences, avatar uploads, support messages and other information you enter into NiteOcean. Supabase also provides a stable internal user identifier which NiteOcean uses to associate account services and protect account isolation.

Digital Logbook information may include manually entered flight records, imported or scanned logbook pages, aircraft type and registration, departure and arrival information, flight times, role, takeoffs, landings, remarks, endorsements, import jobs, draft rows and related aircraft or flight information supplied by you.

If you use Ask the Captain, we process the question you submit, the response produced for you, and limited recent conversation context needed to provide a coherent reply. Depending on where you invoke the feature, NiteOcean may also provide relevant trusted aviation context, such as current pilot-briefing information, or logbook context that the feature makes available for that request. Ask the Captain is not given unrestricted access to your account or device data.

NiteOcean uses per-user local device storage for some logbook and account-related data. Authenticated users have a user-scoped local logbook store so one account's local records are not intentionally shown to another account on the same device. Cloud backup stores supported account data in Supabase for recovery and durability. Where multi-device synchronisation is available to your plan, including Captain multi-device synchronisation, NiteOcean may reconcile the current user's cloud logbook rows with that same user's scoped local store across devices.

Subscription status, purchase history relevant to entitlement, active store product identifiers and store-management links may be processed through Google Play, the Apple App Store and RevenueCat so NiteOcean can unlock and display the correct plan. NiteOcean uses your Supabase user ID as the RevenueCat App User ID. Google Play and the Apple App Store handle payment credentials and payment methods; NiteOcean does not receive full payment-card details.

To apply Ask the Captain plan allowances, NiteOcean sends your authenticated Supabase account identifier to RevenueCat as the RevenueCat App User ID and reads the active entitlements for that customer. NiteOcean records non-content operational metadata for quota, reliability and abuse prevention, such as the UTC usage date, plan resolved by the server, a client request reference, request state, timestamps, model-call and token-usage counts, and a bounded error category. The quota ledger does not store the text of your question or response.

If you enable Analytics in the app, NiteOcean may collect optional app usage and engagement analytics such as app opens, sessions, logical screen views and bounded feature or subscription events.

We may also receive basic technical information from hosting, security and backend services, such as IP address, browser or device type, pages or endpoints requested, timestamps, diagnostics needed to operate the service and similar operational metadata.

AI-Assisted Logbook Processing

If you use AI-assisted logbook import, uploaded logbook pages or files may be processed to extract structured flight information for your review. NiteOcean stores import files and draft extraction results in Supabase and may route extraction requests through NiteOcean backend services on Cloudflare to OpenAI for the implemented AI-assisted processing path.

Extracted entries are intended to help prepare draft logbook rows for user review before final confirmation. AI-assisted extraction can be incomplete or inaccurate, and NiteOcean does not guarantee that AI output is correct. You remain responsible for reviewing and confirming any imported logbook information before relying on it.

Ask the Captain

When you use Ask the Captain, NiteOcean routes your question, limited recent conversation context and any relevant trusted aviation or logbook context through NiteOcean backend services on Cloudflare to OpenAI to generate a response. Cloudflare processes the request as NiteOcean's backend platform, and OpenAI processes the submitted content to provide the requested AI response. Ask the Captain can be incomplete or inaccurate and is not a substitute for official aviation information, operational judgement or a pilot's responsibility for a flight decision.

If Ask the Captain history is enabled, the question and response are stored in Supabase as part of your account's conversation history. If history is disabled, NiteOcean does not add the question or response to saved conversation history. To make a completed response recoverable after an interrupted delivery, NiteOcean may temporarily store an encrypted copy of that request and response in Supabase. The copy is encrypted before storage using a key held in the Ask the Captain Worker environment and is bound to your authenticated account and request reference. It becomes inaccessible through the authorised recovery path no later than 26 hours after creation and is then removed through bounded scheduled cleanup. It is not stored as plaintext in the quota ledger.

You can control whether future Ask the Captain conversations are saved, clear Ask the Captain history, delete individual saved conversations and delete your NiteOcean account. Clear History removes saved Ask the Captain conversations and outstanding temporary encrypted response recoveries for your account. During the version 1.3 transition, deleting a saved Ask the Captain conversation from an older client may also remove your account's outstanding temporary encrypted recoveries; it does not delete your other saved conversations or refund used quota.

How We Use Information

We use information to provide and secure your account, operate Ask the Captain and its daily allowances, operate the Digital Logbook, support cloud backup and eligible multi-device synchronisation, process logbook imports, display subscription entitlements, send account and security communications, respond to enquiries, understand feature usage where Analytics is enabled, improve reliability and meet legal or regulatory obligations. Ask the Captain operational metadata is also used to enforce daily quotas, prevent duplicate execution, recover completed responses, investigate failures, control abuse and monitor service cost and reliability.

Lawful Bases

Where UK data protection law applies, our lawful bases depend on the purpose of processing. Account creation, authentication and core NiteOcean service delivery are processed as necessary for performance of our contract with you. Digital Logbook, cloud backup and eligible multi-device synchronisation are processed as necessary to provide the NiteOcean services you use. Subscription entitlement and account-plan processing are processed as necessary to provide paid plan access. Ask the Captain prompt processing, requested contextual processing, response delivery, optional history storage and subscription-entitlement verification are processed as necessary to provide the feature and plan allowance you ask us to use under our contract with you.

We process security, fraud-prevention, abuse-prevention, service-integrity and necessary operational diagnostic information, including non-content Ask the Captain quota, idempotency, security and cost telemetry, where necessary for our legitimate interests in protecting NiteOcean, users and the integrity and security of the service. We process information where necessary to comply with applicable legal, tax, accounting or regulatory obligations. Where NiteOcean relies on consent for an optional processing activity, you may withdraw that consent where applicable; choosing to use a feature does not automatically mean consent is the lawful basis for all related processing.

Cookies And Analytics

NiteOcean may use necessary local storage or similar device storage to keep account sessions, app preferences, per-user local logbook data and operational state.

If you enable Analytics in the app, NiteOcean uses Firebase / Google Analytics for product usage analytics. Analytics collection is disabled until you opt in. Measured data may include app opens, sessions, logical screen views and bounded feature or subscription events.

NiteOcean's custom analytics events do not include your email, name, account identifiers, precise location, aircraft registration or hex, Digital Logbook records or totals, Ask Captain prompts or responses, airport search terms or ICAOs, METAR/TAF/NOTAM contents, receipts, tokens or payment credentials.

Advertising ID collection is disabled, and ad personalization and ad user-data signals are disabled.

Sharing

We do not sell personal information. We share limited information with service providers who help us host, secure, operate, authenticate, process subscriptions, support logbook import features or communicate about NiteOcean, or where disclosure is required by law.

Service providers involved in these processing activities include Supabase for authentication, account data, database storage, private storage, optional Ask the Captain history, temporary encrypted response recovery and Edge Functions; RevenueCat for subscription customer identity, purchase-status and entitlement processing; Google Play and the Apple App Store for store billing and subscription management; Firebase / Google Analytics for product usage measurement only when Analytics is enabled; Resend for transactional account emails; OpenAI for Ask the Captain responses and AI-assisted logbook extraction when those features are used; and Cloudflare for public website hosting and NiteOcean backend or Worker processing. NiteOcean limits the information shared with each provider to information needed to provide and protect the relevant service.

International Transfers

NiteOcean is operated from the UK, but the service providers listed above may process personal data outside the UK, including in the United States and other countries where they or their sub-processors operate. This includes Ask the Captain processing by Cloudflare and OpenAI and subscription-entitlement verification by RevenueCat where those providers or their sub-processors process information outside the UK. Where a transfer of UK personal data requires a safeguard, we rely on the provider's applicable data processing terms and transfer safeguards where available, such as Standard Contractual Clauses, the UK International Data Transfer Addendum, Data Privacy Framework participation or other lawful mechanisms made available by that provider.

Provider transfer mechanisms can change and may depend on the specific service, contracting entity and processing location. NiteOcean relies on mechanisms made available under the relevant provider's applicable contractual or privacy documentation.

Retention

We keep account, logbook, import and operational records for as long as needed to provide the service, maintain account-backed recovery or synchronisation, support security, resolve disputes, comply with legal obligations or meet legitimate business requirements. We do not set a fixed retention period for every category because retention depends on the account state, feature used and operational need.

Saved Ask the Captain conversation history remains associated with your account until you delete an individual conversation, clear the history or delete the account, subject to the limited exceptions below. When history is disabled, a completed response can be recovered for no longer than 26 hours after creation. The temporary record is stored only in encrypted form, becomes unavailable through the authorised recovery path when it expires, and is removed by bounded scheduled cleanup. Non-content Ask the Captain quota, request-reference, model-call, token-usage and entitlement-verification metadata remains available to NiteOcean's operational systems for no more than 90 days. At the end of that access period, it is no longer used for quota, entitlement, completed-request recovery or other user-facing decisions and is queued for bounded scheduled deletion. Physical deletion may follow after the access period where a cleanup run is delayed or has a backlog. This account-scoped metadata is removed earlier when you delete your account. Short-window abuse-prevention records are removed on a shorter operational schedule, and expired entitlement cache entries are not used to grant paid access. Clearing history does not refund or erase consumed daily quota.

Local device data may remain on a device until it is cleared by the app, by account deletion cleanup, by the operating system or by the user. Cloud account data is handled through the account-deletion process described below, subject to the limited retention exceptions in this policy.

Account Deletion

You can request deletion of your NiteOcean account and associated account data from inside the app or at niteocean.com/account-deletion/. The in-app deletion flow removes the Supabase Auth user, account/profile data and associated NiteOcean user data tied to that account, including cloud logbook and import records, uploaded avatar files, uploaded logbook import files and account-backed usage records where applicable, Ask the Captain conversations and messages, temporary encrypted response recoveries, recovery-clear state, and account-scoped quota and entitlement cache rows.

The deletion backend cleans the configured private storage prefixes for avatars and logbook imports, deletes the associated RevenueCat customer record where applicable for the Supabase UUID used as the RevenueCat App User ID, then deletes the Supabase Auth user so database cascade rules can remove user-owned rows. After an in-app deletion succeeds, NiteOcean also clears device-local NiteOcean user data on that device where practical.

We may retain limited records when reasonably required for security, fraud prevention, legal compliance, dispute handling, tax or accounting obligations, or to protect the integrity of the service. Deleting your NiteOcean account does not automatically cancel an active Google Play or App Store subscription; billing must be managed separately through the applicable store subscription settings. Store purchase history is controlled by the relevant app store, and a future store restore may make store purchase records available again through RevenueCat.

Your Rights

Depending on your location and the applicable lawful basis, you may have rights to request access, correction, deletion, restriction or portability of personal information, to object to certain processing, and to withdraw consent where processing relies on consent. These rights can depend on the circumstances and applicable legal exemptions. You can use the in-app Delete Account flow for account deletion, visit niteocean.com/account-deletion/, or contact us at [email protected] for privacy requests.

Complaints

You can contact Fly Away Today Ltd at [email protected] with privacy concerns. If you are in the UK, you also have the right to complain to the Information Commissioner's Office (ICO) at ico.org.uk/make-a-complaint/.

Contact

For privacy questions or product enquiries, contact Fly Away Today Ltd at [email protected].