Privacy policy

What enters. What stays. What leaves.

How Tracify handles the information that passes through it, in the order it happens.

Updated 16 May 20266 sections

The short version

Collection

Only what runs the service.

Account details and the telemetry your SDK sends.

Protection

Encrypted. Access limited.

Telemetry is encrypted in transit and at rest.

Control

Analytics is your call.

Reject or change optional analytics at any time.

Follow the data

Three stops, one policy.

  1. 01

    Your app

    The SDK sends spans: tool calls, model calls and logs. Obvious secrets are removed before they leave.

  2. 02

    Tracify EU

    Account data, traces and cache are stored in Ireland, encrypted in transit and at rest.

  3. 03

    Event queue

    Inngest Cloud processes queued span events in the United States. Span input and output are redacted first.

In plain words

We collect your account details and the traces your SDK sends, use them only to run and improve Tracify, encrypt them, and let you control optional analytics at any time.

01

Overview

This policy explains how Tracify collects, uses, and safeguards information when you use the agent observability platform.

02

Collection

We collect information you provide directly and technical data generated through use of the platform.

  • Account information such as name, email, and organization.
  • Telemetry sent through the SDK, including spans, tool calls, and model logs.
  • Usage data such as browser type and platform interaction.
03

Use

Collected data is used to provide, maintain, protect, and improve the service. Product analytics is enabled by default and can be rejected or changed at any time through the privacy preferences control. Marketing cookies and marketing scripts are not currently used.

  • Process and visualize agent telemetry.
  • Provide cost and performance analytics.
  • Send requested system alerts and notifications.
04

Protection

Telemetry is encrypted in transit and at rest. Access is limited to authorized people and systems needed to provide the service.

05

Data residency

For the EU region, account data, traces, and cache are stored in Ireland. Inngest Cloud currently processes queued span events in the United States, so the EU region is not end-to-end EU-resident.

  • Span input and output are redacted before being sent to the US event-processing provider.
  • Stripe processes billing and payment information as a separate payment provider; Tracify does not store full card numbers.
  • Redis and the EU application data services are operated in the documented EU region.
06

Control

You can accept, reject, or change optional analytics preferences at any time through the privacy preferences control or the cookie policy. Questions and privacy requests can be sent directly to privacy@tracify.tech.

Privacy questions

Ask us anything about your data.

privacy@tracify.tech →