Sorzio
PricingShowcaseFlowsCompare
Sign inGet started free
Get started

Product

  • Pricing
  • Showcase
  • Flows
  • Models
  • Tools
  • Compare
  • Install

Connect

  • MCP Developer Hub
  • Claude
  • ChatGPT
  • Cursor

Resources

  • Use cases
  • Blog
  • Glossary
  • Help Center
  • Contact Support

Company

  • About
  • Security
  • Sorzio vs Clay
  • Sorzio vs Apollo

Legal

  • Privacy Policy
  • Terms of Service
  • Cookie list
  • Subprocessors

Empra Consultancy LTD
hello@sorzio.com

Sorzio (formerly ReplyLabs) is built and operated by Empra Consultancy LTD (https://www.sorzio.com) and is an independent product and company not affiliated with Reply.io (Reply, Inc.).

Sorzio|PrivacyTermsCookiesSubprocessors

© 2026 Empra Consultancy LTD. All rights reserved.

Home / Trust center

Security / 01

Your data has
a lifecycle.

Clear controls for the credentials, rows, and agent connections that power your work.

01 / Batch inputs

2 hours

Auto-purged after the run reaches a terminal state.

02 / Batch outputs

7 days

Output content is automatically purged after the retention window.

03 / Hosted Lists

Your choice

Plan-based expiry or an explicit purge when you no longer need a list.

Data lifecycle

How long does Sorzio keep data?

Batch inputs are automatically purged two hours after a run reaches a terminal state; batch outputs are purged after seven days. Operational metadata, such as counts and costs, is retained separately. Hosted Lists have their own plan-based retention, and you can request their removal using the purge_lists tool.

DataRetentionControl
Batch inputs2 hoursAutomatic purge after terminal state
Batch outputs7 daysAutomatic purge after terminal state
Hosted Lists: Free2 hoursExpiry or purge_lists
Hosted Lists: Pro7 daysExpiry or purge_lists
Hosted Lists: ScaleForeverRetained until deleted

Controls in practice

How is access protected?

Sorzio uses encrypted credential storage, scoped agent authorization, restrictive data access policies, and outbound request controls. These safeguards cover different points in the lifecycle: storing a provider key, connecting an assistant, accessing workspace data, and fetching a public website for enrichment.

01 / CONTROL

Credentials, encrypted

Vault credentials use AES-256-GCM with authenticated additional data (AAD) binding the ciphertext to its context.

02 / CONTROL

Agents, scoped

OAuth 2.1 and PKCE S256 protect agent authorization. Restrictive deny_agent_tokens row-level security policies isolate direct data access.

03 / CONTROL

Requests, controlled

An outbound SSRF egress firewall blocks prohibited destinations when Sorzio fetches external resources.

04 / CONTROL

Privacy, considered

Empra Consultancy LTD operates Sorzio in compliance with GDPR and UK GDPR. Our privacy and subprocessor pages explain data handling and providers.

Security questions, answered.

Read the privacy policy and subprocessor list for more detail.

How does Sorzio protect connected credentials?

Sorzio encrypts vault credentials with AES-256-GCM and binds the encryption to its context using authenticated additional data. Agent connections use OAuth 2.1 with PKCE S256 and scoped authorization.

When is batch content removed?

After a batch reaches a terminal state, input content is automatically purged after 2 hours and output content after 7 days. Run metadata such as counts and costs is retained separately.

How long do Hosted Lists last?

Hosted Lists expire after 2 hours on Free, 7 days on Pro, and persist on Scale until deleted. The purge_lists MCP tool lets you remove eligible lists without waiting for expiration.

How are outbound requests controlled?

An outbound SSRF egress firewall protects against requests to prohibited destinations. Workspace isolation and restrictive agent-token policies protect data access.