koyomiOpen Koyomi →

Privacy

LAST UPDATED 10 NOVEMBER 2026

Koyomi is a calendar for planning your own time. It is run by 6Away AI FZE LLC, United Arab Emirates. This page says what Koyomi keeps, where it keeps it and what it is used for. For any question or request, write to privacy@6away.ai.

Your Koyomi calendar stays on your device

The events you write in Koyomi are kept in your browser, on the device you write them on. They are not sent to our servers and we cannot see them. Ordinary use needs no account.

There is no cloud copy. If you clear the site’s data in your browser, or remove the installed app’s data, they are gone.

Two more things are kept on the device: whether you chose the light or the dark appearance, and a copy of Koyomi’s own files, so that it opens without a connection.

Connecting Google Calendar

Connecting a Google calendar is optional. You can connect one Google account or several. Koyomi shows their events beside your own, so that you can see which hours are already taken. That is the only thing your Google Calendar data is used for.

To connect an account, you first sign in with 6Away. Google then asks which account, and whether you allow Koyomi two things, both read-only:

  • see the list of your Google calendars (calendar.calendarlist.readonly);
  • view the events on them (calendar.events.readonly).

Koyomi asks for no other permission. It cannot create, change or delete anything in your Google Calendar.

What Koyomi reads from Google

Koyomi reads the names and identifiers of your calendars, and whether each is your main one, is shown in Google Calendar, or has been deleted. A calendar’s identifier can be an email address.

The identifier of an account’s main calendar is that account’s address. Koyomi uses it to tell your connected accounts apart, and to show you which calendars belong to which.

For the calendars you choose to show in Koyomi, it reads these details of each event, from five weeks back to twenty-seven weeks ahead:

  • its identifier at Google, its title, its start and end, and the time zone it was written in;
  • whether it is confirmed, tentative or cancelled, and when it last changed;
  • a link to the event at Google;
  • its type, used only to leave out working-location entries;
  • your own reply to an invitation, used only to leave out events you declined.

Koyomi does not ask Google for descriptions, locations, guest lists or meeting links, so Google does not send them.

Connecting a Microsoft calendar

Connecting a Microsoft calendar is optional too. You can connect one Microsoft account or several, personal or work and school, beside Google accounts or without them. Koyomi shows their events beside your own, and uses them for nothing else.

To connect an account, you first sign in with 6Away. Microsoft then asks which account, and whether you allow Koyomi three things:

  • to sign you in, which tells Koyomi which Microsoft account it is (openid);
  • to go on reading what you allow until you disconnect, without asking each time (offline_access);
  • to read your calendars (Calendars.Read).

Koyomi asks Microsoft for no other permission: not your profile, not your email address, and not calendars other people share with you. It cannot create, change or delete anything in your Microsoft calendar. A work or school account may need its organisation to approve Koyomi first.

Microsoft also has a narrower permission that leaves out an event’s body and attachments, but it does not let a personal Microsoft account’s calendar be read at all, so Koyomi asks for this one. Either way, Koyomi asks Microsoft only for the details listed below.

What Koyomi reads from Microsoft

Koyomi reads the names and identifiers of the account’s calendars, and for each whether it is the account’s main one, whether you can change it, and who owns it. The owner of the main calendar is the account’s address: Koyomi shows it to you beside that account’s calendars, and leaves out calendars that someone else owns.

When you connect an account, Microsoft also tells Koyomi which account it is: an identifier Microsoft gives that account for Koyomi alone, and the identifier of its organisation. Koyomi uses them to tell your connected accounts apart.

For the calendars you choose to show in Koyomi, it reads these details of each event, from five weeks back to twenty-seven weeks ahead:

  • its identifier at Microsoft, its title, its start and end, whether it lasts all day, and the time zone it was written in;
  • whether it is cancelled, shown as tentative, or one occurrence of a repeating event;
  • a link to the event in Outlook;
  • your own reply to an invitation, used only to leave out events you declined.

Koyomi does not ask Microsoft for bodies, locations, attendees, attachments or online-meeting details, so Microsoft does not send them.

Connecting a Yahoo calendar

Connecting a Yahoo calendar is optional too. You can connect one Yahoo account or several, beside your other accounts or without them. Koyomi shows their events beside your own, and uses them for nothing else.

