Trust & Privacy

Gemisis makes supported communications independently checkable. Organizations log outgoing communications against exact linked senders, and receivers compare what they received with those sender-side records.

Matching registered evidence confirms message origin. Account control or a public-source domain association alone does not. No match remains unconfirmed, not proof of fraud.

Gemisis returns a scoped result for the check being performed. Depending on the integration, this may include a registered email, limited display name, connection date, or account-match result. Share only what's needed.

Private credentials and underlying connection records are not disclosed in check results. Information is shared with eligible receivers and other authorized recipients as explained in the Privacy Policy.

Communications data and organizational registration records are encrypted in transit and at rest.

Access to verification records is limited to what's operationally necessary for verification, security, and support.

The Teams integration encrypts stored refresh credentials and temporary check contexts, validates Microsoft tokens on the server, and uses expiring contexts. A positive check does not guarantee transaction safety.

Found a security issue? Book a call with us. We aim to respond promptly and will work with you to confirm and fix the issue before any public disclosure.

We don't have a bug bounty program yet - as we grow, we intend to build one. For now, we'll credit anyone who responsibly reports a real issue.

When reporting an issue, do not:

Banks, insurers, and government agencies have strict privacy, data residency, and audit requirements. Gemisis provides communication traceability to support their workflows alongside the institution's own governance and authorization controls.