Event schema linter — audit your analytics JSON
Paste an analytics event payload (Mixpanel, Firebase, Segment, custom — any shape). The linter walks every field and tells you: which would be rejected by a privacy-first 5-field schema, which contribute to Apple's App Store Privacy Label, which to Google's Play Data Safety, and which count as personal data under GDPR Article 4(1). Helps developers avoid collecting personal data in the first place.
Accepts a single JSON object, an array of events, or JSONL (one event per line). Runs entirely in your browser — your payload never leaves the page.
How it works
Paste your event JSON
Drop in a Mixpanel, Firebase, Segment, or custom payload — single object, array, or JSONL. Or click a sample below to see it work without typing.
See per-field verdicts
Every field gets a classification: would Respectlytics's API accept or reject it, what Apple Privacy Label and Google Play Data Safety categories it triggers, and how GDPR Article 4(1) treats it.
See the API response
The tool simulates the exact HTTP 400 or HTTP 200 body your code would receive — so you know what to expect before changing a line.
Per-field verdicts use these labels:
Try a sample payload
Click any sample — payload loads + lint runs instantly. Edit freely or paste your own.
Live linting. Nothing is sent to a server.
Lint summary
Events
0
Fields total
0
Rejected
0
Accepted
0
Apple Privacy Label categories triggered
Google Play Data Safety categories triggered
Download
Nothing to lint yet
Click any sample above (we recommend starting with ✅ Clean Respectlytics payload to see what a passing case looks like), or paste your own JSON on the left.
↩What Respectlytics's API would return
Exact response body your code would receive if it POSTed this payload to Respectlytics. The API enforces the 5-field schema at the boundary — extra fields are rejected with a 400, never silently stored.
⊕Per-field analysis
Want an analytics API that enforces this for you?
Helps developers avoid collecting personal data in the first place. Five-field event schema, RAM-only event queue, no IDFA, no AAID, no persistent user IDs.