Trust

Security & trust

MeghaX is built for operators who put real company data — people, deals, contracts, and cash — into one system. This page summarizes how we approach security and trust today. It is not a compliance certificate and does not replace a formal security review for your organization.

Last updated: 2026-10-21

Current practices

Access control

Workspace data is gated by company tenancy and role-based permissions. Admins control who can see and change CRM, HR, contracts, time, invoicing, hiring, and custom modules.

Authentication

Users authenticate with secure credentials. Multi-factor authentication (MFA) is supported. Google and Microsoft sign-in are available through MeghaX platform OAuth for supported login flows.

Connected accounts (Google & Microsoft)

When users or Admins connect Google or Microsoft 365 for email, calendar, Meet, or Teams, OAuth access and refresh tokens are stored encrypted at the application layer. Tokens are used only for the integrations the user authorized (such as inbox sync, scheduling, or meeting creation) and can be revoked in product or in the provider account settings.

Meeting Companion data

Meeting Companion may process meeting audio through MeghaX and subprocessors to produce transcripts and summaries stored as Customer Data in the Account Owner workspace. Bot sessions are tied to meetings users or Admins schedule or explicitly dispatch through the product. Account Owners are responsible for participant notice and consent as described in our Privacy Policy and Terms.

Encryption in transit

Customer traffic to MeghaX is protected with TLS (HTTPS). Production hosting uses Let’s Encrypt certificates behind Nginx.

Infrastructure

The MeghaX application and related services are hosted on AWS infrastructure (including EC2 for the marketing site stack and AWS services used by the product platform). Access to production systems is limited to authorized operators.

AI safeguards

MeghaX AI features — including module AI and Mira — are assistive. They help analyze and summarize operating data; they do not autonomously make employment, legal, or financial decisions. Humans remain accountable for outcomes.

Your data, your control

Account Owners control Customer Data inside their workspace. Per our Terms and Privacy Policy, data can be exported, and accounts follow defined retention and deletion windows after termination.

Subprocessors

We use infrastructure and service providers to operate MeghaX. Categories include cloud hosting (for example AWS), payment processing (Stripe), email delivery, customer support tooling, analytics and monitoring, and — where Meeting Companion is enabled — meeting bot hosting and speech-to-text providers. These vendors process data only to provide services to REDYX under contractual confidentiality and security obligations. A current list or questionnaire response is available on request for enterprise procurement; contact us via Contact.

Details on Google and Microsoft integrations and Meeting Companion are in our Privacy Policy.

What we do not claim here

We do not list SOC 2, ISO, or other third-party audit badges on this page unless those reports are complete and available under NDA. If your procurement process needs a questionnaire, pen-test summary, or roadmap for formal attestations, contact us — we will answer honestly about what exists today versus what is planned.

Incident notification

If a data breach affects Personal Information, REDYX notifies affected Account Owners and, where required, individuals and regulators, without unreasonable delay — as described in our Privacy Policy.

Full product documentation — including access and workflow guides — lives in Docu Center, and Mira can guide setup inside the app after you create a workspace.