Consent to Personal Data Processing

1. Purpose and limits of this document

This document explains how a valid consent request must operate when RALMIX LLC relies on consent. It is not an executed consent, and its publication does not establish that a User, child or Parent / Guardian has agreed. Reading it, browsing the website, accepting contractual Terms or acknowledging the Privacy Policy is not blanket consent to every purpose.

The Privacy Policy describes the operator, processing and rights. Some necessary processing can rely on contract, legal obligation or another available ground. Consent must not be used to disguise processing that cannot actually stop when consent is withdrawn. Conversely, another jurisdiction's legal basis cannot be substituted for consent required by applicable local law.

2. What must be explained before a choice

A request must identify RALMIX LLC, the specific purpose, data categories, operations, relevant recipients, the duration or retention criteria, how to withdraw, and any consequence of refusing. Where a transfer, sensitive-data use, media publication or child's data requires further information, it must be included before the choice, not disclosed only after collection.

Operations may include collecting, recording, organising, storing, retrieving, using, disclosing to identified recipients, restricting and deleting data. This list does not authorise all operations on all information. The selection must be limited to the stated purpose. Optional uses need separate choices where they are materially different.

3. Freely given and specific permission

Consent requires a clear, informed affirmative act by a person entitled to give it. Preselected boxes, silence, a misleading button, inactivity and a mandatory acceptance of unrelated purposes do not provide valid permission where an active choice is required. Refusal of optional marketing or analytics must not be treated as a refusal of all contractual services.

A purpose such as “anything useful to the business” is not sufficiently specific. Consent to receive learning reminders is not consent to advertising from third parties. Consent to appear in one authorised publication is not unlimited permission to use a person's image in every channel indefinitely.

4. Separate categories of choice

• Analytics: the Cookie Policy applies to device access and tracking; contractual acceptance does not authorise consent-dependent analytics.
• Marketing: specify the sender, channels and purpose, provide an accessible opt-out, and obtain any required prior permission. Necessary service communications remain distinct.
• Recording, transcription and media publication: these are separate purposes and are not active blanket permissions under this document. The current classroom does not provide routine recording/transcription; a future feature requires its own lawful design.
• AI input: using an available tool requires appropriate disclosure of the processing actually involved. Private teaching communications do not automatically become training data.
• Children's data: any legally required adult permission and verification must be appropriate to the child, purpose and applicable law. A declaration alone does not satisfy every jurisdiction's verification standard.

5. Who may give consent

An adult may consent for their own data when legally capable. A Parent / Guardian must possess the relevant legal authority; a Tutor, sibling or Account holder does not automatically have it. Where a child can exercise a privacy right independently, that right must be respected. Age requirements for online consent differ by jurisdiction and are not the same as contractual majority.

RALMIX must take the reasonable verification steps required for the circumstances. Verification should be proportionate and should not unnecessarily collect identity documents. Merely confirming that an email can receive messages proves control of that email, not parental status or identity verification.

6. Evidence, version and changes

Where consent is relied upon, the relevant record should identify the person or authorised actor, purpose, choice, notice/document version, time, language and context, and any withdrawal. A checkbox without the notice shown at that time may be insufficient evidence. This document describes the required evidence; it does not certify that every current form stores it.

A material change of purpose or scope requires a fresh lawful assessment and renewed consent where required. A spelling correction or harmless clarification does not automatically invalidate previous permission. New terms must not be backdated to create a consent that did not occur.

7. Withdrawal and consequences

Use the relevant preference control where available or contact ralmix.top@gmail.com with the purpose you want to stop. Withdrawal must be as easy as giving consent where law requires. It affects future consent-based processing; it does not make prior lawful processing unlawful.

RALMIX must stop the activity and address relevant recipients as required. It may retain limited evidence of the choice, or data needed on another lawful ground, but must explain that ground and cannot simply continue the optional purpose under a new label. Refusal or withdrawal can prevent a function only where that specific processing is genuinely necessary to that function and no lawful alternative is available. It must not trigger an unrelated penalty.

8. Requests and complaints

Ask for a copy of the relevant notice and consent record through the Contact page. You may also exercise privacy rights and contact a competent authority under the Privacy Policy. This document does not waive rights to challenge the validity of a purported consent or require you to resolve a complaint internally first.

Related documents: Privacy Policy, Cookie Policy, Parent / Guardian Agreement, Child Privacy Notice.