Separate organizations
Each customer’s records and permissions are kept apart. One organization cannot read another’s data.
Security
Your organization. Your boundaries.
Controlled access, encrypted credentials and a person approving every send are part of the foundation, not an add-on.
At a glance
How your data and access are protected.
Access by invitation
There is no public sign-up. Administrators add people, and temporary passwords must be replaced at first sign-in.
Roles that fit the job
Roles combine permitted actions. People see and do only what their role allows.
Credentials stay encrypted
Mailbox and provider keys are stored encrypted and are never shown again after they are saved.
Sheet data is only data
Fields from a spreadsheet are given to the AI strictly as data. Instructions hidden in a cell are ignored.
A person approves sending
The AI writes drafts; a person approves the campaign. Approval is withdrawn if the content changes.
A history behind actions
Sensitive changes and record history are kept, so you can see who did what and when.
Providers on your terms
You connect Google or Zoho with their own sign-in and can disconnect at any time.
Role-based access
The right people, the right access.
Roles decide what each person can open and do. Set them once, adjust them whenever you need to, and every action stays within them.
RoleLeadsCampaignsApproveInvoicesSupportSettings
Administrator●●●●●●
Sales●●—view——
Campaign approverviewview●———
Financeview——●——
Support agentview———●—
● can use · view = view only · — no access. Example roles; you define your own.Menus follow the role
A module a person cannot use is simply not shown to them.
Roles combine
Give someone several roles and they get the permitted actions of each.
Approving is not sending
Clearing a campaign and starting it are separate permissions, on purpose.
Clients stay in the portal
Clients only ever see what you share, never your internal workspace.
Responsible sending
Outreach that respects the people it reaches.
Sending is built to protect your sender reputation and the people you e-mail.
Verified senders only
A sender must pass its DNS checks (SPF, DKIM, DMARC) and be enabled before it can send.
Daily caps and a sending window
Every mailbox has its own daily limit, with gaps between e-mails and the days and hours you choose.
Unsubscribe in every e-mail
Everyone who unsubscribes is skipped in every campaign from then on.
Follow-ups that stop
A reply, a bounce or an unsubscribe ends the sequence for that person at once.
Honest status
A message shows as sent only after the mail provider accepted it. A simulated run says so on the page.
A person approves
The AI writes drafts; approval covers the exact prompt, profile, senders, sheet and promotion.
Found something?
Tell us about a security concern.
If you believe you have found a problem, please write to us and a person will read your message. We ask that you do not share the details publicly until we have had a chance to respond.
Questions about how we handle your data?
Tell us about your team and we will set up your workspace.
Request access
Every request is reviewed by an administrator. There is no public sign-up.