What our staff can read
On the hosted Hearth, the people who run it could read your org's cards. This is the rule for when they may, and the record they keep.
The rule
Hearth's staff open an org's data for two reasons only:
- You asked. An owner of that org wrote to us about a specific problem, and looking is needed to fix it.
- The law requires it. We received a legal demand we must obey. We check it first, and give only what it covers.
Never for curiosity, product research, sales, training anything, or looking at a customer's cards for any other reason.
Every time, a line is written to a log first, and your org's owners can read it.
What "opening an org's data" means
A person at Hearth reading what is inside an org, with any tool: card text, comments, questions and answers, proof, activity lines, computers' reports, files, the assistant's conversations.
What is not opening it
- The service doing its job. Storing your data, backing it up, sending you a notification, running timers. Programs, not people reading.
- Numbers about an org, with no contents. How many people, cards and computers, how many bytes it holds, how many live messages it uses. We need these to bill, to size the service and to keep one org from slowing the rest. We do not read what is behind them.
- Billing records. Plan, dates, and Stripe's numbers for the org.
- Error logs of the service itself. We search them for failures. Engineering must confirm these hold no card text before this line stays.
How it works
- One door. Staff open an org through a single tool. It asks for the org, the reason (org asked or legal demand) and a reference (the request's number, or the demand). It writes the log line before it opens anything, and if it cannot write the line, it does not open. The line is the opening itself: there is no way to open an org that does not leave one.
- It closes by itself. proposal: after one hour, renewable; each renewal is a new line
- Only that org, and only to read. An opening reaches the one org named, nothing else, and lets staff read it, not change it.
- Staff cannot edit or delete the log. No staff login can write to it. The one change the database allows is a staff member closing their own opening early, once, and a closed line stays in the log.
The log
Each line says: when, which member of our staff (their staff login name), which org, the reason, the reference, what was opened, and when it ended. An opening reaches every kind of content an org holds, so every line names the same list: cards, comments, questions and answers, proof, activity, files and the assistant's conversations. Your org's owners (not admins or other members) read it in Settings, Org, Staff access, newest first, in plain words. A line for an opening that is still running says when it ends, not that it ended.
14 March, 10:12 · A Hearth staff member (mira) opened your org's cards, comments, questions and answers, proof, activity, files and the assistant's conversations, because you asked (support request 123). Ended 11:12.
An example of how a line will read. Not a real entry.
The log is kept as long as the org exists, and how long after it is closed.
Legal demands
- We read the demand, and ask for it to be narrowed when it asks for too much.
- We give only what it covers, and write the log line.
- We tell your owners before we do it, unless the law forbids it. If it forbids, the line is shown to the owners once the ban ends, and we publish a count of such demands each year. Both are proposals; a lawyer should say what is allowed where Hearth is based.
What this does not do
We would rather say this here than have you find it out.
- A log covers the door, not the building. The database is held by Supabase, and anyone with the project's admin access (the dashboard, the database owner's login, the service-role key) could read it without our tool. The four small programs that run Hearth's sign-up, invites, computers and notifications hold that key too; they do not read an org's contents for staff. The rule is that nobody on our staff reads an org any other way. Proposal: we keep admin keys to a minimum, and use Supabase's own records to alert us if the database is read any other way. Until that alert is built, a read outside the door leaves no line in this log, and this is a promise plus a log, only as strong as the promise. Not built yet: the alert on a read outside the door (hearth#241)
- Supabase's own staff are bound by their agreement with us, not by this page. Lawyer: is the Supabase agreement enough to rely on?
- Backups hold the same data. Reading one is opening the org, but the door does not cover a backup: nothing writes a line when one is read, so for backups this is a promise only. Not built yet: a log line for reading a backup
- Your data is not encrypted against us. Making it so would break search, the assistant's reading of cards and the notifications that quote a question. If that changes, this page changes.
If you run your own server
None of this applies. On a server you run, you are the operator, and Hearth's staff cannot reach it at all.
Who to write to
To ask us to look at something, or to ask whether we have: support email.