Designed to use less data.

Recap payloads

Konveri processes customer-defined user IDs and submitted fitness activity statistics to generate, host, and measure recap stories. A recap payload does not require an end user's name or email address. Customer-defined IDs and activity data may still be personal data when a customer can link them to a person, so customers should send only the data needed to create a recap.

Do not submit direct identifiers, diagnosis details, medical records, or other unnecessary health information. Customers are responsible for deciding what data they collect and send, and for communicating with their end users.

Account and billing information

Account, workspace, support, and billing information are separate from recap payloads. We use account information to provide access and administer a workspace. Billing information is handled through the applicable payment or platform flow; it is not part of a recap payload.

Recap access windows

Sandbox recap links are available for 30 days. API-generated hosted recap links are available for 90 days. These access windows describe how long a hosted recap link is intended to resolve; they are not a promise of deletion, archival, or legal retention treatment.

Konveri uses limited first-party funnel events to understand product activation. These events record a name, timestamp, fixed source label, and allowed campaign parameters when supplied. They do not include recap statistics, end-user IDs, API keys, names, email addresses, IP addresses, third-party analytics, persistent tracking cookies, or fingerprinting.

Questions and requests

For Konveri account or workspace privacy questions, submit a request through support or email support@konveri.com. Customers may use the same route to request a discussion of a prospective Data Processing Addendum. Konveri does not claim a signed DPA, GDPR certification, an automated deletion workflow, or an EU adequacy position on this page.