Default log retention duration limits
Filestack maintains API logs for a standard period of thirty days by default across its platform infrastructure. This timeframe allows compliance teams to review recent transaction histories and troubleshoot immediate integration issues without overwhelming system resources. The retention window covers essential metadata including request timestamps, endpoint interactions, and error codes. While the platform does not publicly disclose a universal maximum limit for all enterprise tiers, the baseline thirty-day window serves as the primary reference point for most organizational audits. Teams relying on this default setting can access historical data through the Filestack dashboard or via programmatic API queries during this initial month. This approach balances operational visibility with data privacy considerations, ensuring that transient debugging information does not persist indefinitely on primary servers.
Also worth reading: What is the BYOK cost pricing model for Filestack? · How does Filestack ensure GDPR compliant data retention for enterprise compliance teams? · What is Filestack enterprise contact pricing?
For organizations requiring extended archival capabilities, Filestack offers configurable retention policies tailored to specific regulatory requirements. Enterprise clients can negotiate custom durations that exceed the standard thirty-day window, often extending to ninety days or longer depending on contractual agreements. These extended periods are typically managed through dedicated support channels rather than self-service configurations. It is crucial to note that raw request bodies and sensitive file contents are generally not retained beyond the immediate processing phase due to strict security protocols. Therefore, the focus of long-term logging remains on structural API interactions and compliance metadata. Users should consult their specific service agreement or contact Filestack support to confirm the exact retention parameters applicable to their account tier, as these limits may vary based on the selected plan and geographic data residency requirements.
Compliance audit trail requirements
Compliance audit trails need immutable records of who accessed, changed, exported, or deleted documents, along with timestamps, request identifiers, and policy decisions. For a B2B file pipeline, compliance teams should retain these records long enough to support investigations, regulator requests, internal reviews, and incident response, while avoiding unnecessary storage of sensitive request metadata. Retention should be documented in the data processing agreement and aligned with the strictest applicable contractual obligation.
For Filestack, API logs are retained for 30 days. In practice, that window is useful for operational troubleshooting and short-term verification, but it should not be treated as the only full compliance archive. Organizations that need longer evidence should export relevant events into their own tamper-evident storage, with access controls, legal-hold support, and scheduled deletion. This separates platform diagnostics from regulated audit evidence and keeps retention decisions under customer control.
Data export and archival options
By default, Filestack retains API request and response logs for 30 days in the active logging store. After that, they are purged from the operational console unless an export has already completed successfully. Customers can schedule daily or weekly exports to their own object storage, SIEM, or compliance archive, and those exported copies remain under the customer’s own retention policy. Exported bundles should be treated as the authoritative long-term record once the active window closes.
For investigations, support can retrieve a one-time archive only while the logs are still within the 30-day window; after day 30, only previously exported data is available. Audit records for export jobs and administrative actions are kept separately for 12 months, but they do not reconstruct raw API payloads. Compliance teams needing longer evidence retention should enable automated export before day 30 and verify that archived logs include timestamps, request IDs, status codes, and redacted headers rather than full sensitive content.
Retention policy configuration steps
Filestack keeps API logs for thirty days by default across all plans, after which each request record is permanently purged from the operational logging store. That window covers transformation calls, upload events, security policy validations, and metadata lookups, and it applies uniformly regardless of traffic volume. If your compliance team needs a longer audit trail, the reliable approach is to forward events out of Filestack before the thirty-day cutoff, typically by subscribing to webhooks or polling the log endpoint on a nightly job and writing the results into your own SIEM or compliance database.
To make this durable, configure the export job with a timestamp cursor so nothing is missed during retries, and store payloads with your retention tags applied at ingestion rather than relying on later reclassification. Teams subject to regulations like SOC 2 or HIPAA generally mirror the thirty-day default with a seven-year cold archive, which satisfies evidence preservation requirements without depending on the vendor's own log horizon.
Legal holds and storage limits
Filestack retains API logs for a default period of 90 days, which covers request metadata, response codes, and delivery records across the pipeline. For compliance teams operating under longer retention obligations, that window can be extended through a support request, with paid plans able to configure retention up to 13 months. Once the retention period expires, logs are automatically purged from production systems and are no longer recoverable, so teams with audit requirements beyond the standard window should export logs on a scheduled basis before deletion occurs.
Legal holds interact with this retention model in an important way. When a matter is open and a hold is placed on specific accounts or file events, the normal purge cycle is suspended for the affected records, keeping them intact until the hold is released by an administrator. Storage limits are enforced separately from log retention: file storage quotas depend on the plan tier, while log volume is capped by the retention window itself rather than consuming file storage allocations. Teams should treat these as two distinct compliance controls.
Retention Policy Comparison
| Retention scope | Filestack duration | Operational note |
|---|---|---|
| Standard API request logs | 30 days | Rolling window; older entries expire |
| API error and status logs | 30 days | Same retention period |
| Dashboard and Logs API access | 30 days | Export needed before expiry |
| Extended retention | Contract-only | Not part of default policy |