Legal

Privacy

What TimeLoop stores, what it sends to whom and why, how Google user data is used and protected, and how to delete everything.

Last updated 5 November 2026.

What TimeLoop stores

Your commitments, goals, preferences and plans, so your day survives a refresh and a new phone. Guests get an anonymous account; signing in with Apple or Google links the same account to an identity so it can be restored.

Voice and text

What you type is sent to our server, which uses a language model from OpenAI to recognise commitments and times; the text and what was recognised are kept with your request log so you can correct it. When you write several notes in a row, the last few of them and what TimeLoop showed in reply go along, so that move it to nine is understood. The names of your open tasks go along too, so the same task is not added twice. If you share a task list with a circle, the names of those lists and the open lines on them, including lines other members wrote, go along as well, so that I bought the eggs finds the right line. The rest of your plan (your calendar events and their times) is not sent to the model: answers about it are worked out on our server. When you speak, your phone’s own speech recognition (Apple on iPhone, Google on Android) turns it into text; depending on the phone and language, Apple or Google may process the audio on their servers. So that names are written correctly, the phone’s recogniser is given the names of places, people and events from your current week. Where server transcription or the live voice conversation is switched on, your audio is sent to OpenAI to be written out or answered; we do not keep the audio. Events read from your calendars are not sent to the language model.

Calendars and reminders

With your permission TimeLoop reads the calendars you choose and your open reminders, with those you ticked off in the last week, and writes your confirmed plan into a dedicated TimeLoop calendar. Participants of imported events are shown to you only. You can choose per category whether shared events show titles or just Busy.

Google user data

This section says exactly which Google user data TimeLoop accesses, how it uses that data and how the data is protected.

Google user data TimeLoop accesses

  • When you choose Continue with Google (permissions openid, email, profile): your name, your e-mail address, your Google account ID and the picture of your Google account.
  • When you also connect Google Calendar, which is optional and asked separately (permissions calendar.events and calendar.calendarlist.readonly): the list of your calendars (their names and which ones you keep visible), and the events of the calendars you keep visible: title, date and time, place, video link, and the names, e-mail addresses and answers of guests.
  • TimeLoop does not access your Gmail, contacts, Drive files or any other Google data.

How TimeLoop uses Google user data

  • Your name, e-mail address and Google account ID are used to sign you in and to give you your account back on a new phone. Your picture becomes your profile picture, shown to the people who share a circle or an event with you; you can replace or remove it.
  • Your calendar events are shown in your day and week, and TimeLoop plans your tasks and goals around them, so nothing is placed on top of an event. TimeLoop does not move or change events it has read.
  • TimeLoop writes to your Google Calendar only when you ask: when you create a Meet link for an event or invite people by e-mail, that one event is added to your calendar, kept in step when you move or cancel it, and Google sends the invitations; and when you answer an invitation in TimeLoop, your answer is saved on that event and Google tells whoever invited you. If you choose to tell the others that you are running late for such an event, a short note (for example Running about 15 min late) is saved with your answer on that event. Google shows it to whoever invited you and tells them by e-mail.
  • Your Google Calendar is read when you open TimeLoop and, while you have used the app in the last two weeks, on its own in the background, so that an invitation reaches you in time. For this TimeLoop asks Google to tell it when your calendar has changed; that message carries no event details.
  • With TimeLoop Pro, the place of an event that reads like an address (a street and number, or a postcode) is looked up on Photon, komoot’s search over OpenStreetMap, so that TimeLoop can measure the way there and tell you when to leave. Only the words of the address are sent, never the event’s title, time or guests or who you are. It is used for nothing else.
  • If you join a circle, its members see when you are busy. Titles are shown only as you chose in your sharing settings, and an event you mark private is only ever shown as busy.
  • TimeLoop does not sell Google user data, does not share it with advertisers or data brokers, does not use it for advertising, and does not use it to develop, improve or train AI or machine-learning models. Events read from Google Calendar are not sent to our AI provider: it only receives what you say or type, and the names of tasks you created in TimeLoop yourself.

