Security
How we look after your data.
These are the security controls in Hapro today: who can sign in, how your data is kept, and what gets recorded.
Access and sign-in.
You decide who on your team can sign in, and what each person can do.
Role-based access
Seven roles, from owner to read-only. Only the owner can connect payments or change roles.
Two-factor authentication
An authenticator app, with single-use recovery codes if you lose your phone.
Passkeys
Sign in with your fingerprint, face or screen lock.
Protected sign-in
Repeated failed attempts are slowed down, and your session sits in a cookie scripts cannot read.
Data protection.
Hapro uses what the service needs, and limits who can reach it.
Encrypted credentials
Your Stripe, Shopify and messaging keys are encrypted with AES-256 and never shown back.
Hashed passwords
Stored only as one-way hashes. Two-factor recovery codes are hashed too.
Each business kept separate
Every record belongs to one business. A request for an unclear business returns nothing.
Card details stay with Stripe
Customers pay on Stripe's hosted checkout. Card details never reach Hapro.
Records and oversight.
A record of what changed, and an assistant that stays within your limits.
Audit log
Changes to settings, integrations, payments, phone numbers and team access are recorded.
Security events
Sign-ins, failed sign-ins and two-factor changes are logged.
Verified messages only
Stripe, Shopify and Twilio messages are acted on only when their signature checks out.
Automatic clean-up
Old transcripts and raw provider messages are deleted on a schedule.
An assistant within limits
It uses only the actions you allow. It cannot set prices or mark an order as paid.
Card numbers removed
Recognisable card numbers typed into a message are removed before it is stored.
Doing a security review?
Tell us what you need to see and we will get back to you.