Privacy Policy
Effective 11 November 2026.
This policy explains what personal data Draw Daily collects, why we collect it, and what you can do about it. It covers the website at drawdaily.app, the Draw Daily app for iPhone, the daily lesson email, accounts and Draw Daily Pro. For who publishes the site and where it is hosted, read the Legal Notice. For the rules of using it, read the Terms of Use.
Who we are
Draw Daily is published by DFRT Limited, a limited liability company incorporated in Hong Kong (Body Corporate). In this policy, "DFRT Limited", "we", "us" and "our" all mean that company, and "you" means the person using the site or the app, or receiving the email.
- Registered office: Unit 2A, 17/F, Glenealy Tower, No. 1 Glenealy, Central, Hong Kong.
- Hong Kong Business Registration Certificate Number: 78908767-000-10-25-1.
- Email: hello@drawdaily.app
We are the data controller for the personal data described here. We are a small operation and we have not appointed a data protection officer, because we are not required to have one. Email is the only way to reach us, and it goes to an inbox a person reads.
The short version
The newest lesson, the daily email, your streak and your badges are free, and there is a paid tier called Pro. If you read the site and take the daily email, what we hold is your email address, the date you signed up, when and where you asked for it if that was on or after 7 November 2026, and a record of which of our emails reached you and whether they were opened or clicked. Make an account, on the website or in the iOS app, and we also hold your practice history. Use the drawing feedback that comes with Pro, and we hold the photos you upload, in a private folder keyed to your account, and the feedback written about them. Pay for Pro on the website and Stripe takes the payment. Buy it in the app and Apple does, as the seller, while a service called RevenueCat tells us that you have it. Either way your card number never reaches us, and what we hold is which plan you are on, its status and when it renews. RevenueCat also gets your user identifier and device details from the app whenever you are signed in, whether or not you buy. Turn on the daily reminder in the app and we hold what it takes to send it: a push token, your phone's time zone and the time you picked. If you allow ad measurement on the website, we share the events and browser information described below with Meta. Every lesson email carries an unsubscribe link. The website and later versions of the iOS app ask before they add you to the daily email, and have a switch for it: on your practice page, and on the You tab. The first version of the app adds a new address when you sign in with an emailed code, and says so on the sign-in screen. Using the link or a switch stops the daily email, and we keep your address marked that way so that we do not ask again and signing in later does not put you back on the list.
What we collect, and when
1. Newsletter subscription
When you subscribe to the daily lesson, we store your email address, a signup timestamp, and when and where you asked for it: the former newsletter signup form, the website or the app. Addresses added before 7 November 2026, or by the first version of the app, have the timestamp alone. That is the whole record until you unsubscribe or we pause it (section 7 below explains pausing), and from then on it also notes the date and the reason. We do not ask for your name and we do not save your IP address next to it. Signing in does not put you on the daily list, and neither does paying for Pro. After you sign in with an address we have no record of, the website and later versions of the app ask whether you want the daily email, and send nothing unless you say yes. If you say no, we keep your address with the date and that answer, the same way we keep an unsubscribe. A switch on your practice page, and another on the You tab in later versions of the app, changes your answer whenever you like. The first version of the app does add a new address when you sign in with an emailed code, and says so on the sign-in screen, and before this version of the policy, signing in or paying for Pro on the website added one too. Signing in never overrides an unsubscribe or a no: once you have said either, signing in leaves you off the list, and only turning the daily-email switch back on puts you on it. The homepage email form starts account verification and onboarding; it does not subscribe you to the daily email.
The signup form does carry one hidden field, which only automated bots tend to fill in. If anything appears in it we drop the submission. It is a spam check rather than a way of learning something about you, and nothing typed into it is stored.
2. Accounts
An account is optional on the website and required in the iOS app. Sign-in is by emailed code: you type your email address, we send you a one-time code, and typing it in signs you in. The same email carries a link that does the same job on the website. Both work once and expire after an hour. Ordinary accounts have no password, so there is none for us to lose. What we hold is your email address plus the standard authentication metadata our auth provider creates: a user identifier, creation and update timestamps, the time you last signed in, and a record of each signed-in session with the IP address and device details (the user agent) it came from. Those session records exist so that sign-in works and misuse can be spotted. We do not use them to work out where you are, or for marketing. Asking for a code creates the account record straight away, before the code is typed in, so an address that never finishes signing in still leaves one behind. Email us and we will remove it.
The app also offers sign-in with a password. It is there for the few accounts we have set a password on ourselves, and nothing on the website or in the app lets you add one to an ordinary account. Where a password does exist, our auth provider stores it as a one-way hash, never as text anyone could read back.
If you answer the onboarding questions, on the website or in the app, we keep the answers with your account: the name you would like us to use, if you give one, your skill level and your goal, along with the time you finished onboarding.
3. Lesson completions
If you are signed in and you press "mark as complete" on a lesson, or get a drawing graded in the app, we store four things: your user identifier, the lesson identifier, the time you marked it, and the time on your device when you did, so that a streak follows your own day. The first version of the app does not send that last one. Those records draw the streak counter, the completion heatmap, and the day-of-week and time-of-day charts on your account page, and the streak in the app, and they decide which badges you have earned. A badge you unlock is stored with when and how you earned it. Nothing else about pressing that button is recorded. Sending us a drawing is a separate thing you choose to do, and the next section covers it.
4. Drawings you upload for feedback
With Pro, you can photograph a drawing and ask for written feedback on it. It runs when you are signed in and you take or pick a photo, and at no other time. Sending a photo is your agreement to what this section describes, including the photo going to OpenAI. On the website and in later versions of the iOS app, the line beside the upload buttons says it goes to OpenAI and links here. The first version of the iOS app instead asks once, on a screen of its own, and lets you withdraw that answer on the You tab. Nothing is sent until you take or pick a photo. Skip all of it and nothing in this section applies to you.
On the website, your browser shrinks the photo to a JPEG no larger than 1024 pixels on its longest side and sends that to our server. The iOS app shrinks the photo you took or picked to the same size on your phone before sending it. We store the image in a private storage bucket, in a folder named after your account identifier. The bucket is not public, so the file has no public address at all. Later versions of the iOS app show you your own photos through a link only your account can ask for, which stops working after an hour. Anybody holding that link could open it until then, and the app neither shows nor shares it. We then send the image to OpenAI, which runs a vision model over it and returns the notes you see on screen. Alongside it we keep a record of the request: your user identifier, the lesson identifier, where the file is stored, the feedback text and the score out of 100 that comes with it, a short description the model writes of what the photo shows, the name of the model that wrote it, and the time. The photo is stored and sent before anybody knows what is in it. One that the model turns away as not a drawing of the exercise is deleted from our storage as soon as the answer comes back, along with the notes on it, and only the bare record described under "How long we keep it" stays with us. If that deletion ever fails, the delete link stays under the result, and after that you can email us.
The image is the only thing about you that OpenAI receives. It travels with the text of the lesson you were following, not with your email address, your name or your account identifier. OpenAI's terms for their API say content sent through it is not used to train their models. They do keep a copy in their own abuse-monitoring logs for up to 30 days, and if their automated scan flags an image as illegal content their staff can look at it and keep it for longer. Those are their rules rather than ours.
A photo of a drawing usually catches a bit of the room it was made in: a corner of the desk, a hand, whatever else was on the table. Frame it however you like, but whatever is in the shot comes with it. Please do not photograph other people.
There is a ceiling of twenty feedback requests per Pro account per rolling 24 hours, which we may change. Each one costs us money, so it needs a limit. A request that fails counts against it too, because the failure costs us the same call.
To erase an upload, use the delete link that sits under the feedback while it is on screen, on the website or in the app. Later versions of the iOS app also have it on the lesson page, whenever you come back. That wipes the image and the notes together. Otherwise, once you have navigated away, email hello@drawdaily.app and we will do it for you. What survives either way is set out under "How long we keep it" below.
5. Pro subscriptions and payments
If you pay for Pro on the website, Stripe takes the payment. Your card details go to Stripe and never reach us. What we hold is which plan you are on, its status, when the trial ends and when it renews, whether it is set to cancel, whether you have paid at least once, and the identifiers Stripe uses for your customer and subscription records.
If you buy Pro in the iOS app, Apple sells it to you. Apple is the merchant of record: it takes the payment and handles that purchase under its own terms and privacy policy, and we never see your card or your Apple Account details. We use a service called RevenueCat to confirm the purchase with Apple and keep track of the subscription. It knows you by your Draw Daily user identifier, which the app gives it as your customer ID, and never by your email address. The app connects to it for everybody who is signed in, because that is how it finds out whether you have Pro, so RevenueCat holds a record with your user identifier and device details even if you never buy anything. When you do buy, your user identifier also goes to Apple with the transaction. What we keep from RevenueCat is the state of the subscription: which plan, whether it is in its free trial, when it expires or renews, whether auto-renewal has been switched off, whether Apple has reported a billing problem, and whether it was a test purchase made in Apple's sandbox.
6. The daily reminder in the iOS app
The app can remind you each day at a time you choose. It stays off until you turn it on, and iOS asks your permission before any notification can appear. When you turn it on, the app registers the phone with our server, and we store, against your account, the push token Apple issues for the app on that phone, the phone's time zone, the reminder time you picked, whether the reminder is on, and the date we last sent one, so that nobody gets two in a day. The same record notes technical details: the platform, which of Apple's push services the token belongs to, and the last error Apple gave for it, if any. The token reaches that one app on that one phone and nothing else. Before sending, we check whether you have already drawn the day's lesson, and stay quiet if you have.
The reminder travels through Apple's push notification service, which receives the token and the text of the notification. The text names the day's lesson and says nothing about you. If our server cannot send pushes, the phone schedules the reminder itself as a local notification, which does not go through Apple's service at all.
7. Whether our emails arrive and get read
Our email provider tells us what happens to each email we send: whether it was delivered, whether it was opened, and which link was clicked. Opens are noticed through a tiny image in the email, and clicks because links pass through links.drawdaily.app on their way to the page. We store the address, the kind of event, the email's subject line, the time, and for a click the page the link pointed to, with any sign-in or unsubscribe token stripped out. We do not store the IP address or the device details that come with an open or a click.
We use these records to see whether the daily email is worth sending, and we may pause it for an address that has shown no sign of reading it for a long time. A paused address keeps its row, with the date and the reason, and gets no more daily emails until you turn on the daily-email switch, on your practice page or on the You tab in later versions of the app. Opens are a shaky signal, because some mail apps block the image and Apple Mail loads it whether or not anyone looked, so we go mostly by clicks.
8. IP address
To stop automated signup abuse, we limit each IP address to three signups every ten minutes. For this the address sits in the memory of the server handling the request for the length of that ten-minute window, and it goes when the server instance recycles. It is not written to our database for this purpose or linked to your subscription, although a signup that hits the limit does put the address in the short-lived server logs described below.
Your IP address is recorded in two other places. Our auth provider stores it with each signed-in session, as section 2 says, and it appears in the logs described in section 9.
9. Server request logs
Our hosting provider keeps short-lived request logs for the site and its serverless functions, the way any web host does. Supabase, which runs our database and sign-in, keeps logs of the calls made to it, including those the app makes directly, with the IP address, approximate city, device details and user identifier, and its sign-in logs hold the email address. Our own functions also write log lines for events such as a feedback score, a badge, a subscription change or a deletion, which carry your user identifier. We look at all of these to investigate errors and abuse, and for nothing else.
That is the complete list. Most of it comes from you directly, and the rest is what the providers listed below report back about something you did, such as Apple confirming a purchase or our email provider confirming a delivery. We do not buy personal data, and nobody outside that list supplies any to us.
Handing any of it over is voluntary. You can read the newest lesson on the website without telling us anything at all. Without an email address we cannot send you the daily lesson. Without an account we cannot keep a streak for you or sell you Pro, and the iOS app cannot be used at all, because it needs one.
Why we use it, and our legal basis
Where the EU GDPR or the UK GDPR applies to you, these are the legal bases we rely on.
| What we do | Data used | Legal basis |
|---|---|---|
| Send you the welcome email and the daily lesson email | Email address, signup timestamp, when and where you asked for it | Your consent (Article 6(1)(a)), given when you say yes to the daily-email question or turn on its switch, on the website or in the app. The former newsletter signup form also recorded consent; the homepage account signup now asks for this separately during onboarding. Before this version of the policy, signing in by email or paying for Pro on the website counted as well, and signing in with the first version of the app still does. You can withdraw it at any time, with the unsubscribe link in any email or either switch. |
| Remember that you unsubscribed or said no, so that we do not ask again and signing in later does not start the daily email | Email address, the dates you signed up and unsubscribed, when and where you had asked for the email where we have that, or the date you said no | Our legitimate interest in honouring your choice (Article 6(1)(f)) |
| Create your account and send sign-in codes | Email address, authentication metadata, your onboarding answers | Performance of a contract, since the account is the service you asked for (Article 6(1)(b)) |
| Show your streaks, badges, heatmap and practice charts | User identifier, lesson identifier, completion timestamp, the time on your device when you finished, so that a streak follows your own day, and for the score badges and your score chart the scores on your feedback, their dates and the lesson's subject | Performance of a contract (Article 6(1)(b)) |
| Write AI feedback on a drawing you upload, and show it to you | The image, your user identifier, the lesson identifier, the feedback text, the model name | Performance of a contract, since the feedback is the thing you asked for by uploading (Article 6(1)(b)) |
| Keep a minimal record that a feedback request happened, after you erase the upload or a photo is turned away | User identifier, lesson identifier, model name, timestamp, score | Our legitimate interest in enforcing the daily limit, which keeps what the feature costs us under control (Article 6(1)(f)) |
| Sell you Pro and give you what it includes, on the website or in the app | Your user identifier, plan, subscription status and dates, Stripe customer and subscription identifiers, App Store subscription status from RevenueCat | Performance of a contract, since Pro is what you bought (Article 6(1)(b)) |
| Find out whether somebody signed in to the iOS app has Pro | Your user identifier and the device and app details sent to RevenueCat | Our legitimate interest in giving people what they have paid for, and only that (Article 6(1)(f)) |
| Send the daily reminder in the iOS app | Push token, time zone, reminder time, date of the last reminder, whether you have drawn that day's lesson | Performance of a contract, since you turned the reminder on and can turn it off at any time (Article 6(1)(b)) |
| Record whether our emails are delivered, opened and clicked, and pause the daily email for addresses that never read it | Email address, event type, email subject, time, the page a clicked link pointed to | Our legitimate interest in knowing whether our emails arrive and are any use, and in not sending mail nobody reads (Article 6(1)(f)) |
| Rate-limit signups | IP address, in memory only | Our legitimate interest in keeping the signup form from being abused by bots (Article 6(1)(f)) |
| Keep the site running, fix errors, deal with abuse | Server request logs | Our legitimate interest in a working, secure service (Article 6(1)(f)) |
| Measure the results of our Facebook and Instagram ads on the website | Ad click and browser identifiers, IP address, browser details, page path, event type and time. An immediate checkout payment also includes its amount and currency. | Your consent (Article 6(1)(a)). You can withdraw it in the ad measurement section below. |
| Count page views in aggregate | Analytics data that does not identify you | Our legitimate interest in knowing which lessons and guides people read (Article 6(1)(f)) |
How we use your practice history
We do not make automated decisions about you that produce legal effects or anything similarly significant, and we use your practice history to provide your drawing feedback. The streak counter, the badges, the heatmap and the charts on your account page and in the app are worked out from records you created yourself, by pressing "mark as complete" or by uploading a drawing. They are shown to you and to nobody else. The feedback on an uploaded drawing is written by a machine and nobody here reads it before you do, but it has no legal effect and nothing similar: it is an opinion about a sketch, with a score out of 100, produced when you ask for one. Apart from a badge when the score is high and a point on your own score chart, it changes nothing about your account, and we do not use it to rank or profile you.
What goes to the AI provider
The lesson text on Draw Daily is generated by an AI model (OpenAI GPT-6 Luna) and the reference sketch images are generated by an AI image model (OpenAI GPT-Image-2.6 Flare). Neither of those involves you. The generation prompt contains lesson parameters (level, skill focus, duration, difficulty) and a list of drawing subjects already used, so the model avoids repeating itself. Your email address, your account and your completion history are not part of it and never leave our own systems for this purpose.
One thing of yours does go to OpenAI: a drawing you upload for feedback, at the moment you upload it. The image is sent with the text of the lesson it belongs to and nothing else, so no email address, no name and no account identifier travel with it. The section on drawings you upload says what happens to it once it is there. Our Terms of Use says more about how the lessons and the feedback are made, and how much to trust either.
Who processes data on our behalf
| Provider | What they do for us | Where processing happens |
|---|---|---|
| Stripe | Takes Pro payments on the website and holds the card details, which never pass through our servers. A checkout also passes it your user identifier and any name, skill level and goal you gave in onboarding. | United States and the European Union |
| Apple | Sells Pro in the iOS app as the merchant of record, takes the payment and handles refunds, under its own privacy policy. Also delivers the daily reminder through its push notification service (APNs), which receives the push token for the app on your phone and the text of the reminder. | Apple's own systems, in the United States and elsewhere |
| RevenueCat | Manages App Store subscriptions for the iOS app: checks purchases with Apple and tells us whether you have Pro. Receives, for everybody signed in to the app, your Draw Daily user identifier, which it uses as your customer ID, any App Store purchase and subscription history, and the device and app details its software sends with each request: the device model, the iOS and app versions, your language settings, your App Store country, and the identifier iOS gives our apps on your phone (not the advertising identifier). It does not receive your email address. | United States |
| Supabase | Database, file storage for the reference images and for drawings people upload, and authentication, including the session records and logs described above | European Union (Ireland, eu-west-1) |
| Vercel | Website hosting, serverless functions, privacy-friendly analytics | United States, served from a global edge network |
| Resend | Sends the daily lesson email, the welcome email, sign-in codes and billing notices for website subscriptions, delivered over Amazon SES infrastructure, and reports back whether each one was delivered, opened or clicked. It keeps its own log of those events, which can include a sign-in link somebody clicked. | United States |
| ImprovMX | Forwards inbound mail sent to hello@drawdaily.app | Outside Hong Kong, so we treat it as an international transfer |
| Gmail holds the mailbox that receives replies to our emails, so it receives whatever you write to us and your address | United States and elsewhere | |
| OpenAI | Generates the lesson text and the reference images, and writes the feedback on drawings you upload | United States. Receives nothing about you except a drawing you upload, which they keep in their abuse-monitoring logs for up to 30 days. |
These providers act on our instructions and may not use your data for their own purposes. Apple is the exception when you buy Pro in the app: it sells the subscription to you directly, as the merchant of record, so that purchase is handled under Apple's privacy policy rather than ours. Each provider in the table, Apple included, protects the data it receives from us at least as well as this policy does: Apple under its own privacy policy, the rest because their data protection terms with us require it. We also share data with Meta when you allow website ad measurement, as described below. We may disclose data in response to a valid legal order.
International transfers
We are in Hong Kong, our database is in the European Union, and several of our providers process data in the United States. If you are in the EEA or the UK, that means your data is transferred outside your region. Where it is, we rely on the data protection terms each provider offers, including the standard contractual clauses where they apply. For most people the scope is small: an email address and the record of emails sent to it, and for account holders a list of completion timestamps. If you use the iOS app, RevenueCat handles an App Store subscription in the United States, and Apple carries the daily reminder through its own systems. A drawing you upload travels further than that. The serverless function that receives it runs in the United States, the file is then stored in our European database, and the image goes to OpenAI in the United States for the feedback to be written. OpenAI keeps a copy in their abuse-monitoring logs for up to 30 days afterwards.
How long we keep it
- Subscriber record: kept until you delete your account or ask us to remove it. Every lesson email carries a working unsubscribe link, and unsubscribing, or turning off the switch on your practice page or the You tab in later versions of the app, stops the daily email straight away. It does not delete the row: we keep your address, with the dates you signed up and unsubscribed and, where we have it, when and where you had asked for the email, so that we can show what you chose, do not ask you again, and signing in later cannot put you back on the list. We use it for nothing else. A row we have paused is kept the same way, and so is a no to the question.
- Records of emails delivered, opened and clicked: kept until you delete your account or ask us to delete them. Unsubscribing does not delete them by itself.
- Account and authentication data: until you delete the account, which you can do yourself from your practice page or the You tab in the app, without asking us. It removes the account, your onboarding answers, your history and badges, every drawing you uploaded and the feedback on it, your reminder details and our copy of your subscription status, and it takes you off the mailing list and deletes the records of emails we sent you. It happens immediately and we cannot reverse it. If you would rather we did it, hello@drawdaily.app still works.
- Lesson completions: deleted automatically with the account they belong to.
- Drawings you upload, and the feedback on them: kept until you erase them or we delete your account. Erasing removes the image file from storage and wipes the feedback text. There is no fixed expiry, so an upload you leave alone stays. The exception is a photo turned away as not a drawing of the exercise, which is deleted from our storage as soon as the answer comes back.
- The bare fact that a request happened: your user identifier, the lesson identifier, the model that was asked, a timestamp and the score the feedback gave survive that erasure, with no image and no words attached. So does a badge that score earned, which notes the score and the lesson's subject. We are not being coy about why. The daily limit is counted from those rows, so if erasing them reset the count the limit would be trivial to sidestep. They go when the account goes.
- Pro subscription records: our copy of your plan and its status goes when your account goes. Stripe and Apple keep their own records of what was paid, under their own retention rules. Deleting your account also tells RevenueCat to delete your customer record and any App Store purchase history it holds for us.
- Reminder details: kept until something removes them. Signing out of the app deletes them, provided the phone can reach us at the time, deleting your account deletes them, and we delete them ourselves if Apple refuses a reminder because the app is no longer on that phone. Turning the reminder off only switches it off. So if you delete the app without signing out while we are not sending that phone pushes (the reminder is off, or it runs as a local notification), they stay until you delete your account or ask us to remove them.
- IP address used for rate-limiting: held in server memory for the ten-minute window.
- Session records, with IP address and device details: kept until you sign out of that session or delete your account. There is no fixed expiry.
- Server logs: kept briefly by our hosting and database providers under their standard retention, then discarded.
Your place on the mailing list and your account are separate records. Unsubscribing stops the daily emails but does not delete an account you created, and signing in afterwards does not undo it. Turning the daily-email switch back on puts you back on the list. Deleting your account removes both, the record of your unsubscribe included, and so does asking us to erase that record. After that nothing remembers the unsubscribe, so if the same address signs in again later, it is treated like any new one: asked whether it wants the daily email, or on the first version of the app added as described above.
Cookies and similar technologies
If you sign in on the website, an authentication session token is stored in your browser so you stay signed in between visits. It is strictly necessary for the account feature to work. The site also keeps a draft of your answers while you go through the onboarding questions, which is cleared when you finish.
The iOS app keeps the same kind of session in its own storage on your phone, along with your reminder setting, a note that you have finished onboarding and, if you used the first version of the app, a note that you agreed to send drawings to OpenAI. RevenueCat's software keeps a copy of your subscription status there too, so the app can tell you have Pro without asking each time. The app has no advertising software and does not track you across other companies' apps or websites.
On the website we also use Vercel Web Analytics to see how many people read which pages. It is privacy-friendly by design: it produces aggregate page-view figures and does not use cookies to follow individuals from site to site.
Our emails work differently, as section 7 above explains: they contain a tracking image, and their links pass through links.drawdaily.app, which is how we know that an email was opened or a link clicked. A mail app set to block remote images stops the first.
Optional website ad measurement
If you choose Allow, Draw Daily sends Meta the public page you visited and when, whether you requested an account sign-in code from the homepage, opened a Pro checkout, or returned from Stripe after starting a trial or paying. For a payment at checkout we include the amount and currency. Meta receives your IP address, browser details, a random browser identifier and, if you arrived through a Meta ad, the ad click identifier. Meta uses this information to match activity to ads, report results and improve ad delivery. Its processing can take place in the United States and elsewhere. See Meta’s privacy policy.
Your browser remembers your choice for 90 days. If you allow measurement, it also keeps the browser and click identifiers for up to 90 days and a checkout receipt for up to one day. Declining or withdrawing stops future events from this browser. We honour Global Privacy Control. Your account, lessons and email preferences work with either choice.
Your rights under the GDPR and UK GDPR
If you are in the EEA or the UK, you have the right to:
- ask for access to the personal data we hold about you, and a copy of it;
- have inaccurate data corrected;
- have your data erased;
- ask us to restrict how we use it;
- receive your data in a portable, machine-readable form;
- object to processing we base on legitimate interests, and to direct marketing at any time;
- withdraw consent for the daily email or website ad measurement at any time, which does not affect anything we sent before you withdrew it;
- complain to a data protection supervisory authority.
To use any of these rights, email hello@drawdaily.app, ideally from the address you signed up with so we can match the record. It costs nothing and we will reply within one month.
Your rights under the Hong Kong PDPO
DFRT Limited is incorporated in Hong Kong, so the Personal Data (Privacy) Ordinance applies to us too. Under it you may make a data access request, asking whether we hold personal data about you and for a copy of it, and a data correction request, asking us to correct data that is wrong. Send either to hello@drawdaily.app and we will respond within the statutory period of 40 days. The Ordinance lets a data user charge a fee for complying with a data access request. We do not charge one.
You can also tell us at any time to stop using your data for direct marketing, which in our case means the daily lesson email. Clicking unsubscribe, or turning off the switch on your practice page or the You tab in later versions of the app, does exactly that, and it lasts: we keep your address only to remember the choice, so that signing in later does not undo it. We have never provided anyone's personal data to a third party for that party's own direct marketing, and we will not.
Children
Draw Daily is not directed at children under 13, or under 16 in those parts of the European Economic Area where that is the age of digital consent. We do not knowingly collect their personal data. If you believe a child has subscribed or created an account, email us and we will delete the record.
How we protect your data
- Traffic to and from the site, and between us and our providers, is encrypted in transit using TLS.
- Uploaded drawings live in a private storage bucket, in a folder keyed to the account that uploaded them. Only our server can add or remove files there, using a key that never reaches the browser. Your own signed-in session can read the files in your folder, and no other account can.
- Row level security is switched on for our database tables. Signed-in users can read only their own completion, feedback and subscription records. Nothing the browser or the app sends can create or alter a feedback or subscription record, and the subscriber list, the email records and the push tokens cannot be read from the browser or the app at all.
- Administrative database keys live in server-side environment variables and are never shipped to the browser or the app.
- Ordinary accounts have no password. Sign-in is by an emailed one-time code, or the link that comes with it, and each works once and expires after an hour. Any password that does exist is stored by our auth provider as a one-way hash.
- Access to the production database and the email tool is limited to the people who run Draw Daily.
No service can promise perfect security and we are not going to pretend otherwise. What we can say is that we hold very little in the first place, which is the most reliable protection there is. If a breach ever put your data at real risk, we would tell you and the relevant regulator as the law requires.
Complaints
If something here bothers you, tell us first at hello@drawdaily.app. We would rather fix it than have you chase us. You also have the right to go straight to a regulator. In the EEA that is the data protection authority in your country. In the UK it is the Information Commissioner's Office. In Hong Kong it is the Office of the Privacy Commissioner for Personal Data.
Changes to this policy
If we change how we handle personal data, we will update this page and change the effective date at the top. Anything significant will also be mentioned in the daily email, so you are not expected to keep checking back.
See also our Terms of Use and our Legal Notice.