Account security

SECURITY & TRUST

Clear access.
Accountable control.

Your company’s work belongs in the right hands. OrcheSphere combines verified identity, explicit workspace permissions and protected payment flows.

Manage account security

Trust starts with specifics.

Understand the controls available to your team, how enterprise SSO is set up, and what independent assurance has been verified.

Read our assurance status

Protect your sign-in

Managed accounts support authenticator-app multi-factor authentication (MFA / 2FA) and single-use recovery codes. Verification is checked before access when your account requires it.

Recovery codes let you replace a lost authenticator while disconnecting previous security sessions and connected AI clients. Store them offline. A password reset does not bypass MFA.

Text-message verification appears in account settings only when SMS is enabled for the service.

Keep company access explicit

Signing in identifies you. Your active membership, company and assigned permissions determine what you can access. A matching email address alone does not grant a managed account company access.

Workspace requests check current permissions. Customer support conversations stay within their workspace, and staff-only notes are excluded from customer conversations.

Enterprise SSO, with a clear setup path

Microsoft Entra single sign-on is available for approved tenants and explicitly linked company members. Your identity provider authenticates the person; OrcheSphere applies the company’s access assignments.

For SAML, company administrators can request a setup review. We agree the identity-provider configuration, exchange metadata securely, and test issuer, user identifiers, membership mapping and recovery before activation.

Request enterprise SSO setup

Payment details go to Stripe

Checkout redirects to a Stripe-hosted payment page. Card entry takes place there; our application records payment references and verified transaction details.

Payment processing through Stripe reduces the card data handled by our application. It does not remove our merchant responsibilities for website security, access controls, vulnerability management and PCI validation.

Stripe’s integration security guidance (opens in a new tab)

INDEPENDENT ASSURANCE

Controls and assurance are different commitments.

SOC 2

No completed independent SOC 2 report for OrcheSphere has currently been verified. We do not claim SOC 2 certification or provide a report that has not been issued. A SOC 2 report requires examination by an independent CPA firm within a defined system scope and reporting period.

PCI DSS

Stripe’s provider validation does not validate OrcheSphere as a merchant. No completed OrcheSphere merchant PCI validation has currently been verified. The applicable assessment and evidence must be confirmed with our payment provider or acquiring bank and, where needed, a qualified assessor.

For procurement reviews, request the current scope and available evidence through client support. Any assurance document should identify the legal entity, systems covered, assessment date and limitations.

KEEP THE CONVERSATION PRIVATE

Have a security question?

Use your authenticated support workspace for account and company questions. For a security concern when you cannot sign in, contact Platformz. Start with a non-sensitive description; never send passwords, access tokens or card details.

Open client support Contact Platformz