01Infrastructure
EzraPro runs on a major cloud provider in regions chosen for each operator’s market, in single-tenant databases per region with encryption at rest. Production is separated from staging and development, and no customer data is used outside production. Infrastructure is defined as code and every change is reviewed before it is applied.
02Encryption
All traffic between guests, operators and EzraPro is encrypted in transit with TLS 1.2 or higher. Data at rest, including backups, is encrypted with AES-256. Secrets and keys are held in a managed key store, rotated on a schedule, and never committed to source control.
03Payments
Card details are entered directly into fields served by our payment processor, which is certified to PCI DSS Level 1, and never touch EzraPro’s servers. We store a token, the last four digits and the card type. Payouts go only to a bank account verified on the operator’s profile, and a change to that account requires re-authentication and is confirmed by email.
04Access control
Operators control who on their team sees what, with six role levels and permissions down to the field: a guide sees today’s manifest, a bookkeeper sees payouts, and nobody sees the bank account who should not. Every change to a booking, a product or a setting is written to an audit log the operator can read.
Inside EzraPro, access to production is limited to a small number of engineers, requires hardware-key two-factor authentication, is granted for a task and expires, and is logged.
05Backups and resilience
Databases are backed up continuously with point-in-time recovery for thirty days, and restores are tested every quarter. The booking path is served from more than one availability zone so a single failure does not stop sales. The host app keeps working with no signal and syncs when the connection returns.
06Testing and monitoring
Code is reviewed before it ships and scanned for vulnerable dependencies on every build. An independent firm performs a penetration test each year and we fix what it finds. Production is monitored around the clock, with an engineer on call.
07Incident response
If we confirm a security incident that affects an operator’s data, we notify the account owner without undue delay and within seventy-two hours, tell them what happened, what data was involved and what we are doing about it, and keep them updated until it is closed.
08Responsible disclosure
If you believe you have found a vulnerability in EzraPro, please email security@ezrapro.com with enough detail for us to reproduce it. We acknowledge reports within two business days, keep you informed while we fix the issue, and do not pursue legal action against researchers who act in good faith, avoid privacy violations and give us reasonable time to respond.