Security and trust

Custodian of your customer list, and acting like it

A sales platform holds other businesses’ customers. That is a higher bar than holding your own data, so these rules are designed in, tested, and written down here in plain words. This page says only what is true; where something is still being decided, it says that.

Your data stays yours

  • Tenancy enforced by the databaseEvery row carries the business it belongs to, from the very first table. One business never sees another’s records.
  • Platform access to your account is exceptionalTime-boxed, with a stated reason, two people for any write, and written into your own audit log where you can read it.
  • Partners administer, they do not readA reseller can manage your business but needs your grant to open your records, and you can see that grant.
  • Documents as links, in your storageSigned contracts are never kept in a personal drive that disappears with an employee.
  • Secrets are write-onlyA connection token is shown once, stored encrypted with a key held outside the database, and never displayed again. Changes to it are audited, without the token.
  • Export whenever you likeYour records come out as CSV, one file per object.

Every action is attributable

  • One audit trail for agents and peopleEach change records who made it, agent or person, and when. Agent record updates keep the words they came from.
  • Skipped steps are raised, not hiddenStage conditions warn instead of blocking, and moving past one is recorded and shown on Oversight.
  • Approvals that cannot driftAn approval binds to one quote version; any later change to price, discount or terms voids it.
  • Roles with real limitsA permission matrix decides who sees what, including cost and margin. Custom roles can never grant what the never rows forbid.

Consent and sending

  • A consent basis on every contactRecorded with the wording, date and page where it was given. Inbound from marketing and cold outreach are different lanes with different gates.
  • CASL by constructionSender identification, anyone sent on behalf of, a postal address, and an unsubscribe that works for at least 60 days.
  • Suppression with the right scopeA hard bounce stops mail to that address everywhere. A complaint or unsubscribe stops it for that brand.
  • Do Not Call and calling windowsChecked before every dial, in the prospect’s own time zone. No predictive dialer.
  • Mail that authenticates as the right companyEach brand gets its own bounce domain so SPF passes for the sender, not for someone else.
  • Test mode until you mean itA new workspace sends nothing real. Going live is one deliberate, recorded act, never a side effect of finishing setup.

AI under control

  • Agents hold permissions, not powersDrafting, writing and sending are separate grants. Reaching a customer always needs its own recorded grant.
  • Shadow, then promotion by a personTwenty consecutive approved outputs before an agent may act, and every version can be rolled back.
  • Regional AI when your contract requires itA client can be pinned to a model endpoint in a Canadian region, never a global one that routes wherever there is capacity.
  • Failover to a different providerNot just a different model from the same provider, which fails along with it.

Residency is not sovereignty

Pinning a Canadian region keeps data in Canada. It does not put that data beyond the reach of a foreign court if the provider is foreign-owned. If your contract requires sovereignty rather than residency, a region setting does not satisfy it, and we will say so rather than imply otherwise.

Ask us where your workspace’s data would be hosted before you commit, and we will answer specifically, in writing.

What we do not claim yet

Handfast is in early access. There are no certification badges on this site, and we will add one only when an independent audit is complete. If you need a security questionnaire answered, ask us.