Least access, by default
- Sign-in through your own work accounts and their multi-factor rules
- Role tiers plus per-feature permissions
- Managers see their own location; sensitive records only for people cleared to see them
Practical safeguards, built into the software and the way we run it. No certification badges we haven't earned, just the controls we actually use, described plainly.
The baseline controls in the operations platforms we host. Each agreement spells out the details.
Your team signs in with the work account they already use.
People get access to the work they need, and new capabilities start switched off.
See who changed what, when, and what it was before.
Encrypted before they're written, with a written restore procedure.
Your assistant can run on private models, on hardware we control. Your data isn't used to train AI models.
The assistant proposes. A person approves.
We keep the details of our network private on purpose. Here's the shape of it.
It sees only what the person asking is allowed to see, and nothing it suggests happens until a person approves it.
We don't use your records, messages or files to train AI models.
Your assistant can run on private models, on hardware we control, so questions about your business stay inside your boundary.
When it would send, change or delete something, it prepares the action and waits for a person.
Almost nothing. Read the privacy policy →
No advertising cookies, no tracking pixels and no third-party analytics scripts.
Our contact page opens your own email app. Nothing you type there is sent to or stored by this site.
If you pick light or dark, your browser remembers it. It never leaves your device.
We'll walk your team through the details that don't belong on a public page. Found a security issue? Tell us at info@fetchpulse.org.