Security and access boundaries

Your private library

File contents and names are encrypted in your browser before upload. Your wallet recovery key is not uploaded. The service stores encrypted data and opaque references; it does not receive your wallet recovery key. An ordinary company administrator cannot unlock another member’s private wallet. Keep a recovery copy: email access alone cannot decrypt it.

Your hosted AI access copy

A remote AI needs material it can read. You explicitly approve a separate time-limited hosted copy; the service decrypts that copy during authorised retrieval. This is not provider-blind processing. The receiving AI provider also obtains retrieved content. Do not approve a hosted copy if that boundary is unsuitable for your material.

Sign-in and recovery

Email codes expire after five minutes, are bound to the requesting browser and have limited attempts. Sessions expire after eight hours. A remembered browser holds a non-exportable wallet key only when you choose it. Recovery files stay in the browser during import. Passkeys, QR device transfer and a trusted-device management screen are not supplied yet. Protect your email account and device.

Access ends separately from storage

New reusable AI approvals can remain valid after browser verification ends, up to the explicitly approved pack and connection deadlines. Fresh verification is still required to grant or expand access. Existing approvals keep their original deadlines; adding a pack to your library does not approve it for an AI.

Hosted connections have deadlines and can be revoked earlier. Private library packs have their own displayed retention date; they are not an indefinite backup. Scheduled cleanup runs every five minutes online. Deleting a library pack also stops its linked hosted copies. Nothing can recall copies already retrieved by another application.

Private request records

For wallet-created access copies, detailed request receipts are encrypted for the pack owner. The operator retains limited operational references, outcomes and usage metadata. Earlier records can have a different encryption boundary. Repeated unauthenticated requests may be recorded only in security rate counters, rather than as individual private receipts. 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. This is not an independently immutable regulatory archive.

Scope of this pilot

Public signup is a waiting list. No payments are taken. Use non-sensitive test material while commercial client compatibility, independent security assessment and production deletion evidence are completed. Encryption reduces disclosure; it does not remove the need to trust the delivered browser application, protect your device or assess the receiving AI service.

How it works Join 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.