Draft for review — not in force. No lawyer has read this yet. Text in [brackets] is a decision the operator has not made.

Privacy Notice

Version 1.0 — effective [date]. Previous versions: none; this is the first. One notice for everyone who uses myDayScribe, in any country. For people in India it is our privacy policy under the Information Technology Act's SPDI Rules 2011, and our notice under the Digital Personal Data Protection Act 2023 and its Rules 2025, whose duties apply from 13 May 2027. For people in the European Economic Area and the United Kingdom it gives the information the GDPR and the UK GDPR ask for.

1. In short

2. Who is responsible for your data

Embed AI Systems, No. 32/2, 34/1, 11th Floor, Innov8 Prestige Tech Platina, Kadubisanahalli, Bengaluru 560087, Karnataka, India, decides why and how your personal data is processed. Indian law calls that the Data Fiduciary; the GDPR and the UK GDPR call it the controller. Nobody shares that role with us. The companies in §6 that act on their own account answer for what they do with what you give them.

We have not appointed a Data Protection Officer. Indian law asks for one from a Significant Data Fiduciary, and we have not been notified as one. The GDPR asks for one where a controller's main work is processing sensitive data on a large scale, and a service of our size is not that. The contact above answers for us.

3. What we collect, why, and on what basis

The two "basis" columns say the same thing in two legal languages. India's law asks for your consent for almost everything. The GDPR and the UK GDPR, which apply if you are in the European Economic Area or the United Kingdom, let a service rest on the contract with you for what the service itself needs, and ask for consent on top where the data is sensitive.

