Privacy Policy

1. Scope and contact

This policy covers personal data processed through the Truvyx website, hosted application, and API. Questions and data requests can be sent to legal@truvyx.org.

2. Data the product processes

• Account data: email address, display name, optional profile image, organization membership and role, and onboarding selections. Credentials accounts store a bcrypt password hash; OAuth providers supply their account identifier and available profile fields.
• Customer content: scenarios, constraints, verifier definitions, configurations, evaluation inputs and outputs, traces, reports, audit records, monitoring data, and other content submitted to product features.
• Product activity: authenticated page-view and selected action events stored by the application, including a user, organization when available, timestamp, event type, and bounded metadata. The application does not claim a complete record of every request or action.
• API and run data: API-key metadata such as its prefix and last-used time, plus evaluation, quota, status, and result records needed to operate the service. Raw API keys are not stored.
• Service metadata: hosting, database, cache, email, authentication, and inference providers may process request, device, network, or delivery metadata under the active deployment and their policies.
• Communications: messages and contact details supplied when asking for support, security help, or legal assistance.

3. How data is used

• Provide accounts, organizations, evaluations, diagnostics, monitoring, exports, and requested support.
• Authenticate requests, enforce permissions and quotas, limit abuse, investigate failures, and protect the service.
• Send account verification, password recovery, invitation, evaluation, and service messages when the related feature is configured.
• Measure product use and improve reliability using application activity and optional analytics.
• Meet applicable legal obligations and respond to valid legal process.

Truvyx does not sell personal data. Customer scenarios, traces, agent outputs, and constraints are not used by Truvyx to train a general-purpose model.

4. Optional analytics and advertising

Google Analytics and Meta Pixel are optional. Their scripts remain unloaded until you select Accept in the analytics choices. The selection is stored in your browser and can be changed through the persistent Privacy choices control. A browser Global Privacy Control signal forces the declined state. Clearing site storage resets a saved selection.

When accepted and configured, those providers receive browser and page-event data according to their services and policies. Truvyx does not represent this optional measurement as a complete log of product usage.

5. Service providers and customer connections

The hosted service uses configured providers for application hosting, PostgreSQL, Redis-compatible rate limiting and queues, authentication, email delivery, and optional analytics. AI-assisted features send the content needed for the requested operation to the configured inference provider. OAuth sign-in sends and receives the data required by the selected identity provider.

Customers can also configure destinations such as model endpoints, Slack, SMTP, PagerDuty, callbacks, and on-premise evaluation origins. Data sent to a customer-selected destination is governed by that customer's configuration and relationship with the destination.

6. Location and retention

Processing location and retention depend on the active deployment, provider plan, data type, customer configuration, support needs, and applicable law. Truvyx does not promise a universal region, 90-day access-log period, seven-year payment-record period, or fixed backup window on this page. Contact us for deployment-specific information.

The organization deletion workflow removes organization-owned records from the application database. Hosting, database, communications, and security providers may retain backups or logs for periods governed by their configuration and policies, so deletion from the live application does not imply immediate erasure from every provider backup.

7. Security and disclosure choices

The product uses server-side organization checks, role permissions, rate limits, hashed API keys, encryption for stored integration credentials and raw traces, and signed compliance records. Trace visibility controls whether eligible material stays private, is available within the organization, or may contribute to Fault Atlas. Organization exports omit declared secret fields. See the Security page for precise controls and assurance boundaries.

8. Your choices and requests

Depending on where you live, you may have rights to access, correct, export, object to or restrict processing of, or delete personal data. The application provides profile changes, API-key revocation, a versioned organization export, analytics choices, and organization deletion for authorized owners. Email legal@truvyx.org for a request that cannot be completed in the product. We may need to verify identity and authority over the organization before acting.

9. Changes

We may update this policy as the product, providers, or legal requirements change. The date above identifies the current version. Material changes will be communicated through the product or an account contact when appropriate.