CORPSE
The Operating System for Esports
Account Creation & Deletion
Privacy Policy
What We Collect • Why • How It's Protected • Your Rights
DPDP Act 2023 Compliant | Version 1.0 | Final
This Privacy Policy governs data collected and processed exclusively during account creation, sign-up authentication, and account deletion on the Corpse platform. All other platform data practices are governed by the Corpse Full Privacy Policy.
PART I — INTRODUCTION & SCOPE
1. Who This Policy Applies To
[CORPSE ESPORTS PRIVATE LIMITED] ("Company", "we", "us", "our") publishes this Account Creation & Deletion Privacy Policy for the Corpse platform ("Platform"). This Policy applies to:
- Any individual creating a new account on the Platform via the mobile application.
- Any individual who begins but does not complete the sign-up process — to the extent any data was submitted before abandonment.
- Any individual accessing the Platform as a Guest User prior to creating an account.
- Any Registered User who initiates or completes the account deletion process.
This Policy is strictly scoped to the account creation and deletion stages. For all other platform data practices — including tournament participation, payments, communications, and analytics — refer to the Corpse Full Privacy Policy.
2. What This Policy Covers & Excludes
2.1 What This Policy Covers
- Data collected from Guest Users before any account is created
- Personal data submitted in the sign-up registration form
- Data processed via authentication methods at sign-up (passwordless email, Google, Apple)
- Location data collected at the point of registration
- Data auto-generated by the Platform when your account is created
- The authentication event log entry created at sign-up
- Communications directly triggered by the sign-up and deletion acts (Magic Link email and deletion verification link)
- Data processed during the account deletion request and verification flow
- Fate of all data categories after account deletion
2.2 What This Policy Explicitly Does NOT Cover
Excluded Topic | Why Excluded | Where It Is Covered |
OTP, SMS, WhatsApp, promotional communications | Post-registration activity — not triggered by sign-up or deletion | Corpse Full Privacy Policy |
Firebase Analytics data | Post-registration platform usage tracking | Corpse Full Privacy Policy |
Razorpay / KYC financial data | Only triggered after registration at KYC verification stage | Corpse Full Privacy Policy |
Tournament, match, squad data | Full platform scope — not sign-up or deletion specific | Corpse Full Privacy Policy |
IP address & device model/OS | Not collected by the Platform at any stage | N/A — not applicable |
Browser cookies | App uses none; landing page is purely static with zero tracking | N/A — not applicable |
ELO ranking progression & match history | Generated post-registration through tournament participation | Corpse Full Privacy Policy |
3. Legal Basis for Processing
We process your account creation and deletion data under the following legal bases as recognised under the Digital Personal Data Protection Act, 2023 (DPDP Act) and the Information Technology Act, 2000:
Legal Basis | Registration/Deletion Data It Applies To |
Contractual Necessity | Name, email, DOB, state, pincode, in-game ID, in-game username — mandatory to deliver the account creation service you are requesting. Also applies to deletion verification link processing. |
Consent | Precise latitude and longitude location data — collected only when you explicitly grant location permission on your device. You may decline without affecting your ability to create an account. |
Legitimate Interests | Authentication event log (method + timestamp) — collected for security monitoring and fraud prevention at the point of sign-up and deletion verification. |
PART II — DATA COLLECTED AT ACCOUNT CREATION
4. Guest User — Data Collected Before Sign-Up
Before creating an account, you may access the Corpse Platform as a Guest User. During a Guest session:
- No personal data of any kind is collected or stored.
- No registration information, name, email, or location data is recorded.
- The session is entirely temporary and stateless — nothing persists once the session ends.
- If you proceed to create an account after a Guest session, your Guest session is discarded completely. Nothing from your Guest session is associated with or carried over to your new account in any form.
Important: Guest access does not constitute account creation and generates no stored data, profile, or platform history of any kind.
5. Registration Form Data
When you complete the sign-up form to create a Corpse account, you are required to provide the following personal data. All fields are mandatory — the Platform will not permit account creation if any field is blank or contains invalid data.
Field | What You Submit | Why Mandatory |
Full legal name | Your real full name as it appears on official identification | Used to auto-generate your unique, permanent Platform username |
Email address | A valid, active email address you control | Primary account identifier across all three authentication methods; delivers the Magic Link |
Date of birth | Your actual date of birth (DD/MM/YYYY) | Classifies you as Minor User (under 18) or Standard User, determining your access tier |
State of residence | Your current state of residence within India | Region-based ELO ranking and opponent matchmaking grouping |
Pincode | Your current residential pincode | Provides sub-state regional precision for ELO ranking and matchmaking accuracy |
In-game ID | Your unique player ID within the supported game title (e.g., BGMI, Free Fire Max) | Ties your Platform account to your in-game identity for tournament registration and result verification |
In-game username | Your display name within the game (e.g., your Free Fire Max in-game name) | Used for squad display, match records, and public player profile identification |
Note: Phone numbers are not collected at any point during account creation. The Platform does not require a phone number for sign-up under any authentication method.
6. Authentication Method Data
The Platform supports three authentication methods. No passwords are stored under any method. Each method processes data as follows:
6.1 Passwordless Email Authentication (Magic Link)
Data Point | What Happens to It |
Email address | Stored as your primary account identifier. Used to deliver the Magic Link and all future account-essential communications. |
Magic Link token | A cryptographically secure, single-use token. Valid for 6 hours from issue. Expires and is permanently invalidated immediately upon click or after 6 hours — whichever comes first. Not retained after expiry. |
Link click event | Logged as an authentication event — method and timestamp only. Used for security monitoring and session initiation. No IP address or device data is recorded. |
Password | Not collected. Not stored. The Platform is fully passwordless. |
Note: The Magic Link is delivered only to your registered email address. You are solely responsible for the security of your email account.
6.2 Google Sign-In
When you sign up via Google, the Platform receives only the following from Google's OAuth 2.0 service:
- Your Google account's email address — used as your Platform account identifier.
- Your Google account's display name — used as the basis for generating your Platform username.
The Platform does not receive your Google password, recovery details, contacts, Google Drive data, or any other Google account information. Authentication is handled entirely by Google's infrastructure. Corpse only receives the output — email and name.
Note: If you use Google Sign-In, your Corpse account email is your Google account email. Changes to your Google account email do not automatically update your Corpse account. You must initiate an email change separately within Corpse settings.
6.3 Apple Sign-In
When you sign up via Apple (Apple devices only), the Platform receives only the following from Apple:
- Your Apple ID email address — or an Apple-generated relay email address if you use the 'Hide My Email' feature. Either becomes your Platform account identifier.
- Your name as provided by Apple — used as the basis for generating your Platform username. Apple only shares the name on first sign-in; subsequent sign-ins do not re-share it.
The Platform does not receive your Apple ID password, iCloud data, payment information, or any other Apple account data.
Important: If you use Apple's 'Hide My Email' feature, your Platform account is permanently tied to the relay email Apple provides — not your real Apple ID email. If you lose access to that relay address, account recovery becomes extremely difficult. Note your relay email address after sign-up.
6.4 One Email Per Account — Privacy Implications
- Your email address is stored as a unique identifier in our database the moment your account is created.
- The same email cannot be used to create another account via any authentication method.
- This uniqueness constraint is permanent — including after account deletion. A deleted account's email is retired and cannot be re-registered.
- This means your email address remains in our system indefinitely as a retired identifier, even if all other account data is removed.
7. Location Data Collected at Registration
Location Type | How Collected | Mandatory? | What Happens If You Decline |
State of residence | You select from a dropdown — not auto-detected | Yes | Account creation cannot proceed without selecting a state |
Pincode | You manually type your pincode | Yes | Account creation cannot proceed without entering a pincode |
Latitude & Longitude | Collected from your device only after you grant location permission via the app permission prompt — separate from the registration form | No — consent-based | You can still create an account and use the Platform fully. Only region-based matchmaking precision is reduced. |
Precise latitude and longitude are collected only after you explicitly grant location permission to the Corpse app on your device. This permission prompt appears separately from the registration form. You may revoke this permission at any time via your device settings (Settings > Corpse > Location). Revoking stops future collection but does not delete previously collected lat/long data.
Note: To request deletion of your lat/long data specifically, contact legal@corpsearena.com with the subject line 'Location Data Deletion Request'.
8. Auto-Generated Data at Sign-Up
When your account is successfully created, the Platform automatically generates and stores the following:
Auto-Generated Data | How Generated | Permanent? |
Platform username | Algorithmically generated from your submitted full name. Unique across the entire Platform. | Yes — cannot be changed after creation under any circumstance |
Account ID | A unique internal system identifier assigned at the moment of account creation. | Yes — permanent internal reference for all data associations |
Account creation timestamp | The exact date and time your account was created, recorded in IST. | Yes — retained as part of the account record |
Initial ELO score | A default starting ELO value assigned to all new accounts before any match data is recorded. | Yes — forms the base of your competitive ranking history |
Account access tier | Automatically classified as 'Minor User' or 'Standard User' based on your submitted date of birth. | Retained — may be updated upon KYC verification |
9. Authentication Event Log at Sign-Up
At the moment your account is created, the Platform records a single authentication event log entry containing:
- Authentication method used (email Magic Link, Google, or Apple)
- Timestamp of account creation (date and time in IST)
This is the only technical data recorded at sign-up. No IP address, device model, operating system, or any other device-identifying information is collected or stored at account creation.
Note: This authentication event log is retained indefinitely as part of the security audit trail and for fraud prevention purposes.
PART III — COMMUNICATIONS TRIGGERED BY ACCOUNT CREATION & DELETION
10. Magic Link Email — Sign-Up
When you choose passwordless email authentication during sign-up, the Platform sends a single transactional email to your registered email address. This is the only communication triggered directly by the account creation act itself.
Attribute | Detail |
Trigger | You submit your email address on the sign-up screen |
What It Contains | A single-use, secure authentication link (Magic Link) and basic Platform branding |
Data In the Email | Your email address (as recipient) and the Magic Link token — nothing else |
Validity | 6 hours from issue. Permanently invalidated after single use or after 6 hours |
Sent By | Corpse platform via email delivery service |
Can Be Opted Out? | No — this is essential for account creation under the passwordless email method |
Logged | Delivery event logged with timestamp and method only. No read/open tracking at sign-up stage. |
11. Account Deletion Verification Link Email
When you initiate an account deletion request, the Platform sends a single transactional email to your registered email address as part of the identity verification step (Step 3 of the deletion process as described in the Corpse Terms & Conditions, Section 21).
Attribute | Detail |
Trigger | You initiate an account deletion request from Account Settings |
What It Contains | A single-use, secure verification link and a brief summary of what will be permanently lost |
Data In the Email | Your email address (as recipient) and the verification link token — nothing else |
Validity | 6 hours from issue. Permanently invalidated after single use or after 6 hours |
Sent By | Corpse platform via email delivery service |
Can Be Opted Out? | No — this is mandatory for identity verification before account deletion is processed |
Logged | Delivery event logged with timestamp. This log is retained as part of the deletion audit trail. |
Note: The 3-login-attempt limit does not apply to deletion verification links. These are separate, isolated one-time security tokens issued exclusively for the deletion flow.
12. Scope Boundary — What Is Not Covered Here
The following communications are explicitly outside the scope of this Policy. They are triggered by post-registration platform activity and are governed by the Corpse Full Privacy Policy:
Communication | When Triggered | Governed By |
OTP via SMS | At login — post-registration activity | Full Privacy Policy |
Payment receipts via email | After a financial transaction — requires KYC | Full Privacy Policy |
Match alerts via in-app | During tournament participation | Full Privacy Policy |
Promotional emails | Marketing campaigns — opt-out available | Full Privacy Policy |
Promotional SMS | Marketing campaigns — opt-out available | Full Privacy Policy |
Promotional WhatsApp messages | Marketing campaigns — opt-out available | Full Privacy Policy |
Platform update notifications | Service announcements — post-registration | Full Privacy Policy |
PART IV — WHY WE COLLECT EACH FIELD
13. Purpose Mapping Table
The following table maps every data field collected at account creation to its specific documented purpose, secondary use, and legal basis. We collect only what is strictly necessary for the stated purposes.
Data Field | Primary Purpose | Secondary Purpose | Legal Basis |
Full legal name | Auto-generate permanent Platform username | Identity reference for support and dispute resolution | Contractual necessity |
Email address | Primary account identifier and authentication | Delivery of Magic Link and account-essential communications | Contractual necessity |
Date of birth | Classify as Minor User or Standard User | Age-appropriate access tier assignment | Contractual necessity |
State of residence | Assign to regional ELO ranking group | State-level matchmaking grouping | Contractual necessity |
Pincode | Sub-state regional precision for ELO ranking | Accurate opponent matchmaking within state | Contractual necessity |
In-game ID | Link Platform account to in-game identity | Tournament registration and result verification | Contractual necessity |
In-game username | Public display name on squads, match records, profiles | Competitive identity within the Platform | Contractual necessity |
Latitude & Longitude | Granular region-based ELO ranking accuracy | Precise opponent matchmaking by geographic proximity | Consent |
Magic Link token | Secure passwordless authentication at sign-up | One-time account creation verification | Contractual necessity |
Google account email | Account identifier via Google Sign-In | Seamless sign-up without separate email entry | Contractual necessity |
Apple account email | Account identifier via Apple Sign-In | Seamless sign-up without separate email entry | Contractual necessity |
Platform username | Public competitive identity across the Platform | Permanent unique identifier for match and rank records | Contractual necessity |
Account ID | Internal unique identifier for all data associations | Audit trail and dispute resolution reference | Contractual necessity |
Auth event log | Security record of account creation event | Audit trail and fraud detection | Legitimate interests |
Deletion verification log | Security record of deletion initiation and confirmation | Compliance and audit trail for irreversible action | Legitimate interests |
PART V — STORAGE, PROTECTION & RETENTION
14. Security of Registration & Deletion Data
All registration and deletion data is stored on secure, cloud-based servers. The following security measures apply specifically to account creation and deletion data:
Security Measure | What It Protects |
HTTPS/TLS encryption in transit | All data submitted during sign-up and deletion flows is encrypted between your device and our servers. |
Encrypted database storage | Registration data is stored in an encrypted database. Raw data is not accessible without proper decryption keys. |
Passwordless design | No password is ever created or stored, eliminating brute force, credential stuffing, and phishing attack vectors at sign-up. |
Single-use Magic Link tokens | Authentication and deletion verification tokens are single-use and expire within 6 hours, preventing replay attacks. |
Role-based access control | Only authorised Company personnel with a documented operational need can access registration data. All access is logged. |
Email uniqueness constraint | The database enforces that no two accounts share the same email address, preventing duplicate registrations. |
Deletion pre-verification requirement | Account deletion requires identity re-verification via Magic Link before processing — preventing unauthorised deletion requests. |
15. Third-Party Access at Sign-Up & Deletion Stage
At the account creation and deletion stages specifically, your data is shared with the following third parties only:
- Google (if you use Google Sign-In): Google's OAuth 2.0 infrastructure processes your Google credentials to authenticate you. Corpse receives only your email and name from Google.
- Apple (if you use Apple Sign-In on Apple devices): Apple's Sign-In infrastructure processes your Apple ID credentials. Corpse receives only your email (or relay email) and name from Apple.
At the account creation and deletion stage, your data is NOT shared with:
- Razorpay or any payment processor — payment gateway data sharing only occurs at KYC verification stage, which is post-registration and governed by the Full Privacy Policy.
- Firebase Analytics — analytics data collection begins post-registration through app usage, not at sign-up.
- Any marketing platform, advertiser, or data broker — at any stage.
Important: Corpse does not sell, rent, or trade your registration or deletion data to any third party for any commercial purpose. This is an unconditional commitment.
16. Retention Periods by Data Field
The following table specifies how long each piece of registration data is retained. These periods are determined by legal requirements, platform integrity needs, and contractual obligations.
Data Field | Retention Period | Reason |
Full name | Indefinitely (including after account deletion) | Embedded in match history records and platform audit logs |
Email address | Indefinitely — permanently retired post-deletion | Prevents re-registration abuse with same email |
Date of birth | Duration of account + retained for compliance | Age verification audit trail |
State & pincode | Duration of account + retained in anonymised match records | Historical ELO and match data integrity |
In-game ID & username | Indefinitely | Match history and tournament record integrity |
Platform username | Removed from public view on deletion; retained internally | Historical record reference and anonymised match display |
Account ID | Indefinitely | Internal audit trail and dispute resolution |
Latitude & Longitude | Active account + purged within 30 days of account deletion | DPDP Act data minimisation compliance |
Auth event log (sign-up) | Indefinitely | Security audit trail and fraud prevention |
Magic Link tokens | Expire within 6 hours — not retained after expiry | Single-use authentication — no ongoing need |
Deletion verification log | Indefinitely | Compliance audit trail for irreversible account deletion action |
Account creation timestamp | Indefinitely | Account record integrity |
Note: Account deletion does not result in immediate erasure of all registration data. Where retention is legally mandated or necessary for platform integrity, data is retained as specified. The legal basis for any such retention will be communicated upon written request to legal@corpsearena.com.
PART VI — DATA COLLECTED & PROCESSED DURING ACCOUNT DELETION
17. Deletion Verification Data
When you initiate an account deletion request, the Platform processes the following data specifically in connection with the deletion flow:
- Your registered email address — to deliver the deletion verification Magic Link.
- A one-time deletion verification token — generated, sent, and invalidated upon click or after 6 hours.
- A deletion event log entry — recording the deletion request initiation timestamp, verification completion timestamp, and authentication method. No IP or device data is recorded.
- Your Captain and Guild leadership status — checked against active tournaments and Guilds to enforce pre-deletion transfer requirements.
- Your pending financial transaction status — checked to ensure no unresolved disbursements or payments exist before deletion proceeds.
18. Data Fate After Deletion — Full Table
Account deletion does not result in complete erasure of all associated data. The following table details the exact treatment of every data category upon account deletion, consistent with the Corpse Terms & Conditions, Section 22:
Data Category | Outcome After Account Deletion | Legal Basis for Retention |
Account profile & public username | Permanently removed from public view within 24 hours of deletion processing | N/A — deleted |
Registered email address | Permanently retired — cannot be re-used to create a new Platform account | Legitimate interests — prevents re-registration abuse |
Full name | Retained internally; anonymised in all public-facing displays | Platform integrity |
Match history & results | Retained on Platform servers indefinitely | Platform integrity — competitive record preservation |
ELO scores & ranking records | Retained on Platform servers indefinitely | Platform integrity |
Financial & payment transaction records | Retained for minimum 5 years post-transaction | Legal obligation — RBI & PMLA regulatory requirements |
Squad & tournament participation logs | Records retained; username anonymised in all public displays | Platform integrity |
KYC documents | Governed solely by Razorpay's data retention policy | Legal obligation — RBI/PMLA via Razorpay |
Security & activity logs | Retained indefinitely | Legal obligation & legitimate interests — fraud prevention |
Unused Corpse Credits | Permanently forfeited — no monetary refund | N/A — not personal data |
Active subscription plans | Cancelled immediately — no pro-rata refund | N/A — not personal data |
Latitude & Longitude location data | Purged from Platform servers within 30 days of account deletion | DPDP Act data minimisation |
In-app notifications | Deleted immediately upon account removal | N/A — no ongoing need |
Authentication event logs | Retained indefinitely | Legitimate interests — security audit trail |
Deletion event log | Retained indefinitely | Legal compliance — audit trail for irreversible action |
Account creation timestamp | Retained indefinitely | Account record integrity |
Note: Under the Digital Personal Data Protection Act, 2023, you have the right to request erasure of your personal data. Where retention is required by law or for platform integrity, the Company will retain specific data and communicate the precise legal basis upon written request to legal@corpsearena.com.
19. Financial Data at Deletion
The following financial data rules apply at the time of and following account deletion:
- All unused Corpse Credits are permanently forfeited with no refund. This is not personal data but is noted here for completeness.
- Active subscription plans are cancelled immediately. No pro-rata refund is issued.
- Entry fees paid for upcoming tournaments are permanently forfeited.
- Prize money pending disbursement to a KYC-verified bank account will be processed to the registered bank account within 7 working days, provided bank details are valid.
- If pending prize money cannot be disbursed due to invalid bank details, it is permanently forfeited after 30 calendar days from the deletion date.
20. Location Data Purge
Latitude and longitude location data is the only category of registration data subject to a defined post-deletion purge timeline. It will be permanently deleted from all Corpse servers within 30 calendar days of your account deletion being processed.
All other location data (state and pincode) is retained as part of anonymised match and ELO records for platform integrity purposes.
Note: If you wish to request earlier deletion of your lat/long data, contact legal@corpsearena.com with the subject line 'Location Data Deletion Request'. We will process the request and confirm deletion within 30 days.
PART VII — MINOR USERS — REGISTRATION PRIVACY
21. Classification at Sign-Up
Users below 18 years of age ("Minor Users") are identified at sign-up based solely on the date of birth submitted in the registration form.
- If your submitted date of birth indicates you are under 18, your account is automatically classified as a Minor User account at the moment of creation.
- Minor User access restrictions are applied immediately — you cannot act as a Captain, make financial transactions, or complete KYC verification.
- If a false date of birth is submitted to evade Minor User restrictions and this is subsequently identified, the account will be suspended pending review.
22. Data Minimisation for Minors
For users classified as Minor Users at sign-up, the following data minimisation standards apply:
- No financial information of any kind is collected at sign-up or at any subsequent stage. Bank account details, UPI IDs, and payment card data are never collected from Minor Users.
- Minor Users cannot complete KYC verification. Accordingly, their registration data is never shared with Razorpay or any payment gateway.
- Minor Users' registration data is not used for advertising profiling, behavioural targeting, or any commercial data processing beyond what is strictly necessary for basic Platform access.
- Minor Users may only participate in tournaments via squad invite from a KYC-verified Captain — they cannot independently register for any paid tournament.
23. DPDP Act Parental Consent Framework
The Digital Personal Data Protection Act, 2023 requires verifiable parental or guardian consent before processing personal data of a child (under 18 years). Our current approach:
- We rely on the date of birth self-declared at registration to identify Minor Users.
- For Minor Users, data processing at sign-up is restricted to what is strictly necessary for basic Platform access.
- We will implement verifiable parental consent mechanisms as and when directed by the Data Protection Board of India under Rules made pursuant to the DPDP Act, 2023.
Important: If you are a parent or guardian and believe your child has registered on the Platform without your consent, contact us immediately at legal@corpsearena.com. We will review and, where appropriate, delete the account promptly.
PART VIII — YOUR RIGHTS
24. Rights Under the DPDP Act 2023
As a Data Principal under the Digital Personal Data Protection Act, 2023, you have the following rights specifically in relation to your account creation and deletion data:
Right | What It Means for Account Creation & Deletion Data | Limitation |
Right to Access | Request a summary of the registration data we hold about you — name, email, DOB, state, pincode, in-game IDs — and the documented purpose for each field. | Identity verification required before data is disclosed. |
Right to Correction | Request correction of any inaccurate registration data such as incorrect state, pincode, or in-game ID. | Platform username cannot be corrected after creation. It is permanent by design (Corpse T&C, Section 14.1). |
Right to Erasure | Request deletion of your registration data. May also be exercised by deleting your account (Corpse T&C, Part IV). | Data retained for legal compliance (financial records, security logs) or platform integrity (match history) cannot be erased on demand. Legal basis communicated on request. |
Right to Withdraw Consent | Withdraw consent for lat/long location data collection at any time via device permission settings. | Withdrawal stops future collection only. Previously collected lat/long is retained until account deletion + 30-day purge cycle. |
Right to Grievance | Raise a formal grievance regarding collection, storage, or use of your registration or deletion data. | Response within 30 days. If unresolved, escalate to the Data Protection Board of India. |
Right to Nomination | Nominate another individual to exercise your data rights on your behalf in the event of death or incapacity, as provided under the DPDP Act, 2023. | Nomination process to be made available in accordance with Rules under the DPDP Act. |
25. How to Exercise Your Rights
To exercise any of the rights in Section 24, submit a written request to our Grievance Officer:
Subject Line | Data Rights Request — Account Creation/Deletion — [Your Registered Email] |
Include | Your full name, registered email address, the specific right you wish to exercise, and the data concerned |
Response Time | Acknowledgement within 7 days. Full response within 30 days. |
Escalation | If unsatisfied, escalate to the Data Protection Board of India once operational under DPDP Act, 2023 |
PART IX — UPDATES & CONTACT
26. Changes to This Policy
We reserve the right to update this Privacy Policy at any time. When material changes are made:
- Registered Users will be notified via email and in-app notification at least 7 days before the change takes effect.
- The 'Last Updated' date on this Policy will be revised to reflect the update date.
- The updated Policy will be accessible within the Platform.
Your continued use of the Platform after the effective date of any change constitutes your acceptance of the revised Policy. If you do not agree with any change, you must delete your account before the change takes effect.
27. Grievance Officer & Contact
For any queries, concerns, or formal grievances related to this Policy or the processing of your registration and deletion data, contact:
Company | [CORPSE ESPORTS PRIVATE LIMITED] |
Grievance Officer | [TO BE APPOINTED — Name to be updated upon entity registration] |
Designation | Data Protection Officer / Grievance Officer |
Legal Email | |
Support Email | |
Registered Address | Silchar Road Ghat Line, Subashnagar, Karimganj - 788710, Assam, India |
Response Time | Within 30 days of receipt of grievance |
Escalation (unresolved) | Data Protection Board of India (once operational under DPDP Act, 2023) |
This Account Creation & Deletion Privacy Policy was last updated in April 2026 and is effective from May 1, 2026.
Version 1.0 | Final | Corpse — [CORPSE ESPORTS PRIVATE LIMITED]
Confidential & Proprietary. All rights reserved.