Privacy policy

Last updated 17 October 2026

Daysli is a personal app: your calendar, your to-dos and a private journal, with an optional public link so other people can ask for your time. This page says exactly what we store, what we can and cannot read, and who else is involved.

Who we are

Daysli is run by Nazil Afeef, an individual living in the Maldives, who decides how the personal data described here is used and is responsible for it. “We” on this page means Nazil Afeef. If that ever changes — for example because Daysli is moved into a company — we will update this page and tell you before it takes effect.

Post: Heavenly Heaven, G.Dh. Fiyoaree, Republic of Maldives. Email: team@daysli.com, about anything on this page.

Nazil Afeef is not established in the European Union or the United Kingdom and has not appointed a representative there. People anywhere can write to team@daysli.com, or to the address above, about anything relating to their personal data.

What we store, and why

Your account

Your email address, so we can send the six-digit code you sign in with; your display name and time zone. We do not store a password — there isn’t one.

Your day

Events, appointments, tasks and reminders you create, including their titles, times, places and notes. These are private to you. They are used to draw your own screens and, for appointments, to work out which times you have free.

People

Daysli keeps a private record of the people who have sent you requests: a name, the contact details they gave, a history of what they asked for, and any note you write about them. It is yours and nobody else’s — never shown on your public page, never sent to the person it is about, and never included in an email. Two requests are linked to one person only when they come from the same exact address; a matching name never links them, and Daysli asks you rather than deciding. You can combine two records, separate them again, or forget a person entirely.

My Life, if you use it

If you use My Life, Daysli keeps what you write there: your direction, the areas of life you chose, your goals and priorities, your weekly milestones, your reviews, and which suggestions you added or turned down. A suggested step you accept becomes an ordinary task in your To-do. It is private to your account like your tasks are: never shown on your public page or Daysli Card, never in a link preview, never in the Developer API, and never sent to anyone. It is stored on Daysli’s servers in a form the service can read, so it can be shown on every device you use; it is not end-to-end encrypted like your journal. My Life does not read your journal. You can turn My Life off, or delete everything in it from Life settings; deleting your account deletes it too.

Your picture, if you add one

Optional. You can upload a photo or choose one of Daysli’s drawn avatars instead. A photo is cropped and re-encoded on your device as a small square picture, and its camera and location data are removed there and again on our servers. It is stored privately, in a form the service can read, so it can appear on every device you use; it reaches you through links that expire. It appears on your public page only if you turn on “Show on my public page”, and on your card only if you choose it there. Replacing or removing it deletes the old file, and deleting your account deletes it too.

Your public page, if you turn it on

Off by default. When on, daysli.com/your-name shows your display name, your photo if you enable it, your bio and links, the kinds of appointment you offer and which times are free. It never shows what those busy times are — only that they are taken. Your tasks, your journal, your People records and the details of your events are never on it.

Your card

If you make a card, what you write for it is stored with your account: a title, a company, a short note, up to two websites, and — for the back of the card — an address, phone numbers and an email address. The back of a card is never published. It is not on your public page, no part of the public site can read it, and it leaves Daysli only inside a file you choose to share. The front — title, company and websites — appears on your public page only if you turn that on yourself; it is off until you do. The code on the card carries your public address and nothing else.

Requests from other people

When someone asks for your time or sends you a to-do, we store their name, the contact details they gave, their message, and the time or date they proposed. They do not need an account; they follow an unguessable link to see where their request stands. We also keep a one-way hash of their contact details and of the sending network address, so that rate limits and blocking work without us keeping a readable list.

Your journal

Your journal is encrypted on your device before it is sent to us, with a key we do not hold. What we store is what that encryption leaves behind, and both halves are worth being exact about.

What we hold, and cannot read: for each entry, the encrypted writing, the highlight, what you learned, the mood, the place, the moments you captured during the day, the line you keep in front of you, and who you mentioned. Gratitude notes and tag names are encrypted too. Photos are encrypted on your device and stored as encrypted objects. For each device you have enrolled, and for your recovery code, we hold a sealed copy of your journal key — each one encrypted under a key we have never seen: a key held in that device’s own keystore, or one derived from your recovery code.

What we can see: the shape, not the content. Which days have an entry, whether you marked a day a favourite, when a row was written or changed, how many photos there are and how large the encrypted pieces are, and how many tags you have. A tag also carries a keyed fingerprint, so the same tag can be recognised as the same one without its name being revealed.

