How this site and MAKO's tools are secured
Every page on this site runs over HTTPS, and so does every system MAKO uses to deliver client work.
Access to client and Amazon accounts
Where an engagement includes Amazon or other account access, MAKO works through roles the client grants — never through shared or generic logins. Access follows least privilege: a team member or system gets only the access the engagement requires, nothing wider. The client can revoke that access at any time.
Credentials and tokens
Login credentials, API keys, and access tokens are stored in secured, access-controlled systems built for that purpose. They are never placed in shared documents, spreadsheets, or chat messages.
Keeping client records separate
Each client's information and operating records are kept segregated from every other client's. Nothing from one engagement is mixed into another.
Backups
Operating records are backed up on a regular schedule, so work is not lost to a single point of failure.
If something goes wrong
If an incident affects a client's information, MAKO notifies the affected client promptly and works with them on the appropriate next steps.
When an engagement ends
MAKO removes its access and returns the client's materials according to the MAKO Handoff Standard — the account and access register, performance baseline, decision history, client-specific playbooks, reporting definitions, and the open roadmap.
Contact
Questions about how MAKO secures information can go to x@makocommercial.com.
MAKO Commercial Inc. · makocommercial.com