LegalLaw Enforcement & Government Data Requests
Law Enforcement & Government Data Requests
1. Who we are
Being Optimal operates a B2C pregnancy-nutrition technology platform (planner, account surfaces, optional AI assistant, optional community forum, help/content). We are not a healthcare provider, hospital, or clinical laboratory.
Significant categories of data may also reside with sub-processors (Authentication Provider, Database Provider, AI Model Providers, Community Platform Provider, Email Delivery Provider, Billing Provider when live, etc.). Named vendors are listed only in the Sub-processor List. Requests for data held solely by a provider may need to be directed to that provider; we will say so when we can.
2. Valid legal process required
We disclose user Personal Data only when compelled by valid legal process appropriate to the data sought and the requesting authority’s jurisdiction. Examples (illustrative; not exhaustive):
| Data sensitivity (illustrative) | Typical process expectation |
|---|---|
| Basic subscriber / account identifiers | Subpoena, court order, or equivalent under applicable law |
| Stored content (e.g., meal logs, journal, AI conversation content) | Court order, warrant, or equivalent where required |
| Real-time intercept / prospective collection | Generally not something we provide as a product capability; process and technical feasibility reviewed case-by-case |
We may:
- Reject or require additional process for requests that are facially invalid, overbroad, or from a jurisdiction lacking authority;
- Seek clarification or narrowing;
- Consult counsel before responding.
Civil litigants should use lawful civil process (subpoena/court order) served as described in Contact And Legal Notices. We are not a general discovery shortcut for private disputes.
3. How to submit a request
Send requests on official letterhead to:
[email protected] (Copy optional: [email protected])
Include:
- Requesting agency, authorized officer name, badge/ID number if applicable, and direct contact information;
- Legal authority and jurisdiction;
- Specific data sought (categories, date ranges — not “all data ever”);
- Account identifiers (email, user id if known, Environment identifiers if known);
- Response deadline and preferred secure delivery method;
- Any non-disclosure / gag order, with legal basis and duration;
- For emergency requests: factual basis for imminent risk (see §6).
We do not accept law-enforcement data requests via social media, community forums, or unverified phone calls alone.
4. What we may hold (illustrative)
| May be available from Being Optimal (subject to process & retention) | Often with a third party |
|---|---|
| Account email / auth subject linkage we store | Full Authentication Provider account archives |
| Profile & pregnancy-related health fields, meal logs, journal | — |
| AI conversation content we persist | AI Model Provider logs under their retention |
| Notification / push metadata we store | Device push infrastructure |
| Community identity linkage we control | Community Platform Provider post/upload archives |
| Limited operational logs | Hosting / edge provider logs |
| Billing status metadata (when live) | Full payment instruments & invoices at 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 (e.g., a valid non-disclosure order);
- Notice would create an imminent risk of death or serious physical harm, or otherwise be unlawful/counterproductive under applicable law;
- The request is for non-content data where notice is not required and would not be reasonably expected under our Privacy Policy — we still prefer notice where lawful.
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:
- Expedite legal and operational review;
- Disclose information we reasonably believe necessary to prevent the emergency, consistent with applicable law;
- Require the requesting officer to document the emergency basis in writing as soon as practicable.
Emergency channels: [email protected] with subject line clearly marked EMERGENCY.
This section does not create a duty to monitor user content or to act as a crisis hotline. Users in crisis should contact local emergency services; product safety redirects are described in the Medical Disclaimer.
7. Data minimization, preservation, and cost
| 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, letters rogatory, or domestic law implementing international cooperation. We evaluate foreign process with counsel and may require domestic legal process in our incorporation jurisdiction ([PENDING: INCORPORATION_JURISDICTION] — token to be finalized).
9. Related privacy rights of individuals
Individuals seeking their own data should use the Data Subject Request Procedure ([email protected]), not this law-enforcement channel.