What we cannot do: decrypt any of it. There is no master key, no escrow copy and no reset. The one mechanism that could once have unwrapped a journal key on request was removed, and nothing replaced it. This is a property of how the system is built rather than a promise about how we behave.

On your own device, things are different. While your journal is open, your device holds the decrypted text in its memory, because that is what reading it means. Daysli uses that only on that device: searching your journal happens there and nothing you type leaves it, and when Daysli offers you a line you wrote on an earlier day, it is chosen on the device from entries it has already decrypted — Daysli keeps no index of your journal at all. If you ask for a copy of your journal, the file is built on your device and is plain text on that device, which is what makes it readable; what you then do with that file is yours.

Anything Daysli derives from your journal and keeps — the moments in a day, the line you keep in front of you, the people a day mentions — is stored inside that day’s encrypted entry rather than beside it: there is no separate count, time, flag or identifier that would say what an entry contains. And your journal is never used to suggest anything to anyone else.

Your devices, and keeping the account safe

For each device you enrol for the journal we store a label you choose, whether it is a phone or a browser, its public key, and when it was enrolled and last seen — so that you can see your devices and revoke one you no longer have. If you turn on notifications we store the token the platform gives us to reach that device. We keep a record of security-relevant actions on your account — what happened, when, and to which record — with identifiers and changed field names only, never the content of anything.

Travel and weather, if they are offered

Daysli is built to estimate when to leave for an event with an address, and whether rain is likely for an event you have marked as outdoors. Neither is switched on at present, and nothing below happens until it is. When they are, both stay off until you ask for them.

For a journey estimate, your approximate position — rounded before it leaves your device, to roughly a hundred metres — and the event’s address are sent to a routing provider to work out the time. Nothing about the journey is kept afterwards. For weather, the place and the hours of the event are sent to a forecast provider; the answer may be remembered briefly so the same question is not asked twice, and what is remembered is an answer about a place, with nothing recording who asked. Daysli does not track your location: it asks once, at the moment it is working something out, and if you decline you simply get no travel times.

If you connect Google Calendar, Microsoft Outlook or Apple iCloud

Only if you choose to, and you can disconnect at any time.

We ask for the narrowest access that works. For Google Calendar that is three permissions, and Google’s own screen shows you each one: the list of your calendars, when you are busy, and adding, changing and removing the events Daysli puts there, on calendars you own. Daysli needs all three; if any one is left unticked, nothing is connected and the access is handed straight back to Google.

What we keep: which account you connected (its email address), the names of your calendars and which of them you chose, and the start and end of your busy times. We do not keep the titles, guests, locations or notes of your events. Google never even sends them to us: the free/busy answer we ask for holds only times. Apple iCloud sends whole events, and Daysli keeps only their start and end.

What we write: the events you make in Daysli and the appointments you accept go to the calendar chosen to receive them — your main calendar unless you pick another, or none at all — with their title, time, place and notes (for an appointment, the message that came with the request). In Google Calendar a repeating event stays one repeating event; to iCloud Daysli writes one-off events only. An event shown as Free stays free. When they change in Daysli we update them there, and when they are deleted or cancelled we remove them. We never change or remove an event Daysli did not put there.

What we never do with it: sell it or share it with anyone, use it for advertising, or use it to build or train AI or machine-learning models of any kind — Daysli Brain does not use it either. Nobody at Daysli reads it, except when you ask us to help with a problem, to investigate abuse or security, or when the law requires it.

Disconnect and we delete what we stored to keep the connection and the imported busy times; for Google we also revoke our access there. Appointments already written to your calendar stay there, because they are yours. You can also remove Daysli’s access from your Google Account at any time, at myaccount.google.com/permissions.

To keep the connection working we store the access the provider gives us — for Google and Microsoft a sign-in token, for Apple iCloud the app-specific password you create for Daysli. It is stored encrypted, under a key kept in a separate key service (Amazon Web Services, in Frankfurt) that only Daysli’s calendar workers can ask to use, and it is deleted when you disconnect.

Daysli’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Exports

When you ask for a copy of your data we build a file and make it available to you for a short time. Your journal is not in that file: it has its own export, which is built on your device and encrypted, and which has a waiting period before it can be taken.

Keeping the service working

We keep the technical records a service needs in order to run and to stay up: rate-limit counters keyed on one-way hashes, error reports, and the logs our hosting and email providers keep. Error reports are scrubbed of your content before they are sent. We do not use analytics that follow you, and there are no advertising or tracking cookies on this site.

