Verilaud Privacy Policy
Version 1.0 — Effective [date]
DRAFT. Items in [square brackets] must be completed. See 00-code-assessment.md for features that must exist before this policy is published.
1. Who we are
Verilaud is operated by [Full legal name], an Australian sole trader trading as Verilaud, ABN [ABN] ("Verilaud", "we", "us"). Verilaud is a collaborative songwriting and audio workspace.
Privacy contact: [privacy@verilaud.com]. Postal address: [address].
This policy explains what personal information we collect, why, who we share it with, and your choices. It also contains our Cookie and Local Storage Policy (section 15). Our Terms of Service, Intellectual Property Agreement and, where applicable, Data Processing Addendum are separate documents.
2. Information we collect
Account information. Your name, email address and a password (stored only as a salted Argon2id hash). We record whether your email is verified, when you were last active, and, if your account is inactive, when we last warned you about deletion.
Team and collaboration information. Teams you own or belong to, your role (owner, editor or viewer), when you joined, left or were removed, invitations (the invitee's email address and role), team join links (stored only as hashed tokens), ownership transfers, project ownership and transfers, and comments and replies you write, with their authorship.
Creative content. Audio you upload or record, lyrics, chords, timelines, tempo maps, regions, comments and any other material you create or upload ("Your Content"). Your personal playback settings (such as solo, mute, volume, pan, transposition and playback speed) are stored against your account.
Technical and usage information. Today the Verilaud application does not store your IP address, device identifiers or browser details, and does not run analytics. Our hosting and network providers (section 6) generate standard operational logs, which can include IP addresses. Our own application logs may include account identifiers and, in some error cases, email addresses of invitees. We will describe any analytics or observability tools we add here before we begin using them (section 8).
Payment information. Payments are handled by Creem, which acts as the merchant of record. We do not receive or store your card details. We keep your Creem customer and subscription identifiers, plan, subscription status, billing period dates, and checkout records. We send Creem your email address to create your checkout.
Support information. Messages you send us and information you give us or authorise us to access to resolve a problem.
3. How we collect it
Directly from you (registration, using the service, uploading content, contacting us); from other users (for example when a team owner invites your email address, or a collaborator comments on your work); automatically through our systems (activity timestamps, operational logs); and from Creem (subscription and payment status events).
4. How we use it, and our legal bases
| Purpose | Examples | Legal basis (GDPR/UK GDPR) |
|---|---|---|
| Providing the service | Creating accounts and teams, hosting, syncing and processing your content, applying permissions, sending service emails (verification codes, password resets, invitations, billing and lifecycle notices) | Contract |
| Billing | Managing subscriptions through Creem, enforcing plan limits | Contract; legal obligation |
| Security and integrity | Preventing abuse and unauthorised access, enforcing our terms, maintaining backups | Legitimate interests |
| Diagnostics and improvement | Investigating faults and measuring reliability using operational logs and (in future) aggregated technical data | Legitimate interests |
| Support | Responding to requests; accessing your project data only when you authorise it | Contract; legitimate interests |
| Legal and administrative | Complying with law, responding to lawful requests, resolving disputes, keeping records | Legal obligation; legitimate interests |
We send transactional emails only. We do not send marketing email. If that changes we will ask for your consent first.
We do not use your content, or any personal information, for advertising, and we do not sell personal information.
5. Support access to your content
We do not routinely inspect the creative content in your projects. If you ask for help with a technical problem, you may authorise us to access the relevant project. At present this is done by inviting a Verilaud support account to the relevant team as an ordinary team member [CONFIRM mechanism once built]. Access is limited to that team, is used only to investigate and resolve the issue, and ends when you remove the support account or withdraw your authorisation. Where a support account holds a team seat, it counts towards that team's member limit. We may keep limited records of the issue and what we did, for accountability, security and service administration. See also the Intellectual Property Agreement.
6. How we disclose information
We do not sell personal information. We disclose it only as follows.
- Infrastructure and hosting providers. Fly.io (application and database hosting, Sydney, Australia), Tigris (audio object storage, provided through Fly.io's integration; [confirm bucket region setting]), Cloudflare (DNS and network security).
- Email provider. Resend sends our transactional emails and therefore receives the recipient address and message content.
- Payment provider. Creem, the merchant of record, processes payments, tax and invoices and handles billing support. Creem is an independent controller of the payment information it collects; see its privacy policy.
- Professional advisers (lawyers, accountants, insurers) where necessary.
- Legal disclosures. Where required by law, court order or a valid request from authorities, or to protect rights, safety and the security of the service.
- Team members and collaborators. Content and activity in a team are visible to members according to their role. Your name and email address are visible to other members of teams you belong to and to people who share a team with you. Team owners can see members' names, emails and roles. All editors in a team can edit or delete shared project content, including content uploaded by others. A team owner or administrator does not become the owner of another member's intellectual property because of that role. If you leave or are removed from a team, projects you owned in that team are reassigned to the team owner.
- Business transfer. If Verilaud is sold or merged, personal information may transfer to the new operator under this policy.
We take reasonable steps to ensure service providers handle information appropriately, including contractual commitments where appropriate.
7. International processing
Verilaud is operated from Australia and our primary hosting is in Sydney. Some providers (for example Resend, Creem and Cloudflare, and our storage provider depending on its location) process information in other countries, including the United States and the European Union. Where GDPR or UK GDPR applies to a transfer, we rely on adequacy decisions or Standard Contractual Clauses (and the UK Addendum) as applicable. For Australian users, we take reasonable steps under Australian Privacy Principle 8 before disclosing information overseas.
8. Analytics and service improvement
We may in future collect and analyse aggregated usage information, diagnostic information and technical performance data to understand how Verilaud is used, find faults and improve reliability. This policy will be updated, and where required we will ask for your consent, before we start. [List of observability points to be inserted when built: see likely-changes.md.]
We do not use your content to train generative AI models and do not provide it to third parties to train any AI or machine-learning models. We will not use your content to train other machine-learning models unless we have separately explained the proposed use and obtained your permission.
9. Security
We protect information with measures including: encrypted connections (HTTPS/TLS) to the service and between our systems; salted Argon2id password hashing; hashed storage of invitation, link and verification-code tokens; role-based access to teams and projects; a private network between our application, audio and database services; non-root, restricted processes; and security headers on the web application. [Encryption at rest, backups, audit logging and least-privilege administrator access to be added once implemented and verified.] No system is perfectly secure, and we cannot guarantee absolute security.
If a breach is likely to result in serious harm (Australia) or a risk to your rights and freedoms (GDPR), we will notify affected people and regulators as required by law.
10. Retention
- Account information: while your account exists. Accounts inactive for 730 days are deleted after warnings by email 90, 30 and 7 days before deletion, unless you belong to a team with an active paid subscription.
- Projects and content: until you or your team delete them. Deleted projects can be restored for 30 days, after which they are permanently removed from active systems. Stored audio (including transposed versions) is deleted once no remaining region uses it, normally within a day of that region's permanent removal or of its audio being replaced.
- Team content after subscription lapse: if a paid subscription ends or a payment fails and is not resolved, we retain team content in stages: a 14-day payment retry window with full access; up to 90 days with limited features; up to 365 days read-only (you can still open, export or move projects); then projects are deleted, with a further period of up to 30 days before permanent purge. Paying at any stage restores access. We email the team owner and members before each stage.
- Billing records: as long as needed for tax, accounting and dispute purposes (typically up to seven years in Australia).
- Backups: deleted information can remain in backups until they expire [retention period to be confirmed once configured].
- Support records, logs and security records: kept for as long as reasonably necessary [log retention to be confirmed].
11. Deletion
You can delete projects and leave teams in the app. To delete your account or exercise other rights, [use Settings → Delete account / email privacy@verilaud.com]. Deleting your account removes your account information; comments you posted in projects that remain in a team may remain attributed to a deleted account holder or be deleted with the project. We may retain information needed for legal obligations, disputes and security.
12. Your responsibilities
You are responsible for the content you upload, for having the right to share it, and for the personal information of others contained in it (for example voice recordings of other people). Choose team members and roles carefully and keep your password secure.
13. Your privacy rights
Depending on where you live you may have the right to access, correct, delete, export or restrict the use of your personal information, to object to certain processing, and to withdraw consent where we rely on it. Contact us at [privacy@verilaud.com]. We may need to verify your identity. We aim to respond within 30 days.
- Australia: you may access and correct your information under the Privacy Act 1988 (Australian Privacy Principles 12 and 13). Complaints: contact us first; you may then complain to the Office of the Australian Information Commissioner (oaic.gov.au).
- EU/UK: you have the rights above under GDPR/UK GDPR and may complain to your local supervisory authority (in the UK, the ICO).
- Where we process content as a processor on behalf of a team owner, we will refer your request to the relevant team owner where appropriate (see our Data Processing Addendum).
14. Children
Verilaud is not designed for children who are below the minimum age required to enter into a binding agreement in their jurisdiction, and in any case you must be at least 16 years old to register. We do not knowingly collect personal information from children in circumstances where doing so would be unlawful. If you believe a child has provided personal information to Verilaud improperly, contact [privacy@verilaud.com] and we will investigate.
15. Cookie and Local Storage Policy
What these are. Cookies are small files websites place on your device. Similar technologies, such as browser local storage, also keep small pieces of data in your browser.
Cookies. Verilaud does not currently set any cookies, advertising or otherwise.
Local storage (strictly necessary). To keep you signed in we store a session token in your browser's local storage under the key verilaud.token. It is valid for 24 hours and is removed when you sign out or clear site data. Without it you cannot stay signed in.
Local storage (preferences). We store interface preferences such as sidebar size and visibility, timeline height, timing and follow settings, audio latency offset, and project list filters and view (keys beginning verilaud. and projects.). These stay on your device until you clear them.
Analytics and advertising. We do not currently use analytics cookies or trackers, do not use advertising trackers and do not sell tracking data. We load no third-party scripts or fonts in the application.
Third-party services. Creem's hosted checkout and billing portal are on Creem's own site and may set their own cookies under its policy.
Managing storage. You can clear cookies and local storage in your browser settings. If you clear or block local storage, you will be signed out and your preferences reset.
Changes. If we introduce additional tracking technologies, we will update this section and obtain consent where required before using them.
16. Compliance with privacy laws
We handle personal information in line with the Australian Privacy Principles and, for people in the EU and UK, GDPR and UK GDPR. [Representative details if appointed under GDPR Art. 27.]
17. Changes to this policy
We may update this policy. For material changes we will notify you through the service or by email before they take effect. The version and effective date are at the top of this page.