MODLANE COOKIE POLICY
Closed Beta
Version 1.0 | Effective 23 July 2026
At a glance
MODLANE uses strictly necessary browser storage for authentication, consent preferences and user-requested local chat functionality. Optional PostHog analytics is off by default and is activated only after the user gives consent. Rejecting analytics does not prevent use of the core service. MODLANE does not use advertising cookies, cross-site behavioural tracking or Session Replay.
Controller: Aleksandr Boiko, current operator of MODLANE in Ireland
Contact: office@modlane.app
Website: modlane.app
1. Scope of this Policy
This Cookie Policy explains how MODLANE uses cookies, localStorage and similar browser technologies on modlane.app and in the MODLANE closed-beta AI workspace. It should be read together with the MODLANE Privacy Policy.
MODLANE is an early-stage project operated by Aleksandr Boiko in Ireland and is not yet a registered company or separate legal entity.
2. What cookies and similar technologies are
Cookies are small text files stored by a browser. Similar technologies include localStorage, sessionStorage and other browser-storage mechanisms that can save authentication information, preferences, identifiers or user-requested content on a device.
Some storage is strictly necessary to provide a function requested by the user, such as maintaining a secure sign-in session. Optional analytics storage is used only after prior consent.
3. Technologies used by MODLANE
Project-specific names may include a Supabase project reference, a PostHog project key or numbered cookie chunks. The table therefore uses observable name patterns rather than exposing deployment-specific identifiers.
| Name / pattern | Category | Purpose | Data stored or linked | Retention | Consent |
|---|---|---|---|---|---|
sb-<project-ref>-auth-token and possible numbered chunks | Strictly necessary | Maintains the Supabase sign-in session and supports token refresh. | Access token, refresh token and technical session state. | Controlled by the authentication session; removed on sign-out or when the session ends. | No |
modlane_cookie_consent | Strictly necessary preference | Stores the analytics choice, policy version and date so the banner does not repeatedly appear. | Accepted / rejected choice, timestamp and policy version. | Up to 6 months, unless changed or deleted earlier. | No |
ph_<project_key>_posthog and related PostHog browser storage | Optional analytics | Measures product use, sessions, navigation and permitted interface interactions after consent. | Distinct and session identifiers, analytics state and event properties. | Cookie up to 365 days; analytics events up to 12 months. | Yes |
| Application-specific MODLANE localStorage entries | User-requested functionality | Keeps chats and related content available in the current browser. | Chat titles, prompts, AI responses, conversation context and converted document text. | Until the user deletes the content, deletes the account on that device or clears site data. | No separate cookie consent |
4. Strictly necessary authentication and preference storage
MODLANE uses Supabase Auth for email-and-password authentication. Authentication tokens are stored in cookies so the browser and server can maintain and refresh the signed-in session. These cookies are necessary for registration, sign-in, account security and access to protected parts of the workspace.
MODLANE also stores the user's cookie preference. This storage is necessary to remember whether optional analytics was accepted or rejected. It is not used for advertising or analytics.
Blocking strictly necessary cookies through browser settings may prevent sign-in, end the session or stop protected features from working correctly.
5. Optional PostHog analytics
MODLANE uses PostHog EU Cloud for optional product analytics. PostHog analytics is disabled by default. Before consent, MODLANE does not write PostHog analytics cookies or local analytics identifiers and does not send optional analytics events.
PostHog is activated only after the user selects Accept Analytics or enables Analytics in Cookie Settings. When analytics is enabled, MODLANE may collect:
- page views, page exits, screen paths and URLs within MODLANE;
- browser, device, language, operating-system, web-vitals and performance information;
- session identifiers and timestamps;
- permitted clicks and interface interactions used to understand feature use;
- an account identifier or email address where MODLANE identifies the PostHog person profile.
Session Replay is disabled. MODLANE does not use PostHog cookieless tracking after rejection. Rejecting or withdrawing consent stops future optional analytics in that browser.
The PostHog project setting to discard client IP data is enabled. An IP address may still be processed transiently for technical functions such as GeoIP enrichment or bot detection before it is discarded and is not stored with the analytics event.
6. Local browser storage for chats and files
MODLANE currently stores chat history in the browser's localStorage rather than in a server-side chat database. This may include prompts, AI responses, chat titles, necessary conversation context and markdown extracted from uploaded documents.
The original binary file is not stored in localStorage merely because it was converted, but converted text may remain in the chat. Browser-stored content remains on that device until the user deletes it, deletes the account from that device or clears the site's browser data.
Deleting an account clears MODLANE localStorage on the device used for deletion. It does not remotely clear storage on another browser or device.
7. Consent choices
On the first visit, or when no valid preference is available, MODLANE displays a cookie banner with:
- Accept Analytics;
- Reject Analytics;
- Manage Preferences.
Analytics remains off unless the user gives a clear affirmative choice. Reject Analytics is available as directly as Accept Analytics, and the core service remains available after rejection.
The preference is stored separately in each browser or device for up to 6 months. MODLANE asks again after that period, after the preference is deleted or when the analytics purposes materially change.
8. Changing or withdrawing consent
Users can reopen Cookie Settings from the website footer and from Settings > Privacy & Data. Analytics can be enabled or disabled at any time.
When consent is withdrawn, MODLANE stops future PostHog analytics collection in that browser and removes the PostHog analytics cookie and related local analytics storage. The withdrawal does not affect processing that lawfully occurred before withdrawal.
Previously collected analytics may remain for the applicable retention period, currently up to 12 months, unless the user makes a valid erasure request and deletion is technically and legally available.
9. Existing users and legacy analytics identifiers
When the consent controls are deployed, MODLANE removes legacy PostHog browser identifiers for users who do not have a valid analytics consent record. Optional analytics remains disabled until a new affirmative choice is made.
10. Browser controls
Users may also block or delete cookies and localStorage through browser settings. Doing so may sign the user out, remove locally stored chats or reset the cookie preference. Browser controls do not replace MODLANE's own Accept, Reject and Cookie Settings controls.
11. Providers and storage locations
| Provider / storage | Role | Location / environment | Retention summary |
|---|---|---|---|
| Supabase | Authentication cookies and session management. | Supabase infrastructure; further details are in the Privacy Policy. | Authentication session and provider security-record lifecycle. |
| PostHog | Optional product analytics after consent. | EU Cloud. | Browser cookie up to 365 days; product-analytics events up to 12 months. |
| MODLANE local browser storage | Consent preference and user-requested chat functionality. | The user's current browser or device. | Until expiry, deletion, account deletion on that device or site-data clearing. |
12. Legal basis
Strictly necessary browser storage is used to provide functions expressly requested by the user, including authentication, session maintenance, remembering cookie preferences and keeping user-requested chat content on the device.
Optional PostHog analytics is used only with consent. For personal data processed through optional analytics, MODLANE relies on consent under Article 6(1)(a) GDPR. Consent can be withdrawn at any time.
13. Changes to this Policy
MODLANE may update this Cookie Policy when browser technologies, purposes, providers or legal requirements change. Material changes to optional analytics are reflected in the consent interface, and renewed consent is requested where required.
The current version and effective date are displayed at the top of the published Policy.
14. Contact
Questions about cookies, browser storage or analytics preferences can be sent to office@modlane.app.
Controller: Aleksandr Boiko, current operator of MODLANE in Ireland.