Data Processing Agreement

You are the controller of the data your workspace puts through attest_tag. Attest Tag, a Delaware company, is the processor, and we act on your documented instructions — the configuration you set, the connections you authorise, and the requests your people make in Slack.

You remain responsible for having a lawful basis to process that data and for what your people ask the assistant to do with it.

Subject matter: providing attest_tag to your workspace. Duration: the term of the agreement, plus the deletion window in clause 10. Nature and purpose: answering in threads, searching the documents you supply, calling the services you connect, and keeping the operational record that makes those actions auditable.

Categories of data: the content of threads the assistant is mentioned in, the documents you upload, the responses from services you connect, and identifiers for the people using it — Slack user and channel IDs, display names and work email addresses. Data subjects: your workspace members, and whoever is named in the content they send.

We do not ask for special categories of data, and the product is not built for them. If your content contains any, that remains your decision and your risk assessment.

We do not sell your data, and we do not share it for cross-context behavioural advertising or any other purpose outside providing the service. We do not combine it with data from other customers, and we do not retain, use or disclose it for our own commercial ends.

We use it to run attest_tag for you, to keep it secure, and to fix it when it breaks. That is the whole list.

Your content is never used to develop, train, fine-tune or evaluate a model — ours or anyone else’s. This holds for thread text, documents, tool results and the artifacts the assistant produces.

It holds downstream too. Model calls route with deny-training enabled, so a turn only reaches providers contractually barred from training on the prompt. If you point the product at your own endpoint instead, that endpoint’s terms are the ones that apply, and choosing it is yours to make.

Your data is confidential. Access is limited to the people who need it to operate or support the service, each of them bound by confidentiality obligations that survive their engagement.

Support access to a deployment is on request and on the record. We do not read your threads as a matter of routine, and there is no internal dashboard that shows them.

Data is encrypted in transit with TLS and at rest by the storage layer. Credentials for the services you connect are sealed with AES-256-GCM under a master key held in the deployment’s environment; they are injected by the proxy at call time, never placed in a prompt, and never returned to a Slack thread.

Threads are rebuilt from Slack on each turn rather than mirrored into a second copy of your workspace, which keeps the standing surface small. Outbound calls are limited to the hosts you allow-list. Every tool call, proxied request and confirmed write lands in an audit ledger you can read.

Actions that change something in a connected system wait for a person to confirm them, and the confirmation is recorded against the human who gave it.

You authorise the subprocessors listed on the subprocessors page. Each is engaged under written terms no less protective than these, and we remain liable for their performance as if it were our own.

We will update that page and give you at least thirty days’ notice before a new subprocessor begins processing your data. If you object on reasonable data-protection grounds within that window, we will either propose a workaround or you may terminate the affected part of the service without penalty.

If we become aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, or unauthorised disclosure of or access to your data, we will notify you without undue delay and within seventy-two hours. The notice will describe what happened, what data was involved, what we are doing about it, and what — if anything — you need to do. We will give you the information you need for your own regulatory notifications.

If someone exercises a right of access, correction, deletion, portability or objection, and the data sits in your deployment, you can usually answer it yourself: the console exposes the sessions, memories and artifacts for a given person, and can delete them.

Where you cannot, we will help — promptly, and at no extra charge for a reasonable volume of requests. We will not respond to such a request directly unless you instruct us to or the law requires it, in which case we will tell you first unless we are barred from doing so.

We will also give you reasonable assistance with data protection impact assessments and with prior consultation of a supervisory authority.

You can export your data at any time during the term. On termination, we will delete it within thirty days, or return it first if you ask before that window closes.

Backups age out on their own schedule and are deleted within ninety days. We retain nothing beyond that except where the law requires it, and anything so retained stays subject to these terms.

Hosted deployments and their subprocessors process data in the United States. If you need it processed elsewhere, tell us before you sign — attest_tag is built to run on your own infrastructure, so the answer is usually a region you choose, not one we do. Where a transfer of personal data out of the EEA, the UK or Switzerland is involved, the Standard Contractual Clauses apply and are incorporated here by reference.

We will answer your security questionnaire and provide the documentation we hold on our controls. You may request an audit once in any twelve-month period, or after a security incident, on reasonable notice and under confidentiality — conducted so that it does not disturb other customers’ data.

We may update these terms to reflect a change in the product or in the law. If a change materially reduces your protections we will give you notice before it takes effect, and the version in force on the day you signed continues to govern until you accept the new one.

For a signed copy, a security questionnaire, or anything to do with data protection: [email protected]. See also the subprocessors page and the privacy policy.