Privacy policy

Scope and responsibility

This draft covers Coavela’s website, coach studio, masterclass offers, checkout handoff, client library, and support. Proposed operator details and privacy contact information are in the Imprint; these must be confirmed before launch.

The operator determines how data is used to administer and secure the platform. A coach may separately determine how client information and recordings are used for their coaching business. The controller and processor responsibilities for that relationship, including any required data-processing agreement, must be agreed before coaches submit other people’s personal data.

Information we process

Account and access information: coach identity and workspace information, client email addresses, sign-in requests, session records, and access permissions.
Optional Google sign-in: Google account identifier, verified email address, and the account association used to sign you in. Google access and refresh tokens are not retained.
Purchases: the selected offer, amount, currency, payment-provider references, purchase status, and refund or dispute events. Payment details are entered on Stripe’s hosted checkout; Coavela’s checkout endpoint does not collect full card numbers.
Coach content: recordings, voices and images within them, titles, descriptions, transcripts, chapter suggestions, and coach edits. Offer details, coach profiles, and cover images may be displayed on public sales pages when published.
Viewing activity: the masterclass watched, saved playback position, completion information, and timestamps needed to resume viewing.
Personal study notes: notes you write about videos, chapters, or course items, saved transcript passages, and their timestamps. These are shown only in your client account, not in coach CRM or operator reports, and are not sent to AI or product analytics. Notes remain stored if course access expires and can be deleted through the viewer while access is active.
Product activity: server-side event names, internal workspace identifiers where available, normalized coach-page routes, event counts, and timestamps used for operator reporting. Product events do not include client identifiers, email addresses, IP addresses, browser fingerprints, recording titles, or transcript content.
Technical and support information: IP addresses, browser and request information, security and error events, and information included in support enquiries.

We receive information from you, your coach, your browser, and payment or media providers. Coaches must have the rights and lawful basis needed to upload recordings containing other people. Avoid submitting unnecessary sensitive information.

Purposes and legal bases

Where we act as controller, we process information to provide requested access, purchases, playback, and support in order to perform a contract or take requested steps before a contract. Necessary security, abuse prevention, and troubleshooting serve our legitimate interests in protecting users and operating a reliable service. Tax, accounting, and lawful disclosure requirements may require processing to comply with legal obligations.

Where optional processing requires consent, it must be offered separately and you may withdraw that consent. A link to this policy is not consent to advertising or optional tracking. Without an email address and purchase information, we cannot provide paid library access.

The application uses essential first-party cookies:

__Host-coavela_coach: keeps a verified coach signed in to their studio for up to seven days. It is host-only, HttpOnly, Secure, and revoked server-side on sign-out. Local development uses an equivalent non-production cookie name.
coavela_session: keeps a verified client signed in for up to 30 days. Signing out revokes the session server-side.
coavela_checkout: connects a checkout attempt to the browser that started it, for up to 24 hours; it is cleared when a successful claim completes.
__Host-coavela_google_coach / __Host-coavela_google_client: connect Google sign-in to the browser that started it, for up to ten minutes. The client cookie may also hold a one-use library-selection ticket. Local development uses equivalent non-production names.

Email sign-in links are single-use and expire after 15 minutes. An expired link or cookie does not mean the underlying database record has been deleted.

The current application code does not include advertising or behavioural analytics scripts. Payment, media, and security providers may process technical information when their services are used. Optional tracking must be reviewed and any required consent controls introduced before it is enabled.

Coavela records product activity on the server using Cloudflare Analytics Engine. This does not add analytics cookies or browser tracking scripts. A separate private operator dashboard combines event activity, database totals, processing status, and limited Worker-health information. The purposes, lawful basis, and retention arrangements for this reporting must be confirmed as part of the privacy review before launch; server-side collection alone does not determine those requirements.

Recordings and AI processing

Recordings are uploaded to the configured video provider, Mux or Cloudflare Stream, for processing, captions, and streaming. Transcripts and associated metadata are stored for the masterclass. Transcript text is sent to Cloudflare Workers AI to suggest titles, summaries, and chapters; coaches can review and edit the results before publication.

AI output can contain mistakes. This workflow creates content suggestions, not automated decisions about a person’s legal rights. Provider data handling is subject to the relevant service and data-processing terms; this draft does not make an unverified promise about provider training or retention practices.

Providers and recipients

Cloudflare: application hosting, database and file storage, security, processing queues, Workers AI, and transactional email; Cloudflare Stream may also provide video services.
Mux: video uploads, processing, captions, delivery, and playback requests when selected as the video provider.
Stripe: hosted checkout, payment processing, and payment, refund, and dispute notifications.
Google Fonts: the current site requests its fonts from Google. Your browser sends technical request information, including your IP address, when loading those resources.
Google sign-in: if you choose this option, your browser visits Google to authenticate and Google provides the identity information needed for account access. You can use email links instead.

Your coach can access client and purchase information for their workspace. Providers receive information needed for their functions. Information may also be disclosed where legally required or necessary to establish, exercise, or defend legal claims.

International processing

Providers operate internationally and may process information outside the European Economic Area. Before launch, the operator must verify the applicable processing locations, contracts, and transfer safeguards, such as an applicable adequacy decision or Standard Contractual Clauses. This draft does not assert that a particular safeguard has already been put in place.

Retention

Account, purchase, and access records are needed to administer purchased access; recordings, transcripts, and progress records support masterclass delivery and resuming playback. Support and security information should be kept only as needed to resolve enquiries, protect the service, and meet legal obligations. Accounting records or information relating to disputes may need longer retention.

Exact retention periods, backup handling, and deletion procedures are still under review. The current authentication expiry periods above are not automatic data-deletion commitments. Before launch, the operator must adopt and implement a retention schedule and explain any limits on deletion needed to preserve purchase records or comply with law.

Your rights

Subject to applicable law, you may request access, correction, erasure, restriction, or portability of your personal data, and object to processing based on legitimate interests. Where processing relies on consent, withdrawal does not affect the lawfulness of earlier processing.

Use the privacy contact to make a request. Identity verification may be necessary. For information controlled by your coach, contact that coach; we can help route a request. You may complain to a competent data-protection authority, including in the country where you live or work.

Security and changes

Coavela uses access controls, encrypted transport, signed client sessions, time-limited sign-in links, and restricted playback access. No system is completely secure. Keep your purchase email secure and never share a sign-in link.

We will update this document as the service and its data practices change, with additional notice where required. The date at the top identifies this draft’s latest revision.