1. How to Read This Notice
Traseq has more than one user-facing surface:- Public marketing experiences such as the landing site, pricing pages, feature pages, and documentation entry points
- Authenticated product experiences such as the Traseq App, workspace pages, billing screens, onboarding flows, and account settings
2. How Consent Works
- Strictly necessary technologies stay enabled because they are required for requested functionality, authentication, security, fraud prevention, or critical product state
- Optional analytics and session replay are disabled by default on surfaces that use them until the user explicitly allows them
- Users can revisit their choice from available controls, including in-product data settings where supported
3. Shared Baseline Technologies
These technologies may be used across Traseq surfaces where relevant:
These technologies are used to provide the requested service and are not treated as optional analytics.
4. Public Marketing Site and Documentation
As of 2026-04-07, Traseq separates its public surfaces into two tracking baselines:4.1 Public marketing site (traseq.com)
The public marketing site may use the following technologies:
When optional tracking is declined on the marketing site, Traseq intends to keep these technologies off and continue serving only essential functionality.
4.2 Documentation site (docs.traseq.com)
The documentation site may use the following technologies:
As of 2026-04-07, the documentation runtime supports optional Microsoft Clarity on selected article pages, but it remains inactive unless the docs deployment is configured with a Clarity project ID. PostHog session replay and other optional analytics providers are not enabled on the documentation site.
5. Authenticated Traseq App
The authenticated Traseq App may use the following technologies:
Optional tracking in the authenticated app is controlled through a single user-facing preference today. When that preference is declined, optional analytics and session replay are intended to remain off.
6. Session Replay Safeguards
Where session replay is enabled, Traseq intends to use it narrowly for service improvement, support, debugging, and UX investigation. The current baseline safeguards are:- On the documentation site, replay is intended to be limited to selected article-style pages rather than API reference, legal, or changelog surfaces
- Form inputs are configured to be suppressed in replay capture
- Designated sensitive interface regions can be masked at the application level
- Replay is not intended to capture plaintext payment card data, plaintext API secrets, or similar highly sensitive content
- Replay is not used for third-party behavioral advertising
7. Managing Your Preferences
You can manage optional tracking in the authenticated product through the available account data controls. You may also:- Use browser settings to clear cookies or site storage
- Use browser privacy controls or extensions that limit third-party scripts
- Contact support@traseq.com if you believe tracking behavior is inconsistent with this notice