1. The short version
We collect only what we need to run a community where people do real work together, we do not sell personal data, and you decide what becomes public. In summary:
- Newsletter and contact: if you subscribe, we keep your email and the proof that you agreed. If you write to us, we keep your message long enough to reply.
- Accounts: if you join LARP OS, we keep the details you give us, the work you submit and the reviews you write or receive.
- Private by default: your profile and records are private unless you make them public. Certificates are public by design but show only the name you choose.
- No ads and no tracking: we do not use advertising trackers, analytics scripts or open and click tracking in emails.
- Who handles your data: a short list of service providers (hosting, database, email, file storage, rate limiting and GitHub sign-in) process it for us. Section 6 lists them.
- Your choices: you can see, correct, export and delete your data, and you can withdraw consent as easily as you gave it. Sections 5 and 15 explain how.
- Adults only: you must be 18 or older.
- Who to ask: contact@larpintech.com.
2. Who is responsible for your data
Syed Omer, founder of LarpinTech, a student community that is not a registered company and is run with a team of volunteer members, based in Hyderabad, Telangana, India, decides why and how personal data is processed on www.larpintech.com and in LARP OS, and is the "Data Fiduciary" under India's Digital Personal Data Protection Act, 2023 (the "DPDP Act"). We call ourselves "we" and "us".
This policy covers personal data we handle through:
- the public website, the newsletter and the contact form;
- LARP OS accounts, missions, evidence, reviews, proposals, Proof Records, Certificates and badges;
- applications for open roles;
- moderation, security and the administration of the Service.
It does not cover websites or services run by others that we link to, such as GitHub. Their own policies apply.
Privacy contact and Grievance Officer: Syed Furqhan, contact@larpintech.com, Hyderabad, Telangana-500061.
3. What we collect, and when
We collect data you give us, data created by using the Service, and a small amount of technical data. We do not buy data about you, and we do not collect more than the Service needs.
| When | What we collect |
|---|---|
| Visiting the site | Technical data our host records: IP address, browser and device type, pages requested, time and referring page, and error details. Used for delivery, security and fixing faults. |
| Subscribing to the newsletter | Email address, the page you signed up from, optional lane interest, your confirmation that you are 18 or over, and a record of your consent (purpose, policy version, time, and a keyed hash of your IP address). |
| Using the contact form | Name, email address and your message. |
| Creating an account | Verified primary email address; if you use GitHub, your GitHub numeric ID, username, display name and avatar URL; your handle, display name, 18+ confirmation and the time you gave it, consent choices, and onboarding progress. |
| Your profile | Lanes (areas of interest), skills, designation, level, profile visibility, certificate name preference and notification settings. |
| Missions and evidence | Claims you make, deadlines, milestones, Evidence you upload (files up to 10 MB: PDF, PNG, JPG, Markdown, text or CSV), links, notes, file checksums, and the results of automated checks on them. |
| Peer review | Reviews you write (decision, checklist, notes) and reviews of your work. |
| Proposals and interest | LARP IT proposals you write and the proposals you mark as interesting. |
| Proof Records, Certificates and badges | The record of verified work, holder choices about how your name is shown, the Certificate's public ID and signed payload, and the reason and evidence reference for any badge. |
| Applying for a role | Name, email, your written answer, links you provide, an optional resume (PDF), your consent and 18+ confirmation, and the status and notes our team records. |
| Email we send | Delivery events from our email provider (delivered, bounced, complained, unsubscribed) and a suppression list stored as hashes. |
| Moderation | Reports about you or by you, the rules concerned, our internal notes, the actions taken, notices sent, appeals, and, after a removal, a hashed email and reason code (section 13). |
| Security and administration | Session records, sign-in method, hashed IP addresses, rate-limit counters, and an audit log of administrator actions, including when an administrator views your email address or downloads a file. |
What we do not ask for. We do not ask for government ID numbers, bank or card details, health information, caste, religion or political views. Please do not put them in your profile, Evidence, proposals or applications. If you include them by mistake, tell us and we will delete them.
Information about other people. Do not give us other people's personal data unless a Mission requires it and you have the right to share it.
4. Why we use your data, and our basis
We use personal data only for the purposes below, and in each case our basis is your consent or, where the DPDP Act allows, a legitimate use such as data you voluntarily give us for a purpose you asked for, or a legal obligation. [Lawyer to confirm which purposes rely on which provision of the DPDP Act and Rules in force at the time of publication.]
| Purpose | Data used | Basis |
|---|---|---|
| Send the newsletter you asked for | Email, lane interest, consent record | Your consent |
| Reply to your message | Name, email, message | Your request |
| Run your account, sign you in, keep you secure | Account details, sessions, hashed IP, logs | Your consent when you create an account |
| Run missions, reviews, levels and Certificates | Profile, claims, Evidence, reviews, Proof Records | Your consent when you join and claim missions |
| Verify a Certificate publicly | Certificate payload (name as you chose) | Your choice at issue; you can withdraw it |
| Assess an application and reply | Application data and resume | Your consent when you apply |
| Send service messages (account, security, moderation, certificate, review events) | Email, event details | Necessary to provide the account you asked for |
| Protect the community: moderation, abuse prevention, integrity checks | Reports, flags, rules, notices, audit log | Your agreement to the Terms and our need to protect members and the Service |
| Keep the Service working, fix errors, prevent attacks | Technical data, logs, rate-limit counters | Needed to keep the Service secure and working: your consent and, where the DPDP Act allows, a legitimate use. The data is kept short-term |
| Meet legal obligations and respond to lawful requests | Whatever the law requires | Legal obligation |
| Improve the Service | Aggregated counts and your feedback | Your consent or aggregated data that does not identify you |
What we do not do. We do not sell or rent personal data, run advertising, build advertising profiles, use your data to train AI models, or make decisions about you by automated means alone. Integrity checks flag possible problems for a person to look at; a person decides what happens.
If we want to use your data for a new purpose, we will ask you first.
5. Consent, age and withdrawing consent
We ask for your consent in plain language, separately for separate purposes, and you can withdraw it as easily as you gave it.
- How we ask. Consent screens for the newsletter, account creation, onboarding, applications and the 18+ confirmation are written plainly and are never part of the satire. Each states what we collect, why, who sees it and how long we keep it.
- Proof of consent. We record what you agreed to, which version of this policy applied, when, and a keyed hash of your IP address. We keep that record so we can show we acted on your choices.
- Age. You must be 18 or older. We ask you to confirm this before an account exists or a subscription is confirmed. See section 16.
- Withdrawing consent. You can unsubscribe with one click from any newsletter, change email and visibility choices in your account, delete your account, or write to contact@larpintech.com. After you withdraw consent we stop the related processing within a reasonable time, normally within [7] days, and delete the data unless the law or section 9 says we must keep it.
- What withdrawal means for features. If you withdraw consent that a feature depends on (for example, your profile data for an account), that feature may stop working. Withdrawing does not affect processing that happened before you withdrew.
- Optional choices. Your profile visibility, how your name appears on Certificates, and whether your reviewer name appears on public records are your choices and you can change them at any time. A change applies to new views; copies others have already made or cached are outside our control.
6. Who we share data with
We share personal data only with service providers who process it for us, with people you choose to share it with, and where the law requires. We do not sell it.
Service providers (processors)
| Provider | What it does for us | Data it handles | Where |
|---|---|---|---|
| Vercel | Hosts the site and runs our server code; delivers pages through a global network | Technical data, requests, cookies, everything that passes through the site | Edge network worldwide; our functions run in Singapore |
| Neon (Postgres) | Stores the database | Accounts, profiles, missions, reviews, records, subscribers, logs | Singapore (AWS ap-southeast-1) |
| Upstash (Redis) | Rate limiting to stop abuse | IP-based counters (short-lived) | [CONFIRM REGION] |
| Resend | Sends email and reports delivery events | Email address, message content, delivery status | [CONFIRM REGION] |
| File storage ([Vercel Blob / other: CONFIRM]) | Stores uploaded Evidence and resumes privately | Uploaded files | [CONFIRM REGION] |
| GitHub (Microsoft) | Sign-in with GitHub; project repositories | GitHub ID, username, display name, avatar, email (if shared) | United States and elsewhere |
| [Domain registrar / DNS provider: CONFIRM] | Domain and DNS | Domain records; no member data | [CONFIRM] |
Providers may change. We will update this table when they do, and tell members about a material change in how their data is handled.
Other people you choose
- Reviewers, maintainers and administrators involved in a Claim can see your Evidence and related notes, as they need to assess it. Administrators can see account details and, by a logged action, a masked email address revealed on request.
- The public, when you or a Project make something public (section 7).
Legal and safety disclosures. We may disclose data to a court, authority or law-enforcement body where the law requires it, to enforce our Terms, or to protect people from serious harm. We will tell you where we are allowed to.
Change of operator. If the Service is transferred to a successor, personal data may be transferred with it, on terms that protect it at least as well as this policy, and we will tell you first.
7. What is public and what is private
Your account and Evidence are private by default, and only the items below can be seen by other people.
| Item | Who can see it |
|---|---|
| Your account email, consent records, sessions | You and administrators (email masked until an administrator reveals it, which is logged) |
| Profile (handle, lanes, skills, level, designation) | You, administrators and, if you set your profile to public, anyone |
| Evidence files and notes | You, the reviewers and maintainers on that Claim, and administrators |
| Reviews you write | The author you reviewed, the project's maintainers and administrators; your reviewer name appears on public records only if you opt in, otherwise a record says it was reviewed by a number of members |
| Reviews of your work | You, the reviewer, maintainers and administrators |
| LARP IT proposals | Members, and public if the proposal is published |
| Proof Records | You and administrators; public only if you choose |
| Certificates | Anyone with the Certificate's public ID or link, by design, so that it can be verified. They show the name you chose (full name, handle only or none), the project, period, issuer and status |
| Application and resume | Administrators and role reviewers only |
| Moderation records | Administrators |
Public items can be copied, indexed or archived by others, and we cannot take back copies that already exist. Choose carefully what you make public. Certificates are designed to remain verifiable, so we keep them, and if you ask us to erase your data we remove your name from them (section 15).
8. Where your data is stored and international transfers
Your data is stored mainly in Singapore and is processed by providers in several countries, and we use only providers who protect it by contract.
- Storage. Our database is hosted in Singapore. Our server code runs in Singapore. Pages are delivered through a global network, so a page may pass through servers near the person who requests it.
- Transfers outside India. Because our database and some providers are outside India, your personal data is transferred outside India. The DPDP Act allows this except to countries the Government of India restricts by notification. We will not knowingly transfer data to a restricted country, and we will review our providers if a restriction is announced. [Lawyer to confirm the position when you publish.]
- Safeguards. We choose providers that use encryption in transit, sign data-processing terms with us, and keep access limited. We send them only what each needs for its task.
- Providers' regions. Our providers' regions are listed in section 6. If we move data to another region we will update this policy.
9. How long we keep data
We keep each kind of data only as long as the purpose needs it, then delete or anonymise it. Where an exact period is in square brackets, it is a default to confirm.
| Data | How long we keep it |
|---|---|
| Newsletter signup that was never confirmed | 7 days |
| Unsubscribed newsletter address | We keep only a one-way hash, so we do not email you again |
| Confirmed newsletter subscriber | Until you unsubscribe or ask us to delete it |
| Consent records | While your data is kept, plus [3 years] to show that we acted on your choices |
| Contact messages | 180 days |
| Account, profile and records | Until you delete your account (then see the next row) |
| After account deletion | Personal data removed promptly, normally immediately and in any case within 30 days; reviews and Proof Records anonymised to "Former contributor"; Certificates remain verifiable with your name removed |
| Evidence you uploaded | While the Claim and any resulting Proof Record exist; deleted on account deletion unless it is part of a published Project artifact |
| Abandoned or expired Claim evidence | 90 days |
| Notifications | 90 days after you read them |
| Email delivery events and the sending queue | 90 days |
| Sessions | 14 days of inactivity (sliding); an administrator session is shorter |
| Rate-limit counters | Minutes to hours |
| Application data and resumes | [90] days after a decision or after the role closes; deleted sooner if you withdraw |
| Moderation cases, actions and reports | 24 months after closure; the reporter's identity is reduced to a hash after closure |
| Removal record (hashed email, reason code, rules) | [24 months] |
| Administrator audit log | 24 months |
| Server and error logs at our host | [Per the host's default period: CONFIRM] |
| Backups | Deleted data may remain in database backups for up to [CONFIRM: the provider's restore window] before they expire |
We may keep data longer where the law requires it, where it is needed to deal with a dispute or an investigation, or in an anonymised form that no longer identifies you.
10. Cookies and similar technologies
We use only the cookies and browser storage the site needs to work, and we do not use advertising or analytics cookies. [Confirm against the live site before publishing.]
| Name or type | Purpose | Lifetime |
|---|---|---|
| Session cookie (__Host-auth_session in production) | Keeps you signed in. It is HTTP-only, secure and not readable by scripts | Up to 14 days of inactivity |
| Sign-in link token | Lets you complete a magic-link sign-in; it is stored as a hash on our side | Short-lived, single use |
| Preference storage in your browser (for example theme or the LARP/REALITY toggle) | Remembers display choices on your device only | Until you clear it |
Because these are strictly necessary or stay on your device, we do not show a cookie banner. If we later add analytics or any other optional cookie, we will ask for your consent first and update this section.
You can block or delete cookies in your browser, but you will not be able to stay signed in. Our hosting provider records basic request data (such as IP address and time) in its server logs, as described in section 3.
We do not respond to "Do Not Track" signals, because we do not track you across other sites.
11. Email communications
We send different kinds of email, and you can stop everything except the messages we need to run your account.
| Category | Examples | Can you opt out? |
|---|---|---|
| Transactional | Sign-in links, account security notices | No. They are needed to give you access |
| Service | Moderation notices, appeal decisions, changes to these documents, review requests, Certificate or badge notices | Not for notices about your account or rights. Others can be reduced in your settings |
| Announcements | New missions, programme updates | Yes, in your settings or with the unsubscribe link |
| Newsletter | The LarpinTech newsletter | Yes, with the unsubscribe link in each issue. Signup uses a confirmation email (double opt-in) |
| Application | Replies about a role you applied for | Not while your application is open; you can withdraw it |
Every newsletter and announcement has a working unsubscribe link, and we honour it promptly. We keep a one-way hash of an unsubscribed address so we do not email you again. We do not sell or rent email addresses, and we do not send marketing from other companies.
Our email provider may record whether a message was delivered, bounced or marked as spam. We use that to keep our sending healthy, and we do not use open tracking pixels or click tracking for newsletters. [Confirm this against the sending configuration.]
Platform notifications (inside LARP OS) are separate from email and follow your notification settings.
12. Applications and resumes
[Draft, review with a legal professional — Updated Phase A6 / AD-APP-8]
If you apply for an open contribution role or position at LarpinTech, we collect and process your information solely to evaluate your fit for that specific role.
- What we collect. Your name, email address, short answer / motivation statement (max 1,500 characters), external links (such as portfolio, GitHub, or publications), and optional resume file, along with internal qualitative notes recorded by reviewers.
- Plain-language consent (BE-PRIV-11). The application form provides explicit, unvarnished disclosure stating what is collected, who has access, and how long records are retained. Application consent is never wrapped in satire or humorous legal fiction. All applicants must affirmatively confirm they are 18 years of age or older.
- Resume storage & security (AD-APP-2). Resumes must be in PDF format only (maximum 5 MB). Uploads undergo MIME validation and binary magic-byte verification (
%PDF-), filename sanitization, and random key generation. Resume files are stored exclusively in private storage buckets or isolated storage folders and are never assigned public URLs or accessible to unauthenticated visitors. - Administrative access & audit logging. Resumes can only be downloaded by authenticated administrators and designated role reviewers. Downloads are delivered strictly as forced attachments (
Content-Disposition: attachment; filename=...) withX-Content-Type-Options: nosniff, and are never rendered inline within browsers. Each download is rate-limited (60 downloads per hour per administrator) and immutably recorded in our system audit log under thepii_accessevent. - No numeric scoring or automated profiling (AD-APP-3). Candidate review is conducted exclusively by human maintainers. Numeric scoring, star ratings, and algorithmic ranking algorithms are strictly prohibited in our pipeline. Reviewers use qualitative notes, thematic tags, and standard status stages (
new,reviewing,shortlisted,accepted,rejected,withdrawn). - Retention schedule (AD-APP-5). Applications and attached resume files are retained for exactly 90 days (
APPLICATION_RETENTION_DAYS) following a final review decision (acceptance or rejection) or following the formal closure of the role. Upon expiration, automated daily retention jobs permanently delete the resume file from private storage and wipe identifying personal fields (name, email, answers, links, notes). A one-way cryptographic SHA-256 hash of the role and email address is retained solely to prevent abusive re-submissions and maintain duplicate detection integrity. - Immediate self-service withdrawal (AD-APP-1, AD-APP-5). Every applicant receives an automated acknowledgment email containing a secure, single-use withdrawal link. Clicking this link immediately triggers complete hard deletion of their resume and personal responses without requiring manual administrator approval or intervention.
- Independent newsletter consent rule (AD-APP-7). Submitting an application will never enroll you in our general newsletter, mailing lists, or marketing communications without a separate, optional, and un-checked opt-in consent checkbox.
- Third-party processors. Resumes are stored on private cloud object storage (AES-256 encryption at rest) and transactional application notifications are routed through our transactional email infrastructure (Resend). We do not share candidate data with external recruiters, advertisers, or data brokers.
If you apply for a role, we use what you send only to consider you for that role.
- What we collect. Your name, contact details, answers, links and resume file, plus the notes and decisions of the people who review it.
- Who sees it. Only administrators and the reviewers for that role. Resumes are stored privately, are never public, and are opened by administrators through short-lived download links.
- No automated decisions. People, not software, decide on applications.
- How long we keep it. For [90] days after a decision or after the role closes, then we delete the resume and answers. We may keep a short record that you applied, so we do not lose track of a decision, but no resume.
- Withdrawing. You can withdraw an application at any time through the link in the confirmation email or by contacting us, and we will delete it promptly.
- Please do not send what we do not ask for. Do not include government ID numbers, bank details, health information, or details about your family or religion. If you include them anyway, we may delete them.
- Staying in touch. We contact you about other roles only if you agree to that when you apply.
13. Moderation, reports and removal records
When we enforce the Community Rules, we keep the records needed to treat people fairly and to explain our decisions.
- What we keep. Reports (including the reporter's identity, which is hidden from the person reported), evidence, internal notes, the actions taken (note, warning, suspension, removal), the rule involved, notices sent to you, and your appeal and its outcome.
- Who sees it. Administrators only. The person reported sees the notice and the rule but not the reporter's identity.
- How long. Cases, actions and reports for 24 months after closure. The reporter's identity is reduced to a hash after closure.
- Removal records. If you are removed, we keep a record with a one-way hash of your email address, the reason code and the rules involved, for [24 months], so a removed account cannot quietly return. We do not publish this record or share it with other organisations unless the law requires it.
- Why we do this. To protect the community from harm, to keep our decisions consistent, and to deal with appeals and disputes. We rely on your consent given at signup and, where the DPDP Act allows, a legitimate use such as responding to a legal claim or protecting people from harm.
- Your choices. You can ask us to correct a mistaken record or to review a decision (see the appeal process in the Terms). Erasure requests do not remove a record we need to establish, exercise or defend a legal claim.
14. How we protect your data
We use reasonable safeguards, but no system is completely secure.
- Encryption. Traffic to the site uses HTTPS, and our providers encrypt stored data.
- Sign-in. We use passwordless email links and Google or GitHub sign-in, so we do not store passwords. Session cookies are HTTP-only and secure, and sign-in tokens are stored as hashes.
- Access control. Administrator tools are separate from member areas, require stronger sign-in for sensitive actions, and every administrator action is recorded in an audit log. Administrators see masked email addresses unless they have a reason to reveal one, and revealing is logged.
- Least privilege. Each provider and person gets only the access they need.
- Rate limiting and abuse controls on sign-in, forms and uploads.
- Private files. Resumes and Evidence are stored privately and opened only through short-lived links.
- Separate environments. We keep testing separate from live member data and do not use real member data for tests.
- Keep your account safe. Protect your email account, do not share sign-in links, and tell us at once if you think someone else has access.
If you find a vulnerability, please follow the security reporting process in our Terms and in security.txt. We will not take action against good-faith research.
15. Your rights and how to use them
You can control your data, and we answer requests within about [30] days.
Under the DPDP Act you have the right to:
- Access a summary of the personal data we process about you and who we have shared it with.
- Correct data that is wrong, and complete data that is incomplete.
- Erase your data when it is no longer needed for its purpose, or when you withdraw consent, unless the law or a legal claim requires us to keep it.
- Withdraw consent at any time. This is as easy as giving it, and it does not affect what we did before. Withdrawing may mean we can no longer give you the service that needed that data.
- Grievance redressal. Raise a complaint with us first (section 20). If you are not satisfied, you may complain to the Data Protection Board of India once it is operating and you have used our grievance process.
- Nominate another person to exercise your rights if you die or cannot act for yourself.
How to use them
- Do it yourself where you can: edit your profile, download or delete your account, and change email settings in LARP OS.
- For anything else, email the address in section 20 from the address on your account, and say what you want.
- We may ask for details to confirm it is you, and we will not ask for more than we need.
- We reply with the outcome, or explain why we cannot do it (for example, a legal duty to keep a record).
There is no charge for ordinary requests. We may decline requests that are repeated without good reason or that would expose another person's data.
16. Children
LarpinTech is for people aged 18 and over, and we do not knowingly collect data from anyone younger.
You must confirm you are 18 or older to create an account, apply for a role or join the newsletter. We do not track or target children, and we do not monitor behaviour for advertising. If we learn that an account or subscription belongs to someone under 18, we will close it and delete the data, except where we must keep something by law.
If you are a parent or guardian and believe a child has given us data, please contact us (section 20) and we will act promptly.
17. If something goes wrong: personal data breaches
If a breach affects your personal data, we will act quickly and tell you.
- We contain the problem, work out what happened, and fix the cause.
- We tell the affected members by email, as soon as we reasonably can, saying what happened, what data was involved, what we have done, and what you can do (for example, change your email password).
- We report the breach to the Data Protection Board of India and to any other authority, in the form and time the law requires.
- We keep a record of each incident and what we changed afterwards.
We cannot promise that no breach will ever happen, but we will be open about it if it does.
18. Visitors from outside India
LarpinTech is run from India, and this policy is written around Indian law.
If you use the site from another country, your data is processed in India and in the countries where our providers operate (section 8). We do not claim to meet the requirements of other countries' privacy laws, such as the EU or UK GDPR or US state laws, and we do not target the site at people there. We still apply the same practices and rights described here to everyone who is 18 or over, and you can use the contact details in section 20 to make a request. If local law gives you more rights, you may have them, but we cannot promise to meet them.
19. Changes to this policy
We will tell you before a material change takes effect.
- We update the version and date at the top of this page and keep earlier versions available on request.
- For material changes, such as a new purpose, a new kind of data, or a new provider that handles your data differently, we email members and post a notice in LARP OS at least [30] days before the change applies.
- If a change needs your consent, we ask for it again, and we do not treat silence as consent.
- Small changes, such as fixing a typo or adding detail without changing practice, take effect when we post them.
20. Contact and Grievance Officer
Write to us for anything in this policy, and we will answer.
| Purpose | Contact |
|---|---|
| Privacy requests and questions | contact@larpintech.com |
| Grievance Officer | Syed Furqhan, contact@larpintech.com |
| Postal address | Hyderabad, Telangana-500061 |
| Response time | Acknowledgement within [48 hours]; resolution within about [30] days |
The Grievance Officer's name and contact details must be real and monitored before this policy is published. If your complaint is not resolved, you may approach the Data Protection Board of India once it is operating.
This policy describes our practices. It is a draft and should be reviewed by a lawyer licensed in India before you publish it.