A Yahoo calendar is read through Yahoo’s CalDAV service, at caldav.calendar.yahoo.com, with an app password: a password you create for Koyomi yourself, in your Yahoo account’s security settings (Account Security, then External connections). Koyomi never asks for your normal Yahoo password. To connect an account, you first sign in with 6Away, then give Koyomi your Yahoo email and that app password. Koyomi checks them with Yahoo at once, and keeps them only if Yahoo accepts them.

Yahoo does not limit an app password to your calendar: whoever holds one may also be able to open your Yahoo mail with it. Koyomi uses it only to read your calendars through CalDAV, and for nothing else. It never reads your mail, your email content or anything else in your account, and it cannot create, change or delete anything in your Yahoo calendar.

What Koyomi reads from Yahoo

Koyomi reads the names and addresses at Yahoo of the account’s calendars, and for each whether it holds events and whether you can change it. Lists of tasks are left out.

For the calendars you choose to show in Koyomi, it asks Yahoo for these details of each event, from five weeks back to twenty-seven weeks ahead, and of repeating events that began up to five years before that:

  • its identifier at Yahoo, its title, its start and end or its length, whether it lasts all day, and the time zone it was written in;
  • whether it repeats, and how: its rule, the dates added to it or left out, and any occurrence that was changed;
  • whether it is cancelled or tentative, and when it last changed.

Yahoo’s CalDAV service may send each event whole, whatever Koyomi asks for, and if it sends none of the details Koyomi names, Koyomi asks for the events whole: with their description, location, organiser, guests, alarms and attachments. Either way, Koyomi drops all of that on our server the moment it reads it. None of it reaches your device, and none of it is kept or written to a log. Yahoo has no address for a single event, so Koyomi links to none.

Subscribing to a calendar link

Subscribing to a calendar by its link is optional too. Some calendars, Outlook’s among them, can be published as a private, read-only link (an .ics or webcal address). You can give Koyomi one such link or several, beside your accounts or without them. Koyomi shows that calendar’s events beside your own, and uses them for nothing else. It is a subscription, not a copy: Koyomi reads the calendar again from time to time, and shows it as it is.

To subscribe, you first sign in with 6Away, then paste the link. A calendar link works like a password: anyone who has it may be able to see that calendar, so keep it to yourself. Koyomi sends it to our server once, over HTTPS, when you add it. It is never sent back to your browser, never kept on your device, and never written to a log or shown in an error. Our server fetches the calendar, never your browser, and keeps the link only if it gives a calendar. It fetches only from the public internet: never from a private network, and a redirect is checked the same way.

Koyomi only reads a calendar link. It cannot create, change or delete anything in the calendar it leads to.

What Koyomi reads from a calendar link

A calendar link gives the whole calendar, whatever Koyomi would rather have: it may include descriptions, locations, organisers, guests, contacts, comments, attachments, reminders, meeting links and other details. Of each event from five weeks back to twenty-seven weeks ahead, Koyomi reads only:

  • its identifier in that calendar, its title, its start and end or its length, whether it lasts all day, and the time zone it was written in;
  • whether it repeats, and how: its rule, the dates added to it or left out, and any occurrence that was changed;
  • whether it is cancelled or tentative, which version of it this is, and when it last changed.

Everything else in the calendar is dropped on our server as it is read. None of it reaches your device, and none of it is kept or written to a log. Koyomi also reads the name the calendar gives itself, if you give it no name of your own. A calendar link has no address for a single event, so Koyomi links to none.

Connecting an AI assistant

Connecting an AI assistant, such as Claude, ChatGPT or Grok, to Koyomi is optional. You choose which of your connected calendars it may read, one by one and for each assistant separately: none is chosen for you, and a calendar you connect later is not included until you choose it. The access is read-only. The assistant can list those calendars, read their events and look for free time in them. It cannot create, change or delete anything. It is in a private beta, and not yet open to every Koyomi account.

The assistant never receives your Google, Microsoft or Yahoo credentials, your Yahoo app password or a calendar link. It receives a token from Koyomi that works only for reading the calendars you chose, expires within minutes, is renewed only while you allow it, and stops working the moment you revoke its access.

