Security

Your data, your audience and your domain, protected.

Inbrovia stores the two things a business trusts most to an email tool: its customer list and its sending reputation. This page explains how we protect both, in plain language.

Encryption in transit

Every connection to Inbrovia, from your browser and between our services, uses modern TLS. Campaign content, audience data and settings are never sent in the clear.

Encryption at rest

Databases, backups and stored files are encrypted at rest. Passwords are stored as salted hashes, never as plain text, and session tokens are stored only as hashes.

Secrets management

Provider credentials, signing keys and webhook secrets are held in managed secret storage, scoped to the service that needs them. They are never exposed to the browser and never appear in logs.

Tenant isolation

Every record belongs to a workspace and, where relevant, a brand. Access is enforced in the data layer on the server, not by hiding things in the interface. One customer cannot read another's data.

Audit logs

Audience imports, suppression changes, Guardian overrides, approvals and sends are written to an append-only audit trail with the actor, the time and what changed.

Abuse prevention

Bounce and complaint rates are monitored per workspace. Spikes pause sending and notify the workspace. Workspaces that show abuse signals are limited or paused for review.

Permission-based sending

Inbrovia is for sending to people who agreed to hear from the brand. Purchased or scraped lists are not permitted, and every campaign carries a working unsubscribe.

Authenticated sending

Campaigns are sent only from domains the workspace has connected and verified. Mailbox providers can confirm every campaign came from the brand it claims to.

Access and accounts

Who can see and do what.

Access to a workspace is granted by invitation. Each member has a role, and roles map to specific permissions: managing the domain, importing an audience, editing templates, approving a campaign, sending, viewing analytics, managing suppressions. Those permissions are checked on the server for every action.

Sessions use random tokens stored as hashes and expire automatically. Signing out destroys the session on the server, not just in the browser. External reviewers never receive an account; they receive a link that expires and that can only be used for the campaign it was created for.

Platform administration is separated from customer workspaces. Inbrovia staff do not have standing access to workspace content, and administrative actions are logged.

Recipient protection

Your recipients are protected too.

Unsubscribe and preference links are signed and expire. They cannot be forged or altered to affect a different recipient or brand. One-click unsubscribe is supported for mail apps that offer it, so recipients never need to open a page to stop receiving campaigns.

Suppression is permanent for complaints and hard bounces and cannot be undone from the application. Unsubscribes are honored across lists, segments and reimports, and recipients can change topic preferences at any time with immediate effect.

Personal data is used to send the campaigns the workspace creates and for nothing else. We do not sell, share or enrich audience data.

Operational practice

How we run the service.

Infrastructure is defined in code and changes are reviewed before deployment.
Dependencies are monitored for known vulnerabilities and updated on a schedule.
Backups are encrypted and tested by restoring them.
Webhook events from the sending infrastructure are verified and de-duplicated before processing.
Security headers, strict content policies and sandboxed previews protect against injected content in imported HTML.

If you discover a vulnerability, email security@inbrovia.com. We acknowledge reports promptly and keep you informed until the issue is resolved.

Questions

Common security questions.

Where is my data stored?: In managed cloud infrastructure with encryption at rest. Contact us for region details for your plan.
Can I export or delete my audience?: Yes. Authorized roles can export audiences, and workspaces can request deletion of their data.
Do you support single sign-on?: Google sign-in is planned. Email and password accounts are available today, and sessions are protected as described above.
How are imported HTML templates handled?: Imported HTML is sanitized on the server before it becomes part of a document, and previews render inside sandboxed frames.

Email deliverability

Domain authentication and Sender Health.

Audience management

Suppression and preferences.

For agencies

Tenant isolation per client brand.

Send with confidence from your own domain.

Start free. Protection is on for every campaign.

Create Your First Campaign All features