What is in place, and what isn’t yet.
Every control below carries its real status. Where something is planned, we say planned. If a questionnaire asks about something we do not have, we will say so and share what we do have.
Where we stand today.
DeelSignal is pre-launch. We hold no SOC 2 report and no ISO certification today. We will not describe ourselves as certified before a report is issued.
SOC 2 Type I
Planned · April 2027SOC 2 Type I audit planned for April 2027. The report is shared under NDA once it is issued.
Penetration test
PlannedNot completed yet. A summary of a third-party test will be available on request at launch.
Data processing addendum
Draft · publicGDPR-ready draft with Standard Contractual Clauses. Read the draft.
US or EU
In placeChoose where workspace content is stored when the workspace is created.
Five areas, one status each.
Grouped the way security questionnaires ask. Search filters every control on this page.
Data protection
How your content is stored, kept and removed.
- Encryption at rest and in transitIn place
AES-256 at rest, TLS 1.2 or higher in transit.
- No training on your contentIn place
Your content never trains a model, ours or anyone we work with.
- Retention you setIn place
Workspace admins set retention per project type: 90 days, 1 year, or until deleted.
- DeletionIn place
Primary data removed within 30 days of a deletion request; backups roll off within 35 days. Confirmed in writing.
- Data residencyIn place
US or EU, chosen when the workspace is created.
- Export everythingIn place
Library, answers and audit log export in open formats at any time.
Sanitization
What happens to sensitive values before drafting.
- Placeholders before every model callIn place
Sensitive values are replaced with placeholders before drafting. Only placeholders are used to draft.
- What is detectedIn place
Company and customer names, people, email addresses, hostnames, IP ranges, keys and other secrets, prices and contract terms.
- Your own termsIn place
Admins add custom terms, such as code names, to what is detected.
- A record of what was replacedIn place
An audit trail of what was replaced and why.
- Real values only in the approved exportIn place
Values come back only in the export a person approves, never in logs.
Access
Who can sign in, see and change what.
- SAML single sign-onIn place
Okta, Microsoft Entra ID or another standards-based identity provider. SSO can be enforced for everyone.
- RolesIn place
Admin, owner, editor, expert and viewer. Experts see only the questions assigned to them.
- Audit logIn place
Uploads, edits, approvals, exports and sign-ins, with who and when. Exportable.
- Support access only with your approvalIn place
Our staff cannot see your workspace by default. Access is requested, approved by your admin, time-boxed and logged.
- Audit log streaming to your SIEMPlanned
Send audit events to your own security tooling.
- Session limits and IP allow-listsPlanned
Configurable session length, idle timeout and IP allow-lists per workspace.
AI usage
What the drafting may and may not do.
- Citations on every answerIn place
Every answer cites an approved source. If none exists, it says so instead of drafting.
- A person approves before anything is sentIn place
Nothing reaches a buyer without a human approval.
- Conflicts are heldIn place
When sources disagree, the answer waits for the assigned expert instead of guessing.
- Workspace policiesIn place
Block topics and restrict which sources a project may use.
- Two approvers for legal termsPlanned
Require a second approval on answers that touch legal terms.
Infrastructure
Where it runs and how it changes.
- Workspace isolationIn place
Each workspace is isolated. One workspace can never read another’s content.
- Edge protectionIn place
Managed edge protection with a web application firewall and DDoS protection.
- Reviewed, reversible changesIn place
Peer review on every change, automated tests, staged rollout with one-step rollback.
- No credentials in codeIn place
Credentials live in a managed secret store with least-privilege access.
- Responsible disclosureIn place
Report issues to security@deelsignal.com. We acknowledge every report within two business days.
- Third-party penetration testPlanned
Summary available on request at launch.
- SOC 2 Type IPlanned · April 2027
Report shared under NDA once it is issued.
- Public status pagePlanned
Live uptime and incident history.
From your documents to a signed-off answer.
Five steps, in plain language. A person stays in charge of the last one.
Read it here, or ask for it.
Public documents open directly. Documents on request are shared under NDA; we reply from security@deelsignal.com.
- Security overviewSanitization, data handling, access controls and AI governance.
- Subprocessor listWho processes what, and where.
- Data processing addendumGDPR-ready, with Standard Contractual Clauses.
- Privacy noticeHow we handle personal data.
- SOC 2 Type I reportRequest now and we send it once the report is issued.
- Penetration test summarySummary of a third-party test, available on request at launch.
- Our own security questionnaireOur SIG Lite and CAIQ answers, available on request at launch.
- Detailed data-flow documentThe step-by-step flow above, in more detail, under NDA.
Subprocessors, status and updates
Subprocessors
Who processes what, and in which region. Changes are announced before they take effect.
View subprocessorsSystem status
Planned · goes live at launchA public status page with uptime and incident history.
Status page link added at launchWhat changed, and when
- Trust center publishedCompliance status, the documents you can request, and how to ask for them.
- SOC 2 Type I audit planned for April 2027We will post here when the audit starts and when the report is issued.
- Sanitization of transcripts and RFP documentsCall transcripts and RFP documents are sanitized like every other source, with a review queue for each document.
Bring your own security questions.
We answer them on the call, and show you how DeelSignal answers yours.