WhatWhyBasis in India (DPDP Act)Basis in the EEA and the UK (GDPR, UK GDPR)Kept
Your email address when you ask for a sign-in codeTo email you the codeLegitimate use: you gave it to us for this (s. 7(a))A step you asked for before using the service (Art. 6(1)(b))The code record is deleted 30 days after it expires or is used
If you sign in with Google: the email address Google confirms is yoursTo find or create your account, through a one-time code issued for that address instead of an emailed one. We ask Google for nothing else, and keep neither the provider's own id for you nor anything else it sendsConsent, given on Google's screen when you choose to sign in with itContract: signing you in the way you chose (Art. 6(1)(b))Nothing beyond the account's email address; the code record as in the row above
Your account: the email address, a random account id, the date the account was created, and the date and version of the notice you consented toTo keep your account, to prove your consent, and to email you the service notices the Terms require (renewals, changes, security)Consent (s. 6)Contract (Art. 6(1)(b)); for the consent record, our duty to be able to show the consent you gave (Art. 7(1))Until you delete the account. An account is made when you first sign in, before you are asked for consent: if you never give it, and log nothing, we delete the account 30 days after it was made
Session tokens, stored as a one-way hash with their first eight characters, and when each was created and last usedTo keep a device signed in until it signs outConsentContract (Art. 6(1)(b))Up to 90 days, or until you sign out; the record is deleted 30 days after that
Your content: time entries, tallies, notes, tasks, journal pages, habits and ticks, calendar items, the money you log in the Spend Log, categories, spend categories and labels, and their timestamps, including records you deleted. In the Spend Log that is each amount, its day, whether it was spent, received or moved, its spend category, how you paid (cash, UPI, card and the like — never a card, bank account or UPI number) and what it was for; and, with your spend categories, the kind of person you said you are (a job-goer, a student and so on), which only decides which categories are shown firstTo store, sync, back up and show it to you: the service itselfConsentContract: it is the service itself (Art. 6(1)(b)); and your explicit consent for whatever in it is sensitive (Art. 9(2)(a), §4)Until you delete the account (deleted records are kept as tombstones until then)
Sync metadata: a random id per device, revision numbers, sync timestampsTo sync correctly between your devices and resolve conflictsConsentContract (Art. 6(1)(b))Until you delete the account
Plan and payment status: which plan, in rupees or dollars, monthly or yearly, its status, the paid period, when a plan you have scheduled starts, whether it is set to stop renewing, and the references that tie it to the payment provider's record of your subscription. Two yes-or-no marks of our own go with it: whether the purchase was made on a provider's test system, and whether we still owe the provider a request to stop it. For a plan bought in rupees, the state or union territory of India you choose before paying, which decides the GST on its invoice. No card, bank or UPI details, no billing name, and no postal addressTo give you the plan you paid for, and to stop it when it should stopConsent; and GST law, for the invoice of a rupee purchaseContract (Art. 6(1)(b))Until you delete the account. Invoices for a rupee purchase: for the period GST law sets. The record of a dollar purchase is kept by Dodo Payments, its seller (§6)
GST invoices, for a plan bought in rupees: one per payment, with its number and date, your email address, your state or union territory, the plan, the amount, the tax, and the payment provider's reference for the payment. Your name and GSTIN only if you ask us to add themTo issue the tax invoice GST law requires, with the right tax (CGST and SGST in Karnataka, IGST elsewhere), and to email it to youLegitimate use: you gave it to us to buy the plan (s. 7(a)); and GST lawLegal obligation (Art. 6(1)(c))For the period GST law sets, even after you delete your account (§8). Kept apart and used for nothing else
Chat messages and voice-note transcripts: what you type or say on the Chat page, with a random id the app gives each message, when it arrived, whether it was typed or spoken, what became of it (saved, answered, handed to the app as a change you typed — a category added or renamed, a habit deleted — or not saved, with a one-word reason), the ids of the records it created, how it was read (by our parser or by the AI), and what it used of your monthly limits. And the AI switch: whether the AI reading is on, when it was last changed and, while it is on, when you turned it on and which providers it named thenTo do what you asked, to show you what was done so you can undo it, and to keep to the monthly limitsConsentContract, for the feature you use (Art. 6(1)(b)); explicit consent for whatever in a message is sensitive (Art. 9(2)(a))Until you delete the account, even if you undo a message or turn the AI reading off
A voice note's recording, when you record one with the AI reading onTo write down what you saidConsent, given when you turn the AI reading onConsent (Art. 6(1)(a)), and explicit consent where what you say is sensitive (Art. 9(2)(a))Not stored. It passes through our server's memory to the transcription provider and is then discarded; the words are kept in the row above. What the provider keeps is set by its own terms (§6)
What is sent to an AI provider when you have turned on the AI reading: the one message; your list of categories; and the current date and time in your time zone, with the zone's name. The list of categories is the names of all your categories and sub-categories, archived ones included, and the id the app keeps for each category. That id was made from the name the category was first given, so a name you have since changed can still be sent. With it go the names of your spend categories and their sub-categories, and the id of each spend category. No amount you logged is sentTo interpret a message our parser cannotConsent, given when you turn it onConsent (Art. 6(1)(a)), and explicit consent where the message is sensitive (Art. 9(2)(a))Not stored by us beyond the Chat messages row above. What the provider keeps is set by its own terms (§6)
If you connect Google Calendar: the permission Google gives us to read your events (a token), and the events themselves when the Calendar page asks for them: each event's title, start and endTo show your Google Calendar beside what you loggedConsent, given on Google's screen when you connectContract, for the feature you turned on (Art. 6(1)(b))The token, encrypted, until you disconnect or delete your account. Events stay in the server's memory for 5 minutes and are never written to our database, our logs or your device's storage
Application log: for every request to the service, its time, route, status and duration, the random id of the account making it, and its IP address; for sign-in events, a keyed digest of the email address, never the address; error detailsSecurity, abuse prevention, debugging, and the security logs Indian law requiresConsent; and required by the CERT-In directions and the DPDP Rules' security safeguardsLegitimate interests (Art. 6(1)(f)): keeping the service secure, and meeting the Indian law that binds us180 days; one year from 13 May 2027 (§8)
Proxy access log: for every request, its time, IP address, method, path without its query string, status, and your browser's identification string (user agent)As aboveAs aboveAs above180 days; one year from 13 May 2027 (§8)
Rate-limit counters per IP address and per email addressTo stop abuse of sign-in and syncConsentLegitimate interests (Art. 6(1)(f)): keeping the service secureMinutes to an hour, in memory only
Whether your IP address is in India, when a page with prices opens: our server checks the address against a public list of the address blocks registered to IndiaTo show you prices in rupees in India and in US dollars elsewhereConsentLegitimate interests (Art. 6(1)(f)): showing you prices in a currency you can payNot stored. The check happens in our server's memory and only its answer, rupees or dollars, is sent back to the app, which does not keep it either. The request is a line in the application log like any other
Totals. From when each account was created, when each session was last used, and plan status, we count how many accounts there are, how many were created, how many were used in the last day, week and month, how many are on a trial or a paid plan, and how many paid plans ended. For each part of the app, we also count how many accounts used it in the last day, week and month. We count that from three things we already hold to run the service: which kind of thing each account saved and when (a time entry, a note, a task and so on), never what it says; what became of each Chat message or voice note (saved, answered, undone, or refused and the short reason) and whether the AI reading was needed, never its words; and whether Google Calendar is connected. We count accounts, never how many things one account savedTo know whether myDayScribe works — whether people use it and keep using it, and which parts of it — and to plan the serverConsentLegitimate interests (Art. 6(1)(f)): knowing whether the service works, from counts that name no oneOnly the numbers, one set per day, with no account in them, for as long as the service runs. When we look at how many accounts used a part of the app, a number from 1 to 4 is shown only as "fewer than 5"
Backups of all of the above, encryptedTo recover from loss or damageConsentContract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)): being able to restore the serviceRolling: 14 daily, 8 weekly, 12 monthly
Support email you send usTo help youConsent, by writing to usLegitimate interests (Art. 6(1)(f)): answering you12 months after the thread closes

