Privacy Policy

Version 2026-10. Effective 21 October 2026.

The short version

You do not need an account to use this website. Students join our community through our Meetup group.
Only the core team and the group leader (SBGL) sign in. For them we keep a name, email, course, semester, picture and the links they choose to add.
We never sell data, show ads, or track you across the web.
You can ask us to correct or delete your data at any time.

1. Who we are

This website is run by student volunteers of the AWS Student Builder Group at Doon University (“we”, “us”, “the Group”). The Group leader (SBGL) decides how data is used and is your point of contact for anything in this policy.

We follow the principles of the Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000: collect little, use it only for the stated purpose, keep it safe, and let people control it.

2. Who has an account

Visitors and students do not create accounts. To join the community you use our Meetup group, which is run by Meetup under its own policy. Accounts exist only for the core team members and the SBGL, who sign in with Google. A Google account that is not on the team list cannot create an account here.

3. What we collect

Data	Why we need it	Who can see it
Email address (team accounts)	Sign in, security, contact	The person and SBGL admins
Full name	Show on the team page and in comments	Public
Profile picture	Shown on the team page and in comments	Public
Course (B.Tech, B.Sc CS, M.Sc CS, M.Tech CSE) and semester (1 to 8)	Understand who runs the group	The person and SBGL admins
LinkedIn link, GitHub link, website link and bio (all optional)	Show on the team profile	Public
Serial number (SBGDU followed by two digits), role tag and designation	Let people verify a team member	Public
Comments written by team accounts	Discussion under articles	Public
Consent record (the time terms were accepted)	Prove agreement	The person and SBGL admins
Contact form messages (name, email, message)	Reply to you	SBGL admins
Technical logs: IP address, browser, pages requested, time	Security and debugging	Our hosting providers

4. What we do not collect

Anything from students who only visit the website or join our Meetup group, apart from what a normal web request contains.
Phone numbers, home addresses, government ID or enrollment numbers, or payment details.
Advertising identifiers. We run no analytics trackers and no advertising cookies.

5. How we use data

To sign team members in and show their public profile.
To publish events, articles and photos, and to answer messages.
To protect the site from abuse.
We do not sell, rent or trade personal data, and no decision about you is made by automated means alone.

6. Signing in with Google

Team accounts sign in with Google using only the basic scopes openid, email and profile. We receive the name, email address and profile picture of the Google account. We never receive the Google password, contacts, Gmail, Drive or any other Google data.

We use this information only to sign the person in and pre-fill their profile. We do not share it except with the providers below that run this website, and we do not use it for advertising. Our use of information received from Google follows the Google API Services User Data Policy, including its Limited Use requirements.

7. Services that handle data

We rely on these providers. Each acts on our instructions and has its own privacy policy.

Supabase
Database, sign-in and file storage. Holds team accounts, profiles, comments, contact messages and uploaded images.

Vercel
Hosting. Serves the website and keeps request logs, which include IP addresses.

Google
Sign-in for team accounts, as described above.

Meetup
Where students join the community and RSVP. We never receive your Meetup data.

LinkedIn
We link to our company page and to profile links team members add. Following them takes you to LinkedIn, which has its own policy.

GitHub
We display GitHub profile links team members add. Following them takes you to GitHub.

8. Cookies and storage

We use only the essential cookies that keep team members signed in, and a small setting in your browser that remembers light or dark mode. There are no analytics, advertising or tracking cookies.

9. How long we keep data

Team account data: while the person holds a team seat. When someone leaves the team we remove their account and uploaded pictures within 30 days of being asked or of their seat being vacated.
Contact messages: until we have replied, then deleted within 12 months.
Encrypted backups may take up to 90 days to expire. Hosting logs follow Vercel’s and Supabase’s own retention rules.

10. Your rights

You may access your data, correct it (team members can edit their own profile), ask for it to be erased, withdraw consent, and make a grievance. You may also nominate someone to exercise these rights for you if you cannot.

To use any of these rights write to us through the Contact page and mark the message for the SBGL. We reply within 30 days. If you are not satisfied you may complain to the Data Protection Board of India as the Act provides.

11. How we keep data safe

Everything travels over HTTPS.
Every table is protected by row-level security, so one account can never read or change another account’s private data. Admin powers are checked on the server and in the database, never only in your browser.
Image uploads are limited to PNG, JPEG and WebP and are checked by content, not just by file name.
Comments and verification lookups are rate limited, and the site sends strict security headers.
No system is perfectly secure. If a breach affects you we will tell you and the authorities as the law requires.

12. Where data is processed

Our providers may process data on servers outside India under their own safeguards.

13. Changes and contact

If we change this policy in a meaningful way we will update the date above.

Questions or requests: use the Contact page and address it to the SBGL of the AWS Student Builder Group at Doon University.