LegalCookie Policy

Cookie Policy

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

At a glance

We use essential cookies and similar technologies so you can sign in, stay signed in, and use the planner.
Theme and some interface preferences live in first-party local storage, not in advertising cookies.
Browser push is optional. We store a Web Push subscription (VAPID / Web Push) only if you enable notifications.
Clicks on certain partner links may create a first-party, pseudonymous event. The stored record does not include your user id. Your IP address is used only briefly for rate limiting and is not stored on the click record.
We do not use third-party advertising cookies, session-replay products, or marketing pixels today. We do not currently show a cookie banner because we do not use non-essential third-party cookies. If that changes, we will update this policy and add a consent step where required.
The public website may operate a normal visit counter by our CDN / Edge Network Provider. This sets no cookie, stores nothing in your browser, and is not used for advertising.
Help Center search runs in your browser and does not leave the device.
AI assistant or planner data you sync reaches our Database Provider.

The full terms below control.

1. Who We Are

This Cookie Policy explains how Nativity Ltd (Optimal, Optimal Being) uses cookies and similar technologies on beingoptimal.org and related product surfaces.

Controller details and contacts are in the Privacy Policy and Contact & Legal Notices. Privacy questions: [email protected]. Defined terms follow the Definitions.

2. Cookies & Similar Technologies

Cookies are small text files a site stores on your device. Local storage can hold preferences and other first-party data in the browser. Beacons are small requests that tell our servers an event occurred (for example, that a partner link was clicked). Push subscriptions let the browser deliver notifications you have enabled.

In this policy, “cookies” includes these technologies unless a distinction matters.

3. What We Use

3.1 Essential Cookies

These are needed to provide the service you ask for:

Sign-in and session cookies from our Authentication Provider, on our domain and on the provider’s domains if necessary. They keep you signed in and help protect the session. They do not store your meal logs or journal text.
Environment (planning profile) selection, so the product can open the workspace you last used.
Security and delivery cookies from our Hosting Provider and CDN / Edge Network Provider, used to serve the site reliably.

Without essential authentication cookies, you cannot sign in or use the synced planner.

3.2 First-Party Functional Storage

We store some preferences on your device, typically in local storage rather than cookies:

Theme (for example, light or dark).
Basic interface state for the planner.
Help Center search, which runs in the browser. Help search queries do not leave your device. This does not apply to the AI assistant or to data you sync to our Database Provider.

Clearing site data may reset theme and local-only state, and may sign you out.

3.3 Browser Push

If you enable notifications, your browser creates a Web Push subscription. We store the subscription details we need to deliver the notices you opted into. Push is not required to browse public pages. You can turn it off in browser or product notification settings, and account deletion is described in the Privacy Policy.

3.4 Outbound Clicks

When you click certain partner or Certified brand links, we may record a first-party event (brand, destination, and similar fields). That stored record is pseudonymous: it does not include your user id. Your IP address is used only briefly for rate limiting and is not stored on the click record.

This is not a third-party advertising cookie network. See the Advertising & Affiliate Disclosure.

3.5 First-Party Catalog Analytics

We collect first-party analytics about catalog use (for example, which foods people choose, with your country or region and age band) and about which topics people view next to one another. This is on by default and you can turn it off in the Privacy Center. Signals about your health details (symptoms, blood results, stage of pregnancy), your weight, or your ancestry are included only if you give a separate, explicit consent (see Privacy Policy sections 6 and 9.1). These events stay on our infrastructure. They are not sold to advertising networks. We keep them as needed for product improvement (As needed for product improvement (first-party, pseudonymous)).

Health data used for planning is not placed in marketing cookies. That processing is described in the Privacy Policy.

4. What We Do Not Use

We do not currently use:

third-party advertising cookies or ad pixels;
third-party session-replay products;
third-party marketing or behavioral analytics pixels on the consumer app.

We do not use non-essential third-party advertising cookies. If that changes, we will update this policy and add a consent step where required. We do not currently show a cookie banner because we do not use those cookies.

5. Other Parties

Authentication Provider. Sign-in may set essential cookies on the provider’s domains. See the Sub-processor List.

CDN / Edge Network Provider. On the public website, a small script from this provider may count page views and measure performance. It uses no cookies or local storage and does not build a profile of you from your IP address or browser details. See the Sub-processor List.

Community Platform Provider. If you visit the community (https://community.beingoptimal.org), that host may set its own cookies for forum use. Review any notice on that host.

AI Model Providers. AI calls are server-side API requests. Model vendors do not set advertising cookies in your browser through those calls.

Reverse-Geocoding Provider. Place lookup is a server-side call with coordinates we send. It does not set a geolocation advertising cookie on your device.

We aim not to embed third-party social, video, or advertising frames that set tracking cookies on primary product pages. If a future embed requires it, we will update this policy and the consent experience.

6. Controlling Cookies

You can block or delete cookies in your browser. Blocking essential cookies will prevent sign-in and synced planner use.

You can clear local storage with other site data. Where we offer an in-product analytics control, you can turn analytics off going forward, and you can withdraw each separate consent for health-detail, weight and ancestry signals at any time. Historical first-party analytics may be kept in aggregate or pseudonymous form as described in the Privacy Policy.

We do not change essential cookies based on older “Do Not Track” headers. For US state sale/share opt-out signals such as Global Privacy Control (GPC): our current model does not sell personal information and does not use third-party advertising cookies. See the US annex in the Privacy Policy. If our practices change, we will honor applicable browser signals as required by law.

7. Changes

We may update this Cookie Policy when our technologies change. If we introduce non-essential third-party cookies, we will highlight that change and, where required, add a consent step.

See also the Privacy Policy and Terms of Service.

8. Contact

[email protected] · [email protected] · [email protected] Nativity Ltd · 167-169 Great Portland Street, 5th Floor, London, England, W1W 5PF