Privacy and retention

Data retention

Retention is governed by your plan. Each plan may define a retention limit (e.g. number of days raw data is kept).
Raw event data is retained according to your plan’s retention limit. Exact duration depends on your subscription and any negotiated limits; check the Billing / Plan page or contact support.
Aggregated metrics (e.g. organization activity summaries) may be stored longer for reporting purposes, depending on system design.
Retention policies are enforced automatically; expired raw data is permanently deleted.

SaaS Tracker is designed to operate without storing direct personal identifiers. We recommend hashing user identifiers (e.g. SHA-256) before sending them as user_hash so we do not store personally identifiable information (PII) in analytics.
Do not send passwords or tokens in event payloads.

Data isolation is enforced at the database and API layer. A company’s users cannot access other companies’ data.
Data is isolated per company. Only users who are members of that company can access its apps and analytics.
Ingest API credentials are per application; they do not allow access to other companies’ or apps’ data.

SaaS Tracker is operated in the EU. Customer data is stored and processed within EU-based infrastructure.

SSO/SAML, SCIM, and audit logging are not currently part of the product. Access control is managed through the built-in role and membership model (company and app memberships, roles).