How Google user data is protected

  • Everything travels encrypted (HTTPS/TLS) between your phone, our server and Google.
  • The access Google gives TimeLoop to your calendar (the access and refresh tokens) is stored encrypted (AES-256) on our server only. It is never sent to your phone or to anyone else’s.
  • The data is kept on our own server in Germany, in a database that cannot be reached from the internet. Only the people who operate TimeLoop can access the server, and only to keep the service running.
  • Every request is checked against the signed-in account, so an account can only ever read its own data.
  • TimeLoop asks for the narrowest permissions that make the feature work, and for the calendar only when you choose to connect it.

Keeping and deleting Google user data

Google user data is kept only while your account is connected. Disconnecting in Profile → Calendars makes Google forget the access and removes the imported events from TimeLoop. Profile → Delete account & data removes everything, including your name, e-mail address and picture, immediately. You can also revoke the access at any time in your Google Account under Security → Third-party access.

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

Notifications and circles

If you allow notifications, your phone’s push token is stored so TimeLoop can tell you about invitations and answers in your circles, and, with TimeLoop Pro, when it is time to leave for an event whose way our server knows; it is removed when you sign out. Members of a circle see when you are busy. Titles follow your sharing choices, and an event you mark private is only ever shown as busy. If you choose to tell a circle that you are running late, the other members who are coming get a notice with your first name, the event’s name and the number of minutes, or the words that you can’t make it.

Places and location

When you search for a place, the words you type are sent to a map service to find it: on iPhone to Apple Maps, straight from your phone; on other devices through our server to Photon, a search over OpenStreetMap run by komoot, together with a rough area (about ten kilometres) so nearby places come first, and without anything that identifies you. The place you pick (its name, address and point on the map) is stored with your event, and people you share the event with see it. When the forecast is switched on, the name of a place you typed for an event of your own, when it has no point on the map yet, is looked up the same way on iPhone, to find the area the weather is for; places written in events from your calendar are not looked up for the weather. An address written in an event of your phone’s calendar is looked up on Apple Maps, from your phone, so that the way there can be measured and a maps app opens the exact spot. With TimeLoop Pro, an address written in an event that reaches our server without a point on the map (events from Google Calendar and Outlook, and from your phone’s calendar on Android) is looked up by our server on Photon, the search over OpenStreetMap that komoot runs at photon.komoot.io, so that you can be told when to leave for it. Only the words of the address are sent, with a rough area around your home (about ten kilometres) when you set one; never the event’s title, time or guests, and nothing that identifies you. Only a place that reads like an address is looked up, with a street and number or a postcode; a meeting room, a call or a link never is. The point found is kept with the event. Our server then measures the way to it from where your way starts (the start you chose for that event; for today, where your phone last was; otherwise work during your working hours, or home), by asking Google’s Routes service with the two points rounded to about a hundred metres, or by the distance when it cannot ask; with none of these known nothing is measured. Your location is used only if you allow it and only while the app is open: to measure the way to a place and tell you when to leave, and for the weather where you are. For the way, on iPhone it goes from your phone to Apple Maps. So that today’s time to leave is counted from where you are on every device, and the alert to leave can come with the app closed, your phone also sends our server its position, rounded to about a hundred metres. It is kept only in a short-lived cache, never in the database, for at most half a day; it counts as where you are for two hours, and it is deleted with your account. On Android the way is measured by our server, which asks Google’s Routes service: for that your phone sends our server the two points, each rounded to about a hundred metres, and Google is sent those two points, how you travel and the hour, never who is asking; the answer is held briefly and not kept with your account. On Android, the name of a place you typed for an event of your own is found through our server’s place search, as described above. For the weather, only a rounded area leaves your phone, as described below. A home or work place you set for measuring travel time (its name, address and point on the map), and how you usually travel are kept with your account, so your other devices (another phone, the Mac app, the web app) plan from the same place. They are used only to measure the way and tell you when to leave, never shown to anyone else, and deleted when you remove them or delete your account. A start you choose for one event (home, work or another address) is kept with that event in TimeLoop and never written to your calendar. Separately, there is Traffic before you leave (part of TimeLoop Pro), which you switch on yourself. While it is on, our server keeps your home and, if you set it, your work, each rounded to about a hundred metres, and how you travel. It looks at the traffic once before each drive in your plan by asking Google’s Routes service about the way from where your way starts, as described above, and sends you a notification if you need to leave earlier. Switch it off and all of it is deleted.

