Privacy Policy

Drry is operated by Drry, Inc., a Delaware corporation, the controller of the personal data described in this policy. Drry is a platform that lets creators run a membership community: courses, a community feed, audio, and payments. When a creator (a "coach") runs their community on Drry, the coach is the controller of their members' community content, and we process it on their behalf as a service provider. That processing is covered by our Data Processing Agreement, which applies to every coach automatically.

Account data: your email address (we sign you in with a one-time code, there is no password) and the profile you set in a community (display name, username, bio, avatar, and any optional profile fields you choose to fill in).

Content you create: courses, lessons, posts, replies, audio, uploaded files and images, and the direct messages you send to other people in a community. When your browser resizes a large image before uploading it, embedded photo metadata (such as the location data phone cameras attach) is dropped in the process. That resize does not run on every image, so please do not rely on it to strip location data from a photo you would not want shared.

Payment data: when you subscribe or accept payments, Stripe processes the transaction. We store identifiers (customer and subscription ids, plan, status) but never your full card number.

Usage data: basic technical and activity data needed to operate and secure the service (for example, which lessons or audio you have played, to power resume and progress).

Live event data: when you watch a live session or webinar, we record when you joined and left, your approximate location (country, region and city, worked out from your connection, never a precise position), and the kind of device, browser and operating system you watched on. We do not store your IP address for this. It lets a coach see how their session performed, and it is what tells us how much a broadcast costs to deliver. If captions are turned on in a session, we keep, for that day, each signed-in speaker’s captioning allowance (what is left and when they were last captioned), to keep the feature from being abused. We do not keep the audio or the words.

To provide and maintain the service, authenticate you, deliver the content and features you use, process payments, keep the platform secure, and communicate with you about your account.

Communities you join may also email you. This can include transactional messages the service needs (such as sign-in codes and payment receipts), notifications about new content or replies to your posts, and promotional or marketing broadcasts the coach sends to their members. New-content emails and promotional emails are SEPARATE choices: you can turn either off on its own in your account settings, or with the unsubscribe link in any such email. Sign-in and account emails still arrive because the service needs them. A coach's marketing broadcasts may measure whether you opened the email or clicked its links, so the coach can see how their emails performed; turning the emails off stops this too.

We do not sell your personal data.

A community is run by its coach. When you join one, the coach (and any admins they appoint) can see your community profile, what you post there, your membership and payment status, and activity that helps them run the community, such as course progress and how recently you have visited. If you attend a live session or webinar, they also see attendance for that event, including a summary of which countries and device types the audience watched from. That summary is aggregate: it counts the audience, and does not show a coach where an individual attendee watched from. This is the same relationship as any membership site: Drry processes that data on the coach's behalf, and it stays within their community.

When a community has its own iPhone app, Apple's App Review team is given a demo account in that community, which stays available so Apple can review the app and each update to it. It sees the community's content as a member does. Anything it posts, reacts to, reports or sends stays in its own test space and is never shown to the community's members.

Messages between members are private, and a coach cannot browse them. There are three exceptions, and we would rather you know about all of them. First, if someone reports a message, the coach and their admins can read that message, plus a short run of the messages immediately before it, because a single line often cannot be judged on its own. Second, if the coach has turned on AI moderation, an automated classifier reads messages in that community as they are sent, and a message it flags goes to the same review queue even when nobody reported it. A flagged message is still delivered: screening never blocks or edits what you write. When either of those applies, we say so in the messages screen itself. We never show a coach a conversation nobody reported and nothing flagged.

Third, photographs sent in a direct message pass through our own automated safety screen, the same one that reads photos attached to a community post. This one is ours rather than a coach’s, so nobody can turn it off, and it is how we keep illegal imagery off the platform. It does not open a file that is not a photograph, it does not look at a profile picture, and it can miss a photograph that reached us in a form that does not identify it as one. It looks at the image, never at the words around it, and a coach is not shown anything by it. If it flags something, a person on our team can be asked to look. Where it finds child sexual abuse material we report it to the National Center for Missing & Exploited Children through its CyberTipline, as United States law requires of us, and we may pause the community and hold the content and account details while that is dealt with, rather than deleting them straight away. Nothing else at Drry reads your messages to run the product.

