Security controls
How encryption, phone verification, proximity checks, and the final server decision work together.
Explore the security controlsSee how MesaiGo is developed, tested, and operated through named owners, versions, and published documentation.
Every published document identifies the product, version, date, and scope it covers. A certification badge appears only with a verified certificate and scope link.
How encryption, phone verification, proximity checks, and the final server decision work together.
Explore the security controlsShows which product, model, version, and installation types were covered by penetration, relay, and distance tests.
See how testing is performedExplains how security researchers are protected when reporting responsibly, what can be tested, and when to expect a response.
Contact the security teamEach notice identifies the affected product and version, risk, temporary measure, fix, and customer communication.
Explore support pathsService status, incident history, backups, recovery steps, and target recovery times for cells, APIs, and notifications.
Explore service supportWhy data is used, how long it is kept, where it is stored, employees’ access to their own records, and collection limited to what is needed.
See which data MesaiGo usesNetwork design, key protection, customer isolation, disaster recovery, and customer responsibilities.
Explore the platformThe software component list (SBOM), signed builds, source verification, gradual deployment, and safe return to the previous version.
Explore software release securityReview the security controls, attacks addressed, tests completed, and installation responsibilities together.