Trust · Compliance
Trust & compliance
Last updated: 2026-04-24
One page that summarises how XenithPulsehandles data across every product we ship — the consumer EOS Companion mobile app, our B2B ERP and POS suites, and the per-tenant integrations we operate for clients. Every legal page on this site is generated from this same source of truth.
Additional presence: Doha, Qatar
Courts of Doha, Qatar
Response within 30 days
MongoDB Atlas (AWS us-east-1)
Render (us-east region)
Bcrypt password hashing · secrets vaulted
1 · Who you are dealing with
XenithPulse (operating as XenithPulse Software) is a software company operating from Doha, Qatar, with an additional presence in Doha, Qatar. The team has been shipping production software since 2024.
XenithPulse Software is currently operated as a sole proprietorship and is not yet incorporated as a separate legal entity in either jurisdiction. We disclose this rather than imply otherwise. When the entity is formally incorporated, this page and our customer contracts will be updated and customers will be notified through release notes.
Our principal point of contact for any legal, privacy, or security matter is admin@xenithpulse.com.
2 · Governing law and dispute resolution
All customer-facing contracts and policies are governed by the laws of the State of Qatar, with exclusive venue in the Courts of Doha, Qatar for any dispute arising out of or relating to those contracts or our products.
Without prejudice to any mandatory consumer-protection rights you have under the laws of your country of habitual residence (including, where applicable, the European Union and the United Kingdom).
Pakistan was selected as the governing-law jurisdiction because our primary operations, our production infrastructure, our flagship customers, and the founding team all sit there today. This is a conservative, transparent choice; it does not attempt to claim a tax or regulatory residence we do not have.
3 · Infrastructure & data location
Where your data physically lives matters. Production infrastructure for our hosted products runs on:
- Compute: Render (us-east region)
- Database: MongoDB Atlas (AWS us-east-1)
- Object storage: AWS S3 (us-east-1)
- Realtime: Pusher Channels (eu / ap clusters depending on tenant)
- Push delivery: Apple APNs, Google FCM, Expo Application Services
Where personal data of users in the EU/EEA, the UK, or other jurisdictions with cross-border transfer rules is moved outside their region, transfers are made under Standard Contractual Clauses (SCCs) with each sub-processor.
4 · Sub-processors
We use third-party sub-processors only where necessary to deliver the service. Each is bound by contract to act on our instructions and to apply security controls at least as protective as our own.
| Sub-processor | Purpose | Region |
|---|---|---|
| Render | Application compute, deployment | us-east |
| MongoDB Atlas | Primary database for tenant data | AWS us-east-1 |
| Amazon Web Services | Object storage, logs, secrets | us-east-1 |
| Pusher Channels | Realtime event delivery (opaque payloads) | eu / ap |
| Expo Application Services | Push token vending for the EOS Companion app | us |
| Apple APNs | Push notification delivery to iOS devices | global |
| Google FCM | Push notification delivery to Android devices | global |
| Stripe | Payment processing for paid B2B subscriptions | us / eu |
| Meta Platforms (WhatsApp Business) | Customer messaging on tenants that opt in | global |
5 · Security practices
- All traffic encrypted with TLS 1.2 or higher.
- Passwords stored as bcrypt hashes; plaintext never written or logged.
- Multi-tenant isolation enforced server-side from the JWT — never from the URL or a client-supplied header.
- Production secrets held in a managed secret store and rotated on a scheduled basis.
- Network CRUD payloads are binary-schema compressed (~60% smaller than equivalent JSON), reducing the attack surface for replay-based exfiltration.
- Account-deletion intents on the EOS Companion app are signed with HMAC-SHA256 and bound to a username, tenant, and short expiry window.
Security disclosures should be sent to security@xenithpulse.com. Please do not file public issues for security bugs.
6 · Per-product compliance
Different products carry different obligations because they serve different audiences. The matrix below maps each product to its scope, its primary contract surface, and the policy/contact you should reach for.
Public consumer-facing iOS + Android app
B2B web ERP, per-tenant contract
Internal B2B web platform, per-tenant contract
B2B point-of-sale, per-tenant contract
On-premise utility, no data egress
B2B web ERP (in development)
7 · Client-hosted policies
We host individual privacy / usage policies on behalf of clients who use our messaging or POS infrastructure to communicate with their own customers. These pages are the client's policy (the client is the data controller); we are listed as a sub-processor.