This appendix forms part of the Brain-Shot Academy privacy hub.
Privacy hub documents: Main Privacy Notice, Cookie Policy, Cookie Inventory, Processor Appendix, International Transfers Appendix, Retention Appendix, Legal Bases Matrix, and Required and Optional Data Matrix.
It explains, at a category level, which data is generally required or optional and what may happen if the required data is not provided.
Flow-by-flow matrix
| Flow / service context | Data likely required | Data likely optional | Consequence if required data is not provided | Description |
|---|---|---|---|---|
| Public website and public partner pages | no direct form data is generally required for basic browsing, although technical data may be processed automatically | voluntary enquiry, signup, or other submitted data | public browsing usually remains available, but the specific request or follow-up cannot be provided without the relevant submitted data | Basic browsing is distinct from submission-based flows |
| Account sign-in and recovery | the identity, authentication, and verification data needed for the chosen sign-in or recovery method | language or preference context, and anti-abuse challenge response where not required in the specific case | the user cannot sign in, recover the account, or complete the relevant security step | Anti-abuse controls may become effectively required when protection is enabled for the flow |
| Account profile and settings | an authenticated session and any fields required for the specific change being made | optional profile, contact, and preference fields not needed for that change | the requested change cannot be saved or applied | The exact required fields depend on the specific change being made |
| Protected service access across Airport, Shorts, LMS, and similar member services | authenticated identity and any required entitlement or access state | non-essential profile, display, or preference data | the protected service, content, or feature cannot be provided correctly | Covers access, routing, and entitlement-driven functions, including account-gated free introductory or gift-based access where applicable |
| Learning participation, progress, downloads, and gated features | the data needed to deliver or record the relevant learning step, such as required participation, access, or learner responses | optional notes or other non-essential inputs | continuity, progression, completion, or asset delivery may not work correctly | This row covers both user-submitted and service-generated learning records |
| Website enquiries, bookings, webinar or event registration, and similar pre-contract requests | name, contact details, and the request or registration details needed to respond, register, or schedule | phone number, optional notes, and marketing fields not required for the request | the request cannot be answered, the registration cannot be completed, or the appointment cannot be booked | The exact required details depend on the request or registration |
| CRM signup, newsletter signup, and marketing preferences | the email address or other identifier needed for the requested signup or preference action, plus the relevant choice being recorded | optional profile or segmentation fields | the signup or preference change cannot be completed | Non-account holders can opt out through the unsubscribe link in the relevant message; account holders may manage relevant preferences in account settings |
| Purchases, checkout, invoicing, and billing | the identity, contact, billing, and transaction data needed to complete the order, issue records, and administer the contract | additional contact details not required for the transaction | the order, invoicing, or contractual administration cannot be completed correctly | Applies to publicly purchasable and account-linked purchase flows where relevant |
| Support requests and operational messaging channels | contact details and enough context to handle the request or use the chosen channel; phone number where a messaging channel requires it | optional attachments or non-essential profile data | the support request or channel communication cannot be handled properly | Covers email, WhatsApp, and platform-based communication where requested by the user or operationally necessary |
| Live sessions, webinars, meetings, and recorded group training | the identity, participation, and session data needed to attend, administer, or document the session; audio, video, or related interaction data where recording or live participation features are part of the session | optional profile data not needed for participation | the session, administration, recording, or related participation feature may not function correctly | Where recording is used, participants are warned before the recording starts |
| Consent and preference controls | the relevant choice itself and any minimum account or technical context needed to apply it | additional preference detail not required for the request | the choice may not be recorded or applied correctly | Important for unsubscribe, cookie, and withdrawal flows |