While its access is in place, the assistant can ask Koyomi for those calendars at any time. It usually asks when you ask it about your time, but the assistant decides when to ask, and it may ask again later, in the same conversation or another. Each time, Koyomi reads those calendars from Google, Microsoft, Yahoo or the calendar link at that moment, and sends it, for each event, only its title, its start and end, whether it lasts all day or is tentative, and the name of its calendar. Koyomi sends no descriptions, locations or guests, and no identifier of the event. The events pass through our server on their way and are not stored there: Koyomi keeps no database of your events. Our server’s log of these requests records which kind of request it was and how many events were returned, never what they say.

Koyomi does not keep the events it sends to an assistant: they are read from your calendars when the assistant asks, passed on, and not stored on our server. What the assistant receives is then processed by the company that runs it, under that company’s own privacy policy and terms and your settings there, which Koyomi does not control. That company may keep it with your conversation, and whether it uses conversations to improve its models depends on its terms and on your settings there. For your Google calendars, see What your Google data is never used for, below.

What Koyomi does control is access from then on. The assistant can read only the calendars you chose, only with the access you gave it, which Koyomi checks on every request, and only until you revoke it. Revoking its access stops it reading more; it cannot take back what it has already received. Throughout, Koyomi’s handling of your Google data, including what it sends to an assistant, remains bound by Google’s Limited Use requirements, described below.

Your Koyomi calendar, the events you write in Koyomi, stays on your device and is never available to an assistant.

For each assistant you connect, our server keeps a record of which assistant it is (told by the address its sign-in returns to), when you connected it and last used it, the time zone of the browser in which you allowed it, and for each calendar you chose, which connected account it is in and a keyed hash of its identifier, never its name. The assistant’s tokens are kept only as keyed hashes. You can revoke an assistant’s access at any time in Koyomi, under Calendars, AI access: it ends at once, and its record is deleted. Revoking an assistant does not disconnect any of your calendar accounts, and disconnecting an account removes its calendars from every assistant’s access. The same can be done from any device, even one with no calendars on it, at app.koyomi.guru/ai/access.

To keep assistants within fair limits, our server also counts recent requests: those of each assistant, of each person across their assistants, and the registrations that come from each network address. Each count is kept under a keyed hash of what it counts, which cannot be turned back into it, holds nothing else, and is deleted within a day.

Where it is kept

On your device. The calendar names and identifiers and the event details above are kept in your browser, apart from your Koyomi calendar, so that they can be shown when you are offline, together with the address of each connected account, which calendars you chose to show and a note that a calendar is connected. For a calendar link, the device keeps the calendar’s name, never the link, and what the calendar’s server said of the version last read (its ETag and Last-Modified date), so that Koyomi can ask whether it has changed since. They are removed from the device when you hide a calendar, when you disconnect that account or remove that calendar, or when a different person signs in on that device.

On our server. Events pass through our server on their way from Google to your device. They are not stored there and are not written to its log. The server stores one record for each Google account you connect. It holds:

  • your 6Away identifier;
  • a keyed hash that stands for which Google account it is, so that the same account is not recorded twice. It is made from the account’s address and cannot be turned back into it;
  • the refresh token Google issued, encrypted with AES-256-GCM;
  • the permissions Google granted, and whether the connection is working;
  • when the record was made and last changed;
  • a count of recent requests, used to limit how often Google is asked.

It holds no email address, no calendar names and no events.

Each Microsoft account you connect has a record of the same kind: your 6Away identifier; a keyed hash made from the identifiers Microsoft gives that account, which cannot be turned back into them; the refresh token Microsoft issued, encrypted with AES-256-GCM; the permissions Microsoft granted and whether the connection is working; when the record was made and last changed; and a count of recent requests. Microsoft issues a new refresh token each time one is used, and the record keeps only the latest. Microsoft’s events pass through our server in the same way, and are not stored there or written to its log.

Each Yahoo account you connect has a record of the same kind, with one difference: in place of a refresh token, it holds your Yahoo email and the app password, with where that account’s calendars are at Yahoo, all encrypted together with AES-256-GCM, because Yahoo needs the email and the app password with every request. Its keyed hash is made from the account’s identifier at Yahoo. Yahoo’s events pass through our server in the same way, and are not stored there or written to its log.

