01
What the register contains
Each listed provider must include its legal name, service purpose, data categories, processing location, transfer mechanism where relevant, and the date it was added or materially changed.
Vendor transparency
How Omkin documents providers that support identity, hosting, payments, meetings, communications, observability, and operations.
Each section explains the user-facing promise, the operational boundary behind it, and where to go when something needs attention.
Each listed provider must include its legal name, service purpose, data categories, processing location, transfer mechanism where relevant, and the date it was added or materially changed.
The register distinguishes infrastructure hosting, identity and authentication, payment processing, video or real-time communications, email and notifications, customer support, security, observability, and other operational services.
Omkin evaluates necessity, security controls, contractual data limits, confidentiality, incident duties, deletion support, access model, resilience, and relevant transfer safeguards before production use.
Material additions are communicated in advance where required. Questions or legally available objections use the privacy route and are evaluated against the service purpose and applicable agreement.
Use the dedicated support, privacy, safety, accessibility, or legal route. Emergency needs should always go directly to local services.