Trust, security & privacy
This page is maintained by the CollegeBugs team to answer common security and privacy questions about the platform. It describes app-visible controls and current practices. It is editable content and is not an independent certification or audit.
Access & authentication
Sign-in is handled through email/password and Google, with sessions managed by our backend provider. Each user only sees and can act on their own data, enforced by row-level security in the database.
Administrative tools are restricted to verified admin roles tracked in a server-side roles table. Role checks happen on the server, not in the browser.
Data collection & use
We store the information you create in the app — your profile, notes, assignments, certificates, generated PPTs, projects, and career-network posts — so the product works for you. We do not sell personal data.
Profile, post, and project visibility settings (public, followers-only, private) are enforced in the database, not only in the UI.
Platform & hosting
CollegeBugs runs on Lovable Cloud (Supabase + edge runtime). Data is stored in a managed Postgres database with row-level security. Service credentials remain server-side and are never shipped to the browser.
Real-time chat channels are scoped to verified members of each conversation.
Subprocessors & integrations
We use third-party services to deliver core features: Lovable AI Gateway for AI generation, Razorpay for payments, LiveKit for live calls, and image-search APIs for educational imagery. Each call to those services is initiated by your action in the product.
Retention & deletion
You can delete content you created (posts, projects, notes, certificates, PPTs) from the app. To request full account and data deletion, contact us at the address below.
Security & privacy contact
To report a vulnerability or ask a privacy question, email codenest9861@gmail.com. We acknowledge reports and work with the reporter on a fix.
This page reflects the platform's current configuration and is updated as the product evolves. For background on the underlying platform's security features, see the Lovable security documentation.