Where it comes from. Almost all of it comes from you, as you use the app. Four things reach us from someone else, and only when you use them: Google tells us the email address it has confirmed, when you sign in with it, and sends your events, when you connect Calendar; the transcription and AI providers send back the words of a voice note and their reading of a message, when you have turned the AI reading on; and the payment provider tells us the state of your subscription (§6 says what else its messages carry, and that we keep none of it).

What we need, and what happens without it. An account needs an email address, and myDayScribe cannot work without storing what you log. Without those, and without the consent in §4, we cannot provide it. Everything else in the table follows from using the service, or from a feature you choose to turn on.

We do not collect your phone number, your location, your contacts or any device identifier beyond the random sync id, and we keep no name. We do not work out where you are from your IP address, except to answer one question, without keeping the answer: whether it is an Indian address, so that you see prices in rupees or in US dollars (the table above). The app reads your device's time zone, or the one you pick in Settings, to draw your day, and keeps your choice on your device. At two moments the app sends our server the name of the zone it is using: when you change that setting while signed in, and with each message or voice note you send in Chat. It is not sent at any other time. Our server uses the name to read a time in your message as you mean it, so that "this morning" is your morning, and does not store it. If you have turned on the AI reading, the name goes to the AI provider with the message, as the table says. A request that carries the name is a line in our application log like any other, and the zone's name is not in it. The only other thing we hold that hints at where you are is the currency of a plan you bought. There is no advertising identifier and no analytics script, and the app sends no reports of how you use it. Beyond the two logs and the totals above, we record nothing about how you use the app.

Charts, rings and habit trophies are worked out on your device from your own records, and nothing more is stored for them. A category you mark AI-assisted is only a label on that category: no AI runs for it, and nothing is sent to any AI provider. The label is kept with your categories.

Automated decisions. We make no decision about you by automated means that has a legal or similarly significant effect, and we build no profile of you. The AI reading turns a message into records you can see and undo; it decides nothing about you.

4. Sensitive information, and why we ask explicitly

myDayScribe comes with no categories: you create your own, or start from one of three general sets we offer while your list is empty, and change them as you like. None of the sets names a health condition, a belief or a relationship. Whatever you call your categories, a log of your day can reveal your health, your beliefs and your intimate life. The law gives that kind of information special care in most places. Indian law treats information about health, medical history and sexual orientation as sensitive personal data. The GDPR and the UK GDPR call data about health, religious or philosophical beliefs, sex life or sexual orientation special-category data, and let us hold it only with your explicit consent. Several US states call it sensitive data and ask for consent too. That is why we ask for your consent explicitly, with an unticked box, at the consent step shown after your first sign-in, rather than folding it into the Terms.

The Spend Log adds money to that. What you spend on says a good deal about your finances, and through them about your health (a pharmacy, a hospital), your beliefs (a temple, a donation) and your family. Indian law counts the details of a bank account, a card or another payment instrument as sensitive personal data; the Spend Log holds none of them — no card, bank account or UPI number, only how much, on what day, for what, and whether you paid in cash, by UPI, by card and so on. We still treat what you log there like everything else you log: it is covered by the same explicit consent, and used only to store, sync, back up and show it to you.

5. What we store on your device, and why there is no cookie banner

myDayScribe keeps on your device only what the service needs to work. This is the whole list:

