Trust and security

    Built to be verified, not just trusted.

    Where your data lives, who can see it, and what we have and have not been certified for, stated plainly.

    For IT teams

    Every claim on this page maps to code or a documented process. Where something is not done yet, we say so.

    Hosted in Riyadh · STC CloudAES-256-GCM encryptionRegistered with SDAIA
    Where it runs (diagram)
    STC Cloud, RiyadhApplication and database✓
    Daily encrypted backupWith an off-site copy in Riyadh✓
    Dedicated instanceRegulated sectors, by contractOn request
    ConnectionsExample
    SAP Business OneCredentials: ***Production
    PayTabsCredentials: ***Production
    WhatsAppCredentials: ***Staging
    TestExploreEdit→ Staging

    Registered in SDAIA's National Register for Personal Data Protection

    Rich Life Trading Company (Exomations) is registered and active on the National Data Governance Platform of the Saudi Data & AI Authority (SDAIA). Scan the QR code on the certificate to verify it.

    Registration No.: 3260008321 · Issued: 2026-09-24

    View certificate (PDF)

    200+

    security controls in place

    More than 200 security controls, built in and traceable

    Each one is part of the platform and traced to the code that enforces it or to a recorded security review: sign-in and sessions, tenant isolation, encryption, rate limits, sandboxed customer code, AI prompt-injection guards, audit trails and payment checks.

    We share the full register, including what is still in progress, with customers and investors under NDA. We do not claim a third-party penetration test or any certification yet.

    Where it runs

    Hosted in the Kingdom. Here is what leaves it.

    Saudi Arabia

    Platform and database

    The application, the database, uploads and the daily encrypted backups run on STC Cloud in Riyadh, with an off-site backup copy also in Riyadh.

    Outside the Kingdom

    Default AI processing

    Platform AI uses OpenAI, which processes requests in the United States. Every provider we use is listed below.

    Your choice

    Your own model

    On any plan, connect your own model, including one hosted in the Kingdom, or switch AI off. Regulated sectors can ask for a dedicated instance.

    Data residency, stated plainly

    We tell you exactly where your data lives — no vague assurances.

    Today (standard hosting)

    Exomations runs on STC Cloud infrastructure in Riyadh, Saudi Arabia — your platform data is stored and processed inside the Kingdom. Data is logically isolated per tenant and sensitive fields are encrypted with AES-256-GCM, aligned with PDPL expectations for commercial data.

    For regulated sectors (government, banking, health)

    Need contractual guarantees beyond standard hosting? We provision a dedicated, isolated database instance — in-Kingdom or in a GCC region you nominate — as a contractual commitment. The migration touches only the connection string; your data model is unchanged.

    Platform data is hosted inside Saudi Arabia. One honest caveat: when you connect third-party services (a global AI provider, an overseas SaaS API), the data you send through those connectors is processed wherever that provider operates. We state this plainly rather than promise more than any integration platform can keep.

    Credentials and runs

    Credentials stay encrypted. Every change is on record.

    Credentials

    Connection passwords, API keys and tokens are encrypted with AES-256-GCM, with a separate key for each workspace.

    ConnectionsExample
    SAP Business OneCredentials: ***Production
    PayTabsCredentials: ***Production
    WhatsAppCredentials: ***Staging
    TestExploreEdit→ Staging

    Audit log

    Every change goes into a hash-chained audit log, so an edited or deleted entry shows when the chain is checked.

    Audit LogsExample
    TimestampActionUserResource
    09:20:41Flow Activatednouraflow
    09:18:02Flow Updatednouraflow
    09:02:15Execution Viewedfaisalexecution
    08:57:30Login Successfaisaluser
    Export CSV

    Access control

    Roles and fine-grained permissions, two-step sign-in, and sign-out after 60 idle minutes. Single sign-on (OIDC) on Enterprise.

    Settings · SSOExample
    https://login.example.sa
    exomations
    ***
    Enable SSO
    Require SSO (owners exempt)

    Approvals

    Sensitive steps wait for a named approver, and the decision is recorded.

    ApprovalsExample
    PendingApprovedRejectedAll
    Refund 1,240 SAR, order #100482Approver: Noura A. · Node: Approval · Execution: 9f21c0
    ApproveReject

    Emails, phone numbers, national IDs and IBANs are removed from application logs automatically.

    Each workspace's data is kept apart from every other workspace's.

    Code steps run in a locked-down sandbox, and outgoing requests to private networks are blocked.

    Incoming webhooks can be verified by signature (HMAC).

    Backups

    A daily database backup, encrypted with AES-256-GCM, plus an off-site copy.

    Security testing

    Over 20 rounds of internal security review and an internal penetration test in 2026. An independent test is planned after ISO 27001.

    What is true today

    Controls that are enforced in production right now — not aspirations.

    Encryption at rest

    Connection credentials and OAuth tokens are encrypted in the database with AES-256-GCM.

    Encryption in transit

    All traffic is served over HTTPS with HSTS (2-year, includeSubDomains, preload).

    Tenant isolation

    Every database query is scoped to a single tenant — no tenant can read another's data.

    Role-based access control

    Five roles, from super owner to viewer, are enforced server-side for every privileged action.

    PII redaction in logs

    Our logging pipeline redacts personal identifiers — emails, phone numbers, IBANs, and national IDs — before they reach application logs.

    Append-only audit trail

    Logins, role changes, billing, and data requests are recorded and retained for one year.

    Rate limiting

    A three-tier limiter protects login, API, and webhook surfaces from abuse.

    Webhook verification

    Inbound payment webhooks are verified before any billing state changes — by HMAC-SHA256 signature, or by a direct server-to-server query to the provider.

    Idempotency guards

    Idempotency keys prevent the same operation from being executed twice.

    Strong password hashing

    Passwords are hashed with bcrypt (cost factor 12); plaintext is never stored.

    Injection-safe queries

    Access to our own data store uses parameterized queries — request values are passed as bound parameters, not concatenated into SQL strings.

    Secrets isolation

    Encryption keys, database credentials, and provider tokens are stored as environment secrets, never committed to source code.

    Scoped API Keys

    Keys are prefixed with exo_ and cryptographically hashed before storage — never kept in plaintext. A key is therefore shown once, at creation: re-displaying it is impossible, not merely disallowed.

    Token-Based Authentication

    JWT access + refresh tokens with automatic rotation

    Two-factor authentication by email

    Require a 6-digit email code when signing in from a new device

    Two-layer SSRF guards on all outbound and connector traffic — the resolved IP is re-checked at connect time, and obfuscated address forms are blocked

    Enterprise controls by default. Full detail on the Trust page.

    Connection Protection

    Connection HTTP nodes include automatic protection mechanisms that prevent cascading failures when external APIs become unavailable.

    Compliance status

    What we have, and what we do not have yet.

    What we have earned, what is in motion, and what we have not done yet.

    FrameworkStatusWhat it means
    PDPL (Personal Data Protection Law)Self-assessedDPIA and procedures signed in September 2026; a data processing agreement with OpenAI is on file; SDAIA standard clauses with OpenAI are requested, not yet signed. Not a certification.
    SDAIA National Data Governance PlatformRegisteredRegistration No. 3260008321.
    NCA ECC-2:2024MappedOur controls are mapped to the framework as a self-assessment. This is not a certification.
    ISO/IEC 27001RoadmapNot yet certified. Preparation is under way.
    SOC 2 Type IIRoadmapNot yet audited. We will not show a SOC 2 badge before an independent audit.
    Encryption (AES-256)ImplementedAES-256-GCM at rest for sensitive fields; HTTPS + HSTS in transit.
    Tenant isolation & RBACImplementedPer-tenant query scoping and server-side role checks on every privileged route.

    SOC 2 Type II and ISO 27001 are on our roadmap — we are not yet audited, and we will not display a badge we have not earned. Ask us for our current control mapping (NCA ECC-2:2024) and we will share it.

    Built to meet the highest standards of compliance and security for the Saudi and MENA enterprise market.

    SOC 2 Type II — Roadmap

    On our certification roadmap — controls implemented, not yet independently audited. We won't display a badge we haven't earned.

    ISO 27001 — Roadmap

    Not yet certified. Preparation is under way.

    PDPL programme, self-assessed

    Lawful basis, security controls and data-subject requests are in place. We assess this ourselves; it is not a certification.

    Saudi Data Residency

    Production runs in-Kingdom on STC Cloud in Riyadh — your platform data is stored and processed inside Saudi Arabia. See our Trust page for the verified, current status.

    Providers

    The main services that may handle your data, and where.

    From our data residency audit, revised 10 November 2026.

    PurposeProviderLocation
    Application, database, uploads, daily backupsSTC CloudRiyadh, Saudi Arabia
    Off-site backup copyHuawei Cloud OBSRiyadh, Saudi Arabia
    AI processing (default)OpenAIUnited States
    AI processing (your own model, any plan)Your own model endpointWhere you host it
    Email sendingOracle Cloud; Microsoft 365 keeps a Sent Items copy and is the backup senderJeddah, Saudi Arabia; Microsoft regions
    SMS and WhatsAppTwilio, MottaslGlobal; Saudi Arabia
    Card paymentsPayTabs, StripeSaudi Arabia; United States
    Sign in with Google (optional)GoogleGoogle regions
    Web search in the Co-Pilot and flow builderTavily, Brave, OpenAIUnited States / Europe; search text is stripped of secrets and personal data first

    IP data © DB-IP.com (CC BY 4.0)

    How we work

    The day-to-day practices behind the controls.

    Independent code review

    Major changes go through an independent architect review before they ship.

    Continuous scanning

    Dependency, SAST, and secrets scanning catch vulnerabilities early.

    Incident response

    Security incidents are tracked with a documented process aligned to PDPL breach-notification timelines (SDAIA, 72 hours).

    Durable audit record

    An append-only audit trail keeps a tamper-evident record of security-relevant events.

    Security in the product

    Enterprise Security

    Security is not optional

    Every layer of Exomations is designed for enterprise security requirements.

    • Encrypted Credential Vault AES-256 encrypted storage for all API keys and credentials
    • Scoped API Keys Generate scoped API keys for external integrations, with optional expiry and instant revocation
    • Token-Based Authentication JWT access + refresh tokens with automatic rotation
    • Full Tenant Isolation Complete data separation between organizations
    • Per-Plan Rate Limiting Protect platform resources with tenant-scoped limits
    • Immutable Audit Trail Every action logged and tamper-proof for compliance
    security.config
    encryption: AES-256-GCM
    api_keys: one-time display, hashed
    auth: token-based (access + refresh)
    passwords: cryptographically hashed
    tenant_isolation: complete separation
    rate_limit: per-plan enforcement
    credentials: encrypted at rest
    audit: immutable append-only

    Security & compliance

    Enterprise controls by default. Full detail on the Trust page.

    • AES-256 encrypted credentials at rest
    • JWT access/refresh auth, with optional email-code 2FA and trusted devices
    • Per-tenant data isolation enforced server-side
    • Two-layer SSRF guards on all outbound and connector traffic — the resolved IP is re-checked at connect time, and obfuscated address forms are blocked
    • NCA ECC & PDPL-aligned compliance posture
    • Tamper-evident audit logging on sensitive actions

    Request the whitepaper or book an architect call

    Tell us what you need to verify. We will send our control documentation or set up a call with someone who built the platform.

    What would you like?

    Where a security review usually starts

    Where is our data hosted?

    The application, database, uploads and backups run on STC Cloud in Riyadh. Data you send to outside services, such as the default AI provider, is processed where they operate; see the provider list.

    Does our data leave the Kingdom when we use AI?

    With the default platform AI, the text sent to the model is processed by OpenAI in the United States. On any plan you can use your own model, including one hosted in the Kingdom, or switch AI off.

    Who at Exomations can see our credentials?

    Credentials are stored encrypted with a key for your workspace, are never shown in the app, and are removed from logs. The production server is administered over key-only SSH by a named engineer, and admin actions in the app are audit-logged.

    Are you ISO 27001 or SOC 2 certified?

    Not yet. Both are on our roadmap. Today we are registered with SDAIA, our PDPL programme is self-assessed, and our controls are mapped to NCA ECC.

    Can you fill in our security questionnaire?

    Yes. Request the security pack and our register of more than 200 security controls, available under NDA, answers most questions.

    We are in a regulated sector. Can we have our own instance?

    Yes, by contract: a dedicated database and deployment in STC Cloud or another region you name in the Kingdom or the GCC.

    Limitations

    Questions from your security team?

    7-day trial1 SAR card checkHosted in Riyadh