Embers is built by NSIMS LLC to be calm and private. Security is part of that promise, not a bolt-on. This page describes what we do today, honestly, and what we are still building.
What we do today
- Per-account isolation. Your data is scoped to your account at the database layer (row-level security), so one account cannot read another's data.
- Encryption. Traffic is encrypted in transit with TLS. Stored data is encrypted at rest by our database provider.
- You approve everything. Embers drafts; it never sends a message, posts anything, or shares your data on your behalf without your explicit approval.
- Transient processing. When you submit a file or text for Embers to read, it is processed in memory and then discarded. We keep only the structured result you save, not the raw input.
- Protected account settings. Sensitive account state (such as your plan and entitlements) can only be changed by our server, not by tampering with a request.
- Real deletion. Deleted contacts sit in Trash for 90 days so you can recover them, then are permanently removed. You can permanently delete sooner at any time.
- We do not sell your data. Ever. See our Privacy Policy.
- Reputable infrastructure. Embers runs on established providers; the full list is on our Subprocessors page.
What we are still building
We would rather tell you what is not done than imply it is. On our roadmap:
- Multi-factor authentication.
- Additional field-level encryption for the most sensitive data.
- Tamper-evident audit logging.
- Formal third-party attestations as we grow.
Reporting a vulnerability
If you believe you have found a security issue, please tell us privately at security@embers.group before disclosing it publicly. Include enough detail to reproduce it. We will acknowledge your report, work with you on a fix, and credit you if you would like. We will not pursue legal action against good-faith research that respects our users' privacy and does not degrade the service.