Privacy Policy
This policy explains the information used to operate the private cohort portal, why it is used, and the choices available to participants.
1. Information we use
- Approved access information: email address, name, cohort, and role.
- Profile and team information: optional headline, bio, profile image, LinkedIn link, team assignment, project name, and project summary.
- Participation information: office-hour availability, bookings, preparation notes, workshop assignments, event resources, and notification status.
- Security records: policy-acceptance date/version, authentication records maintained by our provider, and audited access to club-owned software credentials. The portal records that a credential was revealed, not the credential value in the audit log.
2. Why we use it
We use this information to verify approved users, show role-appropriate portal content, organize teams and mentoring, schedule office hours, deliver event material, notify participants about bookings, protect club-owned resources, investigate misuse, and administer the cohort.
3. Who can see it
Approved participants in the same cohort can see directory names, roles, profiles, teams, mentors, events, and relevant availability. Builders and mentors involved in a booking can see its details. Portal administrators can manage the underlying records. Approved email addresses and club-owned credential values are not included in the cohort directory.
4. Service providers
The portal uses Supabase for authentication, database hosting, access controls, and server-side functions. The public website is hosted through the Club’s web-hosting provider. An email-delivery provider may be used for verification codes and booking notifications. These providers process information to supply their services and under their own applicable terms and privacy commitments.
5. Retention
We keep active portal and booking data for the cohort and a reasonable administration period afterward. Security and consent records may be kept longer when needed to document access, address incidents, or meet obligations. The Club should set and document a final deletion schedule before launch.
6. Security
We use emailed one-time codes, an approved-email list, row-level database rules, policy-version checks, time-limited software entitlements, and access logging. No internet service can guarantee absolute security. Do not share verification codes or club-owned credentials, and report suspected exposure promptly.
7. Your choices and requests
You can ask to review, correct, or delete profile information, subject to records the Club needs to retain. You may decline the policies, but the portal cannot provide access without the required acceptance. To make a privacy request or raise a concern, email ethanorjoseph@gmail.com.
8. Updates
If this policy changes, its version and effective date will change. When the database marks a new version as current, signed-in users must acknowledge it before seeing protected cohort information.