Privacy Policy
Last updated · 30 September 2026
We Are One Voice (WAOV) is a platform for booking vocal and DJ coaching lessons. This policy explains exactly what personal data we collect when you use WAOV, why we collect it, who else receives it, how long we keep it, and how to get it back or have it destroyed. We have written it in plain language on purpose — if anything here is unclear, email us and we will explain it.
1 · What we collect
We only collect what the service needs in order to run. We do not sell your personal data, and we do not share it for advertising.
Account and sign-in identity
- Google Sign-In: your Google account ID, email address, display name, and profile photo.
- Discord Sign-In: your Discord user ID, username, email address, and avatar.
- Role and profile: whether you are a client, a trainer, or an admin, plus the trainer or client profile you created.
We request only the basic identity scopes (openid,
email, profile). We do not request access to your
Google contacts, Drive files, calendar, or any other Google service beyond
what is listed in section 4.
Content you create
- Bookings: lesson type, date and time, and the notes a trainer or client adds to a lesson record.
- Lesson video: any recording uploaded against a lesson for trainer review.
- Receipts and payouts: payment records created when a trainer is paid or a client is invoiced.
Technical data
- IP address and browser type, seen by our hosting provider when a page loads.
- Your sign-in session, held in an HTTP cookie so you stay logged in.
- A mirror of that session in your browser's
localStorage, which is what keeps you signed in across tabs and reloads.
2 · Why we collect it
Each category of data exists for one operational reason. We do not collect anything for a purpose we have not listed here.
| Data | Purpose |
|---|---|
| Sign-in identity | To create your account, recognise you when you return, and keep unauthorised people out of other people's dashboards. |
| Role and profile | To show the correct experience for a client, a trainer, or an admin, and to route lesson records to the right trainer. |
| Bookings and notes | To run the lesson: schedule it, remind both sides, and keep a record of what was taught. |
| Lesson video | So a trainer can review a performance and give feedback. |
| Payment records | To pay trainers, invoice clients, and keep the accounting the business legally needs. |
| Session cookie and mirror | To keep you signed in without asking you to log in on every page. |
3 · How sign-in works
WAOV does not handle your Google or Discord password. Sign-in runs through Google's and Discord's own authentication, and both send us back only the identity fields listed in section 1. The exchange happens on our server-side authentication callback, and the resulting session is stored in a cookie rather than in a token we keep a copy of.
If you sign in with Google, Google is the processor for that identity check under Google's Privacy Policy. If you sign in with Discord, Discord is the processor under Discord's Privacy Policy.
4 · Google Drive — a third party that holds your data
WAOV uses Google Drive to store lesson video and receipt files. When you are a client, we create a Drive folder that belongs to you and place your material inside it. This means your content is held by Google as well as by us.
Access to those files is limited to the WAOV accounts that need them — your own account, the trainer working with you, and WAOV admin accounts. Google processes this data as a provider under Google's Privacy Policy. If you sign in with Google, this storage is covered by the Google Terms of Service as well. Signing in with Discord does not change where the files live — Drive is used either way.
5 · Payments — PayPal
Trainer payouts and any client invoicing run through PayPal. We never see or store your full card number. What we keep is the outcome and the reference: whether a payment was made, how much, to whom, and when.
PayPal processes your payment details as its own processor under the PayPal Privacy Statement. We receive a transaction reference, not your card data.
6 · Who else receives your data
| Recipient | What they get | Why |
|---|---|---|
| Netlify | Hosting request data, including IP address | Serves the site and runs our server functions |
| Sign-in identity, Drive file storage | Authentication and file storage | |
| Discord | Sign-in identity, if you use Discord | Authentication |
| PayPal | Payment details, only at the moment of payment | Processing payouts and invoices |
| Your trainer | Your name, email, bookings, notes, lesson video | Delivering your lessons |
| Law enforcement or a regulator | What is legally required | Only where we are legally compelled to disclose |
We do not sell your data, and we do not share it with data brokers or advertising networks.
7 · How long we keep it
- Account and identity data — until you delete your account, then removed from our active systems.
- Backups — deleted data may persist in encrypted backups for up to 30 days, after which it is unrecoverable. It is never restored into live use.
- Payment and accounting records — retained for as long as tax and business law requires, independent of your account. This is a legal obligation, not a choice.
- Lesson video — held in your Drive folder. Once you delete the account we remove our copy and our access; anything you have already downloaded is yours.
8 · Your rights
You can do all of the following, and you do not need to ask our permission:
- Access — see the data we hold about you.
- Correct — fix anything inaccurate on your profile.
- Export — take a copy of your data with you.
- Delete — close your account and have your data removed, using the self-serve button below. No email required.
- Withdraw consent — stop a specific use by not engaging with the feature that needs it.
- Complain — to us, or to your local data protection authority.
9 · Deleting your account
Deletion is self-serve and takes one page: delete-account.html. You are asked to confirm three times, and the account is removed when you do. You will be signed out immediately.
What happens on deletion: your user record and session are removed, and if you held a claimed trainer card it returns to the unclaimed pool rather than being destroyed, so the trainer roster stays intact. Accounting and tax records are retained as described in section 7.
10 · Security
Traffic is encrypted in transit over HTTPS. Sessions are held in an HTTP cookie rather than in script-readable storage. Server functions hold credentials as environment variables so they are never sent to a browser. Access to lesson and accounting data is limited to the accounts that need it to do their job.
No system is perfect. If a breach affects your data we will tell you and the relevant authority without undue delay.
11 · Cookies
WAOV uses one first-party cookie, holding your sign-in session so you stay logged in. There are no advertising cookies, no third-party tracking cookies, and no cross-site trackers. We do not use cookies for analytics or ad targeting.
12 · Children
WAOV is not directed at anyone under 13, and we do not knowingly collect data from children. If you believe a child has given us personal data, email us and we will delete it.
13 · International transfers
Our hosting, sign-in, and file storage providers process data outside your country as part of delivering the service. Where that happens, the transfer is covered by the provider's own safeguards, including Standard Contractual Clauses where applicable.
14 · Changes to this policy
When this policy changes we update the date at the top of this page. If a change materially affects what we do with your data, we will tell you by email before it takes effect.
15 · Contact us
For access, correction, export, deletion, or any question about this policy, email ifoundmiles1@googlegroups.com. It reaches the WAOV operator directly. We aim to answer within 30 days.
WAOV is operated by We Are One Voice. Our website is https://waov.art.