WhereNameWhat it holdsWhy
Local storagedailyscribe.accountYour session token, your account id and your email addressKeeps this device signed in
Local storagedailyscribe.consent~ and your account idThe date and version of the consent you gaveA start with no network is not held up by a question you already answered
Local storagedailyscribe-theme, dailyscribe.timefmtLight or dark, and a 12-hour or 24-hour clockYour display choices
Local storagedailyscribe.tzThe time zone you picked in Settings, if you picked oneDraws your day in that zone
Local storagedailyscribe.regopen, dailyscribe.taskfold, dailyscribe.trophyopenWhich panels and task groups you left open or foldedPuts the screen back as you left it
Local storagedailyscribe.dayclosedThe dates of recent days this device has already marked as closedPlays that mark once, not on every visit
Local storagedailyscribe.chatA mark that Chat is switched on for this site. Nothing you typed or saidShows the Chat page in the menu without waiting for our server
Local storagedailyscribe.chatSpeakWhether Speak replies aloud is on, on this deviceReads Chat's replies out, or not, as you chose
Local storagedailyscribe.wakeOnWhether Hands-free is on, on this deviceListens for the wake word on the Chat page, or not, as you chose
The browser's database (IndexedDB)dailyscribe~ and your account idYour records and categories, a random id for this device, how far it has synced, and your settings inside the appThe app works offline, and syncs when it can
The same databasechatThread, one of those settingsUp to the last 60 turns of your Chat page, and any message of yours not yet sent, however old: what you typed, each reply, what a voice note was heard as, and what a reply saved, with the time of each turn and, for each message you sent, the name of the time zone it was written in. Never a recordingA message that has not gone through yet is kept so that it can be sent again, and the thread is still there when you come back
The service-worker cachedailyscribe-v and the app's versionThe app's own pages and icons and, once you turn Hands-free on, the program and model that listen for the wake word (about 14 MB, asked about before it downloads). Nothing you loggedThe app opens without a network, and Hands-free starts without downloading again
Cookieds_oauthA signed, single-use security valueSet only when you choose Continue with Google. It ties Google's answer to the sign-in you started. The page cannot read it, it is sent only to our sign-in address, and it lasts at most 10 minutes and is removed when the sign-in finishes
Cookieds_gcalA random, single-use security valueSet only when you connect Google Calendar. It ties Google's answer to the browser that asked. The page cannot read it, it is sent only to our calendar address, and it lasts at most 10 minutes and is removed when the connection finishes

Every item is ours, set by our own site, and exists only to provide the service you asked for. If you sign in with email and never connect Google Calendar, myDayScribe sets no cookie at all.

There are no tracking cookies, no advertising cookies, no analytics and no third-party scripts. The page loads its scripts, styles, fonts and images only from our own site and connects only to our own server, and our server tells your browser to refuse anything else. Nothing on the list above is used to follow you, on our site or anywhere else. That is why myDayScribe shows no cookie banner: there is nothing on it to ask your permission for.

Signing out removes the session token. Your records and your Chat thread stay on the device until you clear the site's data in your browser, which removes everything on the list; your account on the server is unaffected.

A voice note you record is held in your device's memory until it has been sent or the page is closed, and is never written to its storage. Your browser asks before myDayScribe may use the microphone, and it is your browser that remembers the answer.

Hands-free, when you turn it on, listens to the microphone while the Chat page is open and on screen, to hear the wake word. That listening happens on your device: the sound is examined in its memory a fraction of a second at a time, and none of it is stored or sent anywhere. When the wake word is heard, a voice note is recorded and sent exactly as if you had pressed the microphone button.

When you pay, or when you use Google, you leave our site for a while: the payment page is Razorpay's or Dodo Payments' own, and the sign-in and permission screens are Google's. Those sites set their own cookies, under their own notices.

6. Who else sees your data

We share personal data only with three kinds of recipient. First, the companies that run parts of the service for us: processors, which Indian law calls Data Processors, bound by contract to act only on our instructions. Second, the companies below that act on their own account, because you chose to use them. Third, authorities, when the law compels us. We never sell personal data, and we never share it for advertising.