Weather

When the forecast is switched on, TimeLoop shows the weather for your events and days. Our server asks MET Norway (the Norwegian Meteorological Institute) for the forecast of an area of about ten kilometres around the event’s place or, when you allow location, around where your phone is. For that your phone tells our server only that rounded area, never your exact position, and the area is not kept. The request to MET Norway comes from our server, not from your phone, and carries nothing about you. If you mark a goal as not in the rain, your phone also tells our server the hours for which rain is forecast in the next few days where you are (the hours only, not the place), so that goal can be planned outside them. Those hours are kept with your account, replaced each time the forecast is read again, and no longer used after most of a day without news from your phone. Weather data: MET Norway, CC BY 4.0. You can switch the forecast off under You.

How you feel, and sleep and recovery

Your answer to How are you feeling? is kept on your phone, with your answers of the last two weeks, and nowhere else. When you ask for a lighter day, your phone sends our server one number, how much the day should carry. It is used for that one plan, held for at most half an hour while you look at the before and after, and not saved with the change or with your account.

Sleep and recovery (optional). If you switch on Suggest from sleep and recovery, TimeLoop reads last night’s sleep, your resting heart rate, your heart-rate variability and today’s workouts from Apple Health (iPhone) or Health Connect (Android). They are read and worked out on your phone only: they are never sent to our server, never shared with anyone and never used for advertising, and TimeLoop writes nothing to Apple Health or Health Connect. Switching it off stops the reading at once; you can also take the permission back in the Health app or in Health Connect.

Your rhythm

If you switch on Rhythm (a repeating cycle: your menstrual cycle, a training block, shifts or a sprint), it is kept with your account, encrypted, so you see the same one wherever you sign in to TimeLoop: its kind, its length, how long a period lasts, its colours and the days a cycle started. It is never sent to OpenAI or anyone else, never shown to your circles and never used for advertising. Deleting rhythm data, or your account, removes it everywhere. If you write about your cycle in the chat, that sentence is read by OpenAI like every other note, only so the Rhythm page can be opened for you, and its words are not kept.

Periods from Apple Health or Health Connect (optional). If you switch on reading periods from Apple Health (iPhone) or Health Connect (Android) on the Rhythm page, your phone reads the days of menstrual flow recorded there and keeps only the first day of each period in your rhythm, marked as read from Health. Nothing else is read for it and nothing is written back. Switching it off stops the reading; the starts already read stay in your rhythm until you remove them or delete rhythm data.

Profile picture

If you sign in with Google, TimeLoop takes the picture of your Google account; you can also choose a photo yourself, or remove the picture, under You. We keep only a small square copy of it on our server (the original is not stored), and it is shown to the people who share a circle or an event with you. It is removed when you remove it or delete your account.

Inviting by e-mail

When you are signed in and invite someone to an event by e-mail without Google connected, TimeLoop sends that person one message with the event’s name, time and place and your name, through our mail provider (Mailgun, EU region). Their address is kept with the event so you can see their answer and so they hear when the event moves or is called off; it is removed with the event or your account. The link in the message shows only that one event and lets them answer without an account. Anyone can ask not to be written to again: we then keep only a scrambled form of the address, enough to never send to it again. To keep this from being misused, only signed-in accounts can invite, and the number of messages is limited per event, per account and per address. With Google connected, the invitation is sent by Google from your own account instead.

