A note from the founder
Nova reads your email, your calendar, your notes. That's the deal. In return we owe you a straight answer to every honest question you have about what happens to that data — and a product that behaves like we mean it.
This page is that answer. No compliance-brochure language, no invented certifications. Just what Nova does today and what it will never do.
The awkward question
Nova will see private things. A doctor's appointment. A legal thread. A quiet conversation with a lawyer, an accountant, a therapist. This is unavoidable — it's in the inbox you asked us to watch.
Here's what happens when it does:
Every outbound action lands in your inbox as a draft. Nothing sends, books, or pays without you tapping approve. This is a database-level invariant — not a setting we can flip off.
Every table in the database enforces row-level security scoped to your user id. Your data is unreachable from any other account, even by mistake.
API keys, OAuth tokens, and webhook secrets live only in encrypted server storage. The browser bundle never sees them.
One tap inside your Trust centre exports everything Nova knows about you as a JSON file. Another tap erases your memory and starts you fresh.
Nova learns from how you approve and edit drafts. We don't ship your data to third-party training pipelines.
Payment and integration callbacks reject any payload without a valid HMAC signature. Replays and forged events do nothing.
Card lifecycle (drafted → approved → sent) is append-only logged. A client cannot mark something sent without a prior approval event.
Quiet hours, spend limits, and allowed action types are yours to configure on the Profile page. Nova won't cross them.
Nova uses WhatsApp only to send you approval prompts on your own opted-in number — never as a public AI chatbot. One message when something needs your tap; you approve in Nova. You can turn it off in one tap.
Every card that carries a time — briefings, renewals, watchers, reminders — is computed in your timezone using explicit UTC-anchored dates, not the server's local clock. Daylight-savings changes don't double-book or drop reminders.
About certifications
Nova is early. We follow the access, correction and deletion rights defined by GDPR, POPIA and CCPA today. We are not yet SOC 2 or ISO 27001 certified — SOC 2 Type I is on the roadmap as we grow. We will not claim any certification until it's formally issued to us. If someone tells you otherwise, they're wrong, and we'd like to hear about it.
— The Nova team
Next step
See it on your own inbox. Nova drafts, you approve every send.
No card. Nova drafts — you approve every send.