[ Last updated: 19 SEPTEMBER 2026 ]
Please read this Privacy Policy carefully before registering for or participating in Hacklabify V2.0. By registering for the event, providing personal information, or participating in any event activity, you acknowledge that you have read and understood how your information may be collected, used, stored, and processed as described in this Privacy Policy.
HACKLABIFY V2.0
PRIVACY POLICY
Effective Date: 1 October 2026
Last Updated: 19 September 2026
Founder: Saksham Rastogi
Brand: Hacklabify
Website: www.hacklabify.org
Email: contact @hacklabify.org
This Privacy Policy explains how [Legal Name of Organizing Entity] ("Hacklabify", "Organizer", "we", "us", or "our") collects, uses, stores, discloses, protects, and otherwise processes personal information in connection with Hacklabify V2.0 ("Event"), the Hacklabify website, registration systems, participant dashboards, communications, and related Event activities.
By registering for, accessing, or participating in Hacklabify V2.0, you acknowledge that you have read this Privacy Policy.
This Policy should be read together with the Hacklabify V2.0 Terms & Conditions and Code of Conduct.
1. IMPORTANT INFORMATION
Hacklabify may collect personal information necessary to:
process Event registrations;
verify participant eligibility;
manage Teams;
communicate Event information;
administer judging;
issue certificates;
distribute prizes;
provide Event services;
maintain Event security;
comply with legal obligations;
prevent fraud and abuse;
document and promote the Event.
We seek to collect information that is reasonably necessary for these purposes rather than collecting personal information indiscriminately.
Where applicable, personal-data processing will be governed by applicable Indian data-protection law. India's Digital Personal Data Protection Act, 2023 (DPDP Act) was enacted as India's statutory framework for processing digital personal data, and the Government notified an implementation timeline in November 2025 under which different provisions commence at different times. India Code
2. WHO IS RESPONSIBLE FOR YOUR DATA?
The entity responsible for determining the purposes and means of processing Event-related personal data is:
[LEGAL ENTITY NAME]
Brand: Hacklabify / Hacklabify Org
Address: [Full Address]
Email: [[email protected]]
Phone: [Official Phone Number]
For privacy-related requests:
Privacy Contact: [Name / Privacy Officer / Designated Contact]
Email: [[email protected]]
Do not publish a fictional "Data Protection Officer" title unless the Organizer actually has a person appointed to that role.
3. INFORMATION WE COLLECT
Depending on how you interact with Hacklabify, we may collect the following categories of information.
3.1 Identity Information
This may include:
full name;
photograph;
date of birth or age;
gender, where voluntarily provided and genuinely necessary;
government-issued identification information where required for verification;
participant ID;
student/college identification information where relevant.
We will not request government identification merely for convenience. If identity verification is required, the Organizer should specify the precise purpose and retention period.
3.2 Contact Information
This may include:
email address;
mobile/telephone number;
residential or correspondence address where required;
emergency contact information;
parent/guardian contact information for Minors.
3.3 Educational and Professional Information
Where relevant to eligibility or Event administration, we may collect:
school/college/university name;
educational level;
course/stream;
graduation year;
professional role;
organization/company;
developer or technical profile;
portfolio or professional links.
3.4 Team Information
If you participate as part of a Team, we may collect:
Team name;
Team members;
Team leader;
Team contact information;
project information;
Team submission;
Team communications.
3.5 Project and Submission Information
We may collect and process:
source code;
repositories;
websites;
applications;
documentation;
presentations;
project descriptions;
demonstration videos;
screenshots;
technical documentation;
architecture diagrams;
submitted URLs;
project metadata;
judging information.
Participants should not submit confidential personal information belonging to another person unless they have appropriate authority to do so.
4. INFORMATION COLLECTED AUTOMATICALLY
When you use the Hacklabify website or digital systems, certain technical information may be automatically collected, depending on the systems we deploy.
This may include:
IP address;
browser type;
operating system;
device type;
approximate location derived from technical information;
timestamps;
referring pages;
pages viewed;
session information;
authentication events;
security logs;
error logs;
network information.
We may use this information for security, diagnostics, fraud prevention, system administration, and service improvement.
5. COOKIES AND SIMILAR TECHNOLOGIES
Hacklabify may use cookies, local storage, session identifiers, and similar technologies.
These technologies may be used for:
authentication;
maintaining sessions;
security;
remembering preferences;
analytics;
measuring website performance;
preventing fraudulent activity.
Where legally required, non-essential cookies or similar technologies should be deployed only after obtaining the appropriate consent.
The specific cookies used by Hacklabify should be documented in a separate Cookie Notice where applicable.
6. HOW WE COLLECT INFORMATION
We may collect information:
Directly from you
For example, when you:
register;
create an account;
purchase a ticket;
join a Team;
submit a Project;
contact us;
request support;
apply for a role;
submit a sponsorship inquiry.
From your parent or guardian
Where applicable to Minor participants.
From your Team
For example, when a Team leader adds or manages Team members.
From Event partners
Where such sharing is lawful and necessary for Event administration.
Automatically
Through our websites, applications, security systems, and other technical infrastructure.
7. WHY WE USE YOUR INFORMATION
We may process personal information for the following purposes.
7.1 Event Registration
To:
create participant records;
verify registrations;
confirm eligibility;
manage tickets;
manage capacity;
communicate registration status.
7.2 Event Administration
To:
manage attendance;
manage Teams;
allocate mentors;
administer workshops;
manage submissions;
coordinate judges;
issue certificates.
7.3 Communications
To send:
registration confirmations;
Event announcements;
schedule updates;
deadline reminders;
security notices;
administrative messages;
important changes to Event arrangements.
7.4 Security
To:
detect suspicious activity;
prevent unauthorized access;
investigate abuse;
protect Event infrastructure;
prevent fraud;
maintain system integrity.
7.5 Judging
To administer:
project evaluation;
scoring;
rankings where applicable;
finalist selection;
prize determination.
7.6 Prizes
To verify winners and process prize-related documentation.
8. LEGAL BASES / LAWFUL PROCESSING
Depending on the applicable law and the particular processing activity, Hacklabify may process personal information based on:
consent;
performance of a requested service;
compliance with legal obligations;
legitimate operational or security purposes where legally recognized;
prevention of fraud or abuse;
other lawful grounds available under applicable law.
Under the DPDP Act, the statutory framework distinguishes consent-based processing and certain specified legitimate uses, with commencement occurring in phases under the Government's November 2025 notification. India Code
The Organizer should therefore update this section based on the legal requirements actually applicable on the date each processing activity occurs.
9. CHILDREN AND MINORS
Hacklabify may be accessible to school students and other individuals under 18.
Under the DPDP Act, a "child" is an individual who has not completed 18 years of age. India Code
Where applicable, Hacklabify may require:
parent/legal-guardian consent;
parent/legal-guardian contact information;
age verification;
additional safeguards;
restrictions on certain processing activities.
Where legally required, the Organizer will not knowingly rely on a Minor's consent where valid consent must instead be provided or verified through a parent/legal guardian.
The Organizer should obtain legal review before collecting or publishing photographs, videos, profiles, or other information relating to Minor participants.
10. IDENTITY VERIFICATION
Where identity verification is necessary, Hacklabify may request appropriate documentation.
The Organizer should:
explain why verification is required;
collect only the information necessary;
restrict access to authorized personnel;
apply appropriate security measures;
establish a defined retention period;
securely delete or dispose of information when it is no longer required, subject to legal requirements.
Hacklabify should not retain full government-ID documents indefinitely.
11. PROJECT DATA
Project submissions may contain personal information.
Participants are responsible for ensuring that their Projects do not unnecessarily contain:
passwords;
API keys;
access tokens;
private credentials;
private user databases;
confidential documents;
personal information of unrelated individuals.
Hacklabify may scan or review submissions for security, integrity, plagiarism, malware, or compliance purposes where reasonably necessary.
12. AI AND THIRD-PARTY TECHNOLOGY
Participants may use third-party AI systems, repositories, hosting platforms, APIs, analytics services, and other technologies in their Projects.
Participants are responsible for understanding the privacy and data-processing implications of those services.
Participants must not upload another individual's personal information to an AI or third-party service without an appropriate legal basis or authorization.
Hacklabify is not responsible for the independent privacy practices of third-party services used by Participants.
13. SHARING OF PERSONAL INFORMATION
We may disclose personal information to selected categories of recipients where reasonably necessary and lawful.
These may include:
Event Service Providers
Such as:
registration providers;
ticketing systems;
hosting providers;
email providers;
authentication providers;
database providers;
payment processors;
security providers.
Judges and Mentors
Only information reasonably necessary for Event evaluation or mentoring.
Sponsors and Partners
Only where reasonably necessary, authorized, or otherwise legally permitted.
Legal and Regulatory Authorities
Where disclosure is:
required by law;
required by a lawful governmental request;
necessary to protect legal rights;
necessary to investigate fraud or security incidents.
Professional Advisers
Such as legal, accounting, audit, or compliance advisers where reasonably necessary.
14. WE DO NOT SELL PERSONAL DATA
Hacklabify does not intend to sell participants' personal data as a commercial data-broker product.
The Organizer should not use participant information for unrelated commercial purposes merely because it was collected through Event registration.
Where marketing or promotional communications are separate from essential Event communications, appropriate consent or another lawful basis should be obtained where required.
15. SPONSOR ACCESS
Sponsors may receive limited participant information only where there is an appropriate lawful basis and the disclosure is consistent with the information provided to Participants.
Hacklabify should not automatically provide sponsors with unrestricted access to the complete participant database.
Where a sponsor requests participant leads, the Organizer should establish:
what information is shared;
why it is shared;
the lawful basis;
retention requirements;
sponsor restrictions on further use.
16. INTERNATIONAL DATA TRANSFERS
Some service providers used by Hacklabify may process information outside India.
Where personal information is transferred outside India, Hacklabify will apply requirements applicable to the relevant transfer and processing arrangement.
The DPDP Act contains provisions concerning processing outside India and allows the Central Government to restrict transfers to specified countries or territories under the statutory framework. India Code
The Organizer should maintain an actual list of countries/regions in which relevant vendors process Event data rather than making a generic claim that all data is stored in India.
17. DATA RETENTION
Hacklabify will retain personal information only for as long as reasonably necessary for the purposes for which it was collected, subject to:
legal obligations;
accounting requirements;
dispute resolution;
fraud prevention;
security;
enforcement of agreements;
legitimate archival requirements where applicable.
Example retention schedule:
DataSuggested retentionRegistration informationEvent duration + defined administrative periodTeam informationEvent duration + defined administrative periodProject submissionsAs specified by Event/project rulesPrize documentationPeriod required for accounting/tax/legal purposesSecurity logsDefined security retention periodMarketing consent recordsUntil withdrawal + legally required record periodMinor consent recordsDefined period necessary to demonstrate lawful authorizationGovernment IDMinimum period necessary for verification
Do not publish these periods unless the Organizer can actually implement them.
18. DATA SECURITY
Hacklabify will implement reasonable technical and organizational safeguards appropriate to the nature of the information processed.
Depending on the system, safeguards may include:
access controls;
authentication;
encryption in transit;
encryption at rest where appropriate;
least-privilege access;
logging;
backup controls;
vulnerability management;
security monitoring;
credential management;
incident-response procedures.
No Internet-based system can be guaranteed to be completely secure.
19. DATA BREACHES
If Hacklabify becomes aware of a personal-data breach, the Organizer will assess and respond according to applicable legal requirements.
Depending on the nature and severity of the incident, response may include:
containment;
investigation;
remediation;
preservation of evidence;
notification of affected individuals;
notification of relevant authorities;
password or credential resets;
additional security controls.
The DPDP Act and its associated rules establish requirements relating to personal-data security and breach handling; the applicable provisions have a phased commencement timeline. India Code
20. YOUR RIGHTS
Subject to applicable law and the circumstances of processing, individuals may have rights concerning their personal data.
These may include rights relating to:
access to information about processing;
correction;
updating;
withdrawal of consent where processing is consent-based;
grievance redressal;
deletion/erasure where legally applicable;
nomination or other statutory rights where applicable.
The exact availability and procedure for exercising each right depends on the law applicable at the relevant time.
21. WITHDRAWING CONSENT
Where processing is based on consent, you may withdraw consent through the method provided by Hacklabify.
Withdrawal of consent does not necessarily invalidate processing that was lawfully performed before withdrawal.
Withdrawal may also affect our ability to provide certain Event services where the information is genuinely necessary for those services.
Where another lawful basis permits continued processing, the Organizer may continue processing to the extent legally permitted.
22. DATA CORRECTION
If you believe information associated with your Event account is inaccurate, contact:
Include:
your name;
registered email;
relevant participant ID;
information requiring correction;
supporting information where necessary.
The Organizer may require reasonable verification before modifying account information.
23. DATA DELETION
You may request deletion of personal information where applicable.
Deletion may not be immediate where information must legally be retained for:
tax purposes;
accounting;
fraud prevention;
security;
dispute resolution;
legal claims;
regulatory compliance;
enforcement of agreements.
Where deletion is required, the Organizer should delete or anonymize the information within the applicable retention framework.
24. GRIEVANCE REDRESSAL
Privacy complaints may be submitted to:
Privacy/Grievance Contact:
Email: [email protected]
A complaint should contain sufficient information to identify:
the requester;
the relevant account or registration;
the issue;
the requested resolution.
The Organizer may request reasonable identity verification before responding to privacy requests.
25. AUTHENTICATION AND ACCOUNT SECURITY
Where Hacklabify provides participant accounts, users are responsible for protecting their credentials.
You must not:
share passwords;
share authentication codes;
expose private API keys;
allow unauthorized persons to access your account;
attempt to access another person's account.
If you believe your account has been compromised, notify Hacklabify immediately.
26. MARKETING COMMUNICATIONS
Essential Event communications may be sent regardless of whether a Participant has opted out of promotional communications, where legally permitted.
Marketing communications may include:
future Hacklabify events;
workshops;
announcements;
newsletters;
partner opportunities.
Where consent is required, promotional communications will be sent only on an appropriate lawful basis.
Participants may opt out of promotional communications using the unsubscribe mechanism provided.
27. EVENT PHOTOGRAPHY AND VIDEO
Hacklabify may photograph, record, livestream, or otherwise document Event activities.
Such material may include a Participant's:
image;
voice;
name;
presentation;
project demonstration;
public statements.
Where required, appropriate consent or another lawful basis will be used.
For Minors, the Organizer should implement an appropriate parental/guardian consent process before using their identifiable image or other promotional material where required by law.
28. PUBLIC PROJECT INFORMATION
Unless an applicable Event rule states otherwise, Hacklabify may publish limited information about selected Projects, such as:
Team name;
Project name;
Project description;
public repository;
public website;
award received;
publicly presented screenshots;
presentation materials.
Participants should not include confidential information in materials intended for public submission.
29. SPONSOR AND PARTNER WEBSITES
Hacklabify may provide links to third-party websites.
Once you leave Hacklabify's systems, the privacy practices of the third party are governed by that party's own policies.
Hacklabify does not control independent third-party privacy practices.
30. CHILD-SAFETY CONSIDERATIONS
Because Hacklabify may involve Minors, the Organizer should apply heightened operational safeguards where appropriate, including:
parental/guardian verification;
restricted access to Minor information;
appropriate staff conduct requirements;
controlled publication of Minor information;
emergency-contact procedures;
appropriate supervision arrangements;
procedures for reporting safety concerns.
The exact safeguards should reflect the Event's physical and digital operating model.
31. DATA MINIMIZATION
Hacklabify should collect only information reasonably necessary for a stated Event purpose.
For example, Hacklabify should not request:
"Upload your complete identity documents because we might need them later."
Instead, the registration process should identify the actual purpose and collect the minimum necessary information.
32. ACCURACY OF INFORMATION
Participants are responsible for providing accurate information.
If inaccurate information is provided, Hacklabify may be unable to:
verify eligibility;
contact the Participant;
issue certificates;
distribute prizes;
manage emergency contacts;
resolve account problems.
Participants should update material information where the Event system permits it.
33. CHANGES TO THIS PRIVACY POLICY
Hacklabify may update this Privacy Policy to reflect:
changes to Event operations;
new technologies;
new service providers;
legal or regulatory changes;
security requirements;
changes to data-processing practices.
The updated version will include a revised "Last Updated" date.
Where required, material changes will be communicated through an appropriate channel.
34. GOVERNING LAW
This Privacy Policy shall be interpreted subject to applicable laws of India.
The Organizer shall implement its actual privacy practices in accordance with the legal requirements applicable to the Event and its processing activities.
35. SEVERABILITY
If any provision of this Privacy Policy is determined to be invalid or unenforceable, the remaining provisions shall continue to apply to the extent permitted by law.
36. CONTACT INFORMATION
Privacy Team
Hacklabify V2.0
Founder: Saksham Rastogi
Website: www.hacklabify.org
Privacy Email: [email protected]
37. ACKNOWLEDGEMENT
By registering for Hacklabify V2.0, you acknowledge that you have had an opportunity to review this Privacy Policy and understand how Hacklabify may process information in connection with the Event.
Where a separate consent is legally required, registration alone will not be treated as a substitute for that consent.