Security and compliance
Texting from a real business number is a trust relationship. iTexter is built so you can explain exactly what happened in any conversation, and who — or what — caused it.
Encrypted connector sessions
The Windows connector authenticates with short-lived credentials and keeps an encrypted channel to your workspace.
Consent is a first-class field
Every contact carries a consent record. Autonomous sending disables itself when consent isn't recorded or has been withdrawn.
Role-based permissions
Eight roles from Owner to Read Only, with per-area control over sending, prompt publishing, billing, and exports.
Complete audit trail
Message sends, AI approvals, prompt publishes, MCP tool calls, and permission changes are all recorded.
Scoped MCP access
Each connected AI client gets explicit scopes, an allowlist of numbers, and an approval policy for writes.
Server-side enforcement
Entitlements, billing limits, and authorization are enforced on the server. The browser never holds a secret.
Data minimization
Only the message metadata needed to operate the inbox leaves your device.
Visible AI provenance
Every AI or MCP originated message is attributable in the audit log, even when the bubble looks ordinary.