Privacy Policy

How Ordexs handles personal data

This Privacy Policy explains how Ordexs collects and uses information when merchants, team members, shoppers, and visitors use our websites, dashboard, storefront tools, integrations, and related services.

Last updated: October 14, 2026

1. Scope

Ordexs provides commerce software for online sellers, including storefronts, order management, delivery integrations, payments, analytics, an AI assistant, and automation tools. This Policy applies to Ordexs services, websites, dashboard pages, and communications.

Merchants using Ordexs are responsible for the customer data they collect through their storefronts. Ordexs processes that customer data to provide the services requested by the merchant.

2. Information we collect

  • Account information, such as name, email address, authentication provider, two-step verification settings, store name, and team settings.
  • Store and business information, such as products, inventory, pricing, delivery settings, integrations, and storefront content.
  • Order and customer information, such as customer name, phone number, email, address, order items, payment method, payment status, delivery status (see what each status means), and notes.
  • Team communication, such as team chat messages, shared files, and the time and participants of voice calls. Call audio is relayed live and is not recorded.
  • AI assistant conversations, such as the questions you ask (typed, or spoken and turned into text), the answers, and the changes you confirm.
  • Developer data, such as API keys (we keep only what is needed to recognise a key), API request logs, and webhook settings and delivery logs.
  • Usage information, such as dashboard actions, device data, browser data, IP address, page views, sessions, referrals, and performance events.
  • Integration information, such as courier account settings, payment gateway settings, marketing pixel settings, webhook configuration, and messaging preferences.
  • Billing information for your own Ordexs subscription, such as your plan, subscription status, billing dates, invoice history, and the identifiers our payment provider uses for your account. Card and bank details are collected and held by our payment provider, not by Ordexs.

3. How we use information

  • To create accounts, authenticate users, maintain sessions, and protect the dashboard.
  • To operate merchant storefronts, carts, checkout flows, payments, products, orders, analytics, and stock features.
  • To send orders to delivery providers, refresh delivery statuses, and record shipment history.
  • To run team chat, calls, notifications, the AI assistant, the Platform API, and webhooks.
  • To provide marketing and analytics integrations when merchants enable them.
  • To improve reliability, security, performance, customer support, and product quality.
  • To enforce our Terms, prevent abuse, investigate incidents, and comply with legal obligations.

4. Sharing information

We share information only when needed to provide, secure, or improve the service. We do not sell personal data.

  • Billing. Ordexs subscriptions and credit packs are sold by Paddle.com Market Ltd, our authorised reseller and Merchant of Record. When you buy a plan, Paddle collects your billing name, email, billing address, country, and payment details directly, and shares back the information we need to activate your plan and provide support. It does not include your full card number, which Ordexs never receives or stores. See Paddle's privacy notice.
  • Infrastructure providers that host and run Ordexs for us: Cloudflare (application hosting, file and image storage, live calls), Supabase (database and sign-in), and an email delivery provider for account and billing emails.
  • AI model providers. When you use the assistant, your question (or your voice recording, to turn it into text) and the store data needed to answer it are sent through OpenRouter to the model provider that answers (such as Anthropic, Google or DeepSeek). They process it to produce the answer.
  • Payment gateways a merchant connects, such as Slick-Pay. The shopper enters card details on the gateway's own page; Ordexs receives only the payment status and reference.
  • Merchant-selected integrations, such as courier companies, advertising platforms, pixels, webhook destinations, apps using the merchant's API keys, and messaging providers, including the WhatsApp Business Platform, operated by Meta, which Ordexs uses to send order-related messages (such as order confirmations) on a merchant's behalf when the merchant connects it. Learn how this works.
  • Legal and safety recipients, when required by law or needed to protect Ordexs, users, customers, or the public.
  • Business transfer recipients, if Ordexs is involved in a merger, acquisition, financing, or sale of assets.

These providers may process data outside your country. We use providers that protect it under their own security and privacy commitments.

5. Support access

When a merchant asks for help, or to investigate a fault, security issue, or abuse, authorised Ordexs staff may view that merchant's dashboard as the merchant sees it. These sessions are time-limited, recorded with who started them and why, and are not counted as the merchant's own activity.

6. Cookies and tracking

We use cookies and similar technologies for authentication, security, language preferences, analytics, and performance. Merchant storefronts may also use pixels or tracking tools that the merchant enables, such as Meta or TikTok integrations.

Merchants are responsible for presenting any customer-facing cookie notices or consent flows required for their storefront and market.

7. Security and retention

We use technical and organizational safeguards designed to protect data, including access controls, two-step verification, encrypted transport, row-level access policies, and limited access to sensitive credentials.

We retain information for as long as needed to provide the service, comply with legal obligations, resolve disputes, prevent abuse, and maintain business records. Some logs are kept only briefly: webhook events are deleted after 30 days, and webhook delivery logs after 7 to 30 days depending on the plan. Other analytics data may be aggregated to reduce risk and cost.

8. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export, or restrict certain personal data. Merchants can update many account and store details directly in the dashboard. For step-by-step instructions on requesting deletion, see our data deletion guide.

Customers of a merchant should contact that merchant first for requests about orders, delivery, payments, or storefront purchases. Ordexs can assist the merchant when appropriate.

Merchants can also mark a customer as do-not-contact from the dashboard. Once set, Ordexs skips that customer for every automated message (WhatsApp, SMS, or email) across order confirmations, campaigns, and automations, before any send is attempted.

9. Children

Ordexs is designed for businesses and is not intended for children. We do not knowingly collect personal data from children through merchant accounts.

10. Changes to this Policy

We may update this Policy as Ordexs evolves. If changes are material, we will take reasonable steps to notify users, such as posting a notice in the product or updating the effective date.

This Policy is published in English, Arabic and French. If the versions differ, the English version prevails.

11. Contact us

For privacy questions or requests, contact Ordexs at privacy@ordexs.com. For general support, use the contact page, or browse guides in our Help Center.