A few features send what people write or say to an artificial intelligence service. Each one is listed here, with who provides it and how it can be avoided.

Voice notes. Before your first voice note in a direct message, we ask whether your voice notes may be written out by an AI transcription service. If you allow it, each recording you send goes to Groq, our AI processor, which turns it into text shown under the voice note to everyone in the conversation. If you do not allow it, your voice notes still send, without the text, and your recordings are never sent to Groq. You can change your answer at any time in your account settings on the web, in the member app or in the coach app, and the change applies to the voice notes you send from then on. It is your voice, so only your own answer decides it, never the answer of the person you are writing to.

Meeting notes. When the host of a live session has meeting notes on, the session’s audio is transcribed by Cloudflare, which runs our live sessions, and the transcript is sent to Groq to write a summary of the session for its host. The session shows that it is being transcribed for as long as notes are on.

Live captions. Anyone in a live session or webinar can turn on captions. While at least one person has them on, short clips of what each speaker says are sent to Cloudflare, which runs our live sessions, and written out by an AI speech-to-text model running on Cloudflare’s network (Workers AI). The text is shown, with the speaker’s name, to everyone in the session who has captions on. To help with names, the model is also given the display names of the people speaking and the speaker’s last few words. Neither the audio nor the text is saved. A muted microphone is never captioned. Everyone in the session sees a notice when captions are on. Captions cannot be switched off for a whole session, because they are how people who are deaf or hard of hearing take part.

Moderation and safety. Where a coach has turned on AI moderation, posts, replies and direct messages in that community (including the text of voice notes that were written out) are screened by Groq, as described above under your direct messages. Separately, our own safety screen checks text and images across the platform with OpenAI, and checks published pages and emails with Groq, to keep prohibited content off Drry.

Groq, OpenAI and Cloudflare do not use what we send them for these features to train their models.

We use a small set of trusted processors to run Drry: Stripe (payments), Cloudflare R2 (media storage and delivery), Cloudflare RealtimeKit (live sessions, and the transcripts behind meeting notes), Cloudflare Workers AI (live captions, written out as people speak and not saved), Cloudflare Registrar (registration and DNS for domains bought through Drry, described below), Vercel (hosting and delivery of the application), PlanetScale (our Postgres database host), Sentry (error reports, which can carry technical context such as an organization or user id), Apple (push notifications to the Drry iPhone app, for members who allowed them), Amazon Web Services (all email we send, sign-in codes included: the messages a coach sends to their members, and the receipts and notifications that go with them; and calendar replies to event invitations), Groq (AI content moderation, where a coach has enabled it: this covers posts and replies, and also the text of direct messages in that community, which is why we tell you in the app when a coach has turned it on; and, on every community, the text, links and code of published pages and of emails, which we check in the background for phishing, malware, scams and spam; and, where a coach has switched on one of Auto-DM’s AI features, the text of an Instagram comment or message, to match it to the reply it asks for or to write the public reply posted under it; and the recordings of voice notes whose sender allowed them to be written out, and the transcripts of live sessions with meeting notes on, to write their summaries, as described under How we use AI), OpenAI (automated content-safety screening of text and images across the platform, to detect prohibited content; this one is ours rather than a coach’s, it runs everywhere including on images sent in a direct message, and it is not used to train their models), Anthropic (Claude, the AI model our team uses to build and maintain Drry, which can see account and community data while we do; no feature sends it your data on our behalf; an assistant you connect yourself is covered under Connecting an AI assistant), and Rewardful (partner-program referral tracking on our own marketing site). Each receives only the data needed for its function.

