Privacy Policy

What we store, and what we don't

Your original contracts and SOWs remain in your own document system (Google Drive / Shared Drive, or OneDrive / SharePoint) when linked. SentientScope stores the human-verified commitments extracted from them, the minimum exact excerpts needed to explain why a commitment or alert exists, and source references — not a permanent copy of the full file.

A file uploaded directly is a transient processing input: it is parsed once to build the Living Scope and then deleted, with an automated cleanup enforcing a hard 24-hour maximum for failed or abandoned processing.

Your mailbox is never copied. When a team member connects their own Microsoft 365 mailbox, SentientScope reads new Inbox and Sent Items messages from that point forward under that person's delegated, read-only consent; it holds no organization-wide mailbox permission and does not fetch attachments. Messages forwarded or CC'd to a project address are evaluated the same way. For project-relevant messages we keep only the identifiers, the minimum relevant excerpt, and the decision history; the full message body is transient processing material. Approval emails SentientScope itself sent, and the client's responses to them, are retained as workflow records.

AI processing

AI is used to extract commitments, classify candidate events, and draft bounded summaries. Every AI request is built from SentientScope's own records for a single task; no product feature depends on an AI provider retaining prompts, files, or conversation history, and customer content is not used to train models.

Mobile numbers and text messages

Texting is optional for everyone. A SentientScope user may enter their own mobile number and opt into text alerts in Settings; an external client contact may enter their own mobile number and opt into text updates on the secure change-review page. A number entered about someone else is never used for texting. When you opt in we keep the proof of that consent — the number, the time, the method (web form) and the version of the disclosure you saw — and the time you later opt out, if you do. Mobile numbers are used only to send the transactional project messages described in the Terms of Service.

Text messages are delivered through Twilio, our messaging provider, which processes the mobile number and message content on our behalf in order to send and receive texts. Mobile numbers and SMS consent are not sold, rented, or shared with third parties for their own marketing or promotional purposes. Reply STOP to any message to opt out; we record the opt-out and stop sending. Consent and opt-out records are retained as long as needed to prove the messaging history and meet carrier requirements.

Security and access

Workspace data is tenant-isolated and access-controlled server-side. Multi-factor authentication is required for administrative roles. Platform staff cannot browse customer content; any future support access would be time-limited, reason-coded, and audited.

Your controls

You can export or delete your structured workspace data, disconnect any integration at any time, and configure retention. Questions: contact us through your workspace.