WhoWhat they processWhereWhy
Hostinger Pte. Ltd. (Singapore)Everything on the serverIndia, MumbaiRuns the server and database
Amazon Web Services India Private Limited (Amazon S3)Encrypted backup snapshots (they cannot read them)India, MumbaiOff-site backups
Zoho Corporation Private Limited (ZeptoMail)Your email address and the sign-in code or notice sent to itIndiaSends email on our behalf
Google (Google LLC) — only if you sign in with Google, on its own account, under its own terms and privacy policyThat you are signing in to myDayScribeGoogle's own locationsIt confirms your email address
Google (Google LLC) — only if you connect Google Calendar, on its own account, under its own terms and privacy policyThat you connected myDayScribe, and our requests to read your eventsGoogle's own locationsIt is the calendar you chose to show
Razorpay Software Private Limited (India) — only if you buy a plan in rupees, on its own account, under its own notice and the RBI's rulesFrom us: what you are buying (the plan and the billing period and, for a change of plan, its amount and start date) and a random reference for your account. From you, on its own page: your contact details and your payment detailsIndiaTakes the payment
Dodo Payments Inc. (United States) — only if you buy a plan in US dollars. It is the seller of the plan (the merchant of record) and decides for itself how it uses what you give it, under its own privacy noticeFrom us: what you are buying (the plan and the billing period), a random reference for your account, a reference we make for that purchase, and the address of our own site. From you, on its own page: your email address, your name, your country and postal code, and your card or other payment detailsThe countries its own privacy notice namesSells the plan, takes the payment, works out any tax and pays it out of the price, sends the receipt and pays refunds
OpenRouter, Inc. (United States) — only if you turn on the AI readingThe text of a message our parser cannot read; your list of categories, which is the names of your categories and sub-categories, archived ones included, and each category's id (§3); and the date, time and name of your time zoneUnited StatesInterprets the message
Groq, Inc. (United States) — only if you record a voice note with the AI reading onThe recording, which it writes down. We keep the words and discard the recordingUnited StatesTranscribes the voice note

The two payment providers send our server a notice when a subscription starts, changes, renews or ends. A notice from Dodo Payments also carries the contact details you gave it. From a notice we read the subscription's reference, its plan, its status, the paid period and whether it is set to stop. We keep those with your plan, and the notice's own id for 30 days, so that one notice is never applied twice. We keep nothing else from a notice, and the contact details in it are neither stored nor written to our logs.

After a first purchase on Dodo Payments' page, it sends your browser back to myDayScribe. To the link it uses, Dodo Payments adds its reference for the subscription and the email address you gave it. Our server does not read them, and neither of our logs records them. The app takes them out of the address as soon as the page opens, uses neither, and stores neither on your device.

In each provider's own dashboard we can also see the payments made for myDayScribe, with the contact details you gave that provider. We use those only to answer a question about a payment or to make a refund, and we do not copy them into myDayScribe.

The table above is the current list, with each provider's location, and we update it before a change takes effect.

7. Where your data is stored, and what that means outside India

Your data is stored on servers in India, at Hostinger's data centre in Mumbai, and backed up to India (Amazon Web Services, Mumbai). We operate myDayScribe from India. This is the same whichever country you use myDayScribe from: we have no servers anywhere else, and we use no content-delivery network, so your device connects to our server in India directly.

If you use myDayScribe from outside India, your personal data travels from your device straight to our server in India, over an encrypted connection. You send it to us there yourself; no company in your own country collects it and passes it on. India's data-protection law is not the same as the law of your country. Neither the European Commission nor the United Kingdom has decided that India's law protects personal data to the standard of their own. What protects your data with us is in this notice, and it applies to you wherever you are: the limits on what we use it for (§3), who else sees it (§6), the security in §9, and the rights in §10.

Personal data leaves India only in these cases, and only for the purpose stated in §6:

Indian law allows these transfers except to a country the Central Government restricts (DPDP Act, s. 16), and we do not send data to one. Where the GDPR or the UK GDPR asks for a safeguard when we pass your data to one of these companies, we rely on the safeguards in that company's own data-processing terms, such as the European Commission's Standard Contractual Clauses and the UK's International Data Transfer Addendum where it offers them. You can ask for a copy at privacy@mydayscribe.com.

8. How long we keep things

Section 3 gives the period for each kind of data. These things sit behind those periods:

9. How we protect it

10. Your rights, and how to use them

Most of these you can use yourself, in the app, without asking us. The second column says whose law gives the right; where it says "everyone", we give it to you whatever your country's law says.