On our own marketing site only (described below), we also work with Google and Meta as processors for advertising measurement, so we can see how well our ads bring new coaches to Drry. They receive only the limited measurement data their tags collect on those pages, and never any data from the communities or sites we host for coaches.

If your community gets a domain through Drry, Drry is its registrant, so the public registration record names Drry, not you, and the registrar's privacy service hides the contact details on it. The same is true of a domain you ask us to move into our registrar account.

We keep the domain name, its registration and expiry dates, which account in your community bought it and when, and a record of any transfer, buyout payment and notice we send about it. The DNS records you add or edit are stored with Cloudflare, which runs the domain's DNS. When you ask for your transfer code, our support team sends it to the email address on your account at that moment. We keep the record of a domain's registration, transfers and any buyout after it leaves Drry, because it is the record of an agreement and, where you paid, of a payment.

If someone complains that a domain's name or use infringes their rights, registry and registrar rules can require us to tell them, or a dispute-resolution provider, who uses it. We share only what those rules require.

We use a session cookie to keep you signed in. This is essential to the service and is not used for advertising.

On Drry's own first-party pages on drry.com, which means our marketing pages, the coach sign-up and onboarding flow, and the coach sign-in, we load the Google Ads tag and the Meta (Facebook) pixel. These advertising and analytics cookies let us measure how our ads perform so we can reach and sign up new coaches.

Our marketing pages also set a first-party referral cookie (via Rewardful, our affiliate-program provider) when you arrive through a partner's link, so we can credit that partner if you later subscribe. It identifies the referring partner, not you, and is not used for advertising.

We do not place our own advertising trackers on the communities or sites we host for coaches. The member communities at a coach's Drry address, a coach's funnel and landing pages, and a coach's own custom (white-label) domain never load Drry's Google or Meta advertising tags. You still get ordinary first-party app analytics that keep the product working, such as presence and last-seen and basic product telemetry, but no third-party advertising cookies of ours.

A coach may connect their own advertising pixel. On the Growth plan a coach can add their own Meta, Google or TikTok pixel so that ads they buy can measure the visits those ads bring in. Where a coach has done that, those pixels load on that coach's public pages only: their funnel and landing pages, their bio link and shop, their public guides and event pages, and their join page. They do not load inside the community itself, so lessons, the community feed, direct messages and member profile pages carry no advertising pixels, and they never load in the coach console.

When a coach connects a pixel, that coach is the data controller for it and their own privacy notice governs it; the ad network receives the data under the coach's own agreement with it, not ours. If you are in the EU, the EEA or the UK we ask for your consent before any such pixel loads, and nothing loads unless you agree. You can change that decision at any time from the “Your Privacy Choices” link in the page footer, or the small privacy control on a coach's own pages, and we keep a record of the choice (the date, the version of the notice you saw, and a coarse country) so we can show it was offered. That record holds no IP address, no device fingerprint and no identity.

Where a coach has connected Meta or TikTok, some of this is sent from our servers rather than from your browser. When you buy from a coach or join their community, we tell that coach's ad network that the purchase happened, so the ads they paid for can be measured even where a browser blocks the tag. If that payment is later refunded, or reversed by your bank, we tell them that too, so the coach is not left counting a sale that came back. What goes with it is the amount, the currency, the kind of browser you used, the address of the page you were on when it happened, and, so the network can match it to the ad you clicked, a scrambled (hashed) version of your email address together with the click identifier the ad put in the link you followed. The page address is the plain address of a public page and nothing more: anything after the question mark is dropped before it is stored, so a search you typed or an identifier another site attached never travels with it. We do not send your email address itself, your name, your IP address, the name of what you bought, or anything you have written. Being plain about the hash: it is not the same as being anonymous. We cannot turn it back into your address, but the ad network can match it to an account they already hold, which is the entire reason it is sent. Treat it as a stand-in for your identity rather than as the absence of one. This happens only where the coach has connected that network and only where you have not declined tracking, including where your browser sends a Global Privacy Control signal on your behalf. We keep those delivery records for 90 days, which is long enough to send them and to show the coach whether they arrived, and then we delete them.

