> For the complete documentation index, see [llms.txt](https://docs.taloflow.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taloflow.ai/security/platform-controls/logs-audit-logs-and-backups.md).

# Logs, Audit Logs, and Backups

Retention and contents of auth and audit logs, plus backup schedules.

### Scope

This page covers **platform logs**, **audit logs**, and **backup schedules**. For retention of **evaluation data and exports**, see [Evaluation Data Retention](/security/platform-controls/evaluation-data-retention.md).

#### Authentication Logs

* **Auth0 sign-on and failure logs**: Retained for 6 days
* **Extended analytics**: Authentication events are forwarded to Segment.io with 180-day retention
* **Monitoring**: Threshold-based monitoring runs via scheduled cron jobs
* **Analysis**: Currently, no active real-time analysis is performed on authentication logs

#### Audit Logging

Every API request generates an audit log entry containing:

* **JTI** (JWT Token ID)
* **User ID**
* **Token thumbprint**
* **Token expiration time**
* **Request timestamp**
* **Resolver-level access logs** for data access operations

This zero-trust transaction recording ensures complete traceability of all platform actions.

#### Data Backup Schedule

**PostgreSQL Database**:

* Hourly backups with minimum 3-day retention
* Encrypted and compressed backups stored behind firewall
* Nightly off-site backups for disaster recovery
* State tracking with built-in attribution and archiving

**Redis Database**:

* Replicated database with persistent storage
* Designed for continuous availability
* Persistent storage on backed-up volumes
* Stores current state (not historical data)

**Object Storage**:

* Used for evaluation configurations, generated exports, cached calculations, and static assets
* Buckets are private and not publicly accessible
* Access is key-based and scoped per service (least privilege)
* Encryption keys are held by application services, not stored in object storage
* Sensitive buckets use additional encryption controls
* Most objects are regenerable from the database (backups focus on databases)

**Block Storage**:

* Linode-managed with replication
* Periodic snapshots for application data
* Database data handled through PostgreSQL/Redis mechanisms above


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taloflow.ai/security/platform-controls/logs-audit-logs-and-backups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.