ForgeRivalForm details and browser drafts
The form handles team name; member names, email addresses, mobile numbers and roles; and optional institution, country, city and robot name. These support team administration and price calculation. The in-progress draft stays in browser memory and session storage. Selecting “Save my draft on this device” also stores contact details in local storage until cleared or browser data is removed. “Start over” clears the form draft, but does not erase a server receipt or game reward. Avoid shared devices.
What the registration service receives
Viewing the final amount sends the completed form and selected draft acknowledgements to the local registration service for validation. The quote ledger stores hashed member and leader emails, a team fingerprint, amounts and reward references rather than a full contact directory. A draft acknowledgement receipt stores the typed leader name, hashed leader email, role, server timestamp, document version and text snapshot, selected acknowledgement wording, quote reference and a hash of the normalised form. Hashes can remain personal data; they are not claimed to be anonymous. The signer’s identity is not verified by this preview.
Game, service and payment information
A necessary session cookie associates the browser with game verification, a single reward and quotes. Match seeds, physics snapshots and control replays are processed to verify wins. The cookie lasts up to 30 days; removing it may lose access to a reward. Request metadata is available to the local server, but this acknowledgement feature does not deliberately add IP-address or device-fingerprinting records. Razorpay is planned and currently disabled; no card, bank, UPI or payment credential is collected by this form. Payment references and applicable provider notices must be added before checkout opens.
Recipients and purposes
Local preview records are accessible to the workspace operator and anyone with authorised access to that device or its backups. Country/city options come from a locally installed dataset, not a per-user external lookup. Production hosting, email, payment, storage, support and other processors, locations and transfer arrangements need a verified inventory before launch. We do not request marketing or sponsor-sharing permission in this form. Team submissions must not be supplied to sponsors or used for AI training without an appropriate separate agreement. Legally required disclosures and handling of claims must be assessed and documented.
Retention and deletion
Draft acknowledgement receipts and price quotes are cleaned up after seven days when the local service receives a new session request. Match records older than two hours are cleaned up on a new match. Session and reward records currently remain in the development database until the workspace operator removes them; backup copies may persist separately. A production retention schedule for entries, accounts, financial records, incidents, submissions and consents is not finalised. It must specify a justified period, deletion process and any legal hold before real collection opens.
Choices, requests and security
Use the device-draft option only if you want persistent local saving. Clear the draft or browser data to remove browser copies. Requests about preview records use the published privacy contact; the preview itself has no request inbox. Requests may need proportionate identity checks and explanation of legally required retention. Appropriate access control, backups, incident response and processor arrangements must be implemented and tested; this draft is not a security certification.
Children, sensitive details and updates
Age eligibility and any guardian process for entry remain unresolved; the registration preview does not request children’s data. Do not enter identity documents, medical information or emergency-contact data here. Any later collection needs a specific notice and suitable safeguards. Substantive notice changes must be versioned and communicated, with fresh consent where required. The Indian privacy framework has staged commencement: counsel must verify the provisions in force for the actual launch and collection dates.
Necessary session
The local preview uses fr_preview_session, an HttpOnly SameSite=Strict cookie with a maximum age of 30 days, to connect game verification, reward and quote activity to a browser. It is not set on the public website while team registration is closed. It is not proof of identity. Blocking or clearing it can interrupt reward retrieval. Production cookie security and hosting behaviour must be checked when the site is deployed.
Draft storage
forgerival-registration-v1 in session storage holds the current tab’s registration draft. If you select “Save my draft on this device”, the same key in local storage keeps the draft across visits until cleared. It includes contact information. “Start over” removes these draft copies; browser settings can also clear storage. Neither action automatically deletes server records.
Document owner: Liftor Software and Technology Pvt Ltd. Review status: draft; not effective for paid entry.