If you are a coach, you can choose to connect your Google Calendar so that Drry can see when you are already busy and avoid offering those times to people booking you, and so it can put a booked session on your calendar with a meeting link. Connecting is entirely optional, you start it yourself from your console, and you can disconnect at any time from the same place. When you disconnect we revoke our access with Google and delete the stored authorization.

Drry's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely, that means we use your Google Calendar data only to provide the scheduling features described above; we do not transfer it to others except as necessary to provide those features, for security purposes, or to comply with applicable law; we do not use it for advertising of any kind; and we do not use it to develop, improve, or train generalized artificial intelligence or machine learning models. No human at Drry reads your calendar except where you have explicitly asked us to for support, or where we are required to for security or to comply with the law.

We read only what the feature needs. To work out your availability we look at when your calendar is busy, not at the contents, titles, attendees, or notes of your other events, and we do not store those events. We never show your calendar to anyone booking you: they see only the times you have chosen to offer.

You choose which of your calendars count. To offer you that choice we read the names of the calendars in your Google account, and we store the name and identifier of each one you pick so your settings can show them. To keep your booking page quick we keep a short-lived copy of your busy times (when each busy period starts and ends, nothing else) and refresh it every few minutes; if Google cannot be reached we keep using the last copy for at most a day. The owners and admins of your community see those busy times as grey “Busy” blocks on its calendar in the Drry console, with no titles or details. When you turn this off we delete that copy of your busy times, and when you disconnect Google we also delete the list of calendars you picked.

If you host sessions on a community's team, you can connect your own Google Calendar for just those sessions. That connection asks only for who you are and when your calendar is busy: it cannot create meetings, add calendars, or see what your events are. Your busy times then keep the sessions you host off those times, and nobody else's. We keep the same short-lived copy of them described above, show them to no one, and when you disconnect we delete that copy and our access to your calendar.

You can also choose to have your Drry sessions added to your Google Calendar. We then create one new calendar in your Google account, named after your community, and keep your bookings and events on it up to date: each entry carries the session's title, time, place or meeting link, description and, for a booking, the name of the person who booked. We never invite anyone to these entries, so Google sends nobody an email about them. This permission only lets us manage the calendar we created; we cannot see or change any other calendar. When you turn this off, disconnect Google, hand your community to someone else, or delete your community, we delete that calendar from your Google account. If Google will not let us when you switch it off or disconnect (for example because you already removed our access in Google), we tell you, so you can delete it there yourself.

If you are a coach on an eligible plan, you can connect your Instagram professional account to Auto-DM. When somebody comments a keyword you chose on one of your posts or live videos, replies to your story, mentions you in their story, opens a link or QR code you shared, or sends you a message containing that keyword, Drry sends them one reply on your behalf with the link you picked. Connecting is optional, you start it yourself from your console through Instagram’s own login screen, and you can disconnect at any time from the same place or from your Instagram settings. We never ask for your Instagram password. When you disconnect, every automation stops and our access to your Instagram account ends.

What we receive from Instagram. We use Instagram’s official API, which Meta provides under its Platform Terms. About your account, we receive your Instagram account id, username and profile picture, your recent posts (so you can choose which one an automation watches), and an access token, which we store encrypted. About the people who interact with your account, when someone comments on one of your posts, replies to your story or messages you, Instagram sends us their Instagram-scoped id (a number that identifies them to your account and to no other), their username, the text of that comment or message, and a link to anything attached to it, such as a photo or a shared post. When someone mentions you in their story, we note that they did and never keep the story itself. When someone opens a link or QR code you shared, or messages you from one of your ads, Instagram tells us which link or ad it was, and an ad’s title. If you switch on the option to send the link only to people who follow you, we also ask Instagram whether they follow you, and only after they have tapped the button in your reply. When you reply to someone yourself from your Instagram app, Instagram tells us a message was sent; we note that it happened and who it went to, without its text, so your automations can step back from that conversation.

