Privacy & data
Tally stores bounded AI discovery metadata, not prompt or response content. That metadata can still identify people, devices, and workloads, so protect database access and backups.
What is retained#
Depending on the source, retained fields can include provider/model identities, event time, evidence kind, source user or email, hostnames, IP addresses, destination host and port, workload names, recognized client hints, and connector lineage.
Raw payloads, prompts, responses, documents, arbitrary bodies, headers, cookies, credentials from source logs, and unrelated non-AI events are excluded from durable observations. Tally does not infer a user from an IP address or a destination from a provider name.
Connector and email credentials are separately encrypted at rest. The encryption key remains in the protected installation configuration.
Storage and retention#
| Store | Responsibility |
|---|---|
| PostgreSQL | Accounts, encrypted credentials, connector scheduling/cursors, catalog decisions, findings and attribution, ingestion receipts, scanner jobs, and administrative audit. |
| ClickHouse | Normalized AI observations and durable inventory/coverage aggregates. |
AI logs expire after 90 days by default. Inventory survives log expiration until explicitly removed. Configure retention through the runtime settings documented in .env.example.
Both databases use ordered migrations. Never clear migration history or edit checksums to force an old database into a new schema. Fresh installations use the current baseline.
Preview and delete operational data#
- Open Settings → Data deletion.
- Choose the categories and an older-than cutoff where supported.
- Preview the affected counts. Changing the target clears the previous preview.
- Select Delete…, review the refreshed counts, and enter
delete.
Delete All… selects all operational categories and requires delete all. Connector configuration deletion includes its history and receipts. Configuration and registry resets are not date-filtered; timestamped records use the supported cutoff.
Operational deletion preserves accounts, installation identity, and the built-in catalog. New ingestion can change counts after preview. Deleting managed databases with the uninstaller is different: it removes the database data, including accounts.
Security reporting#
Keep credentials, private source exports, and customer telemetry out of public issues. Follow the repository's security policy for vulnerability reports. Use sanitized fixtures when reporting connector behavior.