Legal
Cookies & Analytics Notice
How Inali uses website analytics, experiments, consent, and related technologies.
Current Website Analytics
Inali uses first-party website analytics for landing-page performance, download intent, and A/B testing. Events are sent to `/api/track` and written to Cloudflare Workers Analytics Engine. Cloudflare may also provide website traffic and operations views.
The setup is intentionally narrow: it measures website behavior and App Store redirect intent without ad pixels, session replay, third-party behavioral SDKs, user-level profiles, names, emails, app user IDs, wallet data, or free-form text.
Analytics Events And Data
| Event/data | Purpose |
|---|---|
| page_view | Measure legal/landing route visits by locale. |
| section_view | Measure whether major landing sections were visible. |
| cta_click, qr_click, download_redirect | Measure App Store download intent. |
| engagement_ping | Measure visible-tab engagement milestones. |
| experiment_exposure, experiment_conversion | Measure active first-party website experiments. |
| route, landing_locale, source, section, experiment_id, variant, campaign, engagement_bucket | Operational funnel fields. Free-form text, names, emails, app user IDs, wallet data, and raw memos are not accepted by the analytics endpoint. |
Consent And Preferences
Nonessential website analytics and experiments are consent-gated where required. If you reject analytics consent, Inali should not send custom analytics events or assign active website experiment variants for that browser session.
You can reset analytics consent by clearing site data for inali.net. A richer preference center may be added later if Inali adds more analytics categories.
No Advertising Tracking
Inali does not use app advertising SDKs, cross-app tracking, retargeting pixels, session replay, or data broker services. If that changes, this notice and the Privacy Choices page will be updated before the change is released.