Authentication
OAMIS Trade uses hosted Supabase authentication for account sign-in, session handling and password flows.
Business ecosystemOAMIS is designed around company-separated workspaces, hosted authentication, server-side secrets and established payment infrastructure. This page avoids certification claims that have not been independently verified.
OAMIS Trade uses hosted Supabase authentication for account sign-in, session handling and password flows.
Application data is scoped by company membership and product access. Supabase Row Level Security policies and server-side checks are used to restrict normal users to their authorised company workspace.
Stripe, Supabase service-role and email-provider secrets are used from server-side code and must not be exposed to the browser.
Payment collection and billing portal flows are handled through Stripe. OAMIS does not ask customers to enter card details directly into the OAMIS website.
Platform admin functionality is separate from normal company membership and is guarded by dedicated platform-admin records and server-side checks.
The platform includes audit logging for platform administration and billing operations where implemented in the product workflow.
Production OAMIS domains are designed to be served over HTTPS/TLS through hosted infrastructure.
OAMIS uses hosted infrastructure providers for database, storage and application hosting. Backup and recovery capability depends on the configured provider environment.
OAMIS does not currently claim ISO 27001 certification, SOC 2 certification, formal penetration-testing certification, guaranteed uptime or end-to-end encryption for all customer records. Those claims should only be added if independently verified.
Contact OAMIS for security, privacy or data-handling questions before starting a company workspace.
Contact OAMIS