1. Who we are and what these Terms cover
LarpinTech is an experimental technology community that presents itself as a satirical corporate company, and its work is real: members take missions, build projects, publish research and get their work reviewed. 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, operates the website at www.larpintech.com and the member portal called LARP OS (together, the "Service"). "We", "us" and "LarpinTech" mean that operator.
These Terms are an agreement between you and us. They apply when you visit the site, subscribe to the newsletter, contact us, apply for a role, create an account, take missions, submit evidence, review other members' work, or verify a certificate. If you do not agree with them, do not use the Service.
These Terms work together with:
- the Privacy Policy, which explains how we handle personal data;
- the Community Code of Conduct, which sets the rules for behaviour;
- the Satire Disclaimer, which explains what is parody and what is real.
If two of these documents seem to conflict on a topic, the more specific one governs that topic.
Words we use
| Term | Meaning |
|---|---|
| Member | A person with a LARP OS account. |
| Mission | A scoped task published on a Project, with deliverables and evidence requirements. |
| Claim | A Member's commitment to work on a Mission. |
| Evidence | Files, links and notes a Member submits to show completed work. |
| Review | A peer assessment of a Claim by another Member. |
| Proof Record | A record of verified work created after a Claim is accepted. |
| Certificate | A signed record issued by LarpinTech that refers to one or more Proof Records. |
| Content | Anything you submit: profile text, Evidence, proposals, reviews, messages, applications. |
| Project | A community project, with its own maintainers and, often, its own open-source repository. |
2. Satire and reality
LarpinTech is not a funded company, a registered employer or a licensed professional body, and anything on the Service that sounds like one is a joke unless we say otherwise. The corporate theatre is the entry point; the engineering, research and review that follow are real.
So that nobody is misled:
- Parody content is parody. Product names such as "LarpPay", fundraising claims such as a "Series A", valuations, press-style announcements, departments and titles are fictional. Where a page or project shows a satirical view, it also offers a Reality view that says what was actually built.
- Designations are fictional. A title such as "The Chief Instigator" or a department name is a role-play device. It is not a job title, not employment, and not evidence of qualifications.
- No employment or engagement. Taking a Mission or holding a title does not make you our employee, contractor, intern, agent or partner. We do not pay for missions, and nothing in the Service promises payment, equity, a future job or a reference.
- No financial or professional claims. Nothing on the Service is investment, legal, medical, engineering-safety or professional advice, and no fictional company should be treated as a real business.
- Real facts are real. When we state a real fact (a repository link, a published paper, a verifiable Certificate), it is meant to be accurate, and you can tell us if it is not.
You must not use our satire to deceive other people. For example, you must not present a fictional LarpinTech title, fundraising claim or product as real to a client, employer, investor, school or the public, and you must not strip the context from a screenshot to make a parody look like a genuine statement.
3. Accepting these Terms and who may use the Service
You accept these Terms when you create an account, tick the box that says you agree, or otherwise use the Service beyond reading public pages. Reading public pages, verifying a Certificate and reading published research do not require an account.
You must be at least 18 years old to create an account, subscribe to the newsletter, apply for a role or submit Content. We ask you to confirm this before an account exists. We may ask for more proof if we have reason to doubt it, and we will close accounts that we find belong to someone under 18.
You also confirm that:
- you have the legal capacity to enter into a contract under Indian law, or the equivalent law where you live;
- you are not barred from using the Service under any law that applies to you;
- the information you give us is accurate and you will keep it up to date; and
- if you act for an organisation, you are authorised to bind it.
We may refuse or end access to anyone who breaks these Terms or the Code of Conduct, as described in section 12.
4. Accounts and sign-in
You are responsible for everything done through your account, so keep your sign-in methods secure and tell us promptly if you suspect misuse.
- Sign-in methods. You can sign in with GitHub or with an email link. We store only a verified primary email address and the profile details you choose to provide. We do not receive your GitHub password.
- One person, one account. Do not create several accounts, share an account, sell or transfer an account, or sign in as someone else. Using several accounts to review your own work or to get around a suspension is a serious breach (see sections 6 and 12).
- Accurate profile. Do not impersonate another person, misstate your skills or experience, or present someone else's work as yours.
- Security. If you use GitHub to sign in, use a strong password and two-factor authentication on that GitHub account. Sign out on shared devices. You can sign out of every device from your account page.
- Inactive and deleted accounts. You can delete your account at any time from your account page. How we handle your data when you do is described in the Privacy Policy. We may close accounts that have been inactive for a long time after giving notice to the email on file.
- Admin access. A small number of people administer the Service. They are bound by the same rules, and their actions on member data are logged.
5. Community rules and prohibited conduct
Treat other people with respect and use the Service for its purpose: making and reviewing real work. The full rules are in the Community Code of Conduct; this section lists what is never allowed.
You must not:
- harass, threaten, demean or discriminate against anyone, including on grounds of caste, religion, gender, sexuality, disability, nationality, age or appearance;
- post or share another person's private information (including addresses, phone numbers, government IDs, private messages or photographs) without their consent;
- upload malware, exploit code aimed at third parties, or anything designed to damage systems, or use the Service to attack others;
- post unlawful content, including content that infringes copyright, defames a person, incites violence, sexualises minors, or violates any law that applies to you;
- submit work you did not do, copy others' work without credit or licence, or use generated content in a way that misrepresents who made it or how (see section 6);
- spam members or subscribers, send unsolicited promotions, or use member data for purposes other than the community's work;
- scrape the Service at scale, bypass rate limits, probe for vulnerabilities, overload the Service, or access accounts, files or admin areas you are not authorised to use;
- interfere with moderation, evade a suspension, or retaliate against someone who reported a problem;
- use the Service for gambling, fundraising scams, pyramid schemes, or the sale of regulated goods.
Security research. If you find a vulnerability, please tell us at contact@larpintech.com and give us a reasonable time to fix it before you disclose it. Do not access data that is not yours, do not disrupt the Service, and stop once you have shown the problem exists. We will not take action against good-faith research that follows these limits.
6. Missions, claims, evidence and peer review
Missions are voluntary, unpaid and only worth something if the work and the reviews are honest. These rules protect that.
Taking missions
- A Mission lists its objective, difficulty, deliverables and the evidence needed. You may claim a Mission if your level and the open slots allow it. Limits on active claims, and deadlines for finishing them, are shown in the portal and may change.
- You may abandon a Claim at any time. Claims that pass their deadline may expire so that others can take the Mission.
- Missions are published by project maintainers. We do not guarantee that any Mission will be available, finished, reviewed by a particular date, or accepted.
Submitting evidence
- Evidence must show work you actually did. It may be a link to a repository or pull request, a document, an image, a dataset, logs or a short explanation. Allowed file types and size limits are shown in the portal.
- Say honestly how you did the work. If you used AI tools, other people's code, templates or data, say so where the Mission asks you to and credit and licence them properly.
- Do not fabricate results, edit data to fit a conclusion, falsify logs, or submit work copied from others. Doing so may lead to rejection, revocation of Proof Records or Certificates, and moderation action.
- Do not upload anything you have no right to share, anything confidential belonging to someone else, or personal data about other people.
Peer review
- Reviewers must be independent. You may not review your own Claim, a Claim by someone you collaborate with on the same work, or a Claim in exchange for a favour.
- Review honestly and on the criteria given. Do not approve work you have not examined, trade approvals with other members, or reject work for reasons unrelated to its quality.
- Reviewers may receive credit toward their own progression, but review decisions are not paid and are not a measure of a person's worth.
- Review notes are visible to the author. Whether your reviewer name appears on public records depends on your choice in the portal.
Integrity checks. We may use automated and manual checks to detect self-review, reciprocal approvals, duplicate claims, plagiarism and other gaming. If you are flagged you can respond, and moderation follows section 12.
7. Levels, designations, Certificates and badges
LarpinTech recognition is a record of work done in an unaccredited community. It is not a degree, licence, professional certification or employment reference, and you must not present it as one.
Levels. Your LARP level (from 0 to 5) reflects verified work and reviews under rules we publish and may change over time. Levels are not points, are not ranked against other members, and are not revoked automatically. Levels 4 and 5 are awarded at our discretion.
Proof Records. When a Claim is accepted we create a Proof Record describing the work, the project, the difficulty and the review outcome. You control whether it is shown on your public profile.
Certificates.
- A Certificate is issued to a Member by a project lead, maintainer or administrator who is not that Member, and refers to one or more Proof Records.
- It carries a random public ID and is digitally signed. Anyone can check it at the verification page or with the public keys we publish. Verification tells you that LarpinTech issued the record and that it has not been altered since. It does not tell you that the holder is skilled, honest or qualified.
- Every verification page shows that LarpinTech is an unaccredited community and that the Certificate is not an academic or professional qualification. Do not remove or hide this wording when you share it.
- You choose whether your Certificate shows your full name, your handle only, or no name.
- We may revoke a Certificate for fraud, for errors in the underlying Proof Record, or for serious breaches of these Terms. A revoked Certificate stays visible as revoked, with the date. You may withdraw your own Certificate at any time; it will then show as withdrawn by the holder.
- Certificates are not deleted, because they have to remain verifiable. If you ask us to erase your personal data, your name is removed from the record and it shows as issued to a former contributor, as described in the Privacy Policy.
Badges. A badge is a short recognition for a specific contribution, always linked to the work that earned it. Badges carry no points and no rank, and we may remove a badge that was awarded in error or obtained dishonestly.
Designations. Fictional titles and departments are part of the satire (section 2). They have no legal or professional meaning.
Digital merchandise. Any digital or physical merchandise we offer is a keepsake, has no cash value, and is not a financial product.
8. Your content and the licence you give us
You keep ownership of the Content you create, and you give us only the permissions we need to run the Service.
Ownership. We do not claim ownership of your Content, including your Evidence, proposals, reviews and profile text.
Licence to us. For Content you submit, you grant us a non-exclusive, worldwide, royalty-free licence to host, store, copy, process, display and transmit it, and to adapt it technically (for example, resizing images or converting formats), for the purpose of operating, securing and improving the Service and showing it to the people you or the Service's rules allow. This licence lasts while your Content is on the Service and for the limited time it takes to remove it from backups and from records we must keep, as described in the Privacy Policy.
Who sees what. Evidence files are visible to the reviewers, maintainers and administrators involved in the Claim. Your profile and records are private unless you choose to make them public. Items that you or a project mark as public (such as a published paper or a public Proof Record) can be viewed by anyone and may be copied by others, which we cannot prevent.
Code and project work. Code and documents contributed to a Project's repository are governed by that repository's licence, which applies to your contribution and overrides the licence in this section for that material. Check a Project's licence file before you contribute.
Your promises. You confirm that you own your Content or have the right to share it, that it does not infringe anyone's rights or break the law, that it does not contain malicious code, and that it does not contain other people's personal data unless the law and the Mission allow it.
Reviews and records after you leave. If you delete your account, reviews you wrote and Proof Records tied to accepted work are anonymised rather than deleted, so that the people whose work they concern keep a complete record. Content that is part of a published Project artifact stays with the Project, with your attribution removed if you ask.
Feedback. If you give us suggestions, you allow us to use them without obligation to you.
Removal and copyright complaints. We may remove Content that breaks these Terms or the law. If you believe Content on the Service infringes your copyright, write to contact@larpintech.com with a description of the work, where to find the material, your contact details and a statement that you are the owner or authorised to act. We will respond and, where appropriate, remove the material and tell the person who posted it.
9. LARP IT proposals, projects and open source
A proposal you share is an invitation to the community to consider it, not a secret or a sale. Please do not submit anything confidential, anything you have promised to someone else, or an idea you are not comfortable others building.
- Proposals. A LARP IT proposal describes a problem, a tongue-in-cheek premise and a way it could really be built. By submitting it you allow us and other Members to read, discuss, and, if you mark it as open to contributors, to work on it. You keep your own rights in your text, but you cannot stop others from independently building something similar, and we do not promise credit, payment or a decision. Maintainers may triage, edit for clarity, merge, hide or decline proposals.
- Projects. Each Project has its own maintainers, repository and licence. Maintainers decide what missions the Project publishes and what work it accepts. We do not own the Projects' code unless its licence says so.
- Open source. When you contribute to a Project's repository you are also bound by that repository's licence, contribution guide and code of conduct, and by GitHub's own terms. Do not contribute code or assets that you cannot license under those terms.
- Credit. We try to credit contributors accurately. If you think an attribution is wrong, tell us and we will correct it where the facts support it.
- No exclusivity. Nothing here stops you from working on other projects or from using your own contributions elsewhere, subject to the licence you chose for them.
10. Experiments, research ethics, hardware and safety
What you build, test or run is your responsibility, and some of it can hurt people or things if done carelessly. Follow these rules.
Research and experiments
- Experiments in our labs follow stages, and an experiment that involves people needs an ethics checklist approved by a maintainer or administrator before any data is collected. Do not collect data from people without that approval, their informed consent and a lawful basis under the law that applies to them.
- Do not run experiments on people who have not agreed, on minors, or on systems you do not own or have no written permission to test.
- Report results honestly, including failures. Our Failure Archive exists because negative results are useful.
- Published research may be marked as satire or real. A "satire" label means the piece is a parody that may contain invented claims; do not cite it as evidence.
Hardware, electronics and firmware
- Projects may involve microcontrollers, sensors, batteries, mains-powered equipment, soldering and radio transmitters. These carry real risks: electric shock, fire, burns, battery failure, eye injury and interference with other devices.
- Schematics, bills of materials, firmware and instructions on the Service are shared for education. We do not test them against safety, regulatory or electromagnetic compliance standards, and we do not promise they are complete or correct.
- You build, power and use anything at your own risk. Work with proper protective equipment, never connect experimental circuits directly to mains power unless you are qualified, follow the rules for radio equipment where you live, and do not use anything from the Service in a medical, automotive, aviation, life-safety or other critical setting.
- Keep minors and pets away from hazardous components.
Software and security
- Test only on systems you own or are authorised to test. Do not publish working exploits for unpatched vulnerabilities in third-party products.
- Do not run code from the Service in production without reading and testing it first.
11. Open roles, applications and newsletters
Applying for a role or subscribing to the newsletter is voluntary, and each has its own limits.
Open roles and applications
- An "open role" is a volunteer contribution position in the community. It is not a job, internship or paid engagement unless a role's description says otherwise in writing.
- Information you send in an application (including a resume) is used to assess your application, to reply to you, and nothing else. The Privacy Policy explains who can see it and how long we keep it.
- Put only accurate information in your application. Do not send documents containing other people's data or government ID numbers, bank details or health information.
- We may decline an application for any reason and do not have to explain. Submitting an application does not create any right to a role or to a reply by a particular date.
- You can withdraw an application, and have your data deleted, using the link in your acknowledgment email or by writing to us.
Newsletter and announcements
- To get the newsletter you confirm your email address through a link we send you and confirm that you are 18 or over. You can unsubscribe at any time using the link in every email; it takes effect immediately.
- We send service messages (such as account, security, moderation or certificate notices) to members even if they have unsubscribed from the newsletter, because they relate to the account. We keep these to what is necessary.
- We do not sell or rent email addresses and do not use open or click tracking in our emails.
- Newsletter content is for information and may include satire. Do not rely on it as advice.
12. Moderation, suspension, removal and appeals
We act on rule-breaking by following a process: a rule is named, you are told, and you can appeal. We may act sooner, and tell you afterwards, where there is a risk to people's safety, to the security of the Service or to the law.
What we may do. Depending on the seriousness and your history, we may add a private note to your record, issue a warning, hide or remove Content, pause or suspend your account for a set time or indefinitely, revoke a Certificate, badge or Proof Record that was obtained improperly, or remove your account permanently.
How it works
- Every action cites at least one rule from the Code of Conduct or these Terms.
- Where we can, we send you a notice by email that states the action, the rule, when it takes effect and how to appeal. We may hold back or delay a notice only for safety, legal or investigation reasons.
- While suspended or removed you cannot sign in or take part in Missions or reviews. Open Claims may be released or extended, and reviews waiting on you may be reassigned.
- Anyone can report a problem. We protect the identity of people who report in good faith and do not tell the person reported who made the report.
Appeals. Reply to the notice or write to contact@larpintech.com within [30] days. Appeals are decided by a person other than the one who made the original decision where we have more than one administrator, and we aim to answer within [14] days. If we overturn the action, we will restore your access and tell you.
Records we keep after removal. If we remove an account for a rule violation, we keep a small record: a one-way hash of your email address, the reason code, the rules concerned and the date. We keep it for [24 months] to prevent a removed account from being recreated. The Privacy Policy explains this. It is separate from, and does not replace, your right to ask us to erase other personal data.
Ending your membership yourself. You can leave at any time by deleting your account, subject to section 8 and the Privacy Policy.
We may end the whole Service, or part of it, at any time. We will try to give notice and a way to export your data first.
13. Our intellectual property, brand and press use
The LarpinTech name, logo, design and original site content belong to us, and you may use them only as these Terms allow.
- Ours. The name "LarpinTech", the "L" mark and wordmark, the site's design and text, and original illustrations and code written for the site belong to Syed Omer or its licensors. Code and content that a Project publishes under an open licence is licensed under that licence.
- Your limited right to use the Service. We give you a personal, non-exclusive, non-transferable, revocable right to use the Service for its intended purpose while you follow these Terms.
- Press and community use. You may use the logo and name from our press page to refer to LarpinTech accurately, for example in news coverage, a profile or a CV line that describes your real contributions. Do not alter the logo, imply endorsement or partnership we have not agreed, or use the name in a way that suggests a fictional title or claim is real.
- Looking like us. Do not register or use a name, domain, social handle or logo that is confusingly similar to ours, or make a site or app that imitates ours.
- Third-party marks. Names and logos of other products belong to their owners. Their appearance on the Service, including in satire, does not imply any relationship.
14. Third-party services and links
The Service depends on other companies' services, and their terms apply to you when you use them.
- Services we use. We rely on providers for hosting and delivery, database storage, rate limiting, email delivery, file storage and sign-in with GitHub. The Privacy Policy lists them. Your use of GitHub (including contributing to repositories there) is governed by GitHub's own terms and privacy statement.
- Links. The Service links to external sites, repositories and papers. We do not control them, are not responsible for their content or practices, and a link is not an endorsement.
- Outages beyond our control. If a provider fails or changes its terms, the Service may be interrupted or changed.
15. Availability, experimental features and changes to the Service
The Service is a student-run experiment, so it may be slow, unavailable or changed without much notice.
- Best effort. We try to keep the Service running, but we do not promise it will be uninterrupted, error-free, secure or available at any given time. We may take it down for maintenance or because of an incident.
- Experimental features. LARP OS, missions, levels and Certificates are evolving. Rules, limits, levels and features may change, and a feature may be removed. We will avoid changing the rules for work already in progress without notice where we reasonably can.
- Free service. The Service is currently free. If we ever charge for anything, we will say so clearly before you pay and will not charge you for existing features without your agreement.
- Your data. You can export your data from your account page. Keep your own copy of work that matters to you, because we cannot guarantee that Content will never be lost.
16. Disclaimers
The Service is provided "as is" and "as available", and we make no promises beyond those in these Terms, to the extent the law allows.
In particular, we do not promise that:
- the Service, or any Mission, Project, instruction, schematic, code or research on it, will be accurate, complete, safe, secure, error-free or fit for a particular purpose;
- any Content posted by Members or Projects is true, lawful or reliable, because we do not check all of it in advance and Members are responsible for what they post;
- any Proof Record, level, badge or Certificate will be recognised by an employer, school, client or authority, or will help your career or admission;
- you will be accepted for a role, a Mission, a review, a level or a Certificate;
- the Service will be free of viruses or other harmful components, though we take reasonable care.
Satire is satire (section 2). Nothing on the Service is professional, legal, financial, medical or safety advice.
This section does not exclude or limit anything that cannot lawfully be excluded or limited.
17. Limitation of liability
Because the Service is free and run by volunteers, our liability to you is limited, to the extent the law allows.
- We are not liable for indirect, incidental, special or consequential losses, or for loss of profit, revenue, data, goodwill, opportunity or reputation, arising from your use of the Service, even if we were told it was possible.
- We are not liable for the acts or omissions of Members, Projects, reviewers or third parties, including what they post or build, or for any injury, damage or loss caused by following instructions, building hardware or running code obtained through the Service.
- Our total liability to you for all claims relating to the Service is limited to [INR 1,000 / the amount you paid us in the last 12 months, whichever is greater: owner and lawyer to confirm the figure].
Nothing in these Terms limits liability for fraud or fraudulent misrepresentation, for death or personal injury caused by our negligence where the law does not allow that to be limited, or for anything else that cannot lawfully be limited.
18. Indemnity
If your breach of these Terms or your Content causes us a third-party claim, you agree to cover our reasonable losses from that claim, to the extent the law allows. This covers, for example, a claim that content you uploaded infringes someone's copyright or that you misused another person's data. We will tell you about the claim promptly, let you help with the defence where that is reasonable, and not settle in a way that admits liability on your behalf without asking you. This section does not apply to the extent a claim results from our own breach or negligence.
19. Governing law and disputes
Indian law governs these Terms, and we would like to settle any problem with you directly first.
- Talk first. Write to us at contact@larpintech.com with a description of the problem. We will try in good faith to resolve it within [30] days.
- Law. These Terms and any dispute arising from them are governed by the laws of India, without regard to conflict-of-law rules.
- Courts. Subject to the above, the courts at [Hyderabad, Telangana: owner and lawyer to confirm] have exclusive jurisdiction, except that either of us may ask any competent court for urgent protective relief.
- Arbitration (optional). [If the owner prefers arbitration: disputes will be referred to a sole arbitrator under the Arbitration and Conciliation Act, 1996, seated in Hyderabad, in English. Delete this bullet if courts are preferred.]
- If you use the Service from outside India, you are responsible for complying with your local laws, and nothing in these Terms removes any mandatory rights you have under the law where you live.
20. Changes to these Terms
We may update these Terms as the Service changes, and we will tell you before material changes take effect. The version number and effective date at the top show the current version. For material changes, such as new restrictions, a change to your rights or a new use of your Content, we will give Members at least [30] days' notice by email and a notice in the portal, and we will keep earlier versions available on request. Small changes, such as fixing typos or clarifying wording, may take effect when posted. If you do not accept a change, you can stop using the Service and delete your account before it takes effect. Using the Service after it takes effect means you accept the new Terms.
21. General provisions
- Whole agreement. These Terms, with the documents they refer to, are the entire agreement between you and us about the Service.
- If part is invalid. If a court finds part of these Terms unenforceable, the rest stays in force and the part will be read to give effect to its purpose as far as the law allows.
- No waiver. If we do not enforce a right straight away, we have not given it up.
- Assignment. You may not transfer your rights under these Terms. We may transfer ours to a successor of the Service, and we will tell you if we do.
- Events beyond our control. We are not responsible for delay or failure caused by events outside our reasonable control, such as outages of providers, power or network failures, or changes in the law.
- No third-party rights. Only you and we may enforce these Terms, except where a Project's licence says otherwise.
- Language. These Terms are written in English. A translation is for convenience only.
- Survival. Sections that by their nature should continue after you stop using the Service (including ownership, licences needed for records we must keep, disclaimers, liability, governing law) will continue.
22. Contact, grievance officer and legal notices
Write to us about anything in these Terms using the contacts below.
| Purpose | Contact |
|---|---|
| General and legal questions | contact@larpintech.com |
| Complaints and grievances (Grievance Officer under India's IT rules) | Syed Furqhan, contact@larpintech.com, Hyderabad, Telangana-500061 |
| Appeals of moderation decisions | contact@larpintech.com |
| Copyright complaints | contact@larpintech.com |
| Security reports | contact@larpintech.com |
| Privacy and data requests | See the Privacy Policy |
We aim to acknowledge complaints within [48 hours] and to resolve them within [30 days] or the period the law requires, whichever is shorter. Formal notices to you will be sent to the email address on your account. Formal notices to us must be sent to the address above and, where you want a record of delivery, by post to Hyderabad, Telangana-500061.