What we use it for, and what we never do with it. We use this data only to decide whether one of your automations should reply, to send that reply, to make sure nobody receives the same reply twice, and to show you how your automations performed. We do not sell it, use it for advertising, share it with any other coach, combine it into profiles of the people who commented, or use it to develop or train artificial intelligence models. No person at Drry reads these comments or messages except where you ask us to for support, or where we are required to for security or to comply with the law.

The AI features, only where you switch them on. Two Auto-DM features use AI, and each stays off until you switch it on for an automation. With Also match what people mean, a comment or message that matched none of your keywords is sent to Groq, our AI processor, together with the description you wrote, only so it can say whether the person is asking for what one of your automations offers. With Write each reply with AI, the comment and the public replies you wrote are sent to Groq so it can write the one public reply posted under that comment, and OpenAI screens that reply for harmful content before it is posted. We keep which automation answered, how sure the model was and the reply that was posted, never another copy of the comment, and neither Groq nor OpenAI uses any of it to train their models.

If you commented on, or messaged, a coach’s Instagram account that uses Auto-DM. The coach runs that account and decides what it sends, so the coach is responsible for that data and we process it on their behalf. We keep what Instagram sends us about your comment or message, including your username, its text and a link to anything attached to it, along with a record of what each automation did for you (whether a reply was sent, and whether you tapped it). We use that to show the coach how their automations performed and to make sure you are never sent the same reply twice. Where the coach has switched on one of Auto-DM’s AI features, the text of your comment or message is also sent to Groq, our AI processor, to match it to the right reply or to write the public reply under your comment; it is not used to train their models. You can send STOP to the coach’s account at any time and automatic messages stop; send START to turn them back on. You can ask us to delete your data at any time, as the next section describes. Deleting your data also deletes your STOP, so send STOP again if you come back. The same happens if the coach disconnects their Instagram account from Drry: your STOP, and any tag or pause the coach set for you, is deleted, so send STOP again if automatic messages start once more after they reconnect. The record of your comments and messages and of what was sent to you stays until you ask us to delete it. If you follow the link and fill in a form on the coach’s page, what you enter there is covered by the rest of this policy like any other form.

If you are a coach, disconnecting Instagram in your Drry console, or removing Drry from your Instagram account under Settings, then Apps and websites, stops your automations and ends our access to your account. To have the Instagram data we hold for your community deleted, send us a request with the form below, using the email address on your Drry account, or delete your community. If you remove Drry from Instagram and ask Instagram to delete your data, Instagram tells us, and we delete the Instagram data we hold for that account and give Instagram a confirmation code for the request. Email us with that code if you want us to confirm it was done.

If you interacted with a coach’s account and want what we hold about you deleted, send us a request with the form below, giving your Instagram username and, if you know it, the coach’s account.

How we handle a request. Before we delete anything, we reply by email to the address on the request to confirm that the request is yours, and we email you again when it is done. The form is also at teamdrry.com/f/instagram-data-deletion. If you would rather not use it, email hello@drry.com with the same details.

Where Auto-DM on Facebook is available to you, you can connect a Facebook Page you manage. When somebody comments a keyword you chose on one of the Page’s posts, opens a link you shared, or sends the Page a message on Messenger containing that keyword, Drry sends them a reply on Messenger on the Page’s behalf with the link you picked. Connecting is optional, you start it yourself from your console through Facebook’s own login screen, where you choose the Page, and you can disconnect at any time from the same place or from your Facebook settings. We never ask for your Facebook password.

