What we receive
We accept the source material the engagement scope describes — files, call recordings or transcripts, forwarded emails, CRM and system exports, supplier documents. We ask for only what the deliverable needs; nothing more.
Data and privacy
How we handle the work you hand off.
This page describes how client inputs flow through an engagement at ElaborationAI — what we accept, where it lives, who can see it, and how AI workflow calls are scoped. It is an operational description, not a legal certification.
Specific data, retention, and processing terms for any individual engagement are agreed inside that engagement, not on this page.
Where it lives
Inputs and conversation are stored against the workspace order that scoped the work. Each order is a per-engagement scope. The public catalog and the site-search retrieval index are built from the published MDX content; they never touch client workspace records.
Who sees it
Operators and reviewers assigned to your active engagement. AI workflow providers receive only the inputs required to run a given model call — the chunks of content that the workflow step actually needs, not the entire order. We do not share order content with other clients or with the public catalog.
What stays out
We do not request passwords, full-account credentials, payment card numbers, or government-issued identity documents unless the agreed deliverable literally requires them. If the scope changes and a sensitive input is needed, that change is recorded in the order before any new material is uploaded.
AI workflow boundaries
What the AI workflow sees, and what it does not.
The middle of the operating loop is an AI-assisted workflow. The assistant is scoped to the work in front of it, not to the rest of your business.
- AI workflow steps run against the inputs explicitly scoped in the order — not against your other orders, not against the rest of the workspace, not against client records that belong to another engagement.
- When a model provider call is required, only the specific text or attachment the step needs is sent. We do not send the entire order payload by default.
- The public site search indexes only the public MDX catalog. It has no read access to operations, orders, files, messages, or any client workspace.
- Client-supplied material from an order is not added to the public site-search retrieval index; that index is built only from the published MDX catalog at build time.
Retention
How long records stay around.
- Order records, inputs, and deliverables stay in the workspace while the engagement is active.
- After an engagement closes, records remain for a reasonable retention window so historic deliverables can be re-issued or audited if you ask for them.
- You can request removal of specific records from your workspace; the request is logged inside the same order.
- Backups follow the storage provider lifecycle and are not exported into our reviewer process.
If you need engagement-specific terms.
Some engagements require a written processing addendum — for example, when an input is regulated, when access to a particular system is agreed in advance, or when retention is shorter than the default. Those terms are agreed inside the order before the engagement runs; nothing on this page overrides them.
For a data access, correction, or deletion request that is not tied to an active order, email [email protected] and we route it to the reviewer who owns that record.