Privacy
Privacy notice.
What LOOM collects, why it is collected, who can see it, and how to request deletion.
Who operates this service
This service is operated by the operator of this LOOM deployment. Privacy questions can be sent to Chapter operations through the contact page. This page describes how the service handles data; it is not legal advice.
Data members provide
- Account identity: name, college email address, and the sign-in identity managed by the chapter's authentication provider (Auth0, or the legacy Supabase Auth fallback where enabled).
- Chapter profile: roll number, branch, year, enrollment details where requested, and selected domains.
- Public identity, when created: username, biography, GitHub handle, skills, endorsements, and profile links.
- Learning and contribution records: roadmap and resource progress, projects, contests, mentorship applications and sessions, forums, wiki contributions, snippets, events, credentials, achievements, and reports.
Data generated by using the service
- Authentication sessions and account-security events.
- In-app notifications about activity that concerns the member.
- Administrative audit records identifying the actor, action, affected resource, and time.
- Aggregated activity, analytics, cohort, ranking, and federation metrics used to operate chapters.
Why the data is used
- Provide accounts, chapter membership, roadmaps, resources, events, mentorship, and proof.
- Attribute work to the correct member and verify credentials or contributions.
- Operate moderation, safety, finance, reporting, handover, and audit functions.
- Measure chapter health and improve learning paths without fabricating activity.
Who can see it
- Members can see their own records.
- Chapter members, leads, mentors, and administrators can see operational records permitted by their role.
- Information becomes public only when a card, profile, credential link, chapter card, or other item is explicitly made public or shared.
- Private chapter data is not made public by default.
Retention and deletion
Operational records are retained for as long as the chapter needs it to operate the service, after which it is deleted or anonymized when a deletion request is completed. Full account deletion is currently handled manually by a chapter administrator and is audited. To request export or deletion, contact Chapter operations through the contact page. Audit history may retain a non-content record where the chapter is legally required to preserve an administrative trail.
Security
Access is scoped by authenticated session, chapter membership, role, and server-side tenant checks. No internet service can guarantee absolute security, but suspected misuse can be reported for administrative and audit review.
Changes
If this notice changes materially, the chapter will publish the updated date and policy here. Continued use after publication means the member accepts the updated notice.