IAM ("we") is operated by Wyrd Media Labs, India. This policy explains what IAM collects, why, who receives it, how long we keep it and what you can do about it. Questions: automation@justgotwyrd.com.
What we collect
- Your account: email address, optional name, time zone, languages and settings (such as nudge limits, quiet hours and work domains), and what you tell IAM about yourself, once you add it: your city and your working hours. IAM also keeps how you want it to ask (as things happen, or at the check-in times you choose), which features it has offered you and your answer, whether you closed the day or put off today's page, the days you opened IAM's Today, and whether you filled in or skipped days you were away (dates only).
- Your devices: each signed-in device's name, platform, app version, its clock offset, and a push-notification token for phones.
- Activity from the IAM apps: which app or website domain is in use and when, idle, lock and sleep times, whether a call has the microphone or camera on, and on phones which app is in the foreground, and when the screen turns on, turns off or is unlocked. Window titles never leave your device: we only receive keywords from them that match your own projects and people.
- Places, only once you add a place: the names you give your places (like "Office") and the Wi-Fi network names you save for them, the Wi-Fi network names you answer "Not a place" for, and which of your places each stretch of your day was at and when, as your devices noted it. That is location information about you, so we list it here as precise location. To note it, the phone app uses your phone's precise location and the name of the Wi-Fi it's on, only while IAM is open on it, and compares them with your places on the phone; a place's spot (its coordinates) stays on the phone that set it, is never sent to us, and is deleted when you sign out there. The desktop app reads the name of the Wi-Fi network the computer is on and compares it with your places on the computer; the name reaches us only if you save it to a place. We never store coordinates and never work out what kind of place something is. We use it only to show where your time was; turning Places off stops it on every device.
- Places found on their own, only once you turn it on in the Android app: the same place names on your stretches as above, noted when your phone arrives at and leaves the places you named, even while IAM is closed. To do this the app asks Android for your location "all the time", and Google Play services tells it only when the phone crosses the edge of one of your places (a geofence around the spot saved on the phone): IAM never follows where you go between them, and the spots still never leave the phone. Turning it off stops the background location at once.
- Health Connect, only once you turn on Health in the Android app: from Health Connect, and only the kinds you allow on its own screen: when you slept, when your workouts were and what kind they were (a walk, a run, a ride, a swim, strength training, yoga, a sport or another workout), each day's step count (today's so far too), and, if you allow them, each day's calories burned and calories eaten (the number only, where an app notes your meals), your weight (each day's latest) and your height (the latest). We keep the sleep and workout times as inputs that put them on your day as IAM's guess, and the steps, calories, weight and height as numbers you can change or delete. In Body, and only once you switch a reading on under “Bring in readings” and allow it on Health Connect’s screen, IAM also reads your blood pressure, blood sugar (a meter’s or a sensor’s), oxygen, resting heart rate and its variability, body fat, temperature and the days of your periods, each as a reading you can change or delete (OD626). IAM never reads your routes, what a meal was, notes or medical records, never writes to Health Connect, never reads it in the background, and never uses health data for ads or shares it with anyone. Turning Health off stops reading; "Delete what Health brought" in Connections deletes all of it.
- Spends from payment notifications, only once you turn it on in the Android app: when a payment app (Google Pay, PhonePe, Paytm, BHIM, CRED and a few others) or your bank's SMS shows a notification that you paid, the app reads, on your phone, only the amount, who you paid and the app, and sends that as a spend on your day as IAM's guess. The notification's words, account numbers, reference numbers and codes are never kept or sent, every other app's notifications are left unread, and IAM never asks for permission to read your SMS. It uses Android's Notification access, the same one the capture button uses. Turning it off stops it at once; each spend can be changed or deleted.
- Numbers from your contacts, only once you turn it on in the Android app: to show a person's number on their page, the app looks for the people you have in IAM among your phone's contacts, by name, and you confirm which contact is them. This happens only on your phone: your contacts, their numbers and which contact you linked are never sent to us, and a number shows only if it is already saved in your contacts.
- Phone calls, only if you turn on Calls in the Android app: when each phone call started and ended and whether it was incoming or outgoing, who you say it was with (one of your own people) and what you say it was about. From the phone the app reads only each call's start, end and direction (the phone's call state): never the phone number, your call log or your contacts, and it never records a call. We use it to put your calls on your timeline and to ask you about them; turning Calls off stops it on every device.
- Things you share to IAM from another app (Android): the text or link exactly as you shared it, when you saved it, and the project and people you filed it under. IAM never opens a link you share.
- Voice and typed logs: the recording or text you send, its transcript and what IAM understood from it (activity, project, people, times, and the log's type, tags, amount and the reminders you asked for), and, while their switches are on, IAM's estimates of the calories, caffeine and nicotine in what you log, worked out from what you log. A log you say in Journal mode, or one IAM puts in your journal because you turned that on, goes to your journal instead of your timeline.
- Snap your food, only when you take a photo: the photo of your food, from which IAM's AI names the dishes and estimates the calories, saved as a food log. The photo (and a small copy for lists) stays with its log until you delete the log or your account, and is in your data export.
- Your journal, if you keep one: the pages you write or say, the word you choose for a day, and each journal recording: its audio until it is turned into text, the words heard, and what it changed on its page. Whether Insights may read your journal (off unless you turn it on).
- Your timeline and lists: the blocks and layers IAM builds, your edits, the plans you make (what, when, and whether they were done), life areas, projects (the areas you mark each with, whether you keep it private, and your notes on it), the people you add (names, aliases, email addresses, relationship, and what you call them, such as "Mom"; only you see it), your groups (their names and who is in each), the moments you add (what you counted, noted, promised or decided, and when), what you measured (such as your weight or a spend), each log's type, tags and amount (such as a distance, your weight, or money you spent, saved, lent or borrowed, and with whom), your tags, the reminders you set or say (what, when and your answer), rules, your answers to nudges, and your answers to IAM's questions about the life areas it guessed (the app or site asked about, the area you chose or that you kept IAM's guess, and when).
- Google Calendar, if you connect it: see "Google user data" below.
- Outlook, ClickUp, GitHub, Linear, Jira and Notion, only if you connect them: the account you connected (its identifier at that service, and its email, username, workspace or site name), the permissions it granted, and its access tokens, which we keep encrypted. From Outlook, your calendar's events, as for Google Calendar: each event's title, start and end, attendees' email addresses, names and replies, your own reply, whether it is an online meeting, and whether it is marked free or out of office, never its notes or attachments; they are used the same ways, and the titles, times and attendees' names of events near a log are sent to OpenAI with it (see "Google user data"). From the others, only your own work, to name the stretches of your day: your ClickUp time entries (their task's name and times); your GitHub pushes, pull requests and reviews (repository, number, title and time, never code or commit messages); the Linear issues assigned to you and when you changed their status; your Jira worklogs and the status changes you made to issues assigned to you; and the Notion pages you share with IAM, with their titles and when you last edited them. Nothing from these work tools is sent to OpenAI, and IAM never changes anything in any of them.
- Spotify and Gmail receipts, only if you connect them; YouTube history and Maps Timeline, only if you import your own file: from Spotify, the tracks you played (song, artist, when); from Gmail, only receipt and order emails, and from each only its total, currency, the sender's name and when, never its subject, words or addresses, read by rules on our server and never sent to AI; from your YouTube or Maps export, read on your phone, only each video's title, channel and time, or each visit's or trip's kind ("At home", "Driving") and times, never coordinates or addresses. They become IAM's pencil guesses on your day. The weather, only while you turn it on: your approximate location (to about a kilometre) is sent with each request to the Norwegian Meteorological Institute (MET Norway), whose data it shows, and not kept; with "Weather on logs" on, the weather when you made a log (like "Rain · 27 °C") is added to it as a tag. Your phone number, only if you add it (typed, or picked from your phone's SIM): saved for you alone, marked as not proved, and nobody can find you by it. Only a number proved with a code our SMS service sends makes you findable by people who have that exact number; then IAM keeps only a one-way keyed fingerprint of the number, never the number itself.
- Sign in with Google, if you use it: your Google account's email address and account identifier.
- AI assistant connections, if you make them: which assistant (Claude or ChatGPT) you connected, its permissions, and the logs you create through it.
- People, only once you turn it on: the name you choose to show the people you connect with (when you sign in with Google, the name Google gives, if it gives one, until you choose your own); whether people may find you by your exact email ("Let people find me"); your email addresses (to start with, the one you sign in with); the people you ask to connect with, the requests you get and the connections you make (who asked whom, when, and how: by email or an invite link); if you answer "Same person?", which of your own people they are; the invite links you make (when each was made, used or taken back; only a scrambled form of its code is kept); and, for each meeting or call you and a connected person are both in, a copy on their day of its kind (meeting or call), start and end, and who else in it they are connected with too, with their answer to it ("Looks right" or "I wasn't there"), which only they see.
- How you use Insights: how many times a day you open Insights in the phone app (a number for each day, nothing about what you looked at), so we can tell whether it helps; and the Mondays your week summary notification was sent. Both are in your data export and are deleted with your account.
- What you capture on your phone, only once you turn on the capture button (Android): each time you tap IAM's floating button, the app in front and when; while it then follows that app (until you leave it, the screen turns off or you press Stop), the title of the video, song or podcast playing, its channel or artist, and how far into it you watched (this needs Android's Notification access, which IAM uses only to read what is playing, only while following, and, while "Capture what's on screen" is on too, to remember each WhatsApp chat's name and the action that opens it, in the phone's memory only and never a message, so a capture of that chat can reopen it), and the moments you mark with another tap (the video's second, or the minute); if you also turn on "Capture what's on screen" (Android calls it Accessibility), each page's title and link in a browser, an email's subject and sender, a doc's or channel's title and a chat's name, as they show, only while following; and the links you share to IAM. If you also turn on "Remember the words on screen", at a moment you mark the words on the screen (the text the app shows, and words inside a picture or video on it) are read on your phone and only the words are kept with the capture: the picture of the screen used to read them is deleted at once, never kept or sent. If you also turn on "Instagram's link, by itself", a tap over an Instagram reel copies the reel's link for you (your clipboard keeps it) and sends IAM a picture of the reel you capture, only with your agreement to AI reading: it is read once by OpenAI to say in one line what the reel shows, and deleted as it is read (one never read is deleted after an hour); only that line is kept with the capture. Apart from WhatsApp chat names, nothing is read while the button isn't following an app you pressed it in. Opening a WhatsApp capture looks the chat's name up in your phone's Contacts, on the phone only: no contact or number is ever sent to IAM. What you share to IAM (Android): a link is kept as a capture; a text becomes one of your logs, read like the others (with your agreement to AI reading); an image, such as a receipt or a screenshot, is read for its words on your phone only (by Google's on-device text recognition, part of Google Play services), and its words open in IAM for you to keep as a note or not. The image itself is never sent to IAM's server, to OpenAI or anywhere else, and isn't kept. IAM never reads message or email bodies, anything you type, password fields, banking and payment apps, password managers, or the apps you made private or excluded. Captures are shown on your day, are in your data export, and are never sent to OpenAI (apart from that one picture of a reel). Holding the button records a voice log, as the mic does, and what you say during a capture is kept with it (read like any log; what was captured is never sent with it).
- Meetings you capture, only once you turn on meeting capture: while you are in a Google Meet, Microsoft Teams or Zoom call (in your browser with IAM's extension, and later in the desktop app or with the phone's capture button), IAM reads the captions the meeting app itself shows. It turns the meeting's own captions on for you, as anyone in the call can; it never records audio or video. Only with "Capture shared screens" on, it sends pictures of the shared slides: the shared presentation only, never anyone's camera, a picture each time it changes. It keeps each caption line exactly as shown, with who said it and when (Hindi kept as captured and shown to you in Latin letters), the meeting's title, its web address without anything after a "?" (so never a passcode), when it started and ended, the marks you make on lines, your private note, and counts of how capturing went (how many tries it took to turn captions on). Captions include what the other people in the meeting say: capture only meetings you are allowed to. To recognise the same meeting when someone you are connected with on IAM (People) also captures it, IAM keeps a one-way code made from the meeting's own code, never the code itself; then each of you sees both of your captions of that call, one in Hindi and one in English, and nobody else does. After the meeting IAM writes a brief: a summary, what was important, the decisions and the action items, each pointing to the lines it came from (or to your note), what came of the lines you marked and of your note, and which of your people were in it; if you change your note or marks afterwards, it writes the brief again. IAM doesn't tell the other people in the call; the meeting app shows everyone that captions are on. IAM's browser extension (Chrome and Edge) can read only Google Meet's pages, and Teams' and Zoom's only after you turn them on in the extension, which then asks your browser for them; it signs in to your IAM account as a browser, like the web app (Settings → Devices lists it, and signing out there or in the extension ends it), and caption lines wait in the extension's own storage on your computer, which web pages can't read, only until they reach IAM. It keeps no record of the pages you visit. When Meet shows captions but the extension reads none of them, it sends IAM Meet's page layout once for that call, never words or names, so the IAM team can fix the reader.
- Meetings the desktop app captures (Windows), only once you turn on meeting capture: while you are signed in, the desktop app looks every 5 seconds at the open windows of the meeting apps you chose on that computer (Microsoft Teams, Zoom) for a call (a window with a Leave or Hang up button). In a call it reads that window's captions about once a second through Windows' accessibility interface (UI Automation, which screen readers use): each caption line's speaker and words. If the meeting's own captions are off and you turned on "Windows Live Captions", it reads the Live Captions window of Windows 11 instead (its lines have no speaker). To turn captions on for you it presses the meeting app's own captions switch (or its "Language and speech" or "More" menu), and to tell whether you switched them off yourself it checks how long ago the computer last had keyboard or mouse input, never what you typed or clicked. It sends IAM the caption lines with who said them and when, whether the call was in Teams or Zoom, the meeting's title as the Teams window names it (none for Zoom), when it started and ended, your marks and your private note, and counts of how capturing went; never a web address or meeting code, audio, video or pictures of the screen. They wait in a file on the computer, kept for the account signed in, only until they reach IAM (another account's waiting captures are deleted when it signs in), and a call with no captions, or one you answer "Not this meeting", sends nothing. While capture is off the app only notices that a call started, to offer capture once, and reads and keeps nothing of it. The Mac app doesn't capture meetings yet.
- About you, only what you add in You: a line about yourself and a photo (the phone makes it small before sending it), up to three goals in your own words with what each is measured by, and, for a week after you tell IAM to forget something it learned (a person, a place, a project, a word or an app), that thing as it was, so you can undo it. When you accept someone on IAM you may say how you know them (like "Colleague" or "Mom"); it is kept with your own name for them, and they never see it. Your rhythm, your goals' weeks and your year are worked out from your own logs each time you look, by fixed rules, and are not kept; none of this is sent to OpenAI.
- Shared groups and your status, only once you choose them: the groups you share or are asked to join (a group's name, picture, what it is for and its goal together, as its admin set them; who is in it, who asked whom, and who is its admin; whether you share your moments with it, off until you turn it on), the invite links its admin makes (when each was made and taken back; only a scrambled form of its code is kept), and who you chose to see your status (people you are connected with, your own groups, or shared groups you are in). Your status itself is not kept: it is worked out from your day each time someone you chose looks.
- Questions you ask IAM (Ask): what you type or say in Ask, and the facts IAM read from your own logs to answer it, kept for about 10 minutes so the answer can reach you, then deleted; a question you say is recorded, written down and its recording deleted at once. IAM answers only from your own data: your logs with their amounts and tags, your words, the briefs of your meetings and your week.
- Money you lend and borrow: when you settle up with someone (they paid you back, or you paid them, all of it or part), with whom, how much, in which currency and when. Who owes whom is worked out from your own logs and these, and only you see it: never the person it is with, even if you are connected on IAM. A settling up you undo no longer counts.
- How IAM is running: to keep IAM working and its costs in check, IAM's admins see counts and metadata for each account: which devices and app versions are in use, how many logs and how many failed, and how much AI processing (OpenAI) each account used and what it cost. They never see what you said or wrote, your titles or your timeline.
- If you test IAM for us: a tester record linked to your account (your group of testers, the platforms you test on, when you were invited and started, and the numbers of issues we filed from your testing), whether you are OK to be contacted (off until you turn it on in the app; only you can change it), notes from our calls with you, and the feedback you send from the app with the screen you sent it from and your app's version (a problem you report by voice is turned into text like a voice log, and only its words are kept). We use it to run the testing and improve IAM. Only IAM's admins see it. Their screens also show how you use IAM as counts and dates (days active, how many logs and corrections, which devices and app versions, what is connected), never what you said, your titles or your timeline; feedback you send is addressed to the team, so they read it. While IAM is in private testing, the Wyrd team looks at testers' data to improve IAM, except what comes from your Google account (your calendar), which no one reads; it never leaves Wyrd. Your tester record, the notes about you and your feedback are in your data export, and are deleted when your testing ends or when you delete your account.
- Server logs: IP address, time, the requested path, the response status, and account or device identifiers; when something fails, what failed and its error code (never the database query or the values in it), including the apps' own reports when something fails on your device: recording or sending a log, a screen that couldn't be shown, or the app closing unexpectedly (a code from a fixed list, the screen or part of the app, the app's version, your device's system and when it happened). Logs never contain transcripts, window titles, audio or calendar titles. While IAM is in testing and sends no email yet, the sign-in link and code and the email address they are for are written to the server log, so the operator can pass the code on, and so are the code that confirms deleting an account and its email address; this stops once emails are switched on. Each part of the server keeps at most its last 30 MB of logs: at today's volume about a week for the parts that handle sign-in and requests, and several weeks or more for the web server's access log and the database's own log. An update starts afresh the logs of the parts it replaces.
How we use it
Only to run IAM for you: to build your timeline, suggest and confirm activities, send the nudges you allow, show totals and summaries, answer your connected AI assistants, keep your devices in sync, keep the service secure, and fix problems, and, while IAM is in private testing, to improve IAM (see "If you test IAM for us"). We don't sell your data, we don't show ads, and we don't use your data to train AI models.
Google user data
If you connect Google Calendar, IAM asks Google for read-only access to your calendar events (Google's permission is worded "View events on all your calendars"; IAM only reads your primary calendar) and for your Google account's email address. We store each event's title, start and end, its Google identifiers, attendees' email addresses, names (when Google gives one) and replies, whether it has a video-call link, its type and whether it is marked busy or free, the meeting code of its Google Meet link if it has one, and your Google account's identifier, email, organisation domain and the permissions you granted. We use this only to suggest and label meetings on your timeline, to know which attendees are colleagues, and to understand your logs.
IAM also asks for permission to make its own calendar (Google's permission is worded "Make secondary Google calendars, and see, create, change, and delete events on them"). IAM uses it for one calendar it creates in your Google Calendar, "IAM plans": each plan you make in IAM becomes an event there (its title and time only), and when you move, delete or add an event in that calendar, IAM changes your plans to match. IAM never changes your other calendars, and the events of "IAM plans" are never treated as meetings. If you disconnect Google Calendar, IAM first deletes the calendar's events from that time on; the calendar and its past events stay in your Google Calendar for you to keep or delete.
When you record or type a log, the titles, times and attendees' names of your events within two hours of it are sent to OpenAI together with the log, so IAM can tell, for example, which meeting you mean. Attendees' email addresses are never sent to OpenAI: they stay on our server, where IAM uses them only to recognise your people and colleagues, and an attendee Google gives no name for is left out. Connecting your calendar is your agreement to this. An event that becomes a meeting on your timeline carries its title, so the title goes wherever your timeline goes: your devices, your notifications, and AI assistants you connect. Nothing from Google is shared with anyone else.
IAM's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. People don't read your Google data unless you ask us to (for example in a support request), or it is needed for security or required by law. You can disconnect Google Calendar at any time in IAM or in your Google Account's third-party access settings.
Who receives data
- Hetzner hosts our server in Germany.
- OpenAI transcribes voice logs, reads voice and typed logs, and reads the food photos you take (to name the dishes and estimate the calories). With each log it reads what IAM needs to understand it: your project and people names and their other names, and what you call your people (such as "Mom"), the names of your tags, the names of your groups and who is in each, your life areas, words IAM has learned it mishears for you, what you were doing when you made the log, your last 3 logs, that day's blocks up to the log (what each was, its type, project and times), your plans from the day before to a week after (what, when, and whether done or skipped), your unfinished plans of the 7 days before, the open suggestions of your weekly review, the names and kinds of your signed-in devices with the day each was last used, whether you test IAM, the log's time and your time zone, and nearby calendar events (see "Google user data"); a log that asked you a question is read again with the question and your answer, and a log saying what a phone call was about is read with the call's time and who it was with. It also transcribes your journal recordings and, if you test IAM, the problems you report by voice (with your project and people names, to spell them right) and, when you talk to a day's journal page that already has words, reads those words together with what you said, to change the page as you asked. We ask OpenAI not to store the requests that read your logs, your food photos or your journal (transcription requests have no such option). If a voice log in Hindi comes back from transcription in Hindi script (Devanagari), we send that text to OpenAI once more, asking it not to store the request, so it can be written in Latin letters (Hinglish); IAM stores and shows only the Latin version.
- Google provides Google Calendar and Sign in with Google, and Google and Apple deliver phone notifications, whose text can include an activity, project or event title and, in the evening's and Monday's summaries, how much of your time went to it.
- Microsoft, ClickUp, GitHub, Linear, Atlassian and Notion, only if you connect them: IAM asks each for your own data with the permission you gave. They receive IAM's requests, never your IAM data.
- Spotify, Google (Gmail) and MET Norway, only if you turn them on: IAM asks Spotify and Gmail for your own data with your permission, and MET Norway for the weather at your rough location. Our SMS service (Twilio or MSG91, once chosen) receives your phone number to send you a code, only when you ask to prove your number.
- Google (YouTube) receives a captured video's title and channel only when you open a YouTube capture that has no link, so IAM can find that video; IAM keeps the video's id on the capture.
- Claude (Anthropic) and ChatGPT (OpenAI) receive what their tools return: your timeline, and the words you said and kept that they search for (your journal's pages only while "Use my journal" is on); only if you connect them and only while the connection lasts.
- The people you connect with, only while you both have People on: your name; your email, if they found you by it or you asked to connect with them; and, for each meeting or call you are both in (one you logged that names them, or a calendar meeting they are invited to by one of their emails), its kind, start and end, and who else in it they are connected with too, shown by their own names for them. When one of them has just started, they're told by a notification (like "Kabir says you're in a meeting together since 4:00 PM", with your name as they know you) and can start it on their own day. Never its title, your notes or words, its project or place, the rest of your day, your apps, places, health, journal, Insights, or how long you worked. You are never told how they answered. While People and "Let people find me" are on, anyone who has your exact email can see your name and that you are on IAM, and ask to connect; IAM never lists people, never matches part of an address, and gives the same answer for someone who can't be found as for an email that isn't on IAM.
- OpenAI also reads the caption lines of a meeting you captured (the words, the speakers' names, your marks and your private note, and the meeting's title and date) to write its brief, only with your consent to send logs to OpenAI, asking it not to store the request; and the pictures of shared slides, only when you press "Describe the slides", to describe each. Your note stays yours: the people you are connected with never see it.
- The people you connect with, only while you both have People on, also see your line and your photo. Nobody else can find or open them.
- The people in a shared group, once each of them has said yes, while they have People on: its name, picture, what it is for and its goal; who is in it (your name on IAM, or their own name for you if you are connected), who its admin is, and how many days this week or month the group has a shared moment. If you turn on "Share my moments" for a group, they also see, for each stretch of your day you logged with others of the group, its title, when it was, and which of them were in it; never your notes or words, its project or place, or anything else of your day. Anyone you send an invite link can ask to join; its admin sees their name on IAM, or their email if they have not set one, and decides. The people you choose to see your status, while you both have People on, see only the kind of what runs now ("In a meeting", "On a call", "Focus", "Busy") and when it ends, never what it is; while you are paused, or in your Private area, they see only "Busy".
- OpenAI also writes Ask's answers, only with your consent to send logs to OpenAI: it receives your question and the few facts IAM read from your logs to answer it (such as an amount, a date, the name of someone in your logs or a meeting's decision), never your logs themselves, and we ask it not to store the request; a question you say is transcribed like a voice log. IAM checks every number in its answer against those facts, and without your consent IAM writes the answer itself.
- An email provider will deliver sign-in emails once they are switched on (see "Server logs" above).
- Authorities, when the law requires it; and a buyer or successor of IAM, only after asking for your consent.
These providers may process data outside India and Germany, including in the United States.
Your consent before logs go to OpenAI. IAM sends nothing of your logs to OpenAI until you have accepted it. Where you send a log, IAM shows a short explanation of what goes to OpenAI and why, and sending the log accepts it (the apps will ask once, with an "Agree and continue" button, before your first log). We store when you accepted and which version of the explanation you saw, and we keep a record of each time you accept or withdraw it (which version, when), even after you withdraw, so we can show your consent was in place for logs sent before; this record is part of your data export and is deleted with your account. Until you accept, logs that reach IAM without that explanation, for example from an AI assistant you connect, wait unread on our server while your timeline, trackers and calendar keep working; once you accept, they are sent. The recording of a waiting voice log is deleted about 24 hours after it started waiting, and that log can't be read after that. Journal recordings go to OpenAI only with this same consent; until you accept, they wait on our server in the same way, and their audio is deleted on the same terms. You can withdraw your consent at any time, in the app under You → Account, or by saying so in a log ("stop sending my logs to OpenAI"); nothing more is sent from then on, and logs already read stay as they are.
How long we keep it
- Audio: of logs, journal recordings and problems you report by voice alike, deleted right after transcription; if transcription keeps failing, about 24 hours after the last attempt; if you haven't accepted sending logs to OpenAI yet, about 24 hours after you recorded it, or, if you accepted an earlier version of that explanation and IAM asks you again, about 7 days after (nothing is sent to OpenAI before you accept); and in any case as soon as you type that log's words yourself, or about 10 minutes after you leave it out (the time Undo has to bring it back), or as soon as you throw a journal recording or a report away.
- Google tokens: deleted when you disconnect Google Calendar in IAM. Calendar events from the time you disconnect onwards are deleted then too; earlier ones stay part of your timeline. If you remove IAM's access in your Google Account instead, the token stops working at once and IAM asks you to reconnect or disconnect; the stored token is deleted when you disconnect or delete your account.
- Tokens of other services you connect: deleted when you disconnect the service in IAM (IAM also asks GitHub and Linear to revoke them; for the others, remove IAM in that service's settings). Outlook events from the time you disconnect onwards are deleted then too; earlier ones, and what the other services brought, stay part of your days until you delete what a service brought (You → Connections) or your account.
- Sign-in and connection codes: sign-in links and codes, account-deletion codes and AI assistants' authorisation codes are deleted about a day after they expire, and AI assistants' access tokens once they expire (checked daily).
- Testing: your tester record, the notes about you and the feedback you sent are deleted when your testing ends, or with your account.
- People: a connection, and what each of you shared through it, is deleted when either of you disconnects or deletes their account; turning People off deletes what was shared to and from you while it is off. A meeting someone said "Looks right" to is on their own day by then, and stays theirs. Invite links stop working once used, after 14 days, or when you take them back.
- Captures: kept on your day until you delete one (with Undo for a moment) or your account.
- Meetings: kept until you delete a meeting (with Undo for a few minutes) or your account; if you choose a time in Meeting capture's settings (30, 90 or 365 days), meetings older than that are deleted. Pictures of shared slides are deleted 30 days after they were taken, and Meet's page layouts 14 days after they arrive.
- About you: your line, photo and goals are kept until you change or remove them (a removed goal can be brought back while it is kept, until you delete your account); what you told IAM to forget is deleted 7 days later.
- Shared groups: your place in a group is kept until you leave it or its admin takes you out; a group is deleted when its last member leaves; your status's audience is kept until you change it. All of it is deleted with your account.
- Everything else: kept while your account exists, until you delete it or ask us to.
- Update snapshots: before each update of the server, and before such a copy is ever put back, a copy of the whole database is kept on the same server, so a failed update can be undone: the last 3, each deleted within a day of turning 14 days old (checked daily). Data you delete can stay in such a copy for up to about 15 days; if a copy is ever put back, accounts deleted after it was taken are deleted again. These copies aren't backups and never leave the server.
Security
All traffic uses HTTPS. In our database, sign-in links, codes and session tokens are stored only as hashes and the tokens of Google and the other services you connect are encrypted, and every request can reach only its own user's data.
Your choices and rights
- Get a copy of your data: one file with your account, devices, sign-in and session dates, logs, calendar events, timeline and its edit history, plans, your journal and its recordings' words, plus your timeline as a spreadsheet file (CSV). Sign-in codes, tokens and other secrets, timeline blocks, plans and journal pages you deleted, server logs and update snapshots aren't included; audio is deleted after transcription.
- Delete your account: IAM sends a code to your email (while IAM sends no email yet, the operator passes it on; see "Server logs") and, once you type it, deletes your account and all its data at once, with no undo. If Google Calendar is connected, IAM first deletes the future events of its "IAM plans" calendar, then asks Google to stop sending updates and to revoke its access; if Google can't be reached, your data is deleted anyway, and you can remove IAM in your Google Account's third-party access settings. Copies in update snapshots and server logs age out as described above.
- IAM's server does both, and you can delete your account on the web at iam.justgotwyrd.com/delete-account, with a code sent to your email. The phone app has both, under You. To correct your data, write to automation@justgotwyrd.com.
- Disconnect Google Calendar, Claude or ChatGPT, or sign a device out, at any time.
- Disconnect Outlook, ClickUp, GitHub, Linear, Jira or Notion at any time, and delete what each brought.
- Disconnect Spotify or Gmail, undo any import, turn the weather off, or forget your phone number at any time, and delete what each brought.
- Undo a settling up; it is in your data export, and is deleted with the person it is with or with your account.
- Pause tracking, exclude apps and websites, or change nudge settings in the apps.
- Turn People off or "Let people find me" off, disconnect from anyone, or take back an invite link, at any time.
- Turn the capture button and "Capture what's on screen" off at any time (You → Capture button, its notification, or Android's settings), and delete any capture.
- Turn meeting capture off at any time (You → Connections → Meeting capture), delete any captured meeting, and export one as a document.
- Change or remove your line, photo or goals in You at any time, and have IAM forget anything it learned from your days, with Undo.
- Say no to a group, leave it, or turn "Share my moments" off at any time; choose who sees your status, or nobody, in Your profile.
Children
IAM is not meant for anyone under 18.
Changes
We update this page when IAM's handling of data changes and move the date above. Before using data in a new way, we tell you in the app or by email and ask for your consent where it is needed.