Dray for Firefox follows this policy for "the browser extension", with two differences. Where the policy says Chrome, read Firefox. And in Firefox, usage stats (Firefox's "technical and interaction data") are off until you allow them, in Firefox's own prompt or from Share usage stats in Dray's settings; Dray sends none while Firefox's permission is off. The same policy is published at https://withdray.com/privacy.

Privacy and data
Dray is not an entirely on-device product. This policy says what Dray collects, why, who else handles it, and how to have it deleted. Last updated 18 October 2026.
Who we are
Dray is run by Rafael Aslanian, an individual based in the United Kingdom, who decides how the personal data on this page is used: in data protection law, he is its controller. Write to support@withdray.com about anything here, including a request to see, correct, export or delete your data.

This website
Dray includes the public website, sign-in and your private dashboard. Public illustrations do not access your account or save memories.
Cookies and your choice
We use essential cookies to run Dray: one keeps you signed in, and others remember your theme, your answers to the plan questions and your cookie choice. Everything else depends on the country your connection comes from:
• In the UK, PostHog’s usage statistics run unless you object, under the UK’s exemption for statistics used to improve a service. Advertising cookies from Meta and Google, and session recordings, wait until you press Accept.
• In the European Economic Area, Switzerland, the Channel Islands, the Isle of Man and Gibraltar, and whenever we can’t tell where you are, nothing beyond the essential cookies runs until you press Accept.
• Everywhere else, analytics and advertising are on unless you opt out.
Reject, or Essential only, turns all of it off and does not affect access to Dray. In Cookie preferences, in Settings or the page footer, you can turn analytics, session recordings and advertising on or off separately, and change your mind at any time. We respect Do Not Track and Global Privacy Control: either one turns all of it off, wherever you are.
The cookies themselves:
• Essential, from Dray: the sign-in cookie, better-auth.session_token (7 days, renewed while you use Dray); dray_theme, dray_plan_asked and dray_beta, which remember your theme, your plan answers and whether you chose beta builds of the extension (one year); and dray_ads and dray_analytics, which pass your advertising and analytics choices to our server (180 days).
• Analytics: PostHog’s ph_…posthog, which tells a return visit from a new one (one year), and Dray’s dray_src, which keeps the campaign tags, first page and referring site of the visit that brought you here, so a purchase can be credited to the ad or creator behind it (90 days).
• Advertising: Meta’s _fbp and _fbc (90 days), and Google’s _ga and _ga… (two years) and gcl… (90 days).
Contacting support
When you use the support form, we send your reply email, topic, and message to our support inbox through our email provider. A message about Dray for a team also gives your name, your company’s name, its size, the assistants it uses and when you’d like to start. A bug report also names your browser and its version, your operating system, and the version of Dray’s extension if you opened the form from it. The form shows that line before you send. No chats, files, or other account data are attached automatically.
The message is handled through email, not stored as a support ticket in the app database. A copy of each email to support@withdray.com is posted to a private channel on Discord, the chat service the team works in, so we see it quickly, and it is deleted there when your account is deleted. To limit spam, the database keeps submission counters and keyed hashes of reply addresses. Expired address counters are cleared on later submissions. Please don’t send passwords, sign-in codes, API keys, or private chat content.

Usage analytics · PostHog
Where your cookie choice allows it, PostHog, hosted in the EU, measures how the site is used: page visits, referring sites and campaign tags, clicks, how far you read, page speed and errors, and steps such as starting setup, choosing a plan or changing it on the Billing page. It sets a cookie so that it can tell a return visit from a new one. When you are signed in, it also gets a SHA-256 hash of your Dray account ID, never the ID itself, so your visits from different devices count as one person, along with your setup answers: your goal and which assistants you use. Our server tells it about your account and subscription: signing up, trials, payments and refunds, and a subscription being cancelled, resumed, ending or failing to renew, with the plan, the amount, any discount code, how the visit that led to your checkout arrived, as dray_src keeps it, and the reason you picked from a list if you cancel. Any comment you write when cancelling stays with Polar. If you tell us where you first heard about Dray, it gets the option you picked. Visits through a creator’s link to Dray (withdray.com/go/…) are counted by creator and campaign, without a cookie or anything that identifies you. We do not send it names, email addresses, sign-in codes, source text, or memory content.
Account and memory page addresses are reduced to page types before they leave your browser, and search terms, pairing codes and other private details in addresses are removed. Outside the public pages, so is the text of whatever you click. PostHog uses your IP address to estimate your country and city, and does not store it. Hosts still receive network information such as your IP address when your browser connects.
Your assistant’s lookups · PostHog
Each time your assistant looks something up in Dray or saves something to it, PostHog gets a record of it with the same hash of your account ID: the tool, which assistant used it, which assistants’ conversations the answer came from, how long it took, whether it worked or what kind of error stopped it, and counts such as how many facts came back. At most once a day, it also notes that your linked chats sent or read messages. It never receives what was asked, saved, returned or posted, or any link code: for anything written, only its length.
The browser extension and your memory · PostHog
Unless you turn off Share usage stats in the extension’s settings, the extension tells Dray how it is being used: installs and updates, signing in, setting up, connecting and removing assistants, opening your dashboard, reading your chat history (with a count of chats), handoffs and links, pausing your memory and, at most once a day, saving or uploading that has stopped working. Dray’s own server keeps only a fixed list of events and values and sends them on to PostHog with the same hash of your account ID. Before you sign in, only installs and updates, sign-in attempts and the reason a sign-in failed are sent, under a hash of a random ID for this installation that is joined to your account when you sign in. Everything else waits in the extension until then.
For the first two weeks after you install it, the extension also records how its own panel is used, such as scrolling and clicks, so that we can see where setup gets stuck. It does so only while your cookie choice on this site allows session recordings, described below, and Share usage stats is on. Before the recording leaves your browser, every word in the panel is replaced with asterisks, pictures are left out and what you type is hidden, so your memory, chat titles and account details are never recorded. It goes to PostHog under the same hashes. The extension never records your conversations on other sites. Recordings are deleted after 30 days.
Our server also notes how Dray is working for your account: which assistants and coding agents send it messages, counts, timings and failures by fixed category as it turns them into memory, and when your plan’s monthly allowance is nearly used or learning has paused.
These server notes, and your assistant’s lookups above, are part of running Dray: they show us when something breaks, where setup fails and how each plan’s allowance is used, and they never include what you said or saved. So neither the extension’s switch nor the website’s cookie choice turns them off. If you object to them, email support@withdray.com.
When you remove the extension, Chrome opens a page on this site asking why. While usage stats are on, the page’s address carries the same hash, so your answer is counted with the rest. With them off, the visit is still counted, without the hash. None of this includes what you said, what Dray saved, chat titles or page addresses.
Advertising · Meta Pixel and Google Analytics
Where your cookie choice allows them, Meta Pixel and Google Analytics set cookies on this site. They learn which ad or campaign brought you here and which steps you take next: asking for a sign-in code, creating an account, viewing plans, opening checkout, starting a trial and paying. The plan and its price go with the steps that involve one. Apart from the one report about using Dray described below, these are steps you take on this website. Nothing the extension reads or saves is sent to Meta or Google.
When you are signed in, both also get a SHA-256 hash of your email address and of an ID made for them, never the address or your account ID. They use the hashes to match your visit to their own users. Google gets page types, as PostHog does. Meta reads the page address itself, so it never runs on memory, pairing, uninstall or email unsubscribe pages, or on a page that is passing you on to another, and its automatic tracking of button clicks is off.
So that a purchase still counts when a browser blocks these tags, our server also reports some of these steps directly. Meta gets sign-ups, checkouts, trials, purchases, the first renewal of a monthly plan and connecting the browser extension, with the same hashes, its cookie IDs, your IP address and your browser type. Google gets checkouts, trials, purchases, the first renewal and refunds, with its cookie ID and the same hashes. When you open a checkout, we keep that information with the order at Polar, our payment provider, for this reason. Both also get one report that you used Dray again: the first time, in the week after you pay, that one of your assistants finds something in your memory on a later day than your plan started. It goes with the same hashes and the advertising details your checkout carried, and only if that checkout had your advertising consent. It says that this happened and when, never what was asked or found. If you opt out while signed in, these reports stop for your account, including for a plan you bought earlier. Nothing reported includes your conversations or memory.
Meta and Google handle this data under their own terms, which include using it to measure and deliver ads. Opting out stops future collection and deletes their cookies from this site. It does not erase what they already received.
Session recordings
Where your cookie choice allows them, and unless you turn off Session insights, PostHog records how pages are used, such as scrolling, clicks and moving between pages, so that we can see where people get stuck. In the UK, the European Economic Area, Switzerland, the Channel Islands, the Isle of Man and Gibraltar, that is only after you press Accept. Public pages are recorded as they appear. On every other page, including your account, memory and billing views, all text is replaced with asterisks before the recording leaves your browser, so your content is never recorded. What you type is hidden on every page. The same choice covers the browser extension’s panel, described above. Where we ask first, the panel counts only a yes given since it was named here. Recordings are deleted after 30 days.
Your cookie choice stays in this browser until you change it or clear site storage. When you are signed in, we also keep it with your account, so that it applies to what our server reports for you. Opting out stops the website’s analytics and ad cookies from collecting more; it does not erase data already received, and it does not cover the server notes described under the browser extension and your assistant’s lookups, which are part of running Dray. Contact support@withdray.com for data requests.
Fonts and provider marks are served with the site. When you sign in, we keep the IP address and browser that sign-in came from with your session, to protect your account. A hosting provider may keep ordinary request logs, including IP addresses. No analytics code runs on your conversations on other sites. In the browser extension, the only analytics code is the panel recording described above; its usage stats go to Dray’s own server, which passes them on.
Following an external link takes you to that service. This website does not submit personal details on your behalf.

The extension and memory
You choose which assistants Dray may read. Dray reads conversations within the scope you choose, and the names of your projects there, and keeps a local chat archive in your browser. To ask an assistant’s site for your conversations, the extension uses the sign-in you already have on that site. That sign-in stays in your browser and is never sent to Dray. When you set Dray up in an assistant, the extension fills in that assistant’s own settings for you. It adds Dray as a connector (in Claude, by uploading Dray’s plugin) and starts the sign-in to Dray. It also writes one line about Dray into your custom instructions, which you save yourself.
Chats you have in the ChatGPT and Claude desktop apps, on your phone, or in the Grok phone app belong to the same account on that site, so the extension saves them too, through the same sign-in. While Chrome is running and signed in to the site, it asks the site for your newest chats, with no tab open: about once a minute while you are using the computer, and every 15 minutes when you are not or it is locked. To tell those apart it uses Chrome’s idle state, which says only whether the computer was used in the last few minutes or is locked. It reads only chats that are new or have changed since it started; older ones come in only when you ask it to read your history. So that Dray can tell you when chats are not being saved, the extension also tells Dray, every 10 minutes and whenever it changes, whether it can still read each of these sites, with a random ID for this Chrome profile so that your computers can be told apart. Dray keeps the latest of these with your account and uses it only to warn you, and the assistants you connect, that a site is signed out or that Chrome has stopped reporting.
The extension sends the text of those conversations, with their titles, dates and IDs, to your Dray account. There, AI models pick out the facts worth remembering and prepare them for search. We store your conversations, the memory made from them, and a link from each fact back to where it came from.
File capture starts on: files and images in your chats, including ones the assistant makes or shows in its replies, are copied to Dray’s storage so connected assistants can retrieve them. An image shown from another website is fetched from that site without your cookies. One switch in the side panel turns file capture off. Do not treat the local archive as a guarantee that all content stays on your device.
The extension also follows what you change on ChatGPT, Claude and Grok so your memory can keep up: when you delete a chat there while Dray is running, Dray deletes it from your memory too. To do this it watches requests to those sites’ own conversation, project and connector addresses, without ever blocking or changing them. It acts on the ones that delete, restore or rename a chat or a project, or add or remove Dray’s connector or plugin. It also counts conversation requests, so that its own reading never comes too fast, and notices when a site refuses a read because there were too many. It looks inside a request only where that is the only way to tell what it does, keeps nothing from it, and sees nothing of the rest of your browsing.
If you import a ChatGPT, Claude or Grok export from your dashboard, your browser reads the file on your computer and sends Dray only the text of your chats and the names of files you attached, never the files themselves.
If you make a project in Dray, or ask an assistant to save something to one, Dray stores its name, the instructions and text files you add, the notes your assistants save there and which assistant saved each, and which of your chats’ projects and folders it gathers, and indexes the instructions, files and notes so your assistants can search them.
Coding agents
The command-line app also sends optional setup and reliability statistics to PostHog: the operating system, app version, agent name, setup or sign-in stage, outcome and counts. Setup and sign-in statistics can be sent before you connect your account, using a random installation ID. They contain no conversation text, file paths, command output, credentials or account email. Run dray analytics off or set DRAY_ANALYTICS=0 to stop these statistics independently of saving your sessions.
If you install Dray for coding agents on a computer and approve that computer in your account, Dray saves your Claude Code, Codex, Cursor, Grok Build, OpenCode and Antigravity sessions from it. It sends the text you typed while the turn is still running or when it ends, and the answer the turn ended on once it ends. Both are read from the session record the agent already keeps on that computer, or for Cursor taken from what Cursor hands its hooks, and are sent with the session’s title, the project folder’s name, times and IDs. For Antigravity, that record is the transcript it keeps for each conversation. Importing past Antigravity sessions also reads Antigravity’s own list of conversations on that computer, for each conversation’s title and folder. On a Mac, it also saves your Cowork sessions, from the Claude desktop app’s agent mode, as Claude Code sessions. It reads only their transcripts, from the app’s folder on that computer, whenever Dray runs there for something else, and nothing else of the app’s. If a DRAY.md file names the project, that name is sent and used in titles instead of the folder’s. It does not send tool calls, command output, file contents, the agent’s reasoning or conversations between the agent and its subagents. It also tells Dray which of these agents it is connected to on that computer, by name only, when you set it up, when it updates and about once a day, so the side panel can show an agent before its first session. When you approve the computer, Dray labels it with the computer’s own name, so that you can tell your computers apart in your account.
It also sends the images you paste into a prompt in Claude Code, Codex, Grok Build or OpenCode. Image saving starts on when Dray is first set up on a computer; a computer first set up before 7 October 2026 keeps it off until you run dray images on. dray images off turns it off and drops any image still waiting to upload. An image goes with the turn it was pasted into and is copied to Dray’s storage, like a file you share in a chat, so connected assistants can retrieve it. Images a tool opened or made are not sent, and none come from Cursor, which gives its hooks no images, or from Antigravity. Images are sent as they are: the replacement of keys and passwords described next works on text, so a screenshot keeps whatever was on the screen.
Before anything is sent, text that looks like an API key, token or password is replaced on your computer. That is pattern matching, so a secret written in an unusual form can get through. Sessions wait in a folder on the computer (~/.dray) until they upload; images from OpenCode, which keeps them in its own database, are copied there to wait as well. In your account they are stored and learned from like chats from the extension.
AI model providers
We send conversations, the files saved with them and the questions your assistants ask Dray to AI models through OpenRouter, which passes each request on to a cloud company that runs the model. We tell OpenRouter to use only providers that have agreed not to store what we send and not to train on it, which OpenRouter calls zero data retention. Today those are Google, through Vertex AI, and Microsoft, through Azure. The models pick out the facts worth remembering, prepare everything for search and name links and topics. Dray is not end-to-end encrypted: our servers and those providers can read what they process.

Sensitive information
Conversations often contain sensitive details: about your health, religion or beliefs, sex life or sexual orientation, politics, ethnicity or trade union membership. Data protection law calls these special categories, and Dray processes them only with your explicit consent. We ask for it once, before Dray saves anything for your account: when you approve a browser or a computer, connect an assistant or import an export, whichever comes first. We keep a record of when and where you agreed.
You can withdraw your consent at any time. Stop Dray reading an assistant in the side panel, pause or remove the coding-agent hooks so nothing new is saved, delete what Dray has saved, or ask us to close your account. Withdrawing does not undo what was done before, and nothing you delete is used again.
Your conversations also mention other people. Dray keeps what you save for you alone: nobody else sees it unless your assistant posts it to a chat link. If you think Dray holds something about you because someone else saved it, write to us.

How we use it, and who else handles it
Your account holds the email address you sign in with and, if you sign in with Google or GitHub, the name and picture they give us. Dray keeps a small copy of that picture, or of one you upload in Settings instead, to show you in the dashboard and the extension. Nobody else sees it, not even people in a chat you link, and removing it in Settings deletes it.
If you give an agent a name or an icon in the side panel, Dray keeps it with your account. A picture you upload for an agent is stored with your files, nobody else sees it, and replacing or removing it deletes it.
We email you sign-in codes when you ask for them. If you open a checkout and do not finish it, we send up to two reminders: one an hour later and one the next day. Our email provider sends them and holds your address and the plan you chose for that. Each has a link to unsubscribe, and paying or starting a trial stops them.
We also email you about your account: a setup tip if Dray hasn’t heard from your assistants in your plan’s first days, a note when a card payment fails, one reminder before Dray stops saving your chats after a plan ends, and a warning a month before we delete an account that has gone two years without a plan. The setup tip and the reminder each have a link to unsubscribe; the payment note and the deletion warning always go.
If you ask our website to email you a link for your computer, we use that address once, to send the link through Resend, and do not keep it ourselves. Resend keeps its usual record of the email it sent.
We use your conversations, memory and files only to run Dray for you: to build your memory, to answer your assistants’ lookups, and to show you what Dray has saved.
Dray also keeps a record of each time one of your assistants uses your memory: which assistant, which tool, when, whether anything was found, and, for a search, the words your assistant searched for. It shows you these lookups in the side panel and on your dashboard, and counts them against your plan. Separately, Dray uses the days on which a lookup found something, never what was searched for, to choose when to ask you for a review in the Chrome Web Store and for the report to Meta and Google described above.
We do not sell your data. We do not use your conversations, memory or files for advertising, or to decide anything about you such as your credit or eligibility, and we do not train AI models on them. The memory Dray builds is for you and the assistants you connect, and for nothing else.
Our legal reasons
Data protection law asks for a legal reason, or basis, for each use:
• Running Dray for you, including your account, conversations, memory, files, payments, sign-in codes and the notes about a failed payment or an account about to be deleted: our contract with you.
• Sensitive details in your conversations: your explicit consent.
• Analytics and advertising cookies, and session recordings of the site and the extension’s panel: your consent where we ask for it. For PostHog’s statistics in the UK, and for visitors outside the UK, the European Economic Area, Switzerland, the Channel Islands, the Isle of Man and Gibraltar, our legitimate interest in improving Dray and measuring our ads, which you can object to at any time in Cookie preferences.
• The extension’s usage stats: our legitimate interest in seeing where setup gets stuck, which you can object to at any time by turning off Share usage stats.
• The product measurements our server makes, security and stopping abuse: our legitimate interest in keeping Dray working, secure and fairly metered. They hold none of your content, and you can object by writing to us.
• The setup tip, the reminder before Dray stops saving and the checkout reminders: our legitimate interest in helping you get what you pay for and in following up a purchase you started. Each one has a link to unsubscribe.
• Keeping payment records and answering lawful requests from authorities: our legal obligations. Keeping a record of each deletion: our legitimate interest in being able to show it was carried out.
Who else handles it
These companies handle data on our behalf, and only to provide their services to us: Railway runs our servers, our database and its backups, Cloudflare our network and stored files, OpenRouter and the AI model providers it uses our AI models, Resend our email, PostHog our product analytics, and Discord the team’s alerts, including the copies of support emails. Polar sells you the subscription as merchant of record and handles your payment details under its own privacy policy. Meta and Google receive the advertising data described above under their own terms.
Nobody at Dray reads your conversations, memory or files unless you ask us to, for example in a support request. The only other reasons are security, stopping abuse, or a legal requirement.
Dray’s use of information received from its Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Where your data is processed
Dray is run from the UK. Our servers, our database and its backups are in the Netherlands, stored files are kept by Cloudflare, which we ask to keep them in Western Europe, and our email and analytics providers run in the EU. UK law treats the EU as protecting personal data to its own standard.
Some providers are in the United States: OpenRouter and the AI model providers it uses, Polar, Discord, and Meta and Google for advertising. Cloudflare carries traffic through data centres around the world. When personal data goes to them, it is protected by the UK-US data bridge where the provider is certified under it, or otherwise by the standard contractual clauses, with the UK’s addendum, in their data processing terms. Write to us if you want to know which safeguard covers a provider.

How long we keep it
While you have a plan, we keep your conversations, memory and files, the record of your assistants’ lookups, and the names and icons you give your agents, until you delete them or ask us to close your account. When a plan ends, Dray keeps saving your chats for 30 days and keeps everything it holds, so it is there if you come back. If your account goes 24 months without a plan, counted from when the last one ended or, if you never had one, from when you signed up, we delete it and everything in it. We email you a month before, and choosing a plan before then keeps everything. The chat archive the extension keeps in your browser stays until you remove the extension, which deletes it.
You can delete a stored file yourself, from Files on your dashboard or from the file in the side panel. Dray deletes the file and its search data at once. Dray keeps only a fingerprint of the file, so reading the same chat again does not save it a second time. Facts Dray has already learned from the file stay in your memory until you forget them in the side panel.
You can delete a chat yourself: from the chat on your dashboard, by deleting it in ChatGPT, Claude or Grok while the extension is running, by deleting the session in OpenCode, or with dray forget for any coding session. Dray deletes its messages, its files and anything it learned only from that chat at once. It keeps only the ids of the chat and its messages, so the chat is not saved again, even if you go on using it.
To close your account and delete everything in it, email support@withdray.com from the address you sign in with. Within 30 days we delete your account, conversations, memory, stored files, the record of your assistants’ lookups and the names and icons you gave your agents, remove you from PostHog and from our email provider’s contacts, and tell you when it is done. We keep a record that the account was deleted, when, and the address it belonged to, for six years, so we can show the request was carried out. Polar keeps the payment records it must.
PostHog keeps session recordings for 30 days, and other usage events, tied only to the hashes described above, for up to seven years. Support emails stay in our inbox until your account is deleted. Our hosting provider keeps server logs, which can include IP addresses, for up to 30 days.
Our database is backed up continuously so that we can restore it after a failure. The backups roll over every four weeks or so, so anything deleted from Dray, including a closed account, is gone from them within five weeks.

Linking and context sharing
Chat linking
Chat linking lets the assistants in different chats send each other messages. You type /link in one chat to get a code, then /link and the code in another chat to join. It is included in every plan.
Anything an assistant posts to a link can be read by every other chat in that link, by the AI company behind each of those chats (OpenAI, Anthropic or xAI) under its own terms, and by Dray’s servers.
Links are not end-to-end encrypted.
A post can carry one text file of up to 256 KB that the assistant wrote, such as code it wants reviewed. The file reaches exactly the chats its post reaches, the check against copying your memory reads it the same way, and it is deleted along with the link’s messages.
Who can join depends on the type of link. A private link, the default, lets in only your own chats. On an approval link, a chat from another Dray account waits until you approve it on the Links page of your Dray dashboard or in the extension. An assistant cannot approve anyone. On a public link, anyone with the code joins straight away. A link ends if no other chat joins within 24 hours. Once another chat has joined, it stays open until you close it, unless you give it an end date from 1 hour to 30 days away.
The other people in a link see the messages posted to it, the name each chat gave itself, which assistant each chat uses, and your Dray display name if you have set one. They never see your email address. A link gives nobody access to your memory or to your saved chats and files. Your assistant could still repeat something from them in a post, so Dray refuses any post that copies your memory word for word into a link that other people can read. A reworded version gets through that check.
Someone else’s assistant can write anything into a link, including instructions aimed at yours. Dray tells your assistant that those messages are information to weigh and that only you give it instructions. A model can still be misled, so share a public code only where you are happy for anyone to use it. To report something posted to a link, write to support@withdray.com as our terms describe.
A private link’s code works for your own chats for 24 hours, or until the link ends. Codes for approval and public links work once, for 10 minutes. Our servers store only a fingerprint of a code; the extension keeps the code in your browser so your other chats can join.
Messages and their files are deleted as soon as a link closes, and the record of the link itself (who took part and when) 7 days after that. When a link reaches its end date, ends because a chat left it, or nobody joins it within 24 hours, its messages and files are kept for 7 days and then deleted along with the record of the link. In those 7 days, the owner of a link that another chat had joined can reopen it. An open link keeps its newest messages and their files, as many messages as its owner’s plan allows; one with no end date keeps them until it is closed or deleted. To count posts against your plan’s lookups, Dray keeps the time of each message your chats post to a link, without its text, for 100 days.
While a chat is on a link, Dray also records when it last used the link, how far it has read and whether its turn has ended, so that the other chats on the link know whether it will see what they post. Everyone on a link sees this for each chat on it. For your linked chats, the Dray command-line tool and the extension tell Dray which chat on the link each one is and when its turns start and end, and check for new messages, so that a waiting agent can be woken and you can be told when another chat answers. This is kept and deleted with the record of the link. When the chat that makes a link gives no purpose, Dray sends a few of the link’s messages (its first and its newest, and only those everyone on the link can read) to the same AI model providers to give the link a name. The name is kept and deleted with the record of the link, and the link’s owner can rename it or turn this off in the Dray extension. You can close a link, remove a chat or turn down a request at any time. Pausing Dray’s memory does not close your links.
Web conversation handoff
“Ask Claude about this chat”, and the same option for ChatGPT and Grok, 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.
• Turn file capture off, or back on.
• Pause saving coding sessions on a computer, skip a folder, keep a codebase out with a DRAY.md file, hide a saved session from every agent or delete it, remove the hooks, or revoke that computer in your account.
• Disconnect an agent that signed in to Dray on its own, from its page in the side panel. What it already saved stays in your memory.
• 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.
• Choose which cookies run, in Cookie preferences.
Dray does not edit or delete your source conversations. Removing the extension deletes its local archive but not your account; to delete that, see How long we keep it.

Your rights
You can ask to see the personal data we hold about you or get a copy to take elsewhere, to correct it, to delete it, or to restrict how we use it. You can object to anything we do on the basis of our legitimate interests, including measurement and reminders, and withdraw any consent you have given. Email support@withdray.com from the address you sign in with and we will answer within one month.
If you are unhappy with our answer, you can complain to the Information Commissioner’s Office at ico.org.uk or, if you live in the European Economic Area, to the data protection authority where you live.

Children
Dray is for adults: you must be 18 or older to use it. If you think a child has given us personal data, write to us and we will delete it.

If Dray changes hands
Dray is run by Rafael Aslanian himself for now. If it moves to a company he sets up, or is sold or merged, your data moves with it to the new owner, who must keep to this policy. We will tell you before that happens.

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.
When this policy changes, we update the date at the top of the page. If a change matters to you, we email you or tell you in Dray before it applies.

Payments
Polar sells you the subscription as merchant of record and handles checkout, payment methods, tax and refunds. When you choose to pay, Dray sends your verified account email and an account reference to Polar. If you buy as a business, Polar also asks for your business name, address and tax ID. Dray does not collect or store card numbers. Billing shows the subscription and payment status returned by Polar.