Skip to content
chapterwise ← Back to Chapterwise

Trust & Transparency

Security

This page explains how Chapterwise is protected, in calm and factual terms. We describe what we actually do today, and we are careful not to overstate it.

Built on Microsoft Azure

Chapterwise is hosted on Microsoft Azure. Azure provides enterprise-grade cloud infrastructure, including physical datacenter security, resilient cloud infrastructure, secure networking, encryption capabilities, identity services, monitoring, and availability capabilities.

Chapterwise benefits from the security capabilities of Microsoft Azure while implementing its own application-level security controls. Being hosted on Azure does not mean Microsoft certifies or endorses Chapterwise — it means we build on a mature, independently audited platform.

Sources: Microsoft Trust Center

Shared responsibility

Cloud security is shared. Microsoft secures the cloud infrastructure — the datacenters, physical network, and platform services beneath the application.

Chapterwise is responsible for the layer you interact with: the application, customer data, authentication, authorization, business logic, and the retirement calculations themselves. We hold that responsibility directly and design our controls around it.

Sources: Azure shared responsibility model

Compliance foundations

Microsoft Azure maintains a broad portfolio of internationally recognized compliance certifications and assurance programs. Examples include ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1, SOC 2, SOC 3, and CSA STAR.

These certifications apply to Microsoft Azure services, not to the Chapterwise application. Chapterwise does not claim any of them for itself. We reference them so you understand the assurance level of the platform underneath us. You can review the current, authoritative list directly from Microsoft.

Chapterwise is not ISO or SOC certified. Independent security assessment for the application is part of our roadmap.

Sources: Azure compliance offerings · Microsoft Service Trust Portal

Authentication

How you sign in

Accounts are managed through Microsoft Entra External ID. Sign-in uses standard, modern authentication flows, and Chapterwise never stores your password.

Password protection

Credential handling and password protection are managed by the identity platform, not by the Chapterwise application. The browser never receives database credentials.

Multi-factor authentication (roadmap)

Support for multi-factor authentication is planned so you can add a second factor to your account.

Account recovery

Account recovery is available through your identity provider using a verified email one-time code.

Authorization

Access is organized around households. You only access the households you have been granted access to, and your role within a household determines what you can do.

Household permissions and roles

Plans belong to a household. Membership and role are checked on the server for every request — the interface reflects your access, but the server is the authority.

Invitation model

Household invitations are bound to a verified email and a one-time invite code, and they expire. Invitations do not expose plan balances or financial details.

Least privilege

Roles are designed so members receive only the access their role requires. Exports require an authenticated session, and deletion requests additionally require authentication within the previous five minutes.

Encryption

Communication with Chapterwise is encrypted in transit over HTTPS, with HSTS enabled. Data stored in the platform is encrypted at rest using Azure platform encryption.

Application secrets are held in a managed secrets store rather than in application code. Azure-hosted application components use managed identity where configured, including access to customer planning data and secrets. Backups are handled by the managed data services.

Encryption protects data in transit and at rest; it does not by itself protect against a compromised account or an authorized household member exporting their own copy.

Sources: Azure encryption at rest

Secure development

  • Automated tests cover the financial engine and the planning experience, and run before changes are released.
  • Changes are reviewed and exercised through automated release checks before production deployment.
  • Dependencies are tracked and updated, with a goal of making dependency and vulnerability scanning a blocking check.
  • We improve controls continuously and respond to responsible vulnerability reports (see Responsible Disclosure).

We do not claim certifications we do not hold. Formal penetration testing and an independent security review are pre-launch commitments on our roadmap.