Legal
Privacy Policy
Last updated 10 October 2026
Who we are
It’s Been A Minute is operated by Wallabout, LLC (doing business as Wallabout Studios), a Delaware limited liability company, of Brooklyn, New York. Wallabout, LLC is the data controller for the personal information described here, except where section 4 says otherwise.
This policy covers the app at my.ibam.app and this site at ibam.app. It sits alongside our Terms of Service.
What we hold about you
Your account
- Your email address — how you sign in, and the only address we send anything to.
- A display name, and an avatar image URL if you give one. We do not host the image; the app just points at wherever you said.
- A hashed password, if you set one. We never see the password itself. If you only ever sign in by emailed link, there is no password to hold.
- Whether the free-text feature is switched on, when the account was created, and the invite code it was created with.
What you write down
- People: first and last name, nicknames, and optionally an email address, phone number, photo URL, free-text notes, tags, whether they are starred, and whether you have set them aside until a date.
- Interactions: a title, a kind (“Coffee”), the date, an optional note, and which people were there. Plans work the same way, filed before instead of after.
- The sentence you typed, if you logged something by describing it in your own words. It is kept next to the interaction it produced — see section 5.
- Your own list of interaction kinds and tags.
Technical
- Server logs, which include IP addresses, timestamps and the requests made. These are also what the rate limits on sign-in, sign-up, password reset and the email-me-a-link endpoint are counted against — the point of which is to stop somebody using our mail sending to bother other people.
- Page views on this site. The public site at ibam.app counts its own page views, using Cloudflare Web Analytics. A view records the path you opened, the site that linked you here, your country, your device type, browser and operating system, and how quickly the page rendered. It sets no cookie, stores nothing on your device, and gives you no identifier — so it cannot recognise you on a later visit, and cannot follow you to any other site.
- Not in the app. my.ibam.app runs no analytics of any kind. Nothing you write down is measured, and no counter can reach it.
- Nothing else. No advertising, no ad network, no session recording, no profiling, and no third-party script beyond the one counter named above.
Why we hold it, and on what basis
| What | Why | Lawful basis (UK/EU) |
|---|---|---|
| Account details | To give you an account and let you sign in | Performance of a contract |
| What you write down | To show it back to you, and work out who you are overdue to contact | Performance of a contract |
| Server logs, rate limiting | To keep the service up and stop abuse of it | Legitimate interests |
| Counting page views on the public site | To know whether anybody is finding ibam.app, without identifying who | Legitimate interests |
| Sending you a draft from a sentence | Only if you use the feature; off at the server when you switch it off | Consent |
| Answering your email | To deal with what you asked about | Legitimate interests |
We do not profile you, make automated decisions with legal effects about you, or use anything here for advertising.
People who never signed up
Almost everything in an IBAM account is personal information about somebody else. The people on your list have no account, are never contacted by us, are not told they are on it, and cannot see what has been written about them. That is worth stating plainly rather than burying.
What we hold about them: whatever the account holder typed — a name and nicknames always, and sometimes an email address, a phone number, a photo URL and free-written notes, along with a record of when they and the account holder saw each other.
Our role. We hold this because an account holder put it there, and we handle it only to run the app for them. Where data-protection law applies to a particular account — it does not apply to most purely personal use — the account holder is the controller of what they wrote, and we act as their processor.
What we never do with it:
- Contact the people on anybody’s list, for any reason.
- Let one account see another’s. Every read is scoped to the account that made it.
- Connect people across accounts, build a social graph, or work out that two users know the same person.
- Enrich the record from anywhere else, or check it against any outside source.
- Sell it, rent it, share it for advertising, or train a model on it.
If you are on somebody’s list and want out. Write to hello@wallabout.studio. Be aware of what we can and cannot do. We are usually not the controller of that information, and we will not go reading through somebody’s private notes to search for you on the strength of an email. What we will normally do is pass the request to the account holder, who is required by our Terms of Service to honour it. If you tell us who holds it and the law requires us to act ourselves, we will, and we will tell you what we did.
Logging in your own words
The app can turn a typed sentence into a filled-in form. This is the only feature that sends anything you wrote outside our own infrastructure, so here is exactly what goes.
Sent to Anthropic, when you use the box:
- The sentence you typed.
- Your device’s current date and time zone, so “yesterday” can be resolved.
- The names of your own interaction kinds, so the draft picks one you actually have.
- A table of the people the sentence might be about: for each one, their name, their nicknames, whether they are starred, how many days since you last logged them, and how many interactions you have logged. The table is a slice of your list, not all of it — everyone the sentence appears to mention, plus your most recent people.
Never sent: the email addresses, phone numbers, photos or notes you hold about anybody, your own email address, or any interaction other than the sentence in front of you.
Anthropic processes it under terms that do not permit training on it, and retains it for up to 30 days for abuse monitoring before deleting it.
Turning it off. The switch is in the app’s Settings. It is enforced on our server, not just hidden in the app: with it off, the feature refuses and nothing is sent. Nothing is sent unless you use the box, and nothing is saved to your log until you press save.
The sentence is kept. When you save a draft, the raw sentence you typed is stored alongside the interaction it became, indefinitely, so we can tell how well the feature reads real writing. Deleting the interaction deletes the sentence with it, and closing your account deletes both.
Assistants you connect
You can connect an AI assistant (such as Claude) so it can read your people and add interactions for you — going through your calendar to catch the log up, for example. There are two ways to connect one, and nothing is connected unless you do one of them yourself: make an access key in Settings and hand it to the assistant, or add IBAM as a connector inside the assistant’s own app, which brings you to a screen in IBAM asking whether to allow it. That screen names the assistant and the website it will send you back to, and nothing is connected unless you press Allow.
What a connected assistant can do. Read your people (including the email addresses and phone numbers you hold, which is how an assistant matches a calendar invitation to a person), read your interactions, add people and interactions, fill in details a person is missing (such as an email address you hadn’t recorded), and mark a plan as having happened. It changes a detail you already hold only when you tell it to. It cannot delete, archive or merge anything, edit an interaction, or reach your account settings. A key and a connection can do exactly the same things.
Where it goes. What an assistant reads leaves our service and goes to that assistant’s provider under your arrangement with them, not ours — they are not our sub-processor, and their policy is the one that applies to it. When an assistant adds an interaction it is marked as added by an assistant, and the line it was working from (such as the calendar event’s title) is kept with it, like a typed sentence is.
Keys and connections. We store only a one-way hash of each key, so we cannot show it to you again or read it back. A connection made through an assistant’s app works the same way underneath: the assistant is given a credential that lasts an hour and one that renews it, we keep only hashes of both, and if it goes ninety days without being used it stops working and has to ask you again. When an assistant’s app connects, it tells us its name and the web address to send you back to; we keep those so we can check them on the next request, and they say nothing about you. Settings lists your keys and connections with when each was last used, and revoking or disconnecting one stops it working immediately. Closing your account deletes them.
Who else touches it
We use a small number of companies to run the service. They may handle your data only to do the job listed, and may not use it for anything of their own.
| Who | What for | Where |
|---|---|---|
| Neon | The database — everything described above is stored here | United States (Ohio) |
| Fly.io | Runs the server | United States (Virginia) |
| Cloudflare | Serves this site and the app’s files, and counts page views on the public site | Global network |
| Resend | Sends the verification, password-reset and sign-in-link emails | United States |
| Anthropic | Turns a typed sentence into a draft — only if you use that feature | United States |
We also disclose information if the law genuinely requires it, and would tell you unless we were forbidden to. If the business is ever sold or merged, your data may transfer with it, under this policy until you are told otherwise.
A small number of people at Wallabout, LLC — currently one — can reach the database to operate and repair the service. The app’s own operator page shows account email addresses and counts of how much each account has logged; it does not show anybody’s people, notes or interactions. We look at account contents only when it is necessary to fix something or when you have asked us to.
Cookies, sessions and what sits on your device
IBAM sets no cookies. Not for sessions, not for preferences, not for analytics. That is why you have never been asked to accept any: there is nothing to consent to. The page counter described in section 2 is the only script this site loads, and it writes nothing to your device either — which is why it, too, needs no banner.
Three things are kept in your browser’s local storage, on your device only:
- Your session token, which is what keeps you signed in. Logging out removes it.
- An offline copy of what the app last showed you, so an installed IBAM opened with no signal shows your own people instead of an error. It holds your people and interactions, is discarded after seven days, never includes the operator page, and is wiped when you log out. On a shared device, log out rather than closing the tab.
- Whether you dismissed the “install this app” prompt, so it does not ask twice.
None of this is readable by us, and none of it is sent anywhere.
Email we send
Only what the account needs: verifying your address, resetting a password, and the sign-in link when you ask for one. There is no newsletter, no digest, and no email about who you are overdue to contact — the app does not nag, by design. If we ever add a summary email it will be something you switch on, never something you switch off.
We would write to you about a material change to this policy or the terms, or about something that affected your account.
How long we keep it
- While your account is open, we keep what it holds, so the app can show it to you.
- Deleting inside the app hides, it does not erase. Removing a person or an interaction marks it as archived: it disappears from every screen and every count, but the row is still in the database, so it can be recovered if you delete something by mistake. If you want it genuinely gone, ask us and we will erase it.
- Closing your account erases it. Everything the account holds — people, interactions, sentences, tags, sign-in identity — is deleted from the live database the moment you close it, in Settings → Your data. It is immediate, it is not the archiving described above, and it cannot be undone.
- Backups of the database are kept by Neon for a limited window for recovery, so deleted data can survive there briefly before ageing out. Backups are never used to bring back something you deleted on purpose.
- Server logs are short-lived and kept only for operating the service.
Your rights, and how to use them
Wherever you live, you can ask us to do all of the following, and we will do it: tell you what we hold, give you a copy in a portable format, correct it, delete it, or stop a particular use of it. Depending on where you live you may also have the right to object to processing, to restrict it, to withdraw consent (for the free-text feature, the Settings switch does exactly that), and to complain to your data-protection authority.
The two commonest ones you can do yourself, now. In Settings → Your data: Download a copy gives you a JSON file of everything the account holds, and Delete my accounterases it. Neither goes through us, neither is logged as a request, and neither needs a reason.
For anything else — correcting something, restricting a use, objecting, or an export or deletion you cannot do because you have lost access to the account — write to hello@wallabout.studio from the address on your account. We will reply within 30 days. There is no charge, and asking will never count against you.
Being straight about what deletion reaches. It empties the live database of everything your account held, immediately. It cannot reach three things: database backups, which age out as described in the section above and are never used to bring back something you deleted on purpose; sentences you sent to the free-text feature, which its provider holds for 30 days and then drops (section 5); and the logs of emails we have sent you. Nothing in any of those is queried by the app, and none of it comes back.
Where it is held
Everything is stored and processed in the United States. If you are in the UK, the EU or elsewhere, using IBAM means your data is transferred there. Where those transfers need a legal mechanism, we rely on the European Commission’s standard contractual clauses, or the equivalent UK addendum, in our agreements with the companies listed in section 6.
Security
Everything travels over HTTPS, and cannot travel any other way: the whole .app domain is on the browsers’ preloaded HTTPS-only list. Passwords are stored hashed. Every read and write in the app is scoped to the account that made it. The endpoints that can be brute-forced or made to send mail are rate limited.
No system is perfectly secure, and this one is a beta. If you find a problem, write to hello@wallabout.studio; we would rather hear it from you than not. If a breach ever put your data at risk, we would tell you and the relevant authority within the time the law requires, and tell you what to do about it.
Children
IBAM is for people aged 16 or over. We do not knowingly collect information from anybody younger, and we will delete an account we learn belongs to one. If you believe a child has an account, write to hello@wallabout.studio.
Data brought over from the previous version
IBAM replaced an earlier version of itself in August 2026. A small number of existing accounts, and the people and interactions they held, were migrated to this app. Nothing was collected in the move that had not already been given to the earlier version, passwords were not carried across — those accounts sign in by emailed link or by setting a new password — and everything in this policy applies to that data exactly as it does to anything typed since.
Changes to this policy
If we change it in a way that materially affects you, we will email the address on your account before it takes effect. The date at the top of this page always says when it was last changed.
Contact
Wallabout, LLC, Brooklyn, New York, United States.
hello@wallabout.studio
A real person reads that address. Access requests, deletion requests, exports and questions about this policy all go there.