Prepare
Include the relevant originals, source dates and a short index. Distinguish evidence from assumptions. Check extracted text before you approve a hosted copy; scans and complex spreadsheets may need a simpler representation.
Choose access
Save an encrypted private pack, then explicitly approve a time-limited hosted copy for your own AI or a named recipient. That copy can be decrypted by the service during authorised retrieval. Different disclosure scopes should use separate packs.
Connect
Copy the MCP URL into a compatible AI app’s connector settings and approve access. Connecting does not automatically execute a supplied prompt. Recipients choose what to ask their own AI.
Review
The ledger shows server-visible requests and prepared responses. Revoke access when the task ends. Expiry cannot recall copies already received, and your library has its own retention deadline.
Choose where decryption happens
The hosted connection uses a separately approved copy that our service can decrypt. The optional local-only connection creates no hosted readable copy: a desktop connector holds a pack-specific key and decrypts on the recipient’s device. The owner approves the exact connector fingerprint. Your chosen AI receives retrieved plaintext in either mode.
A local connector must be installed and remain available. It is an unsigned pilot build; commercial-client installation and individual platform compatibility still need testing. It is not a universal mobile or one-link cloud connection. Local keys are encrypted on disk with a separate device-vault password entered in the extension’s secure settings. Keep that password private; losing it requires fresh pairing. Protect your device.
Approvals and request records
Named email verification and browser-key approval are required by default. A request QR lets someone ask for access; it is not an access credential. The owner can approve or decline, stop new requests, or revoke existing invitations separately. Browser approval is not proof of the physical device used by a cloud AI.
Gateway records describe server-observed operations. Local connector reports are signed and owner-encrypted, and marked as reports. Neither proves that a person read a result or that an AI used it. A modified recipient application can retain previously received content or keys. Revocation cannot recall them.
Subscriber request records are kept during the subscription and for one calendar year after it ends. An owner-encrypted archive is then available for at most 90 days, with email notifications and a fixed download deadline. The public sample keeps its separate 30-day policy.
Files have their own retention deadlines. Scheduled removal and database backup expiry are separate: a recoverable database snapshot may retain an earlier key record. We do not claim immediate irreversible erasure.
OpenDataRoom