Trust Centre. Every answer names its evidence.
For the team that runs vendor risk at a fund. A “Yes” points to the file in our repository that backs it; a “No” is written as a “No”. Last updated November 2026.
Controls
| Area | Answer | What is true today | Evidence in the repository |
|---|---|---|---|
| Data location | Yes | The shared platform runs on one Microsoft Azure virtual machine in Sweden Central (EU). The weekly restore test runs on a separate Azure database server in North Europe. | deploy/azure/provision.shdeploy/azure/restore-drill.sh |
| Sub-processors | Yes | Every third party that receives personal or customer data is listed with what it receives and where. A test fails when the code calls an external host that is not on the list. | marketing/app/subprocessors/subprocessors.tsapps/portal/src/__tests__/honesty/externalHostsAreDisclosed.spec.tsbackend/tests/unit/test_subprocessor_hosts.py |
| Tenant isolation | Yes | Customer data is separated by tenant with PostgreSQL row-level security. With enforcement on, the service checks at start-up that its own database role cannot bypass the policies and that no row lacks a tenant. | backend/src/database/rls_schema.pybackend/tests/integration/test_rls_enforced_postgres.py |
| Encryption in transit | Yes | Traffic to the platform and to the API is encrypted with TLS. The reverse proxy issues and renews the certificates. | deploy/azure/compose.yml |
| Encryption at rest | Partial | Storage encryption of disks is the cloud platform default and is not configured in this repository. Third-party credentials that customers store (exchange and broker keys) are additionally encrypted by the application with a key held outside the database. | backend/src/utils/crypto.pybackend/src/services/integrations/tenant_account_credentials.py |
| Administrator access | Yes | Administrators sign in with a TOTP second factor. Any user can enable it. | backend/src/utils/totp_service.pybackend/src/middleware/auth.py |
| Audit trail | Yes | Account events are written to an append-only hash chain, each entry carrying the hash of the previous one. Data exports, exits and role grants are written to a separate durable journal, intent first and outcome after. | backend/src/services/auth/immutable_audit.pybackend/src/services/governance/audit.py |
| Backups | Yes | A logical database dump is taken every night, kept for 3 days in hot blob storage and up to 60 days in an Azure Files archive share. | deploy/azure/backup.sh |
| Restore test | Yes | Every Sunday the latest dump is restored on a separate database server and the table and row counts are compared with production. A failed run raises an alert. | deploy/azure/restore-drill.shdeploy/azure/restore-drill.run.shdeploy/azure/restore-drill.timerdeploy/azure/nyquist-alert@.service |
| Recovery point and time | Partial | The interval between backups is 24 hours, so after the loss of a disk or database up to 24 hours of changes can be lost. Restore time is measured by every restore test; the latest result is shown on this page when it has been published. Neither figure is a commitment. | deploy/azure/backup.shdeploy/azure/restore-drill.run.sh |
| Data export and exit | Yes | The owner of an organisation can download everything the organisation holds as one archive with a manifest of file hashes, and can leave the platform. Committed trades, execution events and audit journals are not deleted and stay linked to a pseudonymous account number; everything else is erased, including the files the people stored (reports, datasets, notebooks and exported register files) and, by a separate request to the analytics processor, their analytics profiles and events. A refusal of the analytics processor does not hold the exit: the act then says "not performed" for that step with the response code, and the step can be repeated from the act. A refusal of the file storage does hold the exit. The PDFs of report mailings are kept indefinitely. An act records what was erased, what was kept and the result of each outside step. A person in the shared legacy organisation can download an archive of only their own rows and then delete their own account the same way. | backend/src/services/tenant_privacy/registry.pybackend/src/services/tenant_privacy/exit.pybackend/src/services/tenant_privacy/objects.pybackend/src/services/tenant_privacy/registers.pybackend/src/utils/register_paths.pybackend/src/services/tenant_privacy/analytics_erasure.pybackend/src/services/tenant_privacy/analytics_retry.pybackend/src/services/tenant_privacy/account_exit.pybackend/src/services/tenant_privacy/export.pybackend/tests/unit/test_tenant_privacy_api.py |
| Session recording | Yes | Sessions are recorded only on the public demo. The signed-in platform is not recorded. | packages/@nyquist/composables/src/analytics/providers/posthog.tsmarketing/app/privacy/page.tsx |
| Model providers | Yes | Customer books are not used to train models. Hosted model providers receive only what a model feature needs, and are listed with the sub-processors. | marketing/app/privacy/page.tsxmarketing/app/subprocessors/subprocessors.ts |
| AI policy of a firm | Yes | An administrator of a firm can switch AI off, allow only some model providers, switch the assistant, natural-language queries and written explanations on or off one by one, and decide whether data from the firm's books may be sent to a hosted model; until the administrator allows it, that data is not sent. A refused function answers with the reason. Every call to a model is recorded as metadata only (who, function, provider, model, tokens, kinds of data, outcome of the figure check), never the text; the journal is exportable by the administrator and kept for the period the firm sets, at least six months. Results of quality evaluations per function are not published. | backend/src/services/ai_governance/policy.pybackend/src/services/ai_governance/gate.pybackend/src/services/ai_governance/journal.pybackend/src/services/ai_governance/retention.pybackend/src/api/firm_admin.pybackend/tests/unit/test_ai_governance_gate.py |
| Vulnerability disclosure | Yes | Reports go to security@nyquist.pro under a published policy and a security.txt. Python and JavaScript dependencies are audited in the CI pipeline. | apps/portal/public/.well-known/security.txtmarketing/app/disclosure/page.tsx.gitlab-ci.yml |
| Accessibility | Partial | A self-assessed accessibility conformance report against WCAG 2.2 Level A and AA is published at /accessibility/. It marks each criterion supports, partially supports, does not support, not evaluated or not applicable, and lists what was not done: no screen-reader test and no test in Windows high-contrast mode. | marketing/app/accessibility/acr.mjse2e/sweeps/a11y-sweep.mjs |
| Penetration test | No | No third-party penetration test has been done. | — |
| SOC 2 and ISO 27001 | No | Not certified. | — |
| Legal entity and contract | No | Nyquist is not yet a legal entity, so no contract, data processing agreement or service-level agreement can be signed today. | marketing/app/legal/page.tsx |
| Availability commitment | No | No availability target is promised and no availability percentage is published. The status page shows the current state. | — |
| Incident notification deadline | No | No notification deadline is promised. A deadline would be set in the customer contract. | — |
Backups and recovery
- Backups: daily at 03:00 UTC, kept 60 days.
- Interval between backups: 24 hours. After the loss of a disk or database up to 24 hours of changes can be lost.
- Restore test: Sundays at 04:30 UTC, on a separate database server.
- No restore-test result has been published yet.
These are intervals and measured values, not commitments. No recovery time or point is promised.
Sub-processors
11 providers receive data from our servers and 2 are contacted directly by your browser. Each one is listed with what it receives and where on the sub-processors page. The platform is hosted on Microsoft Azure in Sweden Central (EU).
Incidents
- Failed backups and failed restore tests raise an alert to the team. The alert template is in the repository.
- An incident that affected customers is recorded in the incident journal on the status page, with its timeline, impact, cause and the commit that fixed it. The journal is not edited after the fact; a correction is a new entry.
- The status page shows the current state only. It carries no availability percentage, because none is measured.
- No notification deadline is promised today. A deadline would be set in the customer contract.
The current state and the incident journal are on the status page.
Product analytics
The signed-in platform sends these events to product analytics. Sessions are not recorded there.
- Pages opened and the order in which they are opened
- Clicks on interface elements
- JavaScript errors
- Page timings
DORA article 30
Compliance with DORA is the obligation of the financial entity. This is a map of the points a contract covers, not a statement of compliance.
| Point | What exists today | Can it be put in a contract now |
|---|---|---|
| Description of the service and of service levels | The service is described on the platform pages. No service levels are promised. | Not possible until a legal entity exists. |
| Locations where data is processed | Microsoft Azure, Sweden Central, with the restore test in North Europe. Other recipients are listed on the sub-processors page, with their regions. | Not possible until a legal entity exists. |
| Access, inspection and audit rights | A tenant owner can export the organisation’s data and journals. No third-party audit exists. | Not possible until a legal entity exists. |
| Assistance in an ICT incident | Incidents are recorded on the status page. No response time is promised. | Not possible until a legal entity exists. |
| Conditions for sub-contracting | The sub-processors page is the list; it is updated when a provider is added or removed. | Not possible until a legal entity exists. |
| Termination and exit strategy | Export of all organisation data and exit with an act are built into the platform. A transition period would be set by contract. | Not possible until a legal entity exists. |
Vendor-risk pack
The same facts as one document for your questionnaire: Markdown or JSON. Filled CAIQ-Lite and AITEC-AIMA questionnaires are issued on request and follow the controls table. Send them to security@nyquist.pro.