What we receive from Facebook. We use Facebook’s official API, which Meta provides under its Platform Terms. About you, we receive your Facebook user id (so we know when you remove Drry from your account) and the permissions you granted. About the Page, its id, name and picture, its recent posts (so you can choose which one an automation watches), and a Page access token, which we store encrypted. About the people who interact with the Page, when someone comments on one of its posts or messages it, Facebook sends us their Page-scoped id (a number that identifies them to that Page and to no other), their name, the text of that comment or message, and a link to anything attached to it. When someone opens a link you shared, or messages the Page from one of your ads, Facebook tells us which link or ad it was. When you reply to someone yourself from the Page’s inbox, Facebook tells us a message was sent; we note that it happened and who it went to, without its text.

What we use it for, and what we never do with it. Exactly as for Instagram above: only to decide whether one of your automations should reply, to send that reply, to make sure nobody receives the same reply twice, and to show you how your automations performed. We do not sell it, use it for advertising, share it with any other coach, combine it into profiles of the people who wrote, or use it to develop or train artificial intelligence models. The AI features described above work the same way on a Page, and only where you switch them on.

If you commented on, or messaged, a Facebook Page that uses Auto-DM. The coach runs that Page and decides what it sends, so the coach is responsible for that data and we process it on their behalf, as described for Instagram above. You can send STOP to the Page on Messenger at any time and automatic messages stop; send START to turn them back on.

If you are a coach, disconnecting the Page in your Drry console, or removing Drry from your Facebook account under Settings, then Business integrations, stops your automations on that Page and ends our access to it. If you remove Drry from Facebook and ask Facebook to delete your data, Facebook tells us, and we delete the Facebook data we hold for the Pages you connected and give Facebook a confirmation code for the request. Email us with that code if you want us to confirm it was done.

If you interacted with a coach’s Page and want what we hold about you deleted, or you would rather ask us directly, email hello@drry.com with your name as Facebook shows it and the Page you wrote to. Before we delete anything, we reply to confirm that the request is yours, and we email you again when it is done.

If you are a coach, you can choose to connect an AI assistant (such as Claude or ChatGPT) to your community, so it can help you set things up and answer questions about the product. Connecting is entirely optional, you start it yourself, and nothing happens until you sign in and approve it on a consent screen that lists exactly what you are granting. You can disconnect at any time from Settings, and disconnecting takes effect immediately: every request an assistant makes re-checks that your permission still exists before it does anything.

What you send to the assistant goes to the company that runs it. That is the point of connecting one, and it is the part worth being clear about. When the assistant asks Drry for something, our answer is returned into your conversation with that assistant, and from that moment it is held by them under your agreement with them and their privacy policy, not ours. We are not a party to that conversation and we cannot see it. Connect an assistant you are willing to share your community’s working data with.

An assistant sees the shape of your community, not your members’ conversations. This is a deliberate limit in how the connector is built rather than a setting you have to find. It can read the TITLE of a post and the display name of whoever wrote it, together with counts like replies and likes, because a coach asking what their community is talking about is asking about their own community. It cannot read the BODY of a post or a reply: we do not offer it any way to ask for one. Direct messages are out entirely. So are form submissions, and so are your members’ email addresses, which no reading here returns. Where a member has reported something, an assistant is told how many reports are open and nothing more, deliberately, because a report can name a private message. Where automatic moderation has held a post, it sees the title, who wrote it and why it was held, so it can tell you there is something waiting.

What it can do is broad, and six things are held back. Rather than list every action, which would go out of date, here is the rule we build to: an assistant can do most of what you can do yourself in the console, so it can write and arrange your courses, lessons, guides, audio, pages, website, emails, forms, events and booking calendar, and change your settings and branding. It cannot move MONEY: no refunds, no charges, no payouts. It can make a payment link, because that is how you get paid, but making one charges nobody. Somebody has to open it and choose to pay. It cannot read PERSONAL DATA about the people who buy from you or belong to your community, beyond the display name and handle they chose for themselves: not their email address, not their address, not what they paid. It cannot reach your CREDENTIALS, or any door we are billed for by the minute, such as a live video room. And it cannot make a JUDGEMENT ABOUT A PERSON: approving or removing a held post, changing somebody’s role, or removing a member are yours, not its. It cannot DELETE YOUR WORK: it can unpublish a lesson so your members stop seeing it, but no action here destroys a course, a page, a guide or a lesson. The one thing it can delete is CONTACTS, and it is worth naming plainly: undoing an import removes every contact that import added, and the record of any journey email already sent to them goes with it. And it cannot UPLOAD FILES, so no photo or video reaches us through an assistant.

