Privacy and data

This website

Dray includes the public website, sign-in and your private dashboard. Public illustrations do not access your account or save memories.

We use site analytics by default to improve Dray. Open Analytics preferences in Settings or the page footer to opt out. This does not affect access to Dray. We respect Do Not Track and Global Privacy Control.

Usage analytics · Umami

Unless you opt out, our self-hosted Umami service measures page visits, referral sites, campaign tags, and actions such as starting setup. It also receives browser language, screen size, and page-load timings. Umami does not set tracking cookies. We do not send it names, email addresses, sign-in codes, account IDs, source text, or memory content.

Account and memory page addresses are reduced to page types. Search terms, pairing codes, and other private URL details are removed. Only standard campaign tags in a restricted format are kept on public pages. Hosts still receive network information such as your IP address when your browser connects.

Session recordings

Session recordings are not enabled in this unified app. Your account, memory and billing views are not recorded.

Your analytics preferences stay in this browser until you change them or clear site storage. Existing opt-outs are kept. Opting out stops future collection; it does not erase data already received. Contact [email protected] for data requests.

Fonts and provider marks are served with the site. A hosting provider may keep ordinary request logs, including IP addresses. Analytics are not added to the browser extension or your conversations on other sites.

Following an external link takes you to that service. This website does not submit personal details on your behalf.

The extension and memory

You grant access to each assistant separately. Dray reads conversations within the scope you choose and keeps a local chat archive in your browser.

Conversation content is sent for server-side memory processing. Dray uses external model services through OpenRouter to extract durable facts and prepare memory for search. The server stores memory records and supporting references.

If you enable file capture, files are copied to Dray’s storage so connected assistants can retrieve them. Do not treat the local archive as a guarantee that all content stays on your device.

About upstream retention

The backend supports different provider data policies. Retention depends on the deployed policy and the model endpoint used. This site does not claim that processing is always zero-retention, or that the product is end-to-end encrypted.

Contact [email protected] to confirm the active processing policy before connecting sensitive conversations.

Linking and context sharing

Experimental agent channels

The separate linking experiment pairs participants and exchanges the text they post. It is not connected to Dray’s memory store and does not automatically read either participant’s transcript, project files or local workspace.

Use synthetic test text and the approved beta instructions. Channel state can expire and is lost when the test service restarts. Participant names are not verified provider identities, and the experiment is not an end-to-end encryption or cross-user sharing product.

The channel has separate credentials and close controls. Pausing routine memory access does not close this separate channel.

Web conversation handoff

“Ask another assistant” prepares a prompt that refers to the source conversation by ID. Dray opens the target assistant and puts the request in its composer. You review it and press Send; Dray does not press Send for you.

The source needs to be captured and synced before the other assistant can read it. The request may give the target access to the whole chat and any stored files, not just the selected message. Sending it can share that content with the target provider.

Handoff prompts use the explicit /dray marker. This deliberate request can read memory even while routine recall is paused. Pausing is not a substitute for revoking access or disconnecting an assistant.

Your controls

• Choose which assistants Dray may read and how much history to include.
• Choose whether to capture files.
• Pause routine memory use. This does not delete memory or necessarily stop new capture. Explicit /dray requests can still read it.
• Remove provider permissions or disconnect the provider connection when you no longer want it used.

Dray does not edit or delete your source conversations. Removing the extension is not the same as deleting server-side memory. For deletion requests during the beta, contact [email protected].

Accuracy and limits

Capture can be incomplete. Memory extraction can be wrong. Provider interfaces, plans, and connection behavior can change. Review important details, especially before relying on them for a decision.

These are product data notes, not a finalized legal privacy policy. A public launch still needs the operator’s contact details, applicable legal disclosures, and the confirmed deployment-specific retention and deletion terms.

Payments

Polar handles checkout, subscriptions and payment methods. When you choose to pay, Dray sends your verified account email and an account reference to Polar. Dray does not collect or store card numbers. Billing shows the subscription and payment status returned by Polar.