OpenDataRoomYour data room for AI

OpenDataRoom

Privacy during the invited pilot

What we keep, who can see it and how long it lasts.

Optional navigation-search learning

Invited testers can separately choose to share searches entered into workspace navigation. These records include their tester account, query, matching-task count and selected destination. Only the service operator can review them, for up to 90 days. Switching this option off removes that account’s navigation-search records. Do not enter confidential deal information into navigation search. This does not share searches inside private packs or unlock the owner’s encrypted request ledger.

Contact and access requests

Contact amir@i2ntelligence.com about privacy, deletion or a support reference. The waiting list stores your email, optional company, time and notification state for up to 90 days. It does not verify your address, activate an account or subscribe you to unrelated marketing. Only the service operator can review it. Notifications to the operator are sent through Cloudflare; mailbox copies are separate.

Account and verification records

Accounts, company allocations, recipient addresses and grants support access control. Sign-in codes expire after five minutes; sessions after eight hours. Delivery records contain provider references and status, not code text. An accepted email is not proof of inbox delivery. Account and security metadata remain separate from encrypted file contents.

Files and keys

The private library stores browser-encrypted names and contents, opaque IDs, byte counts and retention deadlines. Recovery keys are not uploaded. If you approve a hosted AI copy, our service can decrypt that copy to serve authorised requests. Your AI provider receives requested content and has its own policies. We cannot erase copies it already received.

Request ledger

Detailed receipts for new wallet-created access copies are encrypted for the owner, including the prepared MCP response body where available. These copies follow the request-ledger retention policy, separately from source-file deletion. Limited operational metadata remains available to the service. Earlier records can have a different encryption boundary. Records describe server-visible requests and prepared responses, not the whole AI chat or proof that a person read 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.

Public sample

Starting the real sample creates a unique reference. Its requests, search terms and public-document metadata are visible to the operator for 30 days. Signed-in launches link to that account; anonymous launches identify a connection, not a person. Do not enter confidential information. The fictional example walkthrough does not upload files or create a real MCP connection.

Optional gap notifications

Owners can opt in to grouped alerts about authorised searches returning no matches. Emails contain a reference, not private query text or file content. No match does not prove information is missing. Turning alerts off stops future collection and pending notifications; existing records follow their retention schedule.

Optional pilot feedback and progress

During the invited pilot, you can choose to share technical setup progress: fixed step names, status codes, timing, broad device/browser category and software version. This optional stream excludes file names, document contents, private search terms, verification codes, keys and chats. It is off until you choose it. Turning it off clears this browser’s progress records. Feedback you deliberately submit, including optional comments and value/pricing answers, is separate and visible only to the service operator. Do not include confidential information. You can remove this browser’s feedback using its feedback controls. These diagnostic and feedback records, plus operator support notes and observations, are retained for up to 90 days; this does not change the separate request-ledger policy. Operational activation, access and delivery records also support aggregate pilot reporting. Shared invitation references indicate a link or campaign, not the identity of everyone who opens it.

Storage, removal and this pilot

Cloudflare provides the application, database, file storage and email infrastructure. File retention dates and AI-access deadlines are separate. Scheduled cleanup runs every five minutes; expiry cannot recall copies already retrieved. Browser storage is used for an explicitly remembered wallet key and necessary session state. Public payments and advertising trackers are not enabled. The full operator legal notice, processor terms and regional deployment commitments must be settled before general commercial release.

How it worksJoin the waiting list

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.

A real MCP connection

Ask your AI about OpenDataRoom.

Public information only. This connection cannot access customer files.

Opening this sample records a unique launch reference. Its requests, search text and document metadata are kept for 30 days for the OpenDataRoom operator. Anonymous means unidentified—not unlogged. Do not enter personal or confidential information.