Part H · CS-CF-03
Sub-processor List and Data Processing Terms
1. Purpose
This document lists the third parties (sub-processors) that we engage to process customer data in providing the Cornerstone platform. It forms part of our Terms of Service and supports our Privacy Policy.
It is published so that customers can assess our supply chain without having to ask, and so that we can give the notice of change described in section 5.
2. What counts as customer data
Customer data means content that a customer or its users or invited parties put into the platform, together with account, usage and support information relating to them. It includes any personal information contained in that content.
3. Current sub-processors
3.1 Infrastructure and platform
- Application hosting and delivery. Handles requests, session data and content held transiently in memory. Requests are served from Sydney. Nothing is retained beyond the request except request logs, kept for 30 days.
- Database. A self-hosted database on Australian-owned infrastructure in Sydney, holding all structured platform data for the subscription term.
- File and document storage. Uploaded files and generated documents, stored in Sydney and replicated to Melbourne for backup, kept for the subscription term.
3.2 Artificial intelligence
- Large language model provider. Powers the assistant, extraction, summarisation and drafting. It receives prompts, attached files, extracted text and the generated responses. Processing occurs outside Australia. Content is deleted within 30 days and is not used for model training.
Our commitments on AI processing. Content sent to the model provider is not used to train models. It is sent for the purpose of producing the requested output and for no other purpose. We do not send content to the model provider except where a user has invoked a feature that requires it.
Confirmed retention position. Our model provider deletes commercial API inputs and outputs within 30 days, other than where it is required to retain them to enforce its usage policy or to comply with law. Zero data retention arrangements are available and we will pursue one where a customer's requirements make it necessary. This position is reconfirmed at least annually, and on any change to the provider's terms, under our Vendor and Sub-processor Risk Management Policy.
3.3 Identity and access
These apply only once the feature is offered and an organisation switches it on. Neither is available today.
- Sign-in with Microsoft work accounts. Name, email and tenant identifier, kept for the life of the connection and then deleted.
- Enterprise single sign-on and directory sync. Name, email and group membership, kept for the life of the connection and then deleted.
3.4 Payments
- Card processing, subscription billing and invoicing, provided by Stripe Payments Australia Pty Ltd. Billing contact, billing address, card token and transaction history, kept for 7 years to meet financial record obligations.
We do not store full card numbers. Card data is collected directly by the payment provider in a hosted field and never transits our systems.
3.5 Communications, support and monitoring
- Transactional and notification email. Recipient name, email and message content, kept for 30 days.
- Crew notifications by message. Mobile number and message content, kept for 30 days.
- Error and performance monitoring. Error traces, user identifier and request metadata, kept for 90 days.
- In-platform support ticketing, which runs inside the platform in Australia. Name, email, ticket content and attachments, kept for 3 years.
3.6 Internal business systems
These process our own business records, including customer contact and billing details, but do not hold customer project content.
These are our accounting package, which holds invoicing and financial records, our customer contact records, and our internal document storage.
4. Our commitments on sub-processors
We commit that, for every sub-processor that processes customer data:
- We carry out a documented risk assessment before engagement, covering security posture, data location, retention, breach notification and sub-contracting.
- We have a written contract that limits processing to the purpose of providing the service, requires confidentiality, requires appropriate technical and organisational security measures, prohibits use of customer data for the provider's own purposes including model training, and requires prompt breach notification to us.
- We remain responsible to our customers for the acts and omissions of our sub-processors in relation to customer data.
- We reassess each sub-processor at least annually and whenever we become aware of a material change in its security posture.
- We do not engage a sub-processor to process customer content outside Australia except for the AI processing described in section 3.2.
5. Notice of change
We will publish an updated version of this document at cornerstoneapp.com.au before adding or replacing a sub-processor that processes customer content.
Customers on a written agreement may subscribe to change notifications and will receive at least 30 days notice of a new sub-processor that processes customer content. A customer with a reasonable, documented objection on data protection grounds may raise it within that period. We will work with the customer to find a resolution, and if none is available the customer may terminate the affected part of the subscription without penalty and receive a pro rata refund of prepaid fees.
Self-serve customers receive notice by publication on this page.