For each app or browser you sign in on, we keep one record of what it is. The kind of device (phone, tablet or desktop), its make and model as the platform reports them, the operating system and its version, the Daysli version and build, your language and region settings, your time zone, and whether you were on Wi-Fi, mobile data or a wired connection. We keep when we first saw it and when we last did, and we keep what it was running the first time as well as now.

This exists for one reason: when something breaks we need to know whether it is breaking for everyone or only on one kind of phone, one version of Android or iOS, or one Daysli build. Without it a fault report is a number with nothing to compare it against.

What that record does not contain. No location of any kind — not GPS, not a city, not one worked out from your address. No IP address. No Wi-Fi network name, hardware address, serial number or advertising identifier. Nothing that could be used to recognise your device elsewhere. And none of your own content: no journal, no calendar or event titles, no tasks, no contacts and no photographs. The region we keep is the one your device is set to, not where it is. The identifier we give each installation is a random number made on that device, which we cannot tie to any hardware and which is gone when you remove the app. You can see your devices in settings and remove one you no longer have.

When the Daysli Android app stops unexpectedly, it keeps a short crash report on your phone and sends it to Daysli’s own service the next time you open it: where in Daysli’s code the fault happened (the names of the program’s parts and line numbers), with the app version, Android version, device model and the installation’s random number. Never the error’s message, and none of your content. Crash reports go to no other company and are deleted after 90 days.

Software you connect yourself

If you make a developer token in Settings → Developer, the software you give it to can read what you allowed when you made it — your profile, free times, events, to-dos or requests, and the email and phone number of people who send you requests only if you ticked that — and can send requests to your inbox. If you add a webhook, Daysli sends that address a short notice when something changes: what kind of thing, its identifier and the time, never its contents. That software is yours to choose and its use of your data is between you and it; we keep only a fingerprint of each token, the scopes you chose, and when it was last used. A token can never reach your journal. You can revoke one at any time, and it stops working at once; deleting your account revokes them all.

Daysli Brain: guidance that adapts to you

Daysli Brain is Daysli’s own progress guidance. It is not a chatbot or a large language model, and it is not built on one. It uses Daysli’s own rules, statistics and learning methods to suggest your next step towards goals you choose, and it adapts to you: the longer you use it, the more its suggestions fit what actually works for you.

What it uses: only what you give it for your progress — the goals you set, the steps you plan, your check-ins, the measures you choose to record, and your feedback on its suggestions. It never uses your journal, the words of your to-dos or events, your contacts, anything from a connected calendar, or anything about other people.

Your choices:

• Brain is off until you turn it on. Turn it off at any time; you can also delete everything it holds about you.
• Adapting to you. While Brain is on, it learns from your own progress which steps help you, and personalises your suggestions. What it learns about you is used only for you and is never combined with anyone else’s. You can switch adapting off — Brain then gives the general guidance only — or reset what it has learned, at any time.
• Helping improve the guidance for everyone (shared learning). A separate choice, off unless you turn it on, and turning on Brain never turns it on. With it, Brain adds counts from your progress — for example, how often a kind of step was followed through and whether it helped — to totals combined across at least twenty people. Nothing that identifies you, and nothing in your own words, is included, and nobody’s individual results are shown to anyone. Turn it off and nothing more is added; what you contributed is removed from the totals when they are next recalculated, within thirty days.

Our AI promise: we do not use your data to train third-party large language models or general-purpose AI models, we do not send it to outside AI services, and we do not sell it. Brain’s learning is Daysli’s own, works for you, and stays within Daysli.

We keep a record of each choice — which one, on or off, when, and the version of this explanation you were shown — so that it can be honoured and shown back to you. Deleting your account deletes your progress data, what Brain learned about you, and your contributions to the shared totals.

What we do not do

• We do not sell your data, and we do not share it for advertising.
• We do not profile you for advertising or for anyone else. The only personalisation is Daysli Brain adapting to you, described above, which you control; and we make no automated decisions with legal effects.
• We do not use your data to train third-party large language models or general-purpose AI models.
• We do not read your journal, and — more to the point — the system is built so that we do not have the ordinary means to.

Who else is involved

These are the services Daysli uses: companies that handle data on our behalf so that Daysli can work, each under its own standard terms for customers.