RightWho has it by lawIn the appOr ask us
Access: a copy of what we hold, how we process it, and who we share it withIndia (DPDP Act s. 11); EEA and UK (Art. 15); most US state lawsBackup & sync → Export backup holds every record; Settings shows your account; §6 names every recipientprivacy@mydayscribe.com for anything the export does not show: logs, plan status, the consent record, the log of your Chat messages
Correction, completion and updatingIndia (s. 12); EEA and UK (Art. 16); most US state lawsEdit any recordWrite to us to change the email address on your account
ErasureIndia (s. 12); EEA and UK (Art. 17); most US state lawsDelete any record: it is hidden at once, and erased with your account (Terms §7). Settings → Account → Delete account erases everythingWrite to privacy@mydayscribe.com from the address on your account, and we delete the account for you
A copy you can take elsewhere (portability)EEA and UK (Art. 20); most US state laws. We give it to everyone (Terms §6, §8)Backup & sync → Export backup (JSON), and the Reports page (CSV, Excel, JSONL)—
Withdraw consent, as easily as you gave itIndia (s. 6(4)); EEA and UK (Art. 7(3))Settings → Account → Delete account; turn off the AI reading on the Chat page; disconnect Google CalendarWrite to privacy@mydayscribe.com from the address on your account, and we delete the account for you
Restrict, or object to, what we do on the ground of our own legitimate interests: the logs, the totals, backups, support emailEEA and UK (Arts 18 and 21)—Write to us. We stop unless we have a reason that outweighs yours, or a law makes us continue, and we tell you which
No decision about you made by a machine aloneEEA and UK (Art. 22)We make none (§3)—
Opt out of the sale of your data, of sharing it for advertising, and of targeted advertisingMost US state lawsNothing to switch off: we do none of these, for anyone—
Nominate someone to use these rights if you die or cannot actIndia (s. 14)—Write to privacy@mydayscribe.com with the person's name and email
Grievance redressalIndia (s. 13). We give it to everyone—The Grievance Officer (Terms §1), who acknowledges within 24 hours and resolves within 7 days
Appeal if we refuse a requestMost US state laws. We give it to everyone—Reply to our answer, or write to the Grievance Officer. We answer an appeal within 45 days
Complain to an authorityEveryone—The paragraphs below say which one is yours

To use a right, write from the email address on your account, or sign in and ask. We may ask you to confirm it is you. Someone you have authorised may ask for you, and we will check with you first. We answer every request within 7 days, and never later than one month. We do not charge for one, we do not treat you differently for making one, and we tell you why if we refuse one.

If you live in India. Take a complaint to the Grievance Officer first. If you are not satisfied with the answer, or none comes in time, you may complain to the Data Protection Board of India.

If you live in the European Economic Area or the United Kingdom. You have the rights the table marks for you. You may complain at any time to the data-protection authority of the country where you live or work, or where you think the law was broken. You do not have to come to us first, though we would like the chance to put it right. In the EEA these are the national authorities that make up the European Data Protection Board; in the UK it is the Information Commissioner's Office. We have no representative there yet (§2).

If you live in the United States. We do not sell your personal data, we do not share it for advertising, and we do not track you across websites or apps. So there is nothing to opt out of, and myDayScribe behaves the same whether or not your browser sends a Do Not Track or Global Privacy Control signal. We use sensitive information only to provide myDayScribe to you, with the consent in §4. Many states, California among them, give their residents rights to know, correct, delete and take a copy of their data, to opt out of sale and of targeted advertising, and to appeal a refusal. Most of those laws apply only to businesses far larger than ours. We give the same rights to everyone anyway, as the table shows, and you may complain to the Attorney General of your state.

If you live anywhere else. The rights that the table gives to everyone are yours. Where the law of your country gives you more, we honour it, and you may complain to your country's data-protection authority.

11. Children

myDayScribe is for adults, in every country. We do not knowingly hold an account for anyone under 18, and we delete one when we learn of it; write to privacy@mydayscribe.com. We do not track, profile or advertise to anyone, of any age.

12. Languages

This notice is available in English. If you live in India, you can ask for it in any other language listed in the Eighth Schedule to the Constitution of India by writing to privacy@mydayscribe.com, and we will send it to you. It has not been translated into other languages. If any part of it is unclear to you, write to us and we will explain it.

13. Changes to this notice

We change this notice when the facts change: a new provider, a new feature, a new retention period. We email you and show a notice in the app at least 30 days before a change that affects you. We never turn on a new use of your data without asking for your consent to it first. Previous versions stay published on this site, linked from the top of this page.

14. Contact

privacy@mydayscribe.com · +91-8618085343 · No. 32/2, 34/1, 11th Floor, Innov8 Prestige Tech Platina, Kadubisanahalli, Bengaluru 560087, Karnataka, India · Grievance Officer: Rajnikant Narone, rajnikant@mydayscribe.com · Representative in the EEA or the UK: not appointed yet (§2).