Relay SDK
Ask your users whether they want to contribute structured activity from your app, and send nothing unless they say yes.
Relay turns opted-in activity in your app into licensable training data for AI teams, and pays you when it is licensed. You add the web SDK, choose which in-app actions can be shared, and Relay handles the consent screen, consent records, batching, retries, withdrawal and deletion.
How it works
- Your user is asked. The SDK shows a consent screen that names your app, lists the exact fields that would be shared and explains the purpose. Accept and decline are equally prominent.
- Your backend vouches for them. After an opt-in, your server mints a short-lived attestation for the signed-in user. Relay stores only a pseudonym scoped to your app, so the same person is never linked across apps.
- You send approved events. Events must match a schema you selected. Unknown fields are stripped and quarantined, never stored as submitted.
- Users stay in control. Withdrawal stops collection immediately and clears anything queued. Deletion also removes what Relay holds.
What Relay never collects
No DOM content, keystrokes, screenshots, cookies, passwords, device fingerprints or free-form text. The schemas have no place for them, and the SDK makes no requests, buffers nothing and creates no identifiers before a user opts in.
Platforms
The web SDK (@relay/sdk) is available to early partners today. It is written in TypeScript and has no runtime dependencies. Native iOS and Android SDKs are planned; see Coming soon.
Start here
- Quickstart: keys, backend route and client code.
- Consent: the built-in dialog, custom UI and consent versions.
- Event schemas: every event and field you can send.