Trust & data processing

Human-controlled automation,
documented.

Inference processes inbound business interest on behalf of its customers. This page describes what is processed, by whom, for how long, and the controls in place. It is product documentation, not legal advice; the data processing agreement below is a template pending legal review.

Data categories

What is processed.

Business contacts

Name, business email, role, company, inbound message text

Operators

Name, email, password hash (scrypt), session tokens (hashed)

Derived data

Model output is treated as a suggestion; a human approves every send

Intent classification, needs, score, drafts

Evidence

Lawful basis and source for every contact permission

Not collected

Special categories of personal data; consumer profiling; scraped contacts

Retention

How long it is kept.

Active contacts

For the duration of the customer relationship

Closed contacts

Message bodies, drafts, classifications and tasks are deleted; the contact becomes a pseudonymous stub

Purged after the workspace retention period (default 365 days, minimum 30)

Opt-outs

Address hash kept indefinitely so the objection is honoured

Audit trail

Kept with the workspace; contains no message content

Export / deletion

Full JSON export and per-contact erasure available to workspace admins at any time

Subprocessors

Who else touches data.

Provider	Purpose	Data	Region	When
Anthropic	AI classification and draft generation	Inbound message text, approved company knowledge, contact name and role	Configurable; EU inference geography available	Only when live inference is enabled by the workspace
Microsoft (Graph API)	Mailbox and calendar access	Inbox messages, sent replies, calendar availability	Customer's own Microsoft 365 tenant	Only when a Microsoft mailbox is connected
Google (Gmail, Calendar APIs)	Mailbox and calendar access	Inbox messages, sent replies, calendar availability	Customer's own Google Workspace	Only when a Google mailbox is connected
Resend	Transactional email (invitations, password resets)	Operator email address	EU/US per configuration	Only when configured by the operator
Hosting provider	Application and database hosting	All workspace data, encrypted at rest	EU (eu-west) for Dutch customers	To be named in the signed DPA

Security measures

Controls in place.

— Tenant isolation on every table; PostgreSQL row-level security as defence in depth.
— Provider tokens encrypted at rest (AES-256-GCM); minimum OAuth scopes; PKCE.
— Passwords hashed with scrypt; server-side sessions with hashed tokens; rate-limited sign-in.
— Every send re-checked against suppression, objection, permission and rate limits.
— Inbound content handled as untrusted data in all model prompts.
— Append-only audit trail of classifications, drafts, approvals, sends and settings changes.
— Strict transport security and content security policy headers.

Data processing agreement

DPA outline (template).

1. Roles: the customer is controller; Inference is processor acting on documented instructions.
2. Subject matter and duration: processing of inbound business contact data for the term of the subscription.
3. Subprocessors: those listed above; 30 days' notice of changes with a right to object.
4. Security: the measures listed; breach notification without undue delay.
5. Data subject rights: export and erasure tooling provided in-product; assistance on request.
6. International transfers: EU hosting; standard contractual clauses where a subprocessor requires them.
7. Return and deletion: full export at any time; deletion at end of term after a 30-day grace period.

Template only. Obtain Netherlands/EU legal review (GDPR Art. 28, Telecommunicatiewet, AI Act applicability) before signature.