Skip to content
LEGAL & TRUST

Cookie policy

What the public website stores in your browser, why it is used, and how to control optional analytics.

DRAFT — COUNSEL REVIEW REQUIRED

These documents reflect the intended Homa product and current marketing prototype. They are not effective terms and are not legal advice. Company identity, launch jurisdictions, provider terms, regulatory perimeter, and consumer-law treatment must be approved before production launch.

Effective date
Not yet effective — pending company details and qualified counsel approval
Last updated
16 August 2026
Version
0.5-marketing-draft

1. Current website baseline

The website uses necessary technology for secure account access when Clerk is configured. Optional PostHog product analytics runs only after you select “Allow analytics” in the website preference prompt. Homa does not use advertising cookies or cross-site behavioral advertising.

2. What is a cookie?

A cookie is a small text record that a website asks a browser to retain. Similar technologies include local storage, session storage, pixels, software-development kits, and device identifiers. This policy uses “cookies” as a practical umbrella term unless a distinction matters.

3. Strictly necessary technology

Strictly necessary technology may maintain an authenticated Clerk session, protect forms, remember your analytics preference, balance traffic, prevent abuse, or preserve a setting you request. It is limited to the requested service and is not repurposed for advertising.

4. Analytics and performance

With your permission, PostHog records page paths, navigation and call-to-action interactions, referrer and campaign context, browser and device information, sign-up completion, sign-in sessions, and billing-funnel status. Signed-in analytics uses the stable Clerk user ID; Homa does not send your email, name, password, payment details, form contents, chart data, or desktop-session content to PostHog. Session replay, heatmaps, automatic text capture, and automatic exception capture are disabled in the website integration.

5. Marketing and advertising

Homa does not currently use advertising cookies or cross-site behavioral advertising. Introducing them would require an updated policy and any consent mechanism required in the launch jurisdictions.

6. Browser storage used by the desktop product

The future desktop companion may use local application storage for settings, secure session state, update metadata, and performance. Desktop storage is distinct from public-website cookies and must be explained in product notices and the desktop capture privacy disclosure.

7. Your choices

You may reject optional analytics without losing access to public website content. Revisit this page and use “Analytics preferences” to change your selection. You can also clear or block cookies through your browser. Blocking strictly necessary technology may prevent account or security features from functioning.

8. Provider and retention

PostHog processes analytics in the cloud region configured for Homa’s PostHog project. Analytics retention and deletion are controlled in that project and should be reviewed against the effective launch policy. The saved consent choice remains in your browser until you change it or clear site data.

9. Changes and contact

This policy will be updated when analytics purposes, providers, data fields, retention, or controls materially change. A verified privacy contact and preference-request channel will be published before wider production launch.