Each calendar link you subscribe to has a record of the same kind: your 6Away identifier; a keyed hash made from the link, so that the same link is not recorded twice, which cannot be turned back into it; the link itself and the name the calendar is shown by, encrypted together with AES-256-GCM and bound to that record; whether the link is working; when the record was made and last changed; and a count of recent requests. The calendar’s events pass through our server in the same way, and are not stored there or written to its log.

Google’s tokens never reach your browser. The short-lived access token used to read your calendar is held only in the server’s memory. The same is true of Microsoft’s. A calendar link is decrypted on our server only while that calendar is being read.

Your Yahoo app password reaches our server once, when you give it, and never comes back to your browser: it is not shown again, not sent back in any answer, and not kept on your device. While it is in use it is held in the server’s memory for a few minutes at a time. Your browser or password manager may offer to save it for you; whether it does is between you and them, and Koyomi has no part in it.

Signing in with 6Away

Koyomi asks you to sign in only when you connect a calendar. Sign-in is provided by 6Away.

To keep you signed in, Koyomi sets a sign-in cookie in your browser, for up to thirty days. It is an HttpOnly cookie, which page scripts cannot read. The session it carries can contain your 6Away identifier, your name, your email address and your sign-in credential. Of these, our database keeps only the identifier.

How your Google data is protected

Koyomi protects your Google user data with these technical and organisational security measures:

  • Google’s refresh token is encrypted with AES-256-GCM before it is stored, and bound to your own record, so that a copy moved to another record cannot be decrypted. The encryption key is kept only in the server’s settings, separate from the database that holds the tokens.
  • Everything is sent encrypted, over HTTPS (TLS): between your browser and Koyomi, and between Koyomi’s server and Google, 6Away and the database. A visit over plain HTTP is redirected to HTTPS, and browsers are told to use only HTTPS for Koyomi.
  • Each connection can be used only by the person who made it. The server knows who is asking only from their sign-in cookie, and looks for a connection only among that person’s own. Asking for anyone else’s finds nothing.
  • Google’s tokens never reach your browser. Your events are not stored on our server, and neither tokens nor events are written to its log.
  • Koyomi holds read-only permission only, so nothing it does can change your Google Calendar.
  • On your device, the copy of your Google calendars and events is kept in your browser’s storage for Koyomi, which other websites cannot read.
  • Only the people who run Koyomi at 6Away can reach the production server’s settings and its database.

Disconnecting an account removes what Koyomi holds of it, as described below.

The same measures protect your Microsoft calendar data, and the calendars you subscribe to by link, with their links.

The same measures protect your Yahoo calendar data and app password.

What your Google data is never used for

Your Google Calendar data is not sold. It is not used for advertising, not used for analytics or to build a profile of you, and not used to train artificial-intelligence or machine-learning models. It is not given to anyone for purposes of their own. The only companies that handle any of it are the three named below, and each handles only what is said there, unless you connect an AI assistant yourself.

Connecting an AI assistant is the one way Koyomi sends Google Calendar data to another company, and it does so only because you ask it to: if you choose a Google calendar for an assistant, Koyomi sends that calendar’s events to the assistant when it asks, as described under Connecting an AI assistant, so that the assistant can answer you, and for nothing else. Sending them is itself bound by Google’s Limited Use requirements below: only the calendars you chose, only the details listed above, only for the feature you chose, and only while you allow it. You can revoke the assistant’s access at any time.

Koyomi does not use your Google Calendar data to develop, improve or train AI or machine-learning models, and does not send it to anyone for that purpose. Google Workspace APIs are not used to develop, improve, or train non-personalized AI and/or ML models. Koyomi cannot control what an assistant’s company does with what it has received: some assistants’ personal plans use conversations, including what apps send them, to improve their models unless you turn that off in the assistant’s settings. Check your assistant’s data settings before you choose a Google calendar for it.

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

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

The same is true of your Microsoft calendar data, and of calendars you subscribe to by link: they are used only to show your events beside your own, and for nothing else.

The same is true of your Yahoo calendar data. Koyomi does not use your Yahoo app password for anything but reading your calendars, and has no access to your Yahoo mail or email content.

Who helps us run Koyomi