Content an assistant WRITES arrives as a draft your members cannot see, and publishing it is a separate act you ask for. Settings are different, and the difference is worth knowing: when it changes your branding, your page copy, your discussion rules or the names of your tabs, that is live to your members immediately, because those are edits to a community you already have rather than something new awaiting review. Three other things are immediate too: a payment link works the moment it exists, imported contacts join your audience straight away, and arming an automation starts mailing the people who match it on its own schedule.

Importing contacts is the one place personal data goes in. Those addresses belong to other people, so we ask the assistant to confirm you have permission to email them before anything is written, every address is screened the same way the upload form screens it (including against your own blocked list), and the whole batch can be undone in one step. Nothing in the connector can read a contact back out, so an assistant can add to that list and can never export it.

We keep a record of what an assistant did. For every request we log who made it, which assistant, which community, which action, and whether it was allowed or refused. We do not log the content of the request or the answer. That record has no expiry date and we keep it for as long as the account exists, because it is how you or we answer “what changed my community, and when” long after the conversation itself is gone. Deleting your account or your community deletes it along with everything else, and you can ask us for a copy or for its deletion at any time.

Our help documentation is also readable by an assistant without any connection or account at all. That surface reads published help articles and nothing else, and it involves no personal data in either direction.

We keep your data while your account is active and as needed to provide the service. You can request deletion at any time, and we remove data we are not required to retain for legal or accounting reasons. Three things work differently, and we would rather be plain about them than bury them. Messages you have sent are not on a deletion timer: a conversation stays until the account is deleted or the community is. When you delete your account we detach your name from the messages you sent, but we do not remove the text itself, because doing so would tear holes in the other person's copy of a conversation they also took part in. Photos and files you sent are a different matter and we do delete those: detaching a name does not make a photograph anonymous, so leaving them for the other person to open would let “no longer identifies you” cover something it cannot. That means a conversation you were part of may show that a photo was there and no longer is. You can also take back a message you sent, without deleting your account: it shows as deleted to both of you and anything attached to it is removed for good. The one time you cannot is while we have paused the community to look into a report, for the reason given below. And if an email to you hard-bounces or you mark our mail as spam, we keep your email address on a suppression list so we do not email it again, even after your account is deleted; we use it only to honor that opt-out.

If we have paused a community while we look into a report about it, account deletion is held until that finishes. We do this because the posts and messages in that community are the record we are reviewing, and deleting is the one step nobody can undo. It is a pause and not a refusal: it applies only while the review is open, and the moment the community is restored the delete button works again. If you are caught by this and want to know where things stand, email hello@drry.com.

There is a single exception to the paragraph above, and we would rather state it than let it sit behind “a pause, not a refusal”. If we report material to the National Center for Missing & Exploited Children, United States law obliges us to preserve that material and the related account records for at least 90 days from the report, and longer if we are asked to. In that narrow case a deletion request does not reach those records until the obligation ends, and the account is not restored. Nothing else on Drry works this way: for every other report, the review ends and so does the hold.

You can access, correct, or delete your personal data. Depending on where you live, you may have additional rights under laws like the GDPR or CCPA. To exercise any of these, email us.

Media is stored in a private bucket and served only through access-checked, short-lived links. Payments are handled by Stripe. No system is perfectly secure, but we take reasonable measures to protect your data.

We may update this policy as the product evolves; material changes will be reflected by the date above. Questions or requests? Email hello@drry.com.