Security & data

Security is the plumbing, not the pitch.

How campaign data is held, who can touch it, and what happens when someone asks. Stated plainly, no badge wall.

Sign-in · second factor2FA
4 8 2 9 1 7
Jess · adminSam · senderMarco · approverRiley · viewer
Audit loglive
Encryption where it works

Data encrypted in transit and at rest. And the honest line most vendors skip. A text message itself travels carrier networks unencrypted, a property of SMS, and sensitive data doesn't belong in one.

Trust center →
Walled accounts

Each campaign is its own account. Lists never mix, opt-out pools never share, and no export-import cycle moves consent between them.

Operator console →
Two-factor sign-in

A one-time code to the user's own cell at login. The list is the account's most valuable asset, and a password alone doesn't guard it.

Trust center →
Roles that mean something

Six Roles from Owner to Analyst, each reaching only what it should. Billing is the Owner's alone, and an admin can't touch an owner or mint one.

Solutions →
A log on every action

Sends, edits, exports, and account jumps, timestamped. When the question comes, the answer is a record, not a recollection.

Message log →
Retention the law demands

Message and consent records persist for your jurisdiction's retention. Deleted contacts purge on schedule, and the audit trail of the deletion stays.

Trust center →
What we don't claim. No certification badge appears on this page that an auditor hasn't issued. When a formal audit completes, it posts here with a date. Until then, the practices above are the answer, and your security questionnaire gets filled out honestly.

Ask the hard question. The answer is written down.

Pick your plan