Cookies policy

Last updated: March 11, 2026

Note: If these Terms, Policies, or Agreements are available in multiple languages, and any discrepancies exist between translations, the English version shall prevail.

---

1. What are cookies?

Cookies are small files or browser-side storage records that help a website or web application remember state. In BabySea, they may be used for security, authentication, consent preferences, analytics controls, and related browser-session behavior.

2. Types of cookies we use

2.1 Necessary cookies

These cookies are strictly necessary for the Website and browser-based product surfaces to function properly. They cannot be disabled through the BabySea consent interface because they are needed for security, authentication, consent storage, and basic functionality.

In the current product, necessary cookies include a cross-domain consent cookie (babysea_consent) that shares your consent preferences across BabySea subdomains such as babysea.ai, us.babysea.ai, eu.babysea.ai, and jp.babysea.ai. This cookie is set on the .babysea.ai domain so that your consent choice carries over when you navigate between BabySea properties. It stores only your consent state, a timestamp, and a schema version - it does not contain personal information or tracking identifiers.

2.2 Analytics cookies

When analytics consent is enabled, BabySea may use analytics technologies to understand how visitors interact with the Website and dashboard. These technologies help us:

• Analyze usage patterns and user behavior.
• Improve content delivery and user experience.
• Measure website performance and identify areas for enhancement.

In the current product, analytics consent governs PostHog tracking (in US and EU regions) and Cloudflare Web Analytics loading (in all regions). PostHog may create cookies or browser storage keys with prefixes such as ph_ or _posthog.

2.3 Marketing cookies

BabySea includes a marketing consent category in its banner and settings UI. In the current product, if marketing consent is not granted or is later withdrawn, BabySea attempts to remove common marketing-related cookies such as _fbp, _fbc, _ga*, _gid, and _gcl* when they are present in the browser.

BabySea does not state in this policy that every BabySea property actively serves marketing cookies at all times. The marketing category mainly controls customer consent state and cleanup behavior for common marketing-cookie patterns if they appear.

2.4 Preference cookies

These technologies are intended to remember optional settings and consent choices where BabySea uses them in the browser experience. They may support features such as:

• Cookie consent choices.
• Browser-side display or interface preferences where implemented.
• Other optional user-experience settings that BabySea may store locally in the browser.

3. Similar technologies

BabySea may also use technologies such as:

• Local storage: Browser storage for maintaining user preferences, consent choices, and application state.
• Session storage: Temporary storage that expires when you close your browser.
• JavaScript-based analytics loaders and client-side scripts that respond to your consent settings.

These tools help us remember consent state, improve website and dashboard usability, and enable or disable analytics behavior depending on your choices.

Similar technologies are treated in line with the consent categories described in this policy when BabySea uses them for optional purposes.

4. Managing cookies

You can control your cookie preferences through multiple methods:

4.1 Cookies consent banner

When you first visit a BabySea web property using this consent system, you will see a cookie consent banner that allows you to:

• Accept all cookies.
• Reject all non-essential cookies.
• Customize your preferences by cookie category.

4.2 Cookies settings badge

After providing your initial consent, you will see a small Cookies badge. In the current product, this badge:

• Shows your current consent status with a color-coded indicator.
• Uses a green dot when one or more optional categories are enabled.
• Uses a red dot when only necessary cookies remain active.
• Allows you to change your cookie preferences at any time by clicking on it.
• Remains available as the customer-facing entry point for reopening the cookie settings panel.

4.3 Cookies preferences panel

You can access detailed cookie settings at any time through the cookie preferences interface, which allows you to:

• Toggle Analytics, Marketing, and Preferences on or off.
• View short explanations of each category.

Your consent choices are remembered for 13 months, after which you'll be asked to renew your preferences.

4.4 Browser settings

You can also configure your browser to:

• Block or alert you about cookies.
• Delete existing cookies.
• Disable cookies entirely.

Please note: Disabling essential cookies may affect the functionality of certain features and could prevent core services from working properly.

4.5 Consent withdrawal and automatic cleanup

You can withdraw or modify your consent at any time. When you withdraw consent:

• Optional tracking tied to the withdrawn category will no longer be enabled by BabySea.
• BabySea will attempt category-specific cleanup for supported browser-side records.
• The updated consent state will be stored locally in your browser.

In the current product, BabySea specifically attempts to:

• Opt PostHog out and remove PostHog cookies or storage keys when analytics consent is withdrawn (in regions where PostHog is active).
• Remove common marketing-cookie patterns such as _fbp, _fbc, _ga*, _gid, and _gcl* when marketing consent is withdrawn.

BabySea does not guarantee that every browser-side item created by third parties outside BabySea's control can always be removed immediately in every browser environment.

4.6 Consent storage and record keeping

Your consent preferences are stored locally in your browser using browser storage and a cross-domain cookie controlled by BabySea. The cross-domain cookie (babysea_consent) is set on the .babysea.ai domain so that your consent decision is recognized across BabySea subdomains without requiring you to consent again on each subdomain. In addition:

• Signed-in users may also have consent decisions recorded server-side for compliance and audit purposes.
• Those records may include the consent state, action type, source of the change, region, user agent, and a SHA-256 hashed form of the source IP address. Raw IP addresses are not stored in consent records.

Server-side consent records are only created for authenticated users. They are stored in the regional database that corresponds to the dashboard where the user is signed in. Unauthenticated visitors have their consent stored only in the browser when no signed-in account is present.

5. Cookies table

6. Consent duration and renewal

Your cookie consent choices are valid for 13 months from the date you provided them. After this period, you will be asked to renew your consent to ensure your preferences remain current and compliant with evolving regulations.

7. Data processing and third parties

When you consent to analytics cookies, your data may be processed by analytics providers used by BabySea for the enabled product surface. In the current product, this includes:

• PostHog: For analytics and user behavior tracking (US and EU regions).
• Cloudflare Web Analytics: For privacy-focused traffic and performance analytics (all regions).

These providers are also listed in the List of subprocessors. Our marketing category also supports cleanup of common third-party marketing-cookie names if they exist in the browser.

8. Technical implementation

For transparency, BabySea's current cookie management system:

• Re-prompts for consent after 13 months.
• Stores consent state in browser storage using BabySea-managed keys.
• Shares consent state across BabySea subdomains using a cross-domain cookie on .babysea.ai.
• Attempts cleanup on the current hostname and parent-domain pattern where supported by the browser.
• Records a consent action state such as accept-all, reject-all, or partial.

9. Updates to this policy

We may update this Cookies Policy periodically to reflect changes in technology, legal requirements, or our practices. Updates will be posted on this page with a revised "Last updated" date to keep you informed. We encourage you to review this policy regularly.

If we make material changes that affect how we use cookies, we may notify you through our Services or request renewed consent as required by applicable law.

10. Contact us

If you have questions about this Cookies Policy or need assistance with managing your cookie preferences, please contact us:

• Through our Support page.
• By visiting our Privacy policy for additional contact information.

For specific requests about your data or consent preferences, please use the cookies badge available on our Website.