Where your event data lives
Your event rows are written directly to your ClickHouse database. There is no Infralytiqs-hosted event store to opt out of: the platform requires a ClickHouse host you supply, and it provisions its schema there.
What Infralytiqs retains is the connection details needed to write and query — host, database name, clientKey and clientSecret — together with the tenant and report definitions you create in the console. It does not keep a second copy of your events. Revoke the credentials or point them at a different host and the platform stops reading your data; the rows already in your database remain yours and untouched.
What the browser SDK collects
By default the tracking snippet records the page URL and title, the referrer, the viewport and screen size, the user agent, a coarse locale and timezone, and an anonymous visitor identifier stored in first-party storage. It does not read cookies belonging to other domains, fingerprint the canvas, or collect form input.
Any user identifier or custom property beyond that is something you choose to send. That is deliberate: you decide what personal data enters the pipeline, which makes your own data-protection assessment tractable.
Account data
Signing in with SSO shares your email address, display name and identity-provider subject identifier with Infralytiqs. We use these to authenticate you, associate you with your projects, and contact you about your account. We do not sell them and we do not use them for advertising.
Retention and deletion
Retention is entirely yours, because the database is yours. The schema ships with a 24-month TTL on the events table; change it, remove it or shorten it and ClickHouse enforces whatever you set. Infralytiqs neither extends nor archives that data.
To delete your account and the tenant metadata associated with it, email hello@infralytiqs.com. Deleting the account does not touch the event rows in your own ClickHouse — those you drop yourself.
Cookies on this website
This marketing site stores your theme preference in browser local storage under the key header-theme (dark, light, or auto). That is a functional preference, not tracking, and it never leaves your browser.
This page describes how the product handles data. It is not a substitute for legal advice — if you operate under GDPR, CCPA or similar, review your own configuration and what you choose to send.