Privacy Policy

Last updated October 7, 2026

This policy explains what information the Framework website (the "site") uses, why, and the choices you have. We keep it short because we collect very little.

Reading the site

You can read the site without signing in. We don't use analytics, advertising or tracking cookies, and we don't sell or share your data.

Signing in with Discord

Discord login uses only the identify permission. That gives us your Discord user ID, display name and avatar. We never see your email address, password, servers or messages.

These details are kept in a signed cookie in your browser so the site knows you're signed in. They are not saved in our database. The one exception is the Framework team: when a team member publishes a blog post, their name, avatar and Discord ID are stored with the post so it can show who wrote it.

Cookies

  • fw_session keeps you signed in. It lasts 7 days, or until you log out.
  • fw_oauth_state protects the login process against forgery. It lasts 10 minutes.

Both are strictly necessary for login. There are no other cookies.

Services we rely on

  • Discord handles login, and profile pictures load from Discord's servers.
  • Vercel hosts the site. Like any web host, it processes your IP address and browser details to serve pages and keep the site secure.
  • MongoDB Atlas stores blog posts.
  • Google Fonts serves the site's font, so your browser contacts Google's servers when a page loads.

Each of these services handles data under its own privacy policy.

Your choices

  • Log out at any time to delete the session cookie.
  • Remove the site's access in Discord under User Settings → Authorized Apps.
  • Ask us any question about your data on our Discord server.

Children

Discord login is only for people who meet Discord's minimum age requirement.

Changes

If we change how the site uses data, we'll update this page and the date at the top.