Your database and your files are in the EU (Frankfurt), and that is where they stay. We hold no key to your journal at all — only the sealed copies described above, which need one of your devices or your recovery code to open.

Payments, when they are switched on

Billing is not switched on while Daysli is a personal experiment. When it is (see the terms for the monthly plan and how its price is set), payment will be taken by Google Play in the Android app or by a card payment provider on the web. They receive your payment details directly; Daysli never sees or stores a card number. Daysli keeps only what it needs to know whether your plan is active: its status, the dates of the trial and of the next payment, and which service took it. This page will name the web provider before billing starts.

To show the price for your country, daysli.com uses the country your connection comes from, as Cloudflare reports it. It is used for that page and not kept. When you subscribe, the price is set by the country of your payment method and billing address, which the payment service tells us.

Personal data leaving the EU

Your database and your files are stored in the EU (Frankfurt). Daysli is run from the Maldives, by Nazil Afeef.

What actually crosses a border is the data each processor outside the EU needs for its part of the job, and only that:

• Expo and Google (Firebase Cloud Messaging) (United States) receive a notification’s device token and its text, which can include a requester’s name, a requested time, a short excerpt of their message, or the title of an event or task.
• Cloudflare operates a global edge network, so a request to this site, the app or the private beta — and the Turnstile check on a public form — is handled at whichever location is nearest to the person making it.
• Google or Microsoft receive calendar requests only if you connect that calendar, and a routing or forecast provider receives a rounded position and an address, or a place and a time, only if you use travel times or weather.

We are not claiming any particular legal transfer mechanism here, because we would rather say nothing than say something we have not put in place. If you want to know what covers a specific transfer, write to us at team@daysli.com and we will tell you what is and is not in place.

For your journal the protection that matters most is structural rather than contractual: it is encrypted before it leaves your device, so it is unreadable wherever it is held and from wherever it is reached.

How long we keep things

• Your events, tasks, People records and journal stay until you delete them or close your account.
• Completed tasks remain visible for 30 days, then drop out of the list.
• A handled request is archived rather than deleted, so your history stays intact. The requester’s contact details are removed once they are no longer needed to reach them about it.
• Imported busy times are replaced on every sync and are never accumulated.
• Encrypted recovery copies of the database are kept for up to 14 days, so something you delete may survive in one of them until it expires. They are encrypted before they leave Daysli’s systems, and the key that opens them is kept offline by the operator.
• An export you ask for is available to you for a short time and then deleted.
• A weather answer may be remembered briefly and expires by itself. Nothing recorded with it says who asked.

Your rights

You can ask for a copy of your data, ask us to correct it, ask us to delete your account and everything in it, object to or ask us to restrict a particular use, and — where it applies — ask us to send your data to someone else. Write to team@daysli.com and we will act within 30 days.

Deleting your account permanently removes your private data and your files, and destroys the sealed copies of your journal key that we hold — so anything left in a backup of ours cannot be opened by us or by anyone else. Two things follow from the way your journal is encrypted, and we would rather say them than let you find out: a copy of your journal that we give you is encrypted, and only your device or your recovery code can read it; and if you have lost both, we cannot produce it in a readable form, because we have never been able to read it.

If you are in the UK or the EU you also have the right to complain to your data protection authority. If you are in California or another US state with its own privacy law, you have the rights that law gives you, and we do not sell or share personal information as those laws define it.

Security

Everything travels over HTTPS. Access rules are enforced by the database itself rather than by the app asking politely, so a bug in a screen cannot show you someone else’s data. The journal is encrypted before it leaves your device, and we hold no key that could open it — there is no master key here, and no administrator who can be asked for one. Public forms are rate-limited and protected against automated abuse. Journal photos are resized and stripped of their camera and location data on your device, then encrypted there, before they are uploaded.

No service can promise it will never suffer a security incident, and we do not. Daysli is run by one person, has not been through an independent security audit or certification, and should not be treated as if it had. What we can say is what an incident would and would not reach: your journal is encrypted with keys we do not hold, so it would not become readable to us or to whoever reached it; everything else you put into Daysli could be. If a breach affects your personal data and the law requires us to tell you, we will.

Children

Daysli is not intended for children under 16, and we do not knowingly collect their data.

Changes

If we change how any of this works we will update this page and change the date at the top. If a change materially affects you, we will tell you in the app or by email before it takes effect.

Questions about any of this: team@daysli.com · See also our terms of service.