Policy bundle version: 2026-08-05.
This page describes the current engineering posture and explicit limitations. It is not a certification, service commitment, data-processing agreement, authorization for PHI use, or confirmation that customer signup is active. Customer use requires explicit launch activation and compliance with the applicable published policies. Institution-controlled or restricted use may also require a separately approved trust packet and written agreement.
1. Information MARCUS May Process
| Category | Examples | Purpose |
|---|---|---|
| Account and organization | Name, email, role, memberships | Authentication and administration |
| Customer Content | Authorized documents and source metadata | Prepare documents for search and citation |
| Interaction data | Questions, source passages, answers, citations, feedback | Provide and review the service |
| Derived artifacts | Search indexes, temporary caches, generated pages | Search and answer generation |
| Operational records | Audit events, analytics, request and error metadata | Security and reliability |
| Billing metadata | Plan, invoice, and payment-provider references | Subscription administration |
2. How Information Is Used
- Provide, secure, troubleshoot, and improve the user's MARCUS workspace.
- Authenticate users and enforce organization/project access.
- Process approved documents for retrieval and citation.
- Generate responses and maintain conversation continuity.
- Prevent abuse, investigate reliability issues, and administer billing or support.
- Comply with applicable legal obligations.
3. Service Providers and Model Processing
MARCUS uses hosting, database, object-storage, model, embedding, email, billing, and optional integration providers. The current provider categories are listed on the Subprocessors page.
Effective provider retention, training-sharing, residency, and contractual settings are deployment-specific and remain subject to verified account evidence. Do not rely on this policy as proof that a particular provider control is enabled.
4. Retention and Deletion
MARCUS has not yet ratified a single retention schedule across originals, database records, search indexes, caches, derived content, logs, provider state, exports, and backups. The applicable individual policy or approved institutional agreement must state the relevant periods before launch.
Deletion requests are subject to identity and authorization checks. Until end-to-end deletion and backup/provider expiry are evidenced, MARCUS will disclose unresolved residual copies and expected expiry rather than promise immediate deletion.
5. Requests and Choices
Contact privacy@surgic.ai for access, correction, deletion, or other privacy questions. Do not include source content, patient information, credentials, or secrets in email. Rights and response obligations depend on the applicable law and agreement.
6. Changes
We may update this policy as MARCUS changes. Material changes to providers, data classes, retention, model configuration, storage, deletion, or legal posture require an updated notice and any review required by the applicable agreement before continued use.