01
In-memory processing
Uploaded documents and generated outputs are processed in memory and are not retained after the task is complete.
Privacy Policy
How Cadence handles website and customer information.
Effective 22 April 2026. This page explains the categories of information Cadence handles, why it is used, and how privacy questions can be raised.
Scope of this policy
This policy applies to the Cadence website, direct enquiries received through the contact form or email, and customer-facing discussions about the Cadence platform.
Where Cadence provides platform services to a customer, Cadence may act as a processor for customer operational data and separately act as a controller for its own business, security, and audit records.
Information Cadence may collect
Website enquiries: name, company, work email address, and the details included in a direct enquiry.
Customer account and security records: user account details, authentication records, audit metadata, and support communications.
Platform configuration data: client settings, module assignment information, and encrypted operational secrets where required for a live module.
Why the information is used
Enquiries: to respond to contact requests, discuss potential platform use, and manage follow-up communication.
Platform delivery: to provide module access, maintain customer configurations, secure user access, and support customer operations.
Security and compliance: to monitor access, enforce authentication controls, retain necessary audit records, and meet privacy or regulatory obligations.
How information may be shared
Cadence uses a small number of service providers for hosting, database infrastructure, transactional email, and source control. Relevant categories are summarised in the Trust Centre.
Cadence does not use advertising pixels on this website and does not sell enquiry information to third parties.
Retention and deletion
Enquiry information is retained for as long as reasonably necessary to manage the conversation and related business records. Platform and security records are retained according to operational, legal, and security needs, with scheduled cleanup used for certain token and audit data.
Where Cadence acts as a processor for customer operational data, customer-specific retention and deletion requests are handled within the applicable service relationship and documented process.
Privacy questions and requests
Privacy-related questions, requests, or complaints can be sent to hello@cadence-platform.com. Requests may be handled directly by Cadence or referred to the relevant customer where Cadence acts as a processor on that customer's behalf.
Security & compliance
Built for regulated work.
Cadence is designed for environments where uploaded files, operational credentials, and client records need clear controls from the first day of delivery.
02
Encrypted credentials
Operational secrets are encrypted at rest and decrypted in memory only when a module needs them.
03
MFA enforced
Every user account is protected with multi-factor authentication and access is limited by role.
04
Metadata-only audit logs
Audit trails record who did what and when without storing document content, raw transaction data, or secrets.
05
Privacy review before change
New modules and material processing changes are reviewed against privacy obligations before release.
06
EU and Australian privacy support
Cadence is positioned to support EU and Australian work with documented controller-processor boundaries and data minimisation.