Hora knows what your business needs to do — while keeping your business data under your control.
Three pillars: a compliance engine with sourced rules, event-driven automation, and privacy by architecture. In today's early-access build the rules run in your browser and your profile, obligations, documents and history are encrypted with a key derived from your password before they are stored or synced; Hora servers hold that vault only as ciphertext they cannot read. What our servers do receive in readable form is short and listed below — account, billing, reminder dates and counts — plus two things that pass through briefly when you ask for them: integration events and AI requests. Before general availability we publish the production storage design and an independent audit, and every statement on this page is re-checked against it.
Three kinds of data. Hora can read only one of them.
Hora does not store your company vault in readable form. Some data passes through the server in readable form for a short time when you ask for it: integration events (until your app picks them up), AI requests (sent to the provider you chose, with sensitive numbers masked).
Profile, owners, employees, locations, obligations, documents, history. Encrypted on your device with a key from your password before it syncs to your account. Hora stores only the ciphertext and cannot read it.
Your email, an authentication salt, 2FA status, plan and — only if you turn on email reminders — reminder dates, stages and counts, never titles. This is what lets you sign in and get reminded.
Card, invoices and sales tax are handled by Paddle.com, our reseller and merchant of record; Hora stores the subscription status, not the card.
Page views and funnel events such as "a check was run" — never your answers, your profile or anything from the vault.
Your encrypted vault follows your account to every device — the key never leaves yours.
Sign in with the same account and password: the vault arrives as ciphertext and is opened on that device with your password. Hora in the browser and the desktop app show the same data; changes made on one device appear on the others, and edits made at the same time are merged on your device (you decide field by field when both sides changed the same thing).
Invite them to your team as an advisor with an expiry date: they sign in with their own password and two-factor code, see only what their role allows (no employee personal data for advisors), and lose access automatically on the date you set. The data key reaches them through a one-time access code you give them by phone — never through the server.
Hora cannot reset your password without your recovery key, and cannot rebuild your vault — there is nothing readable on our side to rebuild it from. Keep the recovery key shown when you created the company; you can also export an encrypted backup file at any time from Security.
Encrypted before it's stored
Passphrase → PBKDF2-SHA256 (150,000 iterations) → AES-256-GCM. The session key is a non-extractable CryptoKey; it is never written to localStorage or sessionStorage as text and expires after 30 minutes idle.
Rules flow down, data doesn't flow up
Rules arrive from Hora; matching against your company happens on your device. Each rule declares the fields it reads, and every obligation shows "What data was used?"
You control sharing, backup and deletion
Share one obligation or one document — never the whole company — under a one-time key, and revoke it any time. Export an encrypted backup. Delete everything with one action. All of it is logged.
What stays local, what is sent only if you opt in, what is not sent.
- Business profile, owners, employees, locations, EIN, tax accounts
- Obligations, tasks, calendar, documents, receipts, audit log
- Rule evaluation — "which rules apply to me" is computed on your device; the server confirms it from a minimized profile (entity type, states, dates, counts — no names, tax IDs or addresses)
- The default assistant: a local, rule-based parser
- Hora AI (off by default): the question you type, a summary of your company with people's names and tax IDs replaced by neutral labels and sensitive numbers masked, and a file only if you attach one — through the Hora server, which keeps a usage counter and not the content
- Email reminders: dates, stages and counts — never titles
- Integrations: only the fields shown on the consent screen
- Each is a separate switch in Privacy & data, revocable, logged
- Your passphrase or vault key
- Your vault, or anything to an AI provider that you did not ask to send — with Hora AI on, only your question, the masked summary and the file you chose go out
- Vault content to support staff
Two different promises, kept separately.
"We can't read it" applies to your vault: it reaches our servers only as ciphertext. "We don't sell it" applies to everything, including the account data we do hold in readable form. The table says which is which.
| Data | Your device | Hora servers | Class |
|---|---|---|---|
| Company profile, owners, employees, locations | ✓ encrypted | ciphertext only | Confidential |
| EIN, tax accounts, revenue by state | ✓ encrypted | ciphertext only | Highly sensitive |
| Obligations, tasks, calendar | ✓ encrypted | ciphertext only | Internal |
| Documents and receipts | ✓ encrypted | ciphertext only | Highly sensitive |
| Audit log | ✓ encrypted | ciphertext only | Internal |
| Your passphrase | memory only | not received | Highly sensitive |
| Account email, salt, 2FA status, subscription | ✓ | ✓ (needed to sign you in and bill you) | Confidential |
| Reminder dates, stages and counts (never titles) | ✓ | only if you enable email reminders | Internal |
| Support tickets, technical error reports | — | ✓ (what you type; never vault content) | Internal |
| Rule base, versions, sources | ✓ cached | ✓ (public, not about you) | Public |
Who else touches anything, and what.
None of these vendors receives your vault. The AI provider receives only what you choose to send, masked (see above). Our commitments, which contracts will enforce before launch: a data processing agreement with every vendor; no selling of personal data and no third-party targeting; no use of customer data to train AI models, including at the AI provider.
| Vendor | Used for | Receives |
|---|---|---|
| Paddle | Billing | Email, plan, country, card (card handled by Paddle, not seen by Hora) |
| Email provider | Reminders, digests, support replies | Email address; reminder dates and counts you opted into — never titles |
| Hosting / CDN | Serving the app and the rule base | IP address, standard request logs |
| AI model provider | Optional cloud interpretation of change text | Your question, a summary of your company with names and tax IDs replaced and sensitive numbers masked, and a file only if you attach one — only after you turn Hora AI on in Privacy & data |
| Analytics | Product usage on the public site | Page views, no cookies across sites, nothing from the dashboard |
What is in place, and what is honestly still ahead.
Stated plainly: your encrypted vault is stored on your computer and, as ciphertext only, in your Hora account so your other devices and the browser can open it. An independent security audit and penetration test are scheduled before we call this generally available; until then we won't advertise a guarantee the architecture doesn't yet provide.