Security Policy — Calmony DD
DRAFT FOR LEGAL REVIEW — NOT FOR USE. Prepared 29 September 2026. Items marked [TO CONFIRM] need confirmation before publication.
Last updated: 29 September 2026
This policy describes how agentOS Proptech Group Ltd, trading as Calmony, protects Calmony DD and the data in it.
1. Ownership
[TO CONFIRM: named role accountable for security, e.g. Head of Technology.] Security questions and vulnerability reports go to support@calmony.co.
2. Minimising what we hold
- Payer bank details are not stored in Calmony DD. Account holder name, sort code, account number, mobile and address are passed securely to Modulr FS Limited, which provides the Direct Debit service, and held there.
- We keep only what we need to manage Direct Debits: the payer's email, mandate and collection records, the account-name-check result, the identity-verification video where the business requires one, and evidence of the payer's authorisation.
- Every category of personal data has a defined retention period, after which it is deleted automatically. Records are kept for 6 years where the Direct Debit Scheme or HMRC requires it.
3. Hosting and infrastructure
- The application is hosted on Vercel in the London and Paris regions. The database is hosted by Neon in the UK/EU.
- Identity-verification videos are held in private file storage and are only accessible to the business that requested them.
- Production secrets, such as API keys and signing secrets, are held in the hosting platform's encrypted configuration, not in code.
4. Data protection in transit and at rest
- All traffic to and from Calmony DD uses TLS (HTTPS).
- Data is encrypted at rest by our database and storage providers [TO CONFIRM].
- Connections to Modulr are authenticated and made over TLS.
5. Access control and isolation
- Each business's data is kept separate. Every request is scoped to the signed-in user's organisation, and users can only see data for organisations they belong to. [TO CONFIRM: whether database row-level security is also enforced for the application's database role.]
- The application connects to its database with a restricted, least-privilege role. Schema changes use a separate role that the running application does not have.
- Staff access to production systems is limited to those who need it [TO CONFIRM: access review process and multi-factor authentication for staff and customer sign-in].
6. Protecting incoming payment events
- Every event Modulr sends to Calmony DD (for example a mandate activation, collection or return) must carry a valid cryptographic signature (HMAC) from Modulr, or it is rejected.
- Events are checked against a time window, and each can only be used once (replay protection), so a captured event can't be resent.
7. Application security
- The service uses a Content Security Policy, and protects forms against cross-site request forgery.
- Public endpoints return only generic error messages, and internal details are logged privately.
- The codebase is regularly reviewed by automated security, dependency and quality audits, and findings are fixed before release.
8. Monitoring and incident response
- Errors and security-relevant events are logged and monitored.
- If we become aware of a personal data breach affecting payer data, we will notify the affected business without undue delay, and within 48 hours, so it can meet its own obligations, including notifying the ICO within 72 hours where required.
- [TO CONFIRM: backup frequency, restore testing and disaster-recovery targets; penetration testing schedule.]
9. Reporting a vulnerability
If you believe you have found a security vulnerability in Calmony DD, email support@calmony.co with the details. Please don't access other people's data or disrupt the service while testing. We will acknowledge your report and keep you informed as we investigate.