Koyomi runs on services from three companies. What each one handles is different:

  • Vercel hosts the website and the server. Your Google Calendar events and calendar names pass through that server on their way from Google to your device. They are not stored there.
  • Neon hosts the database, in the United States. It stores only the connection records described above. It receives no events and no calendar names. It also stores the records of the AI assistants you connect, described above, which hold no events and no calendar names either.
  • 6Away provides sign-in. It learns that you signed in to Koyomi. It does not receive your Google Calendar events, your calendar names or Google’s tokens.

As infrastructure providers they process technical information, such as IP addresses and request logs, in order to deliver and protect the service, under their own terms and privacy policies. Your calendar itself comes from Google, under Google’s own terms.

A Microsoft calendar comes from Microsoft, under Microsoft’s own terms. Its events and calendar names pass through Vercel’s server in the same way, and are not stored there. Neon stores only the connection records described above, and receives no events and no calendar names. 6Away receives none of them, and none of Microsoft’s tokens.

A Yahoo calendar comes from Yahoo, under Yahoo’s own terms. Its events and calendar names pass through Vercel’s server in the same way, and are not stored there. Neon stores the connection records described above, with the app password encrypted, and receives no events and no calendar names. 6Away receives none of them, and never your app password.

A calendar you subscribe to by link comes from wherever it is published, under that service’s own terms. Our server fetches it from there; its events and name pass through Vercel’s server in the same way, and are not stored there. Neon stores only its record, with the link encrypted. 6Away receives none of it.

How long things are kept, and deleting them

Our server keeps nothing of your Google data except the connection records described above. A connection record is kept until you disconnect that account or ask us to delete it. The copy on your device is kept until you hide that calendar, disconnect that account, or a different person signs in on that device.

Each connected account has its own Disconnect, in Koyomi’s Calendars pane. It asks Google to revoke Koyomi’s access to that account, deletes that account’s record from our server and deletes the device’s copy of that account’s calendars. Your other connected accounts are not affected. Disconnecting the last one also signs that device out. Another device on which you had connected removes its own copy the next time it is signed in and checks. Your Koyomi calendar is not touched.

If you remove Koyomi’s access in your Google Account instead, Koyomi can read nothing further from that account. Its record stays on our server, marked as needing reconnection, until you reconnect or disconnect.

A Microsoft account’s Disconnect deletes its record, with the only copy of Microsoft’s refresh token, from our server, and deletes the device’s copy of that account’s calendars. Microsoft gives apps no way to withdraw their own access, so Microsoft goes on listing Koyomi among the apps that account has allowed until you remove it there: for a personal account, among the apps and services in your Microsoft account’s privacy settings; for a work or school account, in My Apps (myapplications.microsoft.com). Without the token, that access cannot be used. If you remove Koyomi there first, Koyomi can read nothing further from that account once the short-lived access token it holds has expired, at most about an hour later, and its record is then marked as needing reconnection.

A Yahoo account’s Disconnect deletes its record, with Koyomi’s only copy of the app password, from our server, and deletes the device’s copy of that account’s calendars. Koyomi cannot cancel the app password at Yahoo: it goes on working there until you delete it, in your Yahoo account’s security settings, under External connections. If you delete it there first, Koyomi can read nothing further from that account, and its record is marked as needing reconnection until you reconnect with a new app password, or disconnect.

A calendar link’s Remove calendar deletes its record, with Koyomi’s only copy of the link, from our server, and deletes the device’s copy of that calendar. It does not stop the link working: Koyomi cannot withdraw a published link, and does not claim to. To stop the link itself working, turn off or reset that calendar’s publishing where it lives (for Outlook, in its calendar sharing settings). If a link stops giving a calendar, Koyomi marks it as needing an update and keeps what it read until you update or remove it.

An AI assistant’s access is kept until you revoke it, or allow the same assistant again, which replaces it. Either way its record is deleted from our server. (An assistant that registers itself anew each time it connects, as Grok does, is a new one each time: its earlier access stays until you revoke it.) It is not removed when an account it could read is disconnected: only that account’s calendars are.

You can also ask us to delete the record by writing to privacy@6away.ai.

To delete your Koyomi calendar, delete its events in the app, or clear the site’s data in your browser.

Questions and requests

Write to privacy@6away.ai to ask what we hold about you, to have it deleted, or with any question about this page. How to connect, revoke and remove things yourself is on the Help page.

Changes to this page

If this page changes, the new version is published here with a new date.