Privacy
Last updated 17 November 2026
Solid Hours is a personal planning app. This page explains what happens to your information, in plain language, feature by feature.
Solid Hours is a hosted service. Self-hosting is not offered, so everything below describes the one place your data lives: app.solidhours.com, and the desktop apps that sign in to it.
Where your data lives
app.solidhours.com is operated by the maintainer of Solid Hours on a rented virtual server in the EU (from Hostinger). Your data sits in a database on that server rather than on your own machine, and the maintainer is responsible for it. The Mac and Windows apps sign in to the same account; they are a window onto it, not a separate copy.
Anyone can create an account. Each account sees only its own data: every record is stored against its owner and every query is scoped to it.
What the hosted instance stores
- Your account: email address, name and profile picture address if your sign-in provider supplies them, any other email addresses you add as your own, and when the account was created.
- Everything you put into the app: tasks, projects (including any time, money, contact and logo details you add to them), ideas, notes and their images, habits, journal entries, and your focus and time-tracking records.
- A change history of your tasks (what a task looked like before and after each change, and changes made through a connected AI), kept so changes can be undone and traced.
- Calendar events from any calendar feed you subscribe to (title, time, location, description, organiser and attendees, for 30 days back and 90 days ahead), along with the feed address, which is encrypted before it is stored.
- Messages from the connections you switch on (see "Connections" below), and the credentials those connections need, encrypted.
- Sign-in sessions, held as a hash rather than a usable token, with the browser or app name and the time each was last used; the first time each account signed in from the desktop app.
- If you turn on notifications: the address your browser's push service gave this device, and a record of which notifications were sent so the same one is not repeated.
- Keys you create for AI assistants (see "Connecting an AI assistant"), stored only as a hash.
Connections: email, Slack, WhatsApp
Connections are off until you set one up in Settings → Connections. Each one brings messages in so Solid Hours can suggest tasks from them. Here is what each one does:
- Forwarding address. You get a private address like tasks+…@solidhours.com. Mail you forward there is received by Cloudflare Email Routing, turned into text by a small Cloudflare worker, and sent to the app. The app keeps the sender's name, the subject and the text (quoted replies and signatures removed). Turning it off or making a new address stops the old one working.
- Email inbox. If you connect a mailbox with an app password (Gmail, iCloud, Fastmail, Yahoo or another provider), the server signs in to it read-only and looks at recent mail (the last 3 days on the first check, then new mail), skipping newsletters and automated mail. The app password is stored encrypted. Nothing is ever sent, moved or deleted in your mailbox.
- Slack. Connecting asks Slack for permission to read your direct messages and mentions. Slack sends new messages to the app; only direct messages, group messages and messages that mention you are kept, with the sender's name and a link back to Slack. Your Slack access token is stored encrypted, and disconnecting revokes it at Slack.
- WhatsApp. You link your number to the Solid Hours WhatsApp number with a one-time code. Messages you send or forward to that number are kept as text (voice notes are not transcribed). This uses Meta's official WhatsApp Business service, so Meta handles those messages, and your phone number is stored with the connection.
- How long messages are kept: each message is stored with up to 4,000 characters of text. Once a message has been dealt with (you accepted or dismissed the suggestion, or it needed no task), its text is cut down to a short preview after 30 days. Messages still waiting for you keep their full text until then. Disconnecting a connection erases its stored password or token, but suggestions it already brought in stay until you ask for them to be deleted.
Texts and calls on your Mac
The Mac app can suggest tasks from your iMessages, texts and missed calls. It is off until you turn it on, and it needs you to grant Full Disk Access in macOS settings.
When it is on, the app reads, on your Mac and read-only: incoming messages from the Messages database, your call history, and your Contacts so it can show names instead of numbers. On the first run it looks back 3 days, then checks every 5 minutes. Your sent messages and outgoing calls are never sent anywhere.
What leaves your Mac: the text of incoming messages (up to 4,000 characters each), who each is from (the contact name, or the number or address), the group name for group chats, and for calls a line such as "Missed call from Ana at 14:05", with the number. These are stored like any other connection message, with the same retention. Your Contacts and the rest of the Messages database stay on your Mac. Turning it off stops it immediately.
AI features
No AI runs on the server, and Solid Hours holds no AI key. The AI features (chat with your companion, Plan with AI, breaking a task into steps, turning a brain dump into tasks, task suggestions from your messages) run in the Mac or Windows app on your own Claude (Anthropic), ChatGPT/Codex (OpenAI) or Gemini (Google) sign-in, using that provider's command-line tool on your computer.
For each request, the app sends the text that request needs from your computer to the provider you chose, under your own account and that provider's terms. Depending on the feature that can include your open tasks and their notes, matching notes, projects, ideas and habits, a message you are turning into a task, or the text of a document you attached. Private notes and journal entries are only included in a chat if you switch on "Include private notes" for it.
Chat conversations are not stored on the server; they disappear when you leave the page. Your companion's name, look and tone are kept on your device and only shape how the AI answers.
The Mac app can also add Solid Hours skills to your own Claude Code setup on your computer. That stays on your computer.
Connecting an AI assistant (MCP)
You can let an AI assistant such as Claude or ChatGPT work with your account by creating a key in Settings → AI. A key is shown once and stored only as a hash. A read key can read your tasks, My day and projects for 30, 90 or 365 days; a read & edit key can also change them, including a project's time and money records, for 7, 30 or 90 days. You can revoke any key at any time, and changes made with a key are recorded in your task history.
The ChatGPT connector is read-only and its access lasts 7 days unless you renew it. Whatever an assistant has already read is in that assistant's conversation, under its provider's terms; revoking a key stops further access but cannot erase what was already returned.
Who else is involved
The hosted instance depends on a few outside services. Each one is listed with what it actually receives:
- Hostinger — rents the server in the EU that runs the app and holds the database.
- Cloudflare — routes traffic to the server and terminates HTTPS, so it handles your requests in transit. It also hosts this website and the installer downloads, and receives mail sent to forwarding addresses.
- Brevo — sends the app's emails: sign-in links, a welcome email with your name, and a notice when your account is signed in on a new device (which browser or app, how and when). It receives your address and those contents, and nothing else from inside the app.
- The AI you choose, if you use the AI features — Anthropic, OpenAI or Google, under your own account (see "AI features").
- Slack, Meta (WhatsApp) and your email provider — only if you connect them, and only as described under "Connections".
- An AI assistant you connect over MCP — only with a key you create (see above).
- Google and Apple — only if you choose to sign in with them. They confirm your email address and may supply your name; Google also supplies a profile picture, which your browser loads from Google when you open your account settings. Neither is given access to anything in the app.
- Your browser's push service (Apple, Google or Mozilla, depending on your device) — delivers notifications if you turn them on. Notifications only say that there is a new task or a reminder, not what it is.
- Stripe — not in use. Billing is not switched on. When it is, Stripe will process payments; it will receive your email address and the payment details you enter on its own checkout page, and card details will never reach the Solid Hours server.
What does not happen
- No analytics scripts, no tracking pixels, no cookies for measurement, no advertising, and no third-party scripts — on this website or in the app.
- We keep three counts. Installer downloads per day and platform are counted by this website on Cloudflare: the download link adds one, nothing about you is stored with it, and the daily totals are kept for about 400 days. New accounts per day come from each account's creation date. The first time each account signs in from the desktop app is recorded against that account. Only the operator can see these figures.
- IP addresses are not stored. They are held in memory for a few minutes to limit repeated sign-in attempts, then forgotten.
- Your data is never sold, rented or shared for marketing.
- Solid Hours never uses your data to train AI models.
- Nothing is ever written back to your calendar, your mailbox or your Slack. Those connections are read-only.
- The desktop app sends no telemetry or crash reports. It talks only to app.solidhours.com and, for AI features, to the provider you chose.
Cookies and your device
The app uses only the cookies it needs to keep you signed in: a short-lived signed session cookie (one hour, renewed while you use the app), a sign-in token cookie that lasts 30 days, and a short-lived cookie during Google or Apple sign-in (ten minutes). This website sets no cookies.
Sign-in sessions last 30 days from your last visit and at most 90 days, then you sign in again. Your preferences (companion, sounds, which sections you use, the welcome guide) are kept in your browser's storage on each device, not on the server.
How long it is kept, and getting it back
Your data stays until you ask for the account to be removed. When you delete something in the app it disappears from view, but it is marked as deleted rather than erased straight away, and your task history keeps earlier versions. A deletion request erases all of it, including those copies.
Expired sign-in sessions are deleted automatically. Calendar events outside the sync window are replaced on each sync. Message retention is described under "Connections".
Settings → Account → Download my data gives you a file with everything held for your account (private calendar addresses and sign-in secrets are left out). There is no self-serve account deletion yet: email hello@solidhours.com and it is erased. The server keeps a daily copy of the database for 14 days, plus copies taken just before recent updates; on a deletion request your data is removed from those copies too.
Security, stated honestly
Traffic is encrypted in transit. Calendar addresses, connection credentials (email app passwords, Slack tokens) and forwarding addresses are encrypted at rest. Sign-in tokens and AI assistant keys are stored only as hashes, and sessions and keys can be revoked immediately.
What this is not: a service with a security team, an audit, or a compliance certification. It is one person's project running on one server. Judge it accordingly, and keep your own copy of anything you cannot afford to lose.
Your rights
You can ask what is held about you, get a copy, have it corrected, or have it deleted, and you can disconnect any connection or revoke any key yourself at any time. Email hello@solidhours.com and you will get a real answer. There is no form and no ticket queue.
Changes
If this policy changes in a way that affects what happens to your data, the date at the top changes and anyone using the hosted instance is told by email. Silent rewrites are not the intent.