Timing desk Apex Attack / Legal
Privacy Policy
Effective: [EFFECTIVE DATE] · Updated: 2026-09-13 · privacy-draft-2026-09-12
- 1. Who controls your information
- 2. Information you provide
- 3. Timing, consent and security records
- 4. Purposes and lawful bases
- 5. What everyone can see
- 6. Administrative access and exports
- 7. Optional social publication and withdrawal
- 8. Providers and other recipients
- 9. Locations and international transfers
- 10. Essential cookies and tracking
- 11. Retention by record type
- 12. Backups and permanent erasure
- 13. Security and recovery tokens
- 14. Your rights and requests
- 15. Children and representatives
- 16. Complaints and incidents
- 17. Versions and language
1. Who controls your information
[LEGAL OPERATOR NAME], at [BUSINESS ADDRESS], is the proposed operator and personal-data controller. Contact [PRIVACY CONTACT] about privacy and [CONTACT EMAIL] about the event or website. This development policy describes the registration, timing and public-results application. Bracketed operator details, processing arrangements and effective date remain unresolved and must be completed against the deployed service before collecting real participant information. This draft considers Indonesian Law No. 27 of 2022; it does not claim that deployment automatically complies with that law.
2. Information you provide
Registration requires driver name, public display name, requested race number, car make, car model and category. Driver name is administrative; display name is intended for publication. A social handle is optional. The form does not request a private email address, telephone number, birth date, identity-document scan, payment information or medical information. If you contact the organizer separately, the organizer receives the contact details and information you include. Avoid sensitive or unrelated information in free-text fields and support messages.
3. Timing, consent and security records
The service generates entry references, registration timestamps and status. Staff add lap duration, timestamps, validity, correction reasons and category changes. It stores document versions, Terms acceptance, privacy-notice acknowledgment and optional-social choices and changes. A private recovery token supports social-publication withdrawal; its verifier is separate from public results. Administrative sessions and audit events support security and review. Shared-PIN audits identify a session, not a verified individual staff member. Hosting may receive ordinary request information such as IP address and browser details; actual logging is [HOSTING AND SERVICE PROVIDERS / REQUEST-LOG DETAILS].
4. Purposes and lawful bases
Required details process registration, allocate numbers, identify entries at the timing desk and publish competition results. The proposed basis for these necessary service steps, including core public results, is performance of the registration-and-results service or steps requested before entering it. [OPERATOR MUST CONFIRM CONTRACTUAL NECESSITY AND THE LAWFUL BASIS FOR CORE PUBLIC RESULTS BEFORE LIVE COLLECTION]. Optional social publication uses separate consent. Security, audit review and dispute handling require documented, proportionate bases: [SECURITY, AUDIT AND SUPPORT LAWFUL BASES]. A specific legal duty may require particular records, not unrelated use. Privacy acknowledgment supplies none of these bases by itself.
5. What everyone can see
Public results show display name, race number, car make and model, category, best valid lap and rank. Social handles appear only while optional publication is enabled. Untimed entries receive no timed rank. Choose a display name you are comfortable associating publicly with your car and results. Anyone may view results without an administrator account. Search engines and others may copy, index, screenshot or share them. Removing or correcting our record cannot guarantee removal of external copies; you may also need to contact the external publisher.
6. Administrative access and exports
Private driver names, administration, lap history, correction reasons, acceptance and consent history, recovery-token verifiers and security records are excluded from public leaderboard responses. Authorized staff use them for event operations, corrections and supported requests. Standard administrative Excel exports contain race numbers, public names, cars, categories, valid lap counts, best laps, lap records and export metadata. They exclude private driver names, recovery tokens, consent history and authentication records. Staff must limit exported files to the event purpose and manage retention. A public display name can still identify you even if the private name is excluded.
8. Providers and other recipients
Hosting, backup, support and other providers are [HOSTING AND SERVICE PROVIDERS]. Their roles, access and contractual safeguards must be identified before launch. Necessary records may be disclosed to advisers or competent authorities for supported legal claims or binding requirements, limited to that purpose. Social links lead to platforms with their own policies. This implementation has no participant-data sale feature or marketing mailing list. New uses or providers require assessment and an accurate notice; this draft does not automatically authorize them.
9. Locations and international transfers
Storage, backup and remote administrative-access locations are [PROCESSING LOCATIONS]. We do not claim that all data remains in Indonesia or that a foreign location is already approved. Before international processing, the operator must identify recipients and destinations, assess transfer requirements and put required protection in place. Any transfer relying on consent needs a separate explanation and valid choice. Public viewing from another country and transfer of private administrative records are different situations; one does not authorize the other.
11. Retention by record type
The operator must set [RETENTION PERIODS]. Driver and entry data are needed through the event and defined correction or dispute window; identifiable storage afterwards requires a stated purpose and duration. Results and lap history need a separate archive period. Removed entries remain recoverable for [REMOVAL RECOVERY PERIOD]. Social data remains subject to withdrawal. Acceptance and consent evidence need defined evidence-retention periods. Security and audit logs, support messages and exports each need limited schedules. These criteria do not authorize indefinite storage. A legal hold must cover only relevant records and be reviewed when it ends.
12. Backups and permanent erasure
Recoverable administrative removal differs from a privacy erasure request. Verified erasure requests are assessed against the records concerned and any actual duty or defensible reason to retain specific information. We should explain the decision and scope rather than treating a hidden entry as erased. Backup frequency, storage, expiry and disposal are [BACKUP RETENTION AND RESTORE PROCEDURE]. Backups require restricted access and expiry; restored data must respect recorded removals and withdrawals. Audit history is not a blanket erasure exemption. Staff exports must also be included in retention and request handling.
13. Security and recovery tokens
The application separates public and administrative records, hashes the administrator credential, limits login attempts, checks authorization and uses expiring sessions. It records timing changes for review. Production requires HTTPS, appropriate secure cookies, restricted database and backup access, maintained software and tested recovery procedures. No system is completely secure; no unearned security certification is claimed. Keep the recovery token private because its holder may change your optional publication choice. Report suspected exposure or unauthorized changes to [PRIVACY CONTACT].
14. Your rights and requests
Under applicable law, you may request processing information, access and a copy, correction, ending processing, erasure or destruction, consent withdrawal, and proportionate postponement or restriction. Applicable rights may include portability, objection to solely automated decisions with legal or significant effects, and complaint or compensation remedies. Ranks derive from valid laps; ask for human review of disputed inputs or results. Send requests to [PRIVACY CONTACT] with the entry reference and requested action. We may seek proportionate verification, without routinely demanding a full identity-document copy. We will explain lawful restrictions and respond within applicable deadlines.
15. Children and representatives
The form does not collect age or infer it from GIRLS. It has no verified parent or guardian workflow. The organizer must confirm [MINOR ELIGIBILITY AND GUARDIAN PROCESS] before accepting a child’s entry. Do not submit a child’s information through this development form before that process is established. Contact [PRIVACY CONTACT] about information submitted without appropriate authority. We will assess the report, limit unnecessary processing and arrange a response. Adult representative requests will also be verified proportionately.
16. Complaints and incidents
Report suspected privacy incidents, disclosures or unresolved requests to [PRIVACY CONTACT], giving enough detail without circulating others’ private information. We will review, take appropriate containment and recovery steps and provide legally required notices to affected people and authorities. The incident contact, competent complaint route and notice procedure are [INCIDENT AND PRIVACY COMPLAINT PROCEDURE]. Because registration collects no private contact details, the operator must establish a lawful, effective route for required participant notices before live use. You remain free to contact competent authorities or seek available legal remedies.
17. Versions and language
Version, effective date and last-updated date appear above. Material changes to purposes, recipients or processing arrangements will be explained before new processing where required, with fresh optional consent when necessary. We retain the notice version associated with each registration rather than silently replacing its history. English and Bahasa Indonesia versions have the same intended meaning. The controlling language is [CONTROLLING LANGUAGE — OPERATOR TO CONFIRM]. Ask [PRIVACY CONTACT] for clarification or an accessible explanation.
Withdraw social-handle publication
Enter the reference and private management key you saved when registering. This removes your social handle from this site.
7. Optional social publication and withdrawal
You may register without supplying or publishing a social handle. Publication has a separate, initially unchecked consent choice. Save your registration reference and private recovery token; do not post the token publicly. Use the social-consent control with those details to withdraw, or ask [PRIVACY CONTACT] for help. Successful withdrawal removes the handle from subsequent public responses and records the change; it does not cancel the entry or valid lap results. If the token is lost, contact us for proportionate verification. External copies may remain. Consent evidence may be retained only for a necessary documented purpose under the retention policy.