Know where your context goes.

In your browser

The context studio processes manually entered facts, selected text files, proposal imports and handoffs in your browser. Importing these items does not upload them to Selfrelay. Plain text imports are split into notes; the studio does not send them to an AI for extraction.

Device saving is optional. It stores readable context in this browser profile, without encryption by Selfrelay. JSON backups and Markdown handoffs are also readable files. People with access to your browser profile or downloaded files may be able to read them. Without saving or a backup, closing or refreshing the tab can lose your work.

The separate career workspace also processes its profile, evidence, roles and résumé drafts locally, with optional device saving and downloads.

Encrypted cloud backup

Cloud backup requires sign-in. Your browser encrypts the workspace with a key derived from your passphrase before uploading it. Selfrelay stores the encrypted backup and account, revision and update metadata. The passphrase is not sent to the backup API. We do not hold a recovery key and cannot recover a forgotten passphrase.

This protects the uploaded backup, not plaintext device storage, downloaded JSON, or separately published handoffs. The encryption implementation has not undergone an independent security audit. Cloud backup is a manual save and restore workflow, not automatic synchronization.

Published snapshots and legacy cloud statements

Publishing a studio handoff uploads the selected snapshot in readable form, including its title, assistant label, objective, facts and source references. We store it with grant metadata and a hash of the access token. Anyone holding the token can read the selection until expiry or revocation. Labels do not authenticate an application or enforce how a recipient uses a copy.

Local studio corrections do not update or revoke published snapshots. Revoke affected grants in Live access and publish a newly reviewed snapshot when needed. Revocation blocks future reads and clears the grant's stored snapshot. It cannot recall text already copied or received.

The legacy cloud statement workspace stores statements in readable form. Editing or deleting one of those cloud statements revokes its linked grants. That automatic link does not apply to studio snapshots.

Optional assistant connections

Where the experimental OAuth flow is enabled, each connection records your account, the configured client and callback, the selected snapshot, consent duration and most recent access check. Authorization codes and assistant access and refresh tokens are stored as hashes. Your Cognito sign-in tokens are not shared with the assistant. A public client configuration does not prove which application process holds a bearer token.

Disconnect in Account to stop future access. Revoking a snapshot ends its linked connections, and deleting cloud context removes those connections and pending account-bound connection requests. Copies already retrieved are separate. Expired connection records may remain until cleanup runs; operational backups follow their separate retention cycle.

Deletion, providers and contact

Clear local workspace removes the Studio browser copy and current workspace. The Career workspace has its own clearing control. You can delete a cloud backup separately. The Delete your cloud context control in Account removes hosted statements, grants, assistant connections and encrypted backup content, and ends Selfrelay sessions. It keeps your Cognito sign-in identity. A backup revision counter remains to prevent stale tabs from overwriting later backups.

Delete your Selfrelay account is a separate action. It requires a fresh sign-in check, shows the verified account and asks you to type DELETE ACCOUNT before starting removal of both cloud context and the sign-in identity. Returning from sign-in does not start deletion. Once removal starts, it cannot be cancelled.

Cloud-data deletion can finish while sign-in identity removal remains unconfirmed. The deletion page reports completion only when both are confirmed. If a request times out or the result is uncertain, check deletion status before explicitly retrying. A new sign-in check may be required. If you cannot sign in and the result remains unconfirmed, contact us to reconcile the deletion. After confirmed deletion, use Finish sign out to complete browser sign-out; this does not repeat deletion.

An account-deletion record remains to prevent stale sessions or saves from recreating deleted account data. Browser workspaces, downloaded files, recipient copies, accounts on the earlier hosting service, provider backups and operational logs are separate. We do not promise immediate physical erasure from every provider backup.

AWS Cognito manages sign-in and email verification. It does not give Selfrelay your AI conversation history. Encrypted session tokens and account metadata are stored on our server. Hosting and infrastructure providers process service data such as request times, IP addresses and browser information. If you email us, we receive your message and address to respond. There is no sale of personal profiles or population analytics in this beta.

Inspect handoffs before sharing. Free text and source URLs can contain personal details. Content pasted into another AI is handled under that service's policies. Keep passwords, identity documents and confidential third-party material out of this early product.

The operator is Mitaanshu Agarwal, Australia. For privacy or deletion requests, contact mitaanshu137@gmail.com. Identify your account without sending passwords, access tokens or identity documents.