Skip to content
Optimal
ConnectPlansApp
Sign inGet started

Legal / Law Enforcement & Government Data Requests

Law Enforcement & Government Data Requests

Version 5.0.0 · Effective 2026-10-18 · Operator Nativity Ltd

At a glance

  • Requesting agencies must serve valid legal process before we disclose user data.
  • Health data is treated carefully. Optimal is not a healthcare provider.
  • We notify affected users unless legally prohibited or notice would create imminent harm.
  • Submit requests to [email protected] on official letterhead, with specificity.
  • We may hold account, planner, and AI content that we persist. Some data lives only with sub-processors.
  • Emergency requests involving imminent death or serious physical harm have an expedited channel.
  • Individuals seeking their own data should use the Data Subject Request Procedure, not this channel.

The full terms below control.

Contents

  1. 1. Who We Are
  2. 2. Valid Legal Process
  3. 3. Submission
  4. 4. What We May Hold
  5. 5. User Notice
  6. 6. Emergency Requests
  7. 7. Minimization, Preservation, Related Practices
  8. 8. Mutual Legal Assistance & Foreign Process
  9. 9. Data Of Individuals

1. Who We Are

Optimal operates a consumer pregnancy-nutrition technology platform (planner, account surfaces, optional AI assistant, optional community forum, and help content). We are not a healthcare provider, hospital, or clinical laboratory.

Significant categories of data may also reside with sub-processors (including the Authentication Provider, Database Provider, AI Model Providers, Community Platform Provider, Email Delivery Provider, and Billing Provider). Named providers appear only in the Sub-processor List. Requests for data held solely by a provider may need to be directed to that provider.


2. Valid Legal Process

We disclose user Personal Data only when compelled by valid legal process appropriate to the data sought and the requesting authority's jurisdiction. Examples are illustrative, not exhaustive:

Data sensitivity (illustrative) Typical process expectation
Basic subscriber or account identifiers Subpoena, court order, or equivalent under applicable law
Stored content (for example, meal logs, journal, AI conversation content) Court order, warrant, or equivalent where required
Real-time intercept or prospective collection Generally not a product capability we provide. Process and technical feasibility are reviewed case by case.

We may reject or require additional process for requests that are facially invalid, overbroad, or from a jurisdiction lacking authority. We may seek clarification or narrowing, and we may consult counsel before responding.

Civil litigants should use lawful civil process (subpoena or court order) served as described in Contact and Legal Notices. We are not a general discovery shortcut for private disputes.


3. Submission

Requesting agencies should send process on official letterhead to:

[email protected] (Copy optional: [email protected])

Include:

  1. Requesting agency, authorized officer name, badge or ID number if applicable, and direct contact information;
  2. Legal authority and jurisdiction;
  3. Specific data sought, including categories and date ranges;
  4. Account identifiers, such as email or user id, if known;
  5. Response deadline and preferred secure delivery method;
  6. Any non-disclosure order, with legal basis and duration;
  7. For emergency requests, a factual basis for imminent risk.

We do not accept law-enforcement data requests via social media, community forums, or unverified phone calls alone.


4. What We May Hold

Availability is always subject to valid process and our retention practices.

May be available from us Often with a third party
Account email and authentication-subject linkage we store Full Authentication Provider account archives
Profile and pregnancy-related health fields, meal logs, journal Usually only in our systems
AI conversation content we persist AI Model Provider logs under their retention
Notification or push metadata we store Device push infrastructure
Community identity linkage we control Community Platform Provider post and upload archives
Limited operational logs Hosting or edge provider logs
Billing status metadata Full payment instruments and invoices at the Billing Provider

We disclose only what we reasonably possess and what valid process requires. We do not provide bulk dumps of unrelated users.


5. User Notice

We notify affected users of government or law-enforcement requests for their data so they may seek to quash or limit disclosure, unless:

  • We are legally prohibited. For example, by a valid non-disclosure order;
  • Notice would create an imminent risk of death or serious physical harm, or would otherwise be unlawful under applicable law.

When a non-disclosure order expires, we may notify the user of the prior request.


6. Emergency Requests

For requests asserting an imminent risk of death or serious physical harm, we may:

  1. Expedite legal and operational review;
  2. Disclose information we reasonably believe necessary to prevent the emergency, consistent with applicable law;
  3. Require the requesting officer to document the emergency basis in writing as soon as practicable.

For an emergency channel, please contact [email protected], with the subject line clearly marked EMERGENCY.

This section does not create a duty to monitor user content or to act as a crisis hotline. People in crisis should contact local emergency services. Product safety redirects are described in the Medical Disclaimer.


7. Minimization, Preservation, Related Practices

Practice Detail
Minimization Disclose only data within the scope of valid process
Preservation We may honor lawful preservation requests for a limited period pending valid process
No backdoors We do not provide unrestricted bulk access or continuous surveillance feeds as a product feature
Costs We may seek reimbursement for extraordinary costs where permitted by law
Transparency We may publish aggregate request statistics where lawful and operationally practical

8. Mutual Legal Assistance & Foreign Process

Requests from foreign authorities may require process under applicable mutual legal assistance treaties (MLATs), letters rogatory, or domestic law implementing international cooperation. Foreign process may need to be accompanied by domestic legal process in our incorporation jurisdiction (England and Wales, United Kingdom).


9. Data Of Individuals

Individuals seeking their own data should use the Data Subject Request Procedure ([email protected]), not this law-enforcement channel.


See also: Privacy Policy, Data Subject Request Procedure, Security and Compliance, Contact and Legal Notices, and Sub-processor List.

Content hash: c9e826a0fc0e… · Built 2026-10-18

← Back to the legal hub

Optimal
ProductAppPlansConnect
LearnLibraryNutritionMedicalArticlesHelp
ConnectAI AssistanceSuper IntelligenceAlexa+Early access
Trust and safetyCertifiedPrivacyTermsDisclaimerCookies
PartnershipPractitionersMosaicPartnersAtlasSponsorsAuraAffiliates
CompanyAboutContact
© 2026 Optimal · Life Begins With You

Optimal Being is operated by Nativity Ltd, trading as Optimal. Registered in England and Wales, company no. 17457413. Registered office: 167-169 Great Portland Street, 5th Floor, London, England, W1W 5PF.