# Requested registration and administration fields

| Requested information | v1 location / control |
|---|---|
| Timestamp | Server-created user, profile-update, declaration, membership and submission timestamps |
| Name, Surname, Known As | My registration → Personal |
| Date of Birth, Identity Number | My registration → Personal; encrypted profile record |
| Email, Mobile, Physical Address | Personal profile; account email remains authoritative |
| Proposed Class | Each garage car; approved class is controlled separately |
| Race Number, Sponsor Name, Team Name | Each garage car and event entry |
| BMWCCCT Membership Number, MSA License Number | My registration → Racing |
| Model, Year, Engine Capacity, Cylinders, Aspiration | Each garage car |
| Tyre Type, Tyre Size | Each garage car |
| Emergency Contact Person and Number | My registration → Safety |
| Medical Aid Company, Type, Number and Contact Number | Encrypted safety profile |
| Any Allergies, Doctor Name and Number | Encrypted safety profile |
| SSA acknowledgment and voluntary participation declaration | Exact supplied declaration; checkbox, version/reference and server acceptance time |
| Proof of Payment | Private membership application upload |
| Driver portrait | Private membership application upload |
| Supplied club bank account details | Membership application screen; no invented annual fee |
| Paid | Administrator-controlled verification flag, distinct from card status |
| Membership ID and ID code | Unique year/member number; random public verification token is not a login credential |

Medical fields can explicitly state “None” or “Not applicable” where appropriate. Drivers can save progress; the lounge shows missing requirements. Admin lists do not expose the full confidential profile; opening an individual record is logged.

Disabling access does not delete historic race/incident evidence. Permanent deletion, statutory retention and migration are controlled operational tasks, not a casual “delete member” button.
