Security
Last updated: 29 October 2026
ConnectWiz is operated by SIMURGH MEDIA, LLC (Delaware, USA). This page describes the security controls that protect the platform and the data our customers entrust to it. It lists only controls that are in place today, and says plainly what we do not have.
Where data is hosted
- The application servers and the primary database are in the United States.
- Attachments and media are stored in Cloudflare R2 object storage, separate from the application server.
- Database backups are kept with a different provider from the production server (see Backups below).
- The companies that process data for us, what they process and where, are listed on the Sub-processors page.
Workspace isolation
Every workspace's data is separated in the database itself, not only in application code. Each workspace-scoped table is protected by PostgreSQL row-level security, enforced even for the table owner, so a query that forgets to filter by workspace returns nothing instead of another workspace's records.
- The application connects with a database role that cannot bypass row-level security.
- Backups run as a separate read-only role.
- Inside a workspace, what each member can see and change is decided by roles and permissions enforced on the server.
Encryption
- In transit: TLS for every external connection — browsers, the mobile app, channel and platform APIs, and our sub-processors.
- At rest: the credentials a workspace connects (API keys, access tokens) are encrypted at the application layer before they are stored; two-factor secrets and recovery codes are encrypted; passwords are stored only as one-way hashes; the hosting platform encrypts the disks.
- Secrets are never kept in source code. They live in the server environment and in provider dashboards.
Accounts and access
- Two-factor authentication is available for every team account; publishing custom code to a website requires a fresh two-factor check.
- Sessions and API access use signed, expiring tokens. Website visitors get a separate, narrowly scoped token that carries no staff rights.
- Access to production systems is limited to named administrators, used only for operation, support and incident response, and bound by confidentiality.
- ConnectWiz staff can open a workspace only as far as that workspace allows under Settings → Security → Platform access.
Application security
- Incoming webhooks from channels and platforms are checked against the sender’s signature before anything is processed.
- Sign-in and every public endpoint, such as the website chat and the cookie banner, are rate limited.
- Repeated deliveries from a provider are recognised and never recorded twice.
- When a security decision cannot be made — an unknown workspace, an invalid token, a signature that does not verify — the request is refused.
- Custom code a workspace adds to its website through the tag manager is scanned before publishing and can be rolled back; in a workspace with more than one member it needs a second person’s approval by default, which only an admin can turn off, with a two-factor check and an audit record.
Development and monitoring
- Every change passes automated gates before release: static analysis, type checks and more than 13,000 automated tests, including tests that fail if a security control is removed.
- Application errors are reported to an error-monitoring service with personal data scrubbed before sending; server logs record sign-in events, failed webhook signatures and rate-limit events.
- The source code is held in a private repository.
Backups
- The database is backed up twice a day to private object storage with a different provider from the production server, and each backup is kept for 30 days.
- The hosting provider also keeps a daily snapshot of the server for 7 days.
- A backup that looks incomplete is rejected and reported, and old backups are deleted only after a new one has been stored.
Incidents
We follow a written incident response procedure. If a security incident affects your data, we notify you within 48 hours of becoming aware of it, as our Data Processing Agreement states, and keep you informed until it is closed.
Certifications
ConnectWiz does not currently hold ISO 27001 certification or a SOC 2 report, and we do not commission annual third-party penetration tests. We say so here so that you can assess the risk accurately. Our written security policies and detailed answers to security questionnaires are available on request.
Reporting a vulnerability
If you believe you have found a security vulnerability in ConnectWiz, email [email protected] with “Security” in the subject. We acknowledge every report within one business day. Please do not access other people’s data and give us reasonable time to fix the issue before disclosing it.