Straight answers about privacy, security and control. Several of them are “not yet”. Those are the useful ones: a list where every answer is yes tells a buyer nothing, and they will find the no later anyway.
What can the AI provider actually see?
Only the request after identifying information has been replaced. They don\u2019t see your company, your people, or the original values.
Can we verify the redaction rather than trust it?
Today, partly. The redaction runs inside an AWS Nitro Enclave that can provide cryptographic attestation. Independent reproducible builds and automatic verification are not yet available. We\u2019re working on both.
What can Secure AI see?
Your conversations are encrypted to your devices. We see billing information and request volume \u2014 not the contents of your conversations.
Can an admin read what their team writes?
No. Personal chats and notes belong to the person who created them. Shared work belongs to the team.
What happens when somebody leaves?
Their seat is revoked. Work they shared with the team remains available to the team; personal work remains private.
Do you rotate the team key when somebody is removed?
Not yet. Removing a member prevents future access, but does not revoke anything they previously decrypted. Key rotation is on our roadmap.
Do you support SAML or SCIM?
Not yet. Sign-in uses Google or Apple, and seats are managed in Secure AI.
Do you have SOC 2 or a DPA?
Our DPA is available at secureai.one/dpa. We do not currently have SOC 2.
Can we pay by invoice?
Yes. Invoice billing is available on request and is standard above 500 seats.
What if redaction misses something?
Redaction is one layer of protection, not the whole system. Unusual identifiers can sometimes pass through, which is why Secure AI uses multiple layers rather than relying on redaction alone.
Anything else
Write to sales@secureai.one and we will answer the awkward questions first. The rest of what procurement asks is on the security page.