Verilaud Data Processing Addendum
Version 1.0 — Effective [date]
DRAFT. Based on the DPA in draft.md, revised to match the code (see 00-code-assessment.md). Items in [square brackets] must be completed.
This Data Processing Addendum ("DPA") forms part of the Terms of Service between:
- Service Provider: [Full legal name], an Australian sole trader trading as Verilaud, ABN [ABN] ("Verilaud", "we", "us"); and
- Customer: the individual or organisation that subscribes to or uses Verilaud, including a team owner acting for a team ("Customer", "you").
It applies where Verilaud processes Personal Data on behalf of the Customer in providing the service.
1. Definitions
- Data Protection Laws: applicable privacy and data protection law, including the EU GDPR, the UK GDPR, the Australian Privacy Act 1988 where applicable, and associated regulations.
- Personal Data: information relating to an identified or identifiable natural person, or equivalent information protected under Data Protection Laws.
- Processing, Controller, Processor, Personal Data Breach: as defined in Data Protection Laws.
- Subprocessor: a third party engaged by Verilaud to process Personal Data on behalf of the Customer.
- Customer Content: content the Customer or its team members create or upload ("Your Content" in the Intellectual Property Agreement).
Terms not defined here have the meaning given in Data Protection Laws.
2. Roles of the parties
2.1 The Customer is Controller, or a Processor acting for another Controller, of Personal Data it submits to or manages through Verilaud (principally Customer Content and team membership data). 2.2 Verilaud is Processor when processing that Personal Data on the Customer's documented instructions to provide the service. 2.3 Verilaud is an independent Controller for Personal Data processed for its own purposes: account registration and administration; authentication and account security; subscription administration and billing records; operational diagnostics and service reliability; fraud and abuse prevention and legal compliance; and direct service communications to the Customer and its users. The Privacy Policy governs that processing. 2.4 Verilaud is not a Controller of Personal Data merely because it provides the infrastructure through which the Customer manages it. 2.5 Each member of a team is also a user with their own account. Where a team owner is the Customer, members' account data is processed by Verilaud as Controller and team content as Processor, as above.
3. Subject matter and duration
3.1 The subject matter is provision of the Verilaud collaborative songwriting and audio workspace service. 3.2 Processing includes hosting, storing, organising, synchronising, transmitting, displaying, converting, modifying, backing up and deleting Personal Data as necessary to provide the service. 3.3 Processing continues for the Customer's use of the service and the retention periods in section 15 and the Terms of Service.
4. Nature and purpose of processing
Verilaud processes Personal Data to:
- provide collaborative workspaces and team functionality;
- store and manage project information, lyrics, chords, recordings, audio regions, comments and related material;
- authenticate users and apply roles and permissions;
- synchronise and transmit project information between users;
- perform audio processing (conversion to FLAC, waveform generation, transposition, time-stretching, playback rendering, export) and store the resulting cached versions;
- provide technical support where authorised by the Customer;
- maintain security, availability, reliability and performance; and
- perform backups and restore data where necessary.
Verilaud will not process Personal Data for unrelated commercial purposes or independently exploit Customer Content.
5. Categories of Personal Data and data subjects
Personal Data:
- names and email addresses;
- account identifiers, team membership, roles and invitation records;
- collaboration activity, comments, replies and authorship of project contributions;
- Customer Content where it contains Personal Data, including voice or other audio recordings that identify individuals;
- per-user preferences (for example mute, volume, transposition);
- operational and diagnostic data created by hosting and network providers and our logs (which can include IP addresses and account identifiers); and
- support correspondence and troubleshooting information.
Data subjects: the Customer's employees, contractors and team members; invited collaborators; individuals whose Personal Data appears in Customer Content; and individuals mentioned in project materials or correspondence.
The service is not designed to require special-category or sensitive information. The Customer should not upload it unless processing is lawful and appropriate safeguards exist.
6. Customer instructions
6.1 Verilaud processes Personal Data only on the Customer's documented instructions, including through the service's normal functionality, the Terms and this DPA. 6.2 Verilaud may process Personal Data where required by law and, where legally permitted, will tell the Customer first. 6.3 The Customer is responsible for having a lawful basis for providing Personal Data to Verilaud, providing notices to affected individuals, obtaining necessary permissions, and ensuring its instructions comply with Data Protection Laws. 6.4 If Verilaud reasonably believes an instruction infringes Data Protection Laws, it will inform the Customer.
7. Confidentiality and personnel
7.1 Verilaud will ensure persons authorised to process Personal Data are subject to confidentiality obligations. 7.2 Access to Personal Data is restricted to those who need it to provide the service. 7.3 Verilaud will take reasonable steps to ensure authorised personnel understand their responsibilities. [As a sole trader, Verilaud currently has no employees; update if that changes.]
8. Security measures
8.1 Verilaud will implement and maintain appropriate technical and organisational measures to protect Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access, as described in Schedule 3. 8.2 Verilaud will periodically review these measures and make reasonable improvements as the service develops. 8.3 Verilaud does not warrant that any measure will eliminate all risk.
9. Subprocessors
9.1 The Customer authorises Verilaud to engage Subprocessors where reasonably necessary to provide the service, including those in Schedule 2. 9.2 Verilaud will impose data protection obligations on Subprocessors materially equivalent to those in this DPA, so far as relevant to their services, and remains responsible for their performance as Data Protection Laws require. 9.3 Verilaud will maintain information about its material Subprocessors (Schedule 2 and any updates) and make it available on reasonable request. 9.4 Where required by Data Protection Laws, Verilaud will give [30] days' notice of intended material Subprocessor changes (by email to the team owner or by updating Schedule 2 at [URL]) and allow the Customer a reasonable opportunity to raise a substantiated objection on data protection grounds. If the objection cannot be resolved, the Customer may cancel the affected subscription.
10. Customer content and support access
10.1 Verilaud does not routinely inspect individual Customer Content. 10.2 Service improvement uses only aggregated usage, diagnostic and technical performance data. 10.3 Verilaud will not use Customer recordings, lyrics or other creative content to train generative AI models, and will not train other machine-learning models on it without separate explanation and authorisation. 10.4 Where the Customer requests technical support involving access to its workspace, the Customer may invite a Verilaud support account to the relevant team [as an ordinary team member; update when a dedicated mechanism exists]. This access: (a) is restricted to the team that invited the support account; (b) is subject to the permissions applicable in that team; (c) is limited to the relevant support request; and (d) ends when the user who opened the request removes the support account from the team. 10.5 Verilaud will not use this mechanism to obtain general access to unrelated Customer workspaces.
11. Assistance with data subject rights
11.1 Taking into account the nature of processing, Verilaud will provide reasonable assistance in responding to requests from individuals exercising rights under Data Protection Laws (access, correction, deletion, restriction, portability, and identifying relevant Personal Data in the service). 11.2 The Customer remains responsible for deciding whether a request is valid and how to fulfil it. 11.3 If Verilaud receives a request directly about Personal Data it processes for the Customer, it will, where reasonably practicable and lawful, refer the individual to the Customer.
12. Personal Data Breaches
12.1 Verilaud will notify the Customer without undue delay, and where feasible within 72 hours, after becoming aware of a Personal Data Breach affecting Personal Data processed on the Customer's behalf. 12.2 The notice will include, to the extent reasonably available: the nature of the breach; categories of Personal Data and approximate number of individuals or records; likely consequences; measures taken or proposed; and contact details. 12.3 Verilaud will take reasonable steps to investigate, contain and mitigate the breach and provide reasonable assistance with the Customer's notification obligations. 12.4 The Customer decides whether to notify regulators or individuals, except where Verilaud is itself required to notify as Controller.
13. Impact assessments and regulatory assistance
Taking into account the nature of processing and information available to it, Verilaud will provide reasonable assistance with data protection impact assessments and consultations with supervisory authorities relating to the processing covered by this DPA, limited to information reasonably available to Verilaud and relevant to the service.
14. International transfers
14.1 Personal Data may be processed or stored in countries other than where the Customer or affected individuals are located. Verilaud is operated from Australia and its primary hosting is in Sydney, Australia. Subprocessors may process Personal Data elsewhere (see Schedule 2). 14.2 Verilaud will take reasonable steps to ensure transfers comply with Data Protection Laws. 14.3 Where GDPR applies and a transfer to a country without an adequacy decision requires a safeguard (this includes transfers of EU Personal Data to Verilaud in Australia), the parties agree that the EU Standard Contractual Clauses (Module Two, Controller to Processor, or Module Three where the Customer is a Processor) are incorporated by reference, with: Clause 7 docking clause included; Clause 9 option 2 (general authorisation, [30] days' notice); Clause 11 optional language omitted; Clause 17 governed by the law of [Ireland]; Clause 18 courts of [Ireland]; Annexes completed by Schedules 1 to 3. For UK GDPR the UK International Data Transfer Addendum is incorporated in the same way. [Solicitor to confirm.] 14.4 The parties will cooperate on transfer assessments and supplementary safeguards where required.
15. Return and deletion
15.1 During the retention period, Verilaud provides functionality for the Customer to export data from projects and teams it owns, subject to permissions and technical limits. [Bulk export is under development; until available, Verilaud will assist on request.] 15.2 Unless law requires otherwise or the parties agree, Customer Content is retained under the Terms of Service: for the remainder of the paid period; then, after a subscription ends or an unresolved payment failure, in stages (a 14-day retry window, up to 90 days limited, up to 365 days read-only) and then deletion, with a further period of up to 30 days for purge. 15.3 The Customer must export anything it wishes to keep before the end of the applicable period. 15.4 After that, Verilaud will delete or de-identify Personal Data processed on the Customer's behalf, including stored audio and derived (transposed or cached) versions, except where retention is required or permitted by law. 15.5 Personal Data in backups may remain until backups expire or are overwritten [backup retention to be stated]. 15.6 Where data is retained for legal, security or dispute purposes, access is limited to what is necessary.
16. Audits and compliance information
16.1 Verilaud will make available information reasonably necessary to demonstrate compliance with this DPA. 16.2 Where Data Protection Laws require, Verilaud will allow and contribute to reasonable audits by the Customer or its independent auditor. 16.3 Audits must be requested with reasonable notice, occur during business hours, be limited to relevant systems, avoid unreasonable disruption, and protect other customers' information. 16.4 Verilaud may satisfy audit requests through security documentation, written responses, independent reports or other reasonable evidence. 16.5 The Customer bears its own audit costs unless law or agreement requires otherwise.
17. Liability
17.1 Each party remains responsible for its obligations under Data Protection Laws. 17.2 Liability under this DPA is subject to the liability provisions of the Terms of Service to the extent permitted by law. 17.3 Nothing excludes or limits liability that cannot be excluded or limited by law, including data subjects' rights against either party and the Standard Contractual Clauses.
18. General
18.1 This DPA supplements the Terms. If they conflict regarding processing of Personal Data on the Customer's behalf, this DPA prevails to the extent of the conflict. 18.2 This DPA does not transfer ownership of Customer Content or intellectual property. 18.3 Amendments must be in writing or by updated version notified under the Terms. 18.4 If a provision is unenforceable, the rest continues. 18.5 This DPA is governed by the law and dispute provisions in the Terms, subject to mandatory law and to clause 14.3.
Schedule 1 — Processing details
| Item | Description |
|---|---|
| Subject matter | Provision of the Verilaud collaborative songwriting and audio workspace service |
| Duration | Customer's subscription plus applicable retention periods (section 15) |
| Nature | Collection, storage, organisation, retrieval, transmission, conversion, modification, synchronisation, backup and deletion |
| Purpose | Collaborative workspaces, audio processing, project storage, account permissions, support, service security |
| Data subjects | Customer employees, contractors, team members, collaborators and individuals included in Customer Content |
| Personal Data | Names, email addresses, identifiers, team membership and roles, comments and authorship, audio recordings and project content, preferences, technical/operational data |
| Special-category data | Not intentionally required or solicited |
| Frequency | Continuous for the duration of the service |
| Competent supervisory authority (SCCs) | [authority of the exporter's Member State, or the ICO for UK] |
Schedule 2 — Subprocessors
| Provider | Purpose | Location | Status |
|---|---|---|---|
| Fly.io | Application hosting (web, backend, audio), private networking | Sydney, Australia (hosting entity: United States) | In use |
| Fly Managed/Postgres on Fly | Structured database | Sydney, Australia | In use |
| Tigris Data, Inc. (via Fly.io integration) | Object storage for audio files | US company; bucket location per Tigris setting [confirm: global or restricted to Sydney] | In use |
| Cloudflare | DNS; network security and bot prevention (planned) | Global | DNS in use |
| Resend | Transactional email delivery | United States | In use |
| Creem | Merchant of record, checkout, subscription and payment administration (independent controller for payment data) | [to confirm] | Test mode; live planned |
| [Analytics/diagnostics provider] | Product diagnostics | Not in use. Add when built |
Provider entity details, processing locations and each provider's DPA must be confirmed before publication. Additional providers may be engaged as the service develops, subject to section 9.
Schedule 3 — Technical and organisational measures
In place today:
- Encrypted connections (TLS) for public traffic with HSTS; private network between application, audio and database services; TLS to the database.
- Authentication: salted Argon2id password hashing; email verification; short-lived (15 minute) hashed one-time codes with attempt limits; 24-hour signed session tokens.
- Authorisation: team-based roles (owner, editor, viewer) enforced server-side for all project and audio operations.
- Hashed storage of invitation, join-link, transfer and verification tokens.
- Signed, time-limited tokens for audio upload (15 minutes), streaming and waveforms (60 minutes).
- Separation of customer workspaces by team and project.
- Web security headers (CSP, HSTS, X-Frame-Options, nosniff, referrer and permissions policies) and origin allow-listing.
- Process hardening: non-root execution with no-new-privileges, restricted snapshot directory permissions.
- Soft-delete with scheduled purge; warning emails before lifecycle deletions.
- Restricted production access via the hosting provider's authenticated tooling.
To be in place before launch (tracked in Planning/future-items.md): verified encryption at rest for databases and object storage; configured and tested backups; audit logging of administrative and support access; least-privilege database roles; rate limiting and bot protection; automated breach and fault alerting across providers; documented incident response; security audit; periodic review of subprocessors and access.