Data Handling and Retention

Tabstack processes data on your behalf: the pages it fetches, the structured output it extracts, and the inputs you send (tasks, queries, schemas, and any form data). This page documents what happens to that data once a request completes.

---

What is stored

For every API request, Tabstack stores request metadata: which endpoint was called, whether it succeeded, credits spent, timestamps, and the organization and key that made the call.

The payloads (the target URL, request parameters, response data, and extracted output) are not stored by default. They are retained for 90 days only when an organization opts into detailed data collection. Personal information is kept out of logs.

Per the privacy policy, IP logs are retained 60 days, referral data 30 days, and opt-in browsing history 90 days.

Caching

Tabstack caches fetched page content by URL to improve performance and reduce redundant fetches, with a short time-to-live. You can bypass the cache for any request by passing nocache: true. See Production Reliability for the behavior.

The content cache is keyed by URL, effort, and region, not by account. Cached page content can be served across accounts. Pass nocache: true when you need a fetch that bypasses this shared cache.

Inputs and form data

When you use /automate, you can pass a data object and, in interactive mode, supply form field values mid-task. See Automate Tasks and Interactive Mode.

Inputs are not persisted by default. With detailed data collection enabled, the automate data object, the research query, the extraction schema, and the full task stream are stored and retained 90 days. Interactive form values are always ephemeral. They expire within minutes and are never stored. Request data that appears in error reports is sanitized.

Privacy policy

The canonical privacy policy is at https://tabstack.ai/legal/privacy.