Privacy

What we collect

• Your GitHub username, display name, avatar and email address, from signing in with GitHub.
• Your progress: modules started and completed, steps done, resource ratings, and the public handle on your portfolio.
• For each project you connect: the repository name, the GitHub App installation, and the result of each Check my work run (commit, time, which checks passed).
• Basic usage events and error reports, tied to your account id and never to your name or email. Analytics and error tracking are off unless the service is configured.
• Your notification inbox, email preferences and delivery status. Public contact forms store your name, email and message. Product updates store your email and consent.
• If you post a community question, we send your question, app username, optional Discord username and lesson link to Stacc’s Discord #help channel. We store an account-linked posting cooldown to limit spam.
• For invited Pro clients: learner contact details, agreed teaching terms, plans, assignments, submissions, feedback, session attendance and payment records. These records are private. Tutor-only notes are not shared with the learner.

What we read from GitHub

Check my work uses a GitHub App that you install on one repository per track. It has read-only access to repository metadata, contents, commit checks and pull requests. It cannot write to your code. We read your latest commit, the file list, the files and headings a milestone requires, your CI result and, for the Foundations capstone, whether a pull request was merged. We do not copy or store your code.

What is public

Your portfolio at /u/<handle> shows your handle, avatar, completed modules and links to the verified work. Draft answers stay in your browser.

Pro teaching records do not appear on public portfolios. Product analytics and session recording are excluded from the Pro workspace and notification pages.

Community questions are visible to members of Stacc’s Discord server when you choose to post them. Replies stay in Discord. Joining Discord and posting questions are optional.

Where it lives and who handles it

• Supabase hosts the database and sign-in.
• Vercel hosts the app (Frankfurt region).
• GitHub provides sign-in and repository access.
• Discord receives community questions only when you choose to post them. Discord handles those messages and replies under its own policies.
• PostHog (analytics) and Sentry (errors) are used when configured.
• Resend handles platform, form and Pro notification emails when configured. Supabase handles sign-in email. Emails include teaching or billing updates and a private workspace link.

We do not sell your data or use it for advertising.

Cookies and storage

We set the cookies needed to keep you signed in. Your browser also stores your theme, progress in demo mode and lesson drafts. Nothing is used to track you across other sites.

Your controls

In Settings you can download everything we store about you, or delete your account. Deletion removes your profile, progress, project connections and verification history. Your GitHub repositories are never touched, and you can uninstall the GitHub App at any time from your GitHub settings.

Data exports include your accessible Pro records, excluding private tutor notes for learner exports. Account deletion also removes linked Pro teaching records. Contact your tutor before deleting if you need a copy of lesson or payment history.

Deleting your Stacc account removes its posting cooldown but does not remove messages already posted to Discord. Contact a Stacc moderator if you need a community question removed.

Contact

Questions or requests: hello@getstacc.org. If we change this page we update the date at the top.