Privacy
Last updated 4 October 2026
Version 2.15, in effect from 4 October 2026. It replaces version 2.14 of 2 October 2026, which replaced version 2.13 of 2 October 2026, which replaced version 2.12 of 2 October 2026, which replaced version 2.11 of 1 October 2026, which replaced version 2.10 of 1 October 2026, which replaced version 2.9 of 29 September 2026, which replaced version 2.8 of 28 September 2026, which replaced version 2.7 of 27 September 2026, which replaced version 2.6 of the same day, which replaced version 2.5 of 26 September 2026, which replaced version 2.4 of 25 September 2026, which replaced version 2.3 of the same day, which replaced version 2.2 of 23 September 2026, which replaced version 2.1 of 19 September 2026, which replaced version 2.0 of 16 September 2026, which replaced the notice of 29 August 2026. What changed in 2.15: you can now tell the Mac app, or your coach, that you use an app across all your work, and we keep that app's name and your answer until you remove it in Settings. To decide when to offer this, the Mac app reads your answers from the last 30 days about which apps count for your work. With each message to the coach on the Mac, the app also sends a short record of what it did during your session today and the names and current values of its own settings, and we do not store either. What changed in 2.14: when the Mac app checks whether what is in front of you is part of your work, its answer now counts toward that session's score: time it read as part of the work counts as work, and time it was unsure about counts neither way. If it read one app as part of the work for ten minutes or more, it may ask you at the end of the session whether to count that app for that kind of work. The answer itself, the text and the title are still never stored. What changed in 2.13: during a session, when the app or browser tab in front of you has a title that says nothing about what is in it, such as just the app's name, "New Tab" or "Untitled", and the Mac app cannot tell from its own rules whether it is part of your work, it now reads up to 800 characters of the text in that window, including anything you typed there, and sends it with your commitment to the model that answers that one question. None of it is stored. It never reads password fields, mail or messaging apps, or private browser windows, and you can turn it off in Settings. What changed in 2.12: when your coach suggests where a piece of work happens, it is now sent the names of the apps and websites you have spent the most time in on your Mac over the last 30 days, never a window or page title, so it suggests tools you actually use. It is also told which tools you have taken out of a commitment before, so it stops suggesting them. What changed in 2.11: when you stop a commitment before finishing it, your Mac may ask once more the same day whether to pick it up again, and your phone may ask when you are away from the Mac. We keep that question for two days, log that it was sent, and keep whether your Mac had been used in the last two minutes. This version also describes the record of whether your Mac is open, which earlier versions left out. What changed in 2.10: on YouTube, Reddit and X, the Mac app now asks about the page in front of you during every session, not only one whose work can involve those sites. It asks about a search, a video, a thread, a post or a channel, never about the home page or a feed, and none of it is stored. What changed in 2.9: on YouTube, Reddit and X, during a session whose work can involve them, the Mac app now sends the one page in front of you to the model to ask whether it is part of your work: its title, the words you searched, and, only when those say too little, the first 600 characters of the page. None of it is stored. What changed in 2.8: the section on what was in front of you on your Mac now says that, during a session, the title of the browser tab in front of you is sent to the model when the Mac app cannot tell from its own rules whether that site is part of your work, and that we do not keep it. This check already ran before 2.8, and the notice did not say so. What changed in 2.7: the download link you can ask for on your phone is now emailed to you straight away, and the section on email says so and what we keep about the request. What changed in 2.6: the section on email now covers an email we send to a list, such as the launch announcement: what we keep about it (your address, when it was sent, and whether it was delivered, bounced or marked as spam), and that a link in it carries the campaign's name so we can count visits that came from it, never who clicked. What changed in 2.5: the section on email now says that the weekly recap and the note after your trial ends name the things you finished, so our email provider handles those names; that the first question comes two hours after you sign up, not a day; which trial notes you get and when; and how the stop link works. The list of other companies now says that Dodo Payments also receives the name on your account. What changed in 2.4: the section on your coach now says that on the Mac it makes the changes you ask it for, asking first before it replaces or removes anything you wrote and offering Undo for the rest, and what it can never do. What changed in 2.3: what you type or say to the coach card on the Mac, and the coach's replies, are now kept for 30 days so that a problem you report can be checked against what was actually asked, and the section on what you say to your coach says so. What changed in 2.2: Drifft now sends a few scheduled emails, keeps a record of which kind went when, and stores your timezone so they arrive at a sensible hour, and all three are described above; and your calendar is now read for times only, on every device and on every path, so the part of this notice that described event titles being sent with a question is gone because that no longer happens. What changed in 2.1: this website now counts what people do on it with our own records instead of only a third party's, and the section on this website says exactly what that means. Version 2.0 added where your data is stored, how long we keep each kind, what allows us to hold it, who else touches it, and every right you have, and corrected three things the old notice got wrong about what the Mac app records.
Drifft is an accountability app. It works by watching a narrow, specific thing: what is in front of you while you are working. We would rather be precise about that than vague, so this page lists it exactly. The short version: we never see your screen or your keystrokes, and we never keep what is in your documents or windows. During a session, a short stretch of the text in a window can be sent once to check it against your commitment, and the rule for when is below. We do see where your attention went, in detail, because that is what makes the app able to learn anything about how you work. Everything below is checkable against the app you installed.
Who we are. Drifft is run by Teghbir Singh, a sole trader in India. We decide what happens to your data, which makes us the controller under UK and EU law and the data fiduciary under India's Digital Personal Data Protection Act. You can reach a person at hello@drifftapp.com, and we will give you our postal address if you ask for it.
What Drifft never sees
This list is the important one, so it comes first. Drifft does not record the contents of your screen. There is no screenshot mechanism in the Mac app at all, and there could not be one without us shipping a new version and asking macOS for a permission we have never requested. It does not capture your keystrokes: it counts how long you typed and how many characters you added, and it never learns which keys those were. It never records what you type, and it never reads a password field.
The Mac app does read text in a window in a few narrow cases, and they are worth stating precisely. On a page it is about to cover, it reads that page here on your Mac to check whether it mentions the work you committed to, so it does not take your screen away from something that turns out to be the job. That check happens on your device, it answers a yes or a no, and nothing from it is saved, sent or kept.
Text from a window leaves your Mac in two cases, both during a session, both sent once to the model that checks it against your commitment, and neither stored: on YouTube, Reddit and X, the first 600 characters of a page whose title and search say too little; and, when the app or browser tab in front of you has a title that says nothing about what is in it, up to 800 characters of the text in that window, which can include what you typed there. Both are described in full under what was in front of you on your Mac, below.
What you type into Drifft itself, into a commitment or the brain dump, is a different thing entirely. You handed it over on purpose, it is listed below, and you can delete all of it.
What Drifft collects, and why
Each block below says what we collect, what we use it for, how long it stays, and what allows us to hold it in law.
Your account
What. An email address, or an Apple sign-in. If you use Sign in with Apple with Hide My Email, we only ever see the relay address. If you give a display name or a photo, we store those.
Why. So your work survives, and so one working session can span your Mac and your phone.
How long. Until you delete your account.
What allows it. Performance of our contract with you. Without an account there is no service.
What you commit to
What. The commitments you write: the result, your definition of done, your minimum, your first action, and the steps you mark finished.
Why. To hold the plan, sync it across your devices, and build your record.
How long. Until you delete your account. A commitment you did not get to leaves today's plan at the end of the day, and the record of it stays.
What allows it. Performance of our contract with you.
Questions about picking work back up
What. When you stop a commitment before finishing it, your Mac may ask once more later the same day whether to start it again, and your phone may ask when you are away from the Mac. For that we keep one row: which commitment, when to ask, how the question ended, and the words of the notification, which are your commitment's title and the step you stopped at.
Why. To ask that one question at a time that suits your calendar, on the device you are at, and never twice.
How long. Two days, then deleted.
What allows it. Performance of our contract with you.
Whether your Mac is open
What. One row for your Mac: when the Drifft app last checked in (every thirty seconds while it is open), its version, when it was last closed, the name of the session running on it if there is one, and whether the Mac had been used in the two minutes before it checked in. Nothing about what you were doing on it.
Why. So your phone knows whether a session can start on your Mac, and so a question about picking work back up goes to your phone only when you are away from the Mac.
How long. One row, replaced each time the app checks in, until you delete your account.
What allows it. Performance of our contract with you.
What you empty out of your head
What. If you use the brain dump, whatever you type into it, exactly as you typed it, plus which of it you chose to protect.
Why. To turn a rough list into two or three things you can actually finish today.
How long. The text is deleted the next time you use Drifft after the day it belongs to. One thing outlasts it: a lossy fingerprint of each line, which we cannot reverse into your words, kept so Drifft can notice when something keeps coming back and you keep setting it aside. That fingerprint is deleted when you delete your account.
What allows it. Performance of our contract with you.
What was in front of you on your Mac
What. While the Mac app is running and tracking is switched on, it records the name of the app you are in, the website host if you are in a browser, the name of the document or file or project you have open, the title of the window, how long you typed, how many characters you added, and how long you were idle.
This is the most detailed thing Drifft collects, so here are the three things a reader deserves in plain words. First, it is recorded while the Mac app is running and tracking is on, whether or not a session you started is live, so that Drifft can tell your work from something else and learn how you actually work. Second, the window title is written by your other apps and can hold more than an app name, so the Mac app reduces it before it is sent: in a browser we record the website host and never the page title, in a messaging or mail app we record only the app name, and everywhere else we record the window title with a length cap, which for an editor is the name of the document. So the record says youtube.com, never what you watched, and invoice-q3.pdf, never a word of what it says. Third, a private browsing window is not observed at all. Some things are sent rather than recorded. During a session, when the Mac app cannot tell from its own rules whether the site in front of you is part of your work, it sends the website host and the title of the browser tab, cut to 200 characters, with your commitment, to the model that answers that one question. It goes through our server to Anthropic, the same way as what you say to your coach, and we do not store the title or the answer. On YouTube, Reddit and X the question is about the one page in front of you, because those sites are sometimes the work and sometimes not. During a session, on a search, a video, a thread, a post or a channel there, the Mac app sends that page's title, the words you searched for and the search that led you there, and, only when those say too little to judge by, the first 600 characters of the page's own text. It never sends the home page or a feed, and we do not store any of it: not the words, not the page, not the answer. What we keep is the kind of page (a search, a video, a feed) and how the moment ended, never what was on it. When a window says nothing about itself. During a session, when the app or browser tab in front of you has a title that says nothing about what is in it, such as just the app's name, "New Tab" or "Untitled", and the Mac app cannot tell from its own rules whether it is part of your work, it reads up to 800 characters of the text in that window, the most recent it can see, including anything you typed there, and sends it once with your commitment to the model that answers that one question. It goes through our server to Anthropic in the same way, and we do not store it: not in the record above and not in our logs. It never reads a password field, a mail or messaging app, or a private browser window. It is text the app reads through the Accessibility permission, never a picture of your screen. You can turn it off in Settings in the Mac app, and the rest of the protection keeps working without it. What the answer is used for. When the Mac app checks whether what is in front of you is part of your work, its answer is used only during that session. It counts toward that session's score: time it read as part of the work counts as work, time it was unsure about counts neither way, and time it read as something else counts as time away from the work, as it always has. If it read one app as part of the work for ten minutes or more, the Mac app may ask you at the end of the session whether to count that app for that kind of work. What we keep is the score, and, if you answer that question, the app's name, the kind of work and your answer, so it is not asked again. The answer itself, the text and the title are never stored.
Why. So the Mac app can tell your work from something else while you are in a session, so the recap at the end can say where the time actually went, and so Drifft can learn how long you really focus and what tends to pull you away.
How long. 90 days, then it is deleted automatically every night.
What allows it. Performance of our contract with you for the part that runs your sessions, and your consent, given through the macOS Accessibility permission, for the reading itself. You can withdraw that consent at any time in the two ways below.
How to stop it. Open Settings in the Mac app and turn tracking off. Nothing more is recorded, on that Mac, from that moment. You can also remove the Accessibility permission in macOS System Settings, which has the same effect. Either one turns the protection off too, because the app cannot hold a line it cannot see.
Drifft for Mac 0.131.0 adds a second switch beside it, track only during sessions, which records nothing outside a session you started and leaves the protection on. Until you are on that version, tracking is on or off and there is nothing in between, and this page will say so for as long as that is true.
What was blocked on your iPhone
What. The time a shield was reached and which step of the ladder it was. That is all.
Because of how Apple's Screen Time system is built, we cannot see which apps you picked, and we never receive your Screen Time history. iOS hands the app opaque tokens, and the record that reaches us says only that a blocked app was reached. Apple's rules for that system also forbid us from using anything it gives us for advertising or for profiling, and we do not.
Why. So the ladder knows where it is, and so the record is honest about the day.
How long. Until you delete your account.
What allows it. Performance of our contract with you, and the Screen Time permission you granted.
Your sessions and how the work went
What. When a session started and ended, whether it was paused, whether you said you were stuck, how it concluded, the outcome you picked, how much of the session was spent on the work (in the tools the commitment expects, or in something the Mac app read as part of the work), and how often you came back.
Why. It is the record. It is also what the next commitment is sized from.
How long. Until you delete your account.
What allows it. Performance of our contract with you.
What Drifft learns from all of that
What. Your typical focus length for a kind of work, which times of day tend to hold, which apps and sites tend to pull you off, which apps you said count for a kind of work when the Mac app asked you, and which apps you told the Mac app or your coach you use for all your work.
Nothing here decides anything about you on its own. Drifft reads and proposes. Your tap is what goes on the record, every time, and you can change or ignore any of it. Nothing irreversible happens because a model suggested it. Apps you use for all your work. When you tell the Mac app, or your coach, that you use an app across all your work, we keep that app's name and your answer, and it is not treated as a distraction in any session until you remove it in the Mac app under Settings, Protection, Always allowed. If you say no, we keep that too, so you are not asked again. To decide when to offer this, the Mac app reads your answers from the last 30 days about which apps count for your work. Games, video and social apps cannot be allowed this way.
Why. It is the reason the app gets more useful over time.
How long. Until you delete your account.
What allows it. Performance of our contract with you.
What you say to your coach
What. The words you type or dictate to your coach, sent together with your commitments and your session state to the model that writes the reply, and, when it suggests where a piece of work happens, the names of the apps and websites you have spent the most time in on your Mac over the last 30 days (never a window or page title) and the tools you have taken out of a commitment before, and on the Mac the coach's replies to you. On the Mac, if you ask the coach about what you are doing right now, the title of the browser tab in front of you is sent with your question. If you ask about your day, the start and end times of today's events are sent with it, and never their titles. On the Mac, each message also carries a short record of what the app did during your session today and the names and current values of the app's own settings.
Where it goes. Through our own server to Anthropic, which runs the model. The key never sits on your device. Anthropic's terms say it may not train its models on what we send, and its published practice is to delete what it receives within 30 days. If a request is flagged by its safety systems it may be kept for up to two years, and the scores from that check for up to seven. What the coach is told about the app. With each message to the coach on the Mac, the app also sends a short record of what it did during your session today, for example that it paused the clock because your screen locked, put apps away, hid an app or showed you a catch card, with the names of the apps involved, and the names and current values of the app's own settings, for example whether the timer in the notch is on. This is sent so the coach can answer about what just happened and where a setting is. We do not store it.
Why. So the coach can answer about your actual work rather than in general.
How long. On the Mac, what you say to the coach card and its replies: 30 days, then deleted automatically every night. In the iPhone app's coach chat: with us, until you delete your account. You can turn the coach off in Settings and the whole app still works: starting, blocking, recovering and recording are all deterministic and never depend on it.
What allows it. Performance of our contract with you.
Proof you attach
What. On iPhone, links, notes, counts or photos you choose to add at the end of a session. Drifft never takes an image itself, on either device.
Why. So a finished session can carry something you decided to keep.
How long. Until you delete your account.
What allows it. Performance of our contract with you.
Your profile picture
What. If you add one, it is stored in your own account's private storage and shown on your devices. Nothing else can see it.
Why. So your own devices show you rather than a blank circle.
How long. Until you delete your account.
What allows it. Performance of our contract with you.
Diagnostics
What. A small event record saying which feature was opened, finished or failed, with the time and your account. No text you wrote.
Why. To tell whether something is broken.
How long. Until you delete your account.
What allows it. Our legitimate interest in knowing whether the app works, weighed against the fact that these records carry nothing you wrote.
Measurement
What. A record that you reached a step: first launch, signing up, your first commitment, your first session started, your first session finished, and each permission you grant. The name of the step, the time, and your account. No text you wrote, no app, no site, no window.
Why. To see where people get stuck between installing Drifft and finishing a first session.
How long. Until you delete your account.
What allows it. Our legitimate interest in knowing where the product loses people, weighed against the fact that these records are a step name and a time and carry nothing you wrote.
Which emails we have sent you
What. One row for each message the app sends you by itself: which kind it was (the day-one question, a trial reminder, the weekly recap, an invite, a question about picking work back up), which day it was for, whether it went by email or as a notification, the time, and the identifier our email provider gives it. No subject line, no body, no content of any kind.
It is what stops you being sent the same thing twice. The schedule runs every fifteen minutes (every five for a question about picking work back up) and this record is how it knows a message has already gone. Nothing here says whether you opened anything. We do not track opens. A link in a campaign email carries the campaign's name, so we can count visits that came from that email; it never says who clicked.
Why. So a scheduled message is sent once, and so we can tell whether the messages work at all.
How long. Until you delete your account.
What allows it. Performance of our contract with you for account and trial email, and our legitimate interest in not sending you the same message twice for the rest.
Campaign emails
What. For an email we send to a list, like the launch announcement: your address, when it was sent, the identifier our email provider gives it, and whether it was delivered, bounced or marked as spam.
Why. So nobody gets the same email twice, and so addresses that bounce can be removed.
How long. Until you ask us to remove it. It is kept by address, not by account, so deleting your Drifft account does not remove it: ask us and we will.
What allows it. Our legitimate interest in not sending you the same email twice and in keeping the list working.
A download link you asked for
What. Your address, when you asked, your country, the campaign tag in the link you followed if there was one, and whether the email was delivered, bounced or marked as spam.
Why. So the link is sent once, so the form cannot be used to send email to strangers, and so we can see whether it arrived.
How long. Until you ask us to remove it. It is not connected to your Drifft account, so deleting the account does not remove it: ask us and we will.
What allows it. Your request, and our legitimate interest in stopping misuse of the form.
What time it is where you are
What. Your timezone: its name, such as Europe/London, and how many minutes it is from UTC. Sent by the app you are signed in to. Not your location, not your city, not a coordinate.
A scheduled message has no way to ask. A notification meant for half past nine in the morning has to know whose morning, and a job running on a server has no request from you to read it from. Without it we would either send at the wrong hour or guess, and a guess here is the difference between a reminder and a message at three in the morning.
Why. So anything scheduled arrives at the right hour for you, and so a week or a day means your week or your day.
How long. Until you delete your account. It is overwritten whenever your device reports a different one.
What allows it. Performance of our contract with you.
What the models cost us
What. For each request to an AI model: the time, which model, how many tokens, and what it was billed at. No prompts. No commitment text. No message bodies.
When you delete your account we remove your name from these rows rather than deleting them, so the total cost of running the service stays accurate and the rows can no longer be connected to you.
Why. So we know what the service costs to run and can price it honestly.
How long. While we run the service. Rows still linked to an account go when the account does, by being unlinked.
What allows it. Our legitimate interest in running and pricing the service.
The Mac app, and the Accessibility permission
The Mac app asks for Accessibility access. That permission is what lets it read the title of the window in front, which is how it knows you are on a video site rather than in your editor, and how it knows which document you are working in. It is the same permission that makes the keyboard shortcut for the coach card work.
What it is deliberately not used for: there is no keyboard tap, no screen recording, and no file watching. It never types, never clicks, and never reads a password field. Inside a window it reads the title bar and the name of the open document; only on a page it is about to cover, that page's text for the yes or no check described above; and, during a session, when the title of the window in front says nothing about what is in it, up to 800 characters of that window's text for the check described above.
Blocking on the Mac is a full screen panel the app draws over the distraction. It is not enforced by macOS itself, so it is friction rather than a lock. On the card the way out is one instant tap. On the full screen panel you hold a button for a few seconds, and it opens that one site for ten minutes.
Your sign-in on the Mac is kept in the macOS keychain, not in a file we wrote. The app also keeps working files on your Mac, in your own Application Support folder, so it can pick up where it left off after a crash or a quit. They hold the session it was running, the setups you named and the addresses they open, and the app you were last in. They are readable only by you, they never sync, and they are not encrypted beyond whatever encryption your Mac applies to your own disk.
Your calendar and your tasks
If you connect it, Drifft reads the start and end times of today's events so it can tell how long a session fits before your next one. It is read only and today only. It never writes to your calendar, never creates anything on your behalf, and there is no screen in the app that shows you a merged list.
It reads times, never titles, on every device and on every path, including when you ask the coach a question about your day. What is sent with such a question is that you have something from 2:00 to 3:00, never what it is called, never who is in it, and never a note or a location attached to it. Nothing from your calendar is stored by us at all.
Apple Calendar and Reminders are read on your device. Todoist, on iPhone, is connected through its own OAuth flow using a read only scope, so write access is refused by Todoist itself rather than left to our good behaviour. You can disconnect any source at any time, and disconnecting deletes the connection we stored. Removing Drifft from the connected apps list in your Todoist account is what ends its access at their end.
What allows all of these: your consent, given through the permission you granted on your device or through Todoist's own sign-in screen. Withdraw it by removing the permission or disconnecting the source.
Email we send you
Besides your sign-in code, Drifft sends a small number of scheduled messages: a question two hours after you sign up if you have not run a session; if you use Drifft on a Mac, a note when your trial has two days left, one on its last day (the evening before, if it ends before noon) and one the day after; a note after three days without a session; a weekly recap of what you finished; the download link, straight away, if you ask for it on your phone; and an invite if you asked for one from the waitlist. Now and then we also send one email to a list, such as the launch announcement to the waitlist. That is the whole list, and you never get more than one of the scheduled ones on the same day. The scheduled ones are the same for everybody and a list email is the same for everyone on the list: nobody here watches your account and decides to write to you.
They come from hello@drifftapp.com and the reply-to is the same address, which a person reads. Replying is the intended way to tell us something, including to tell us to stop, or to turn an email you stopped back on. The weekly recap and the note after your trial ends name the things you finished, so those names pass through our email provider on their way to you.
The weekly recap and the three-day note carry a stop link at the foot. It opens a page with one button, and mail apps that show their own unsubscribe button beside the sender stop it in one click. No sign-in, no form, no reply needed. We record that one setting changed and nothing else, and the setting is read before every send. The messages about your account and your trial do not carry one, because they are part of the service you signed up for, and you can still reply and ask.
Talking to Drifft
On the Mac you can summon a card with a keyboard shortcut and say what you want. Speech is turned into text on your Mac, by macOS, without going to a server. If your language is not supported for on-device recognition, the app falls back to sending the audio to Deepgram to be transcribed, and it tells you so rather than doing it quietly. We do not keep the recording, and we send Deepgram the instruction that excludes it from their model training and from being kept to improve their service.
Drifft never listens unless you have summoned the card or pressed the microphone, and it never speaks back. There is no text to speech anywhere in the product.
What allows it: your consent, given through the microphone permission, which you can remove at any time.
Your coach is an AI
The coach is a model, and the app says so on the card at the start of every coach session. It sharpens what you wrote, proposes a cut, answers questions about your own work, and on the Mac makes the changes you ask it for. It acts only on what you ask: before it replaces or removes anything you wrote it asks you first, and anything else it changes comes with Undo. It can never turn protection off, sign you out, delete your account or touch your billing. Turn it off in Settings and every other part of the app carries on.
If you name a witness
You can name someone and send them a link. What they see is your first name, the commitment you named, one word for how it is going from a fixed list of eight, the clock, the outcome when you finish, and anything you chose to send them at the end.
Nothing beyond that list can reach them. The record their page reads has no field capable of holding an app, a website, a document, or anything you did. That is a limit built into the shape of the data, not a policy we promise to keep.
We never ask for their phone number and never store one. You send the invite yourself, from your own messages, and you can turn their link off at any time, which stops it working immediately.
What allows us to keep their name: our legitimate interest in providing the feature you asked for. It is one name, you supplied it, we never contact them, and it is deleted with your account.
Who else touches your data
These are the companies that handle your data so the product can work. We do not sell your data, and we do not share it with advertisers.
- Supabase. The database and the sign-in system. Everything we store, at rest, in India.
- Anthropic. What you send the coach, the context described above, and, during a session, what the Mac app sends to ask whether what is in front of you is part of your work.
- Deepgram. Audio, only on the speech fallback described above.
- Vercel. This website, and the form you fill in on it.
- Expo. The token your phone needs to receive a notification.
- Apple. Sign in with Apple, and delivery of notifications to your phone.
- Todoist. Only if you connect it, and only through its own read only permission.
- Resend. Your email address and the message we send you, so it can reach you. The weekly recap and the note after your trial ends include the names of the things you finished.
- ImprovMX. Email you send to our addresses, on its way to us.
- Dodo Payments. Only if you buy a plan. Your email, the name on your account, and your payment details, which they take directly. We never see or store a card.
Where your data is
Drifft stores your data on Supabase in India, in Mumbai. When you use the coach, what you send is processed by Anthropic in the United States. If speech has to be transcribed off your device, the audio goes to Deepgram in the United States. This website is served by Vercel from data centres around the world, and notifications are delivered through Apple and Expo in the United States.
If you are in the United Kingdom or the European Economic Area, this means your data is transferred outside that area. We rely on the European Commission's Standard Contractual Clauses, which these providers have agreed to, to carry the same level of protection with it. Ask us and we will tell you which applies to which.
If you buy a plan, the payment is taken by Dodo Payments as the merchant of record. They receive your email address, the name on your account and your payment details directly; we never see or store a card. Where they process it is not stated here, because unlike every provider above we have not verified it. Ask us and we will tell you what we know.
This website
If you join the waitlist we store your email address, which form you used, the site you arrived from, any campaign tag in the link you followed, your country, and a one way hash of your IP address for abuse prevention. The IP address itself is never stored. We use the address to email you about access, and for nothing else. Reply to any of those emails with "remove", or write to us, and we will delete it. Deleting your Drifft account does not remove a waitlist signup, because the two are not connected to each other, so ask us and we will do both.
This website uses Vercel Web Analytics to count visits. It uses no third party cookies and stores nothing on your device. It records the page, the site you came from, your country and your browser type, and it never records who you are. There is one cookie on this site and it is the sign-in for our own admin console, which no visitor ever meets.
We also keep our own count of what happens on this website, so we can tell which parts of the page people actually read. We record which page you are on, which step of the product tour you reached, which button you pressed, the host name of the site that sent you, any campaign tag in the link you followed, and your country. There is no cookie and nothing is stored on your device: each page load gets a random number that lives in your browser's memory and is gone when you close the tab, so a second visit is a separate count and the two cannot be joined. We do not store your IP address, hashed or otherwise, and we do not store your browser type. None of it is linked to an account, an email address or a name, and it cannot be. These records are deleted after 90 days by a job that runs every night.
What allows it: your consent for the email address, and our legitimate interest in preventing abuse and in knowing where people hear about us for the rest.
Your rights
Wherever you live, you can ask us for any of these and we will not ask you why. See it: get a copy of everything we hold about you. Take it with you: get it as files you can open and move somewhere else. Correct it: tell us anything wrong and we will fix it. Delete it: remove your account and everything under it. Restrict it, or object: ask us to stop using it a particular way, including anything we do on the basis of our legitimate interest. Withdraw consent: for anything you gave permission for, and as easily as you gave it.
How to do it. Deleting is in the app: open Settings on your Mac or your iPhone, go to your account, and choose Delete account. For a copy of your data, and for anything else on that list, email hello@drifftapp.com and we will send it to you. We answer every request within 30 days. A copy you can download yourself is being built, and until it ships, asking us is how you get one.
Deleting your account. It removes your account and everything stored under it: your commitments, your sessions, what was in front of you while tracking was on, what Drifft learned about how you work, anything you uploaded, and any witness links you made. It deletes from our servers first and only removes your sign-in once every table has come back clean, so you are never left signed out with data behind you. Deleting is final and there is no undo. Two things are not covered by it and both are named above: the cost record, which is kept with your name removed from it, and a waitlist signup, which you can ask us to delete in the same message.
There is a separate option on both devices that is not a deletion and is easy to mistake for one. On iPhone it is called Restart onboarding and on the Mac Start over on this Mac. It takes you through the first run again and keeps your account.
Giving us your data is not a legal requirement, and there is no contract that forces you to. But the app cannot do its job without most of it. Without an account nothing syncs. Without the Accessibility permission on your Mac, nothing is protected, because the app cannot hold a line it cannot see.
How old you have to be
Drifft is for adults. You must be 16 or older to use it, and 18 or older in India. We do not knowingly collect anything from a child. If you believe a child has an account, email us and we will delete it and everything stored under it.
Questions, or a complaint
Write to Teghbir Singh, who handles privacy questions and complaints for Drifft, at hello@drifftapp.com. We answer within 30 days. Telling us which device you were on and what you want done gets you a faster answer.
If we do not sort it out. In India you can complain to the Data Protection Board of India. In the United Kingdom or the European Economic Area you can complain to your national data protection authority, or to the Information Commissioner's Office in the United Kingdom. You do not have to come to us first.
When this changes
We will update this page when what we do changes, and the version and date at the top will say so. If a change is significant we will tell you in the app rather than quietly editing this page.