What has been tested
Automated local tests exercise file tools, email-code controls, OAuth consent, PKCE, expiry and revocation. These are not certification of every commercial AI app. Named AI logos illustrate intended compatible clients, not partnership or completed qualification.
What the app needs
Private connections require remote Streamable HTTP MCP and the supported OAuth flow. Client registration and redirect URLs must be qualified. The public service-information sample is a separate read-only connection without private-account access.
How to connect
Copy the server URL from your connection page into your AI app’s MCP or connector settings. Follow its authorisation steps. Pasting a URL into a normal conversation does not install a connector. A localhost preview is reachable only from the same computer; the live domain is separate.
What can be read
Tools list packs and files, search prepared text with literal matching and read excerpts. Originals are retained in encrypted storage, but these AI tools do not deliver complete original files. Charts, images and layout are not faithfully represented by extracted text. Image-only scans are refused; no OCR or spreadsheet recalculation is provided. Search can miss relevant information if different words are used. Ask your AI to list the files and inspect relevant text, then check against the originals; we cannot guarantee its coverage.
Send a request, comment or note
Use your connected AI to deliberately send a message to the pack owner. Review the exact text before sending. The owner sees your submitted message and verified email in Recipient inbox; your private chat is not collected. Messages are encrypted at rest and kept for up to 90 days, or deleted sooner. No agent setup, API key or automatic answer is included in this version. See the workflow and boundaries.
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