Skip to app content
Skip to main content

Security & Zero-Data-Retention

Give agents operational context without handing over your raw data

Synter runs autonomous agents on your ad accounts using an ephemeral context model: we read budgets, pacing, account structures, and warehouse or CRM cohorts in volatile memory to achieve your requested outcomes, without persisting your raw customer records at rest.

Zero-Data-Retention & Ephemeral Context

Connect your data warehouse or CRM without creating a second database of customer PII or ePHI.

Ephemeral CRM & warehouse reads

Queries against BigQuery, Snowflake, Databricks, Azure Data Lake, HubSpot, Salesforce, and Attio stream in volatile memory during the active turn so agents extract aggregate context. Raw rows, SQL/SOQL queries, and schema columns are stripped before database persistence.

PII-scrubbed agent memory

Agents remember operational context such as budgets, target CPA, account IDs, and pacing rules, not customer records. Conversational and operational memory writes (excluding operator-authored workspace skill templates) pass through a deterministic scrubber removing emails, phones, person names, SSNs, IP addresses, and click IDs.

Stateless conversion & lead relay

Workspaces can enable Strict ZDR or HIPAA BAA mode so Synter Pixel and hosted landing-page forms forward match signals in memory to your CRM and CAPI destinations while scrubbing PII at rest. HIPAA BAA mode also strips query strings from stored pixel URLs and form referrers.

Non-PII aggregate telemetry

Pacing guardrails and dashboards run on aggregate campaign numbers (campaign ID, date, spend, impressions, clicks, conversions) retained on a rolling 90-day window without storing Personal Data or ePHI.

Workspace Isolation

Every customer operates in a fully isolated workspace. Data, ad account credentials, and agent activity from one workspace are never visible to another.

Workspace-scoped data access

Every query for campaigns, ad accounts, connections, and agent threads is scoped to the authenticated workspace. No request can enumerate or read data belonging to another organization.

OAuth tokens tied to workspace

Ad platform credentials (Google Ads, Meta, LinkedIn, and others) are stored and resolved per workspace. A token belonging to one workspace cannot be used by another, even by the same user across their own workspaces.

Connection ownership verified at every call

Before an OAuth token is used to execute a platform action, Synter verifies the requesting workspace is the owner of that connection. Mismatched ownership is rejected and logged.

No cross-tenant enumeration

Campaign IDs, connection IDs, and account identifiers are validated against the authenticated workspace before returning data. An unauthorized caller receives a 404 rather than a permission error to avoid confirming the existence of data in another workspace.

Access Control

Control who in your organization can view campaigns, approve agent actions, and connect ad accounts.

Role-based permissions

Every workspace member is assigned an explicit role (Owner, Admin, Editor, or Viewer). Owners and Admins approve launches and configure Workspace Zero-Data-Retention settings. Editors build campaigns and review agent actions. Viewers hold read-only access.

Campaign-level collaborators

Campaign access can be granted to specific users with granular permissions, distinct from their workspace role. Pending invitations do not grant access until accepted.

SSO & MFA

CUSTOM enterprise workspaces can enforce SAML/OIDC single sign-on and multi-factor authentication for all members.

Approval workflows

Workspaces choose their autonomy level: agents can suggest and require human approval before executing, or execute autonomously within configured guardrails.

Campaign Safety

Agents operate within hard constraints enforced at the infrastructure layer, not by prompt instructions, so they cannot be bypassed by model behavior.

New campaigns always launch paused

Every campaign creation, regardless of instruction source, is coerced to a paused state before reaching the platform API. An agent cannot launch a live campaign without an explicit activation step.

Budget hard cap

A configurable spend ceiling is enforced server-side before any platform API call. The agent cannot exceed this limit even if instructed to. The ceiling applies to all create and update paths.

Conversion tracking gate

Campaign launches are blocked if verified conversion tracking is not active on the workspace. This prevents spend from running without measurement in place.

Unknown operations require approval

Any action that cannot be statically classified as safe requires explicit human approval before execution, regardless of the workspace's autonomy level.

Audit Log

Every action taken by an agent or a user is recorded. Logs are immutable, record workspace operator identity without storing customer CRM or warehouse payloads, and include:

TimestampWhen the action occurred (UTC)
ActorAgent or authenticated user
EntityCampaign, ad group, ad, audience, or budget
ActionWhat was created, changed, or blocked
Before / AfterOriginal and resulting non-PII configuration values
HMAC ReceiptTamper-evident HMAC-SHA256 Agent Shield verdict (allowed, coerced, or blocked)

Mutation receipts are retained for the active life of the workspace; closing an individual workspace does not terminate the master subscription Agreement while the customer account remains active. Upon termination of the Agreement, remaining Customer Personal Data in active systems (including operator-scoped mutation receipts) is deleted within 30 days unless earlier deletion is requested or retention is required by applicable law, and encrypted backups age out through automated rotation within 90 days in accordance with DPA Section 10. Required HIPAA compliance policies, procedures, and executed Business Associate Agreements are retained for six (6) years per 45 CFR 164.530(j). Export the workspace trail as CSV or JSON for compliance reviews.

Data Privacy & Hosting

No model training on your data. Model providers access data strictly under enterprise API terms prohibiting model training, with zero-data-retention API routing supported for regulated workspaces.

Deterministic PII & PHI redaction. Before writing long-term agent memories or persisting tool execution records, Synter scrubs emails, phone numbers, SSNs, IP addresses, ad click IDs, and API credentials, while connected warehouse and CRM rows are processed in volatile memory during the active turn and dropped before database storage.

Your raw data stays in your warehouse and CRM. First-party records remain in your connected Snowflake, BigQuery, Databricks, Azure Data Lake, Salesforce, HubSpot, or Attio instance. Synter reads only the context required for the requested task in volatile memory and drops the rows before persistence.

Google Cloud Platform infrastructure. Synter runs on Google Cloud Run in the United States, with isolated Daytona cloud sandboxes for opt-in background bot threads. EU and UK transfers are covered by our DPA and Standard Contractual Clauses.

Compliance

SOC 2 Type II

In progress

Synter operates SOC 2 security, availability, and confidentiality controls across Google Cloud Run, encrypted credential vaults, and tamper-evident mutation receipts, with independent Type II observation underway.

HIPAA

BAA on CUSTOM

Healthcare organizations on CUSTOM plans can execute a HIPAA Business Associate Agreement and enable Workspace HIPAA BAA mode for stateless CAPI/CRM relays, URL query scrubbing, and automatic suppression of non-BAA subprocessors.

Read HIPAA & Zero-Data-Retention Guide ->

GDPR

Compliant

A Data Processing Agreement (with EU Standard Contractual Clauses and UK Addendum) is available for EU and UK customers, backed by ephemeral CRM and warehouse reads by default.

Read Data Processing Agreement ->

CCPA / CPRA

Compliant

California residents can request access to or deletion of personal data. Synter never sells or shares personal information for cross-context behavioral advertising.

Read Privacy Policy ->

Security review, DPA, or HIPAA BAA request?

Our team responds to security questionnaires, executes DPAs and CUSTOM-plan HIPAA BAAs, and configures Strict Zero-Data-Retention or SSO for enterprise workspaces.

Contact Security Team
Security & Zero-Data-Retention | Synter