Your booking link

If you make a booking link (trytimeloop.com/@yourname), its page shows only what you chose for it: the name you show, a few words about yourself if you wrote them, your profile picture if you switched that on (otherwise your initial), the link’s title and your free times. It never shows your e-mail address or what is in your plan: no titles, places or people. The free times are worked out from your plan on our server when the page is opened.

Someone who asks for a time needs no account. They give a name and an e-mail address, and their browser sends its language and time zone, so that the letters about the request are in their language and their time. That is all we take from them, and only to ask for that time. You see the name and the address with the request, in the app. Through our mail provider (Mailgun, EU region) they get one letter saying the request was sent, with a link to withdraw it while it waits, and later a letter with your answer: a kind no, or another time to take or turn down. A yes is your invitation to the event, sent as described under Inviting by e-mail. One address can have three requests waiting at a time, and gets at most four letters a day from TimeLoop altogether. Every letter has a link to get no more letters; we then keep only a scrambled form of the address, enough never to write to it again. Nobody is sent marketing, and no account is made for them.

Their name and address are deleted when you decline or they withdraw, when a request that was never answered reaches its time (we check every hour), and, for a request you accepted, with the event or your account. The page and its letters are counted as numbers only: how often the page was opened, how often it was opened from the link’s square code, how many requests came, how often the store buttons were tapped, and how many Android installs came from them. Nothing in those numbers says who.

Contacts

When you invite someone to an event you can choose them from your phone’s contacts, or switch on suggestions while you type. Your contacts are looked up on your phone and are never sent to our server; only the address of a guest you invite is stored, as when you type it. Suggestions ask for the phone’s permission when you switch them on, and you can switch them off again at any time.

How the app is used

To know which parts of TimeLoop matter and what to make better, TimeLoop keeps a record of use on our own server: which screens are opened and for how long, and which kinds of actions are taken (for example an event was added or a day was replanned), each with your account, the time, whether the phone is an iPhone or an Android, and the version of the app. Only the kind of screen or action is recorded, never what you wrote, the names of your events, or anything from your calendar. From it we count things such as how many people come back and which features are used. Nothing of this goes to an analytics or advertising company, and the record is deleted with your account.

The same record of use also goes to Sumly, our own analytics on a server of ours, so we can see how people find TimeLoop and which parts they use before and after they buy Pro. There it is kept under the number RevenueCat knows your account by, with your country and the kind and version of the app. When you are signed in, our server also keeps your name and e-mail address in Sumly, so we know whose it is and which purchase is whose. A guest who has not signed in is not named. If you change your name or address, Sumly is told the new one, and when you delete your account, it is removed from Sumly too.

The first time an account is used with a new install of the app on a phone or a Mac (when you sign in, or when the app opens still signed in after it was installed again), the app also tells Sumly how it came onto that device, once for each install. On Android this is the referrer Google Play gives the app: the page and source that led to the download, such as a page of this website or a search in the store. It is kept with your account and deleted with it. An iPhone or a Mac has no such referrer. Instead, our server passes the device’s IP address to Sumly with that one message, and Sumly uses it once, as a hash, to match it with a tap on an App Store button of this website in the hour before. The address itself is never stored, by our server or by Sumly. In a browser (app.trytimeloop.com), the first sign-in passes on the code Sumly’s cookie gave that browser on this website, where the cookie is allowed (see This website), so the visit that led to it is known as yours.

TimeLoop Pro

Purchases in the apps are handled by the App Store or Google Play; a purchase at app.trytimeloop.com is paid by card through Stripe. In neither case do we see or keep your card number. For a card payment Stripe receives the e-mail address you type at the checkout, your card details, your country and your IP address, and keeps them under its own privacy policy as a payment provider; we learn from it that the payment was made, the amount and the country. A service called RevenueCat tells our server whether an account has Pro. It knows the account only by a number, not by your name or e-mail address. So that the free days of Pro are given once per phone, the app keeps a random word on your phone and says it to our server when an account is created there. The word says nothing about you or the phone, and we keep only a scrambled form of it.

