Scope
This policy covers the uplb.tools organization hub (this website) and describes practices common across our volunteer projects — including Room TBA, Elbi GradeSim, and other tools linked from our GitHub organization. Individual apps may publish more specific policies on their own domains; where they differ, the app-specific page controls for that product.
What we build
We create free campus utilities for UPLB students: maps, schedule tools, browser extensions, and related open-source software. Most tools are maintained by volunteers in their spare time. Data quality depends on community contributions and may be incomplete or out of date.
Information we may process
Using this hub site
- Hosting logs. Vercel and our infrastructure providers may log request metadata (IP address, user agent, timestamps) for security and reliability.
- Analytics. We may use privacy-focused web analytics (for example Vercel Analytics) on public pages to understand traffic patterns. We do not intentionally collect student numbers or legal names through analytics.
Using linked tools (general patterns)
- Browsing without an account. Many tools work without sign-in. They may store preferences locally in your browser (recent searches, term selection, offline caches) and use analytics similar to this hub.
- Contributors and editors. Tools with edit flows (for example Room TBA) may store usernames, hashed passwords, roles, and audit metadata for proposals and published changes. Sessions typically use httpOnly cookies scoped to that app.
- Class and campus data. Schedule and map data come from public or volunteer-curated sources. We do not import or store instructor names in our public databases where sanitization policies apply.
- Browser extensions. Extensions like GradeSim run in your browser and interact with third-party campus portals under their own terms. Extension permissions are described in each store listing and repository README.
Community channels
- GitHub. Contributions, issues, and pull requests are public on GitHub under GitHub's privacy policy.
- Discord. Our Discord server is governed by Discord's terms and privacy policy. Messages you post there are handled by Discord.
How we use data
- Operate, secure, and improve our tools.
- Debug outages and abuse.
- Attribute edits and proposals to contributor accounts where applicable.
We do not sell personal data.
Data retention
Campus entity data is kept while a tool remains useful to students. Contributor accounts and audit history may be retained for integrity and moderation. You may request account-related questions through our community channels; complete erasure may be limited where records are needed for abuse prevention or edit attribution.
Third-party services
Our stack commonly includes Vercel (hosting), Supabase or similar Postgres providers (application data), Cloudflare (assets/CDN where configured), Mapbox or MapTiler (maps), and GitHub (source). Each provider processes data under its own policy.
Children
Our tools are intended for university students and volunteers. We do not knowingly collect data from children under 13.
Changes
We may update this policy. Material changes will be reflected by the "Last updated" date above.
Contact
Questions? Open a discussion on GitHub or reach volunteers through our Discord.