Compliance & Privacy
The platform is designed to be a PII-free analytics layer. It intentionally does not accept or store personally identifiable information.
Our approach to personal data
The platform is designed to be a PII-free analytics layer. It intentionally does not accept or store personally identifiable information.
What the platform stores
| Stored | Not stored |
|---|---|
user_id (your identifier, opaque to us), after you call identify | |
Anonymous device id (anonymous_id) generated by the SDK | Name |
| Session identifier (sessions are tracked per SDK session) | Phone number |
| Event names, event properties (flat key-value) and timestamps | IP address (see below) |
| Country and region (derived from the IP address) | Device fingerprint |
Attribution: UTM parameters, ad click id (for example gclid), referrer domain, landing page | |
| Platform, screen, app version | |
| Consent flag (whether analytics consent was given) |
How the IP address is used
The server uses the request IP address transiently to derive the country and region of the event. The IP address is not stored in analytics storage. It is held only in the short-lived SDK session so it can be forwarded to destinations you enable (for example Meta Conversions API).
Consent mode
The SDKs support a consent mode: with requireConsent: true nothing is tracked until you call setConsent({ analytics: true }). Withdrawing consent clears the queue and the stored anonymous id. See the Browser SDK and the other SDK pages for details.
Your responsibility
⚠️ Do not pass personally identifiable information in event properties. No email, name, phone, address, or any other information that could identify a real person. Use only an anonymous
user_idfrom your own system.
This warning appears at three points:
- During project creation (onboarding)
- In the SDK documentation (including Quickstart and the REST API reference)
- In the UI when the platform detects suspicious property names (e.g., a field named
email,phone, orname)
Roles under GDPR
| Party | Role | Responsibility |
|---|---|---|
| TrichiData | Data Processor | Processes data according to client instructions |
| You (the developer / company) | Data Controller | Legally responsible to your end users; must ensure no PII enters the platform |
Data Processing Agreement (DPA)
A standard DPA is available for signing at trichidata.com/legal/dpa. The DPA is required if you process data of EU residents under GDPR.
Right to erasure
Self-service deletion of a user's data (GDPR Article 17) is not available yet.
Until then, send erasure requests to support at [email protected] with your project and the user_id. We delete that user's events from TrichiData storage, including their earlier anonymous activity linked through identify. Requests are completed without undue delay and in any case within one month, as required by GDPR Article 12(3).
Data that was already forwarded to destinations (for example GA4 or Meta) is not covered. Delete it in those tools directly.
Privacy Policy
The platform's full Privacy Policy is available at trichidata.com/privacy.