Look it up

When you ask TimeLoop to look something up about an event or a task, your question goes to our server together with that one event’s name, time and place, your time zone, and the last few questions and answers about it. Our server passes this to a language model from OpenAI, which searches the web for the answer. The answer and its sources are kept with the event so you can read them again; when you remove an answer, or the event itself, what you asked and what was found are erased. Nothing else of your plan is sent, nothing is looked up unless you ask, and events read from your calendar cannot be looked up at all. There is a limit to how many questions can be asked in a day.

Connecting an assistant

You can connect an assistant of your own, such as ChatGPT or Claude, to your TimeLoop account, and only you can: it is off until you add TimeLoop in the assistant and say yes on a page of ours, in a browser where you are signed in. That page names the assistant and lets you choose whether it may only read or also change your plan. A plan kept on a phone without signing in cannot be connected.

A connected assistant can read what your own account holds: your events with their times, places, notes and the people in them, your tasks and the lists you share, your goals, and your circles with when their people are free or busy (never what they are doing). If you allowed it, it can add, change, finish and delete those things for you; deleting needs your yes as a second step. It cannot see how you sign in, your payment details or anyone else’s account, and it cannot connect calendars, buy anything or delete your account.

What an assistant reads this way goes to the company that makes it (OpenAI for ChatGPT, Anthropic for Claude, or whoever makes the one you chose) and is kept under that company’s own terms and privacy policy, as part of your conversation there. We do not receive your conversation: our server receives the requests the assistant makes. For each request we keep which tool was called, when, through which assistant, whether it worked and how long it took, for up to 180 days. We do not keep what was asked or what was answered. One tool hands a sentence to our own language model (see Voice and text above); it is part of TimeLoop Pro and is used only when the assistant calls it.

An assistant holds a key of its own that stands for your account and nothing else. We keep only a fingerprint of it, it is renewed every day, and it stops working when it has not been renewed for 90 days. You see every assistant you connected, and disconnect one, in TimeLoop on the web under Settings → Assistants; it stops working at once and what we kept about the connection is erased within 30 days. Deleting your account removes them all immediately.

This website

If you sign in to TimeLoop in a browser (app.trytimeloop.com), that browser keeps two cookies of ours: one keeps you signed in and cannot be read by any page, and one says only that you are signed in, so that this website can offer Open TimeLoop instead of Sign in. Neither is used to follow you, and both go when you sign out.

Visits to this website (not the apps) are counted with Sumly, our own analytics. The pages that open an invitation are not counted, because their addresses carry a private link. In the EU, the rest of the EEA, the UK and Switzerland, and wherever your browser sends Global Privacy Control, it sets no cookie: a visitor is told apart for one day only, by a code made from the request that changes every day and is not kept. Elsewhere it keeps one cookie of ours, sumly_vid, for 13 months from your first visit and never extends it, so that a visitor who comes back is recognised as the same one. Your IP address is not stored: the country and city are read from the request and kept without it. It is used only to see which pages and which sources bring people to TimeLoop. What the apps send to Sumly is under How the app is used.

The waiting list

If you leave your e-mail address on trytimeloop.com to hear when the app is out, we keep that address, the country and language your browser reported and the page you were on, on our own server. It is used for one e-mail when TimeLoop is in the stores, is shared with nobody, and that e-mail carries a link that removes your address at once. Where the form is protected by Cloudflare Turnstile, Cloudflare checks that a person is filling it in; no advertising or tracking comes with it.

Deletion

Profile → Delete account & data removes everything immediately. Nothing is sold, no advertising identifiers, no tracking across apps. Delete your account says how on every device, and what to do if you cannot sign in.

Contact

For privacy requests, write to [email protected].