Privacy

What the hosted Hearth keeps about you and your work, where it is, who can read it, and how to take it away.

Last changed: date it goes live. This page covers the service at hearth.cards and app.hearth.cards. If you run Hearth on your own server, none of this applies: that server is yours and Hearth never sees it.

The short version

  • Hearth keeps your cards, comments, questions and proof pictures so it can show them back to your org. That is all it is for.
  • Your code stays on your computers. Your agents run there. Their transcripts stay there.
  • Hearth never holds your Claude sign-in or key, and never sees your model use.
  • Your org's people can read your org's data. Hearth's staff cannot, except to answer your request or a legal demand, and every time they do, a line is written that your org's owners can read. The staff rule.
  • Your data is not encrypted so that we cannot read it. That is why the staff rule exists.
  • We do not sell it, show ads against it, or use it for anything but running Hearth for you.

What is stored

Everything below sits in Hearth's database for your org. Nothing here is a guess: it is the list of what the service writes.

WhatDetails
Your accountYour email address, the name you give, and how you sign in: a password (stored only as a one-way scrambled form, by the sign-in service) or your GitHub identity. Hearth asks GitHub who you are, nothing else: no access to your repositories.
Orgs and peopleThe org's name, who is in it, their roles, invites, and which boards each person may open.
Cards and boardsTitles, goals, "done when" lists, comments, questions and the answers to them, files you attach, and what happened to each card (moved, landed, deleted).
Your assistantThe messages you type to your assistant in Hearth, and its replies. The assistant runs on your own computer with your own Claude Code; Hearth keeps the conversation so you can read it from any device.
What an agent writes to a cardShort progress lines ("ran the tests", "read 3 files"), its questions, its hand-in notes and the check results it reports. These can quote a file name, a command or a line of code. Hearth does not receive the agent's transcript, only what it chooses to put on the card.
ProofPictures, short recordings, command output and checked-build results that agents attach to a card. They can show parts of your code, your screens or your data. Anything shown there is stored.
Computers' reportsFor each computer you add: its name, its system, whether Claude Code is installed and ready or at its usage limit until a time, CPU, memory, disk and GPU readings over time (split by card), the folder names of repos it found, which repos it serves and which commands you accepted, and the permission questions agents ask (the command, with secrets removed by the helper before it is sent).
Problem reportsWhen the app or helper crashes or misbehaves it can send a short report: what went wrong, where, the app's version and your browser or system. A report can hold up to a few thousand characters of detail.
Phone notificationsIf you turn them on: the address your browser's push service gave this device, and the label you chose for it.
BillingYour org's plan, its trial and paid-until dates, the number of people last billed, and Stripe's customer and subscription numbers. Never a card number. See Stripe below.
Staff access logA line each time Hearth's staff open your org's data through the one door they use, written before anything opens. Your org's owners read it in Settings, Org, Staff access.

Where it is

All hosted orgs are kept in one database project at Supabase, in region not chosen yet: the hosted project (hearth#221) picks it, and this line names it. Hearth runs one region at first. Pictures and files are stored in that same database, so backups carry them.

Orgs are kept apart by rules in the database: every row belongs to one org, and every read asks whether you are in that org and may open that board. Those rules keep orgs from each other. They do not stop the people who run the database, which is why the staff rule is written down.

Who can read it

What Hearth never collects

How long it is kept

WhatHow long
Proof (pictures, recordings, output)60 days after the card's check is decided or withdrawn, and at most 1 GB per org. This is how the service works today.
Everything else you make in an orgUntil you or an org owner deletes it, or the org is closed. Time-limits for the rest are not designed yet.
Deleted cards and boardsKept briefly so you can bring them back, then removed. Confirm the number of days before this page says one.
Computer readings over timeFolded into coarser steps and pruned each day. The keeping time is not named yet.
BackupsThe database's own daily backups. How long Supabase keeps them on the chosen plan: confirm and write it here. Deleted data leaves the backups when they expire.
Billing recordsAs long as the law makes us keep invoices. How long, in your country
A paused org (unpaid)Nothing is deleted because an org did not pay. After 90 days paused, we tell the owners by email before anything else happens. What "anything else" is, is not decided.

Take it with you, or delete it

The companies that run parts of Hearth

Each sees only what its part needs.

WhoFor what
SupabaseThe database, sign-in, live updates and server functions. Holds everything in "What is stored". Region: not chosen yet.
StripeTaking payment. Sees your name, email, billing details and the org's plan. Hearth never sees a card number.
A mail providerSending sign-up, password-reset and invite mail from hello@hearth.cards. Sees the address and the message. Provider not chosen yet.
A static hostServing this site and the app's files. Sees your address and browser as any web host does; holds none of your data. Host not chosen yet.
A captcha serviceOn sign-up only, to keep out bots. Not chosen yet; the design calls for one.
GitHubOnly if you choose "Continue with GitHub": to tell us who you are.
Your browser's push service (Apple, Google or Mozilla)Only if you turn on phone notifications: it delivers them to the device. It sees that a notification was sent, and the words in it.

The first three are the ones named in the plan for the hosted service; the last four follow from how the service is built.

If this page changes

If we change what is stored or who can read it, we tell every org's owners by email before it takes effect, and the date above changes. proposal: 30 days ahead

Who to write to

Business name
Address
Support email