(HT) hold that

Privacy

Last updated: October 6, 2026

Hold That is a place to keep your own things. Here is exactly how your information is treated — in plain words.

What we collect

Your email address, to sign you in, and your name if you give one. The things you put in the app — thoughts, tasks, events, lists, notes, goals, and the times you set. And, if you sync a calendar, the events from it, so they show on your days on every phone you sign into.

Where it lives

Your words are stored in a secured database (hosted by Supabase), scoped so that only your signed-in account can ever read your rows. Pictures and files you add are stored in your account, in a private folder only your signed-in account can read. We use them for nothing else, and they are deleted with your account. Videos stay on the phone that took them. When you add a picture or a file, the app reads the words in it on your phone, to suggest a name and a few facts; nothing leaves the phone to do that, and the name and facts it suggests then travel with the thing like any words you typed. A reminder or alarm you set shows the thought’s words on your lock screen.

What we don’t do

No analytics. No tracking. No ads. No selling your data. No sharing it, except what you choose yourself: connect Claude, and you’re telling us to hand Claude what it asks for (see The Claude connector, below). The site and the app’s cloud are served by Cloudflare and Supabase, which see what any host sees and keep the ordinary request logs any host keeps; fonts are served from this site. The app has no push notifications. Every reminder or alarm is created on your device, from a time you set. The one thing the app fetches on its own is the title of a link you share in, from that site, the first time you open it. Speaking a thought uses Apple’s speech recognition, under Apple’s terms. Add to calendar writes that one event to the calendar you chose, and nothing else on your calendar.

Google Calendar

If you connect Google Calendar, Hold That asks Google for two permissions: to see your calendars and their events (calendar.readonly), and to add events (calendar.events). It also learns which Google account you connected (your email address), so Settings can show it.

How Google user data is used

The events from the calendars you switch on are shown on your days in the app, next to your own things, and kept in your Hold That account so they appear on every phone you sign into. Add to calendar writes the one event you chose to the one calendar you picked. If you later change or delete that thing in Hold That, that one event changes or goes with it; nothing else on your calendar is ever touched. That is the whole use. Your Google data is never sold, never used for advertising, and never used by us to train AI or machine-learning models. It is shared with no one unless you choose to: if you connect Claude, the synced events in your account go to Claude along with the rest of it (see The Claude connector, below). Otherwise it is used only for the features described here, which you can see in the app.

How Google user data is protected

The keys Google issues to Hold That are stored in your phone’s secure keychain, filed under your account, and never on our servers: the app talks to Google directly. The only Google data that reaches our servers is the synced events themselves (title, day, time, place, and Google’s id for the event). They travel over encrypted connections (HTTPS) and are stored encrypted at rest in a secured database (hosted by Supabase), protected by row-level security so that only your signed-in account can read your rows. There is no admin screen; the only person who can reach the database is the one who runs the service, through the hosting company’s console, to keep it running — never to read your things. On a shared phone, each person’s Google connection is kept under their own account and is never used by anyone else.

Retention and deletion of Google user data

Synced events are shown only while Google Calendar is connected and that calendar is switched on. Disconnect Google in Settings asks Google to cancel Hold That’s access, deletes the keys from your phone, and takes its upcoming events off your days; what already happened, and what you answered, stays in your history. Switching a calendar off does the same for that calendar. A removed event’s record is kept in your account marked as deleted, so your phones agree on what left, until you delete your account. Delete my account in Settings erases your entire account, including every synced event and its history, as soon as the request completes; our database host’s routine backups expire on their own schedule. The phone you deleted from clears its own copy then; another phone signed into the account finds it gone the next time it connects, and what it kept on its own goes when the app is deleted there. An event that Add to calendar put on your Google calendar is yours; it goes only if you delete the thing that put it there, never otherwise. You can also remove Hold That’s access at any time from your Google Account’s third-party access page. Email us and any of this is done for you.

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

The Claude connector

If you add Hold That to Claude (Anthropic’s assistant), you sign in with your Hold That account on holdthatapp.com and allow it, and from then on Claude can read your account — your things, lists, days, counters and pictures, and the synced calendar events in it — and hold, move, dress or mark things the way the app does. It works only for the account you signed in with, under the same rules as the app: your rows, no one else’s. Connecting is your choice to share: whatever Claude asks for from your account goes to Anthropic, and what Claude keeps of it, and for how long, is governed by your Claude account and Anthropic’s policy (Anthropic says what a connector hands Claude isn’t used to train its models). The connector itself stores none of your content: each request is answered from your account and passed on; the hosts it runs on (Cloudflare, Supabase) keep ordinary request logs, as any host does. Remove the connector in Claude’s settings and its access ends there — it doesn’t erase what Claude already received. How to set it up is on the connector page.

Your data is yours

You can export everything you’ve written as a single file, anytime, from Settings in the app. Pictures aren’t in it — they’re in your account, and on your phone. If you want your account and everything in it deleted, Delete my account is in Settings in the app: two taps. Your account and everything in it goes from the cloud and from that phone as soon as the request completes; another phone signed into it finds the account gone the next time it connects, and what it kept on its own goes when the app is deleted there. If you signed in with Apple, deleting your account also hands your Apple sign-in back to Apple; for an account made before this, or if Apple can’t be reached at that moment, you can do it yourself: Settings → Apple Account → Sign in with Apple → Hold That. Or email us and it’s done.

Questions

Write to invites@holdthatapp.com.