Your workspace data is not marketing inventory.

Trevra processes account identity, workspace settings, GTM People and Accounts, connected-provider records authorized by the user, inbound submissions, messages and conversations, campaigns, minimal opportunity state, prepared actions, approval history, and security or operational logs.

Data is used to operate go-to-market workflows, qualify demand, coordinate outreach and conversations, prepare and execute authorized GTM actions, maintain audit records, secure the service, and measure aggregate product adoption.

Connected providers remain independent third parties. Depending on deployment configuration, infrastructure and processing may involve cloud hosting, PostgreSQL, Nango, model providers explicitly enabled for GTM agents or skills, and connected email, CRM, social, calendar, or research providers.

Workspace records, evidence, integrations, and credentials are used to provide the product. Provider credentials belong in the integration provider or a secret manager rather than application tables or source control.

Trevra records limited first-party events such as page views and clicks on the main calls to action, attribution fields, a session-scoped visitor identifier, and the current path. The contract excludes message bodies, captured submission content, Person or Account records, provider credentials, and IP-address storage. Browsers sending Do Not Track or Global Privacy Control are not measured at all.

Trevra’s built-in traction measurement does not store IP addresses. It stores a salted hash of a session-scoped random identifier, the landing path, referral domain, campaign parameters, and product conversion events. Browser Do Not Track and Global Privacy Control signals disable client-side marketing events.

Commercial records are retained while a workspace is active and as needed for security, dispute, backup, or legal obligations. Workspace owners may request account export or deletion through the support contact below. Backup deletion can follow a delayed rotation schedule.

Self-hosted operators control their own infrastructure, retention, backups, access policy, and legal obligations. Trevra does not receive self-hosted workspace data unless the operator deliberately sends it to a Trevra-managed service.

Applicable privacy rights vary by location. Requests may be sent to [email protected]. Identity verification may be required before fulfilling a request.