Cookie and Local Storage Policy

Summary

The public liralang.com site is static and does not need first-party cookies to work. The app app.liralang.com uses essential authentication cookies and local storage for sessions, security, preferences, and drafts. Product analytics (Aptabase) is anonymous and cookieless.

Essential cookies

We use session/authentication cookies to sign in, keep accounts open, protect routes, and remember security states. If you open an invitation or referral link, lira_ref may keep only its code to apply the requested benefit even when you reject measurement. These functional cookies are not used for behavioural advertising.

Local and session storage

• Measurement choice: ll_marketing_measurement_consent_v1 remembers for up to 180 days whether you allowed or rejected optional attribution, using local storage and a first-party preference cookie shared across our subdomains; it is not used for measurement.
• Only when allowed: ll_lv identifies the visit in sessionStorage until the tab closes; UTM labels may pass to the app in a first-party HTTP-only cookie (lira_ref) for up to 30 days to attribute signup and conversion.
• Analytics opt-out: ll_analytics_opt_out, used to remember that you turned analytics off and do not want to send events.
• Transient data: drafts, local preferences, or temporary UI state where a feature needs it.

Analytics

Product metrics (Aptabase): we measure usage with Aptabase, an anonymous, cookieless analytics tool, across all our sites (app, landing, and help). It sets no cookies or persistent ids, is not linked to your account, and honors Do Not Track and Global Privacy Control. You can turn it off in Settings > Privacy (which stores ll_analytics_opt_out).

Funnel analytics (first-party): liralang.com sends views and CTA clicks to api.liralang.com/v1/events. Before measurement is allowed they carry no visit identifier; after permission they may use ll_lv to join the funnel. We honor Do Not Track and Global Privacy Control and store hashed IP, not raw.

Opaque advertising click parameters are removed from the app URL and are not stored on the account.

Third parties

We do not use third-party advertising cookies. Google may be involved if you choose Google sign-in. Paddle may use its own cookies or technologies when you leave for checkout or the payment portal.

We use Aptabase for anonymous product analytics: it processes aggregated usage data in the EU, sets no cookies, uses no persistent storage, and does not store your raw IP.

We use Sentry solely for error logging (crash reporting): it sets no cookies, does not record your session, uses no browser storage, and does not store your raw IP.