Back to Magister

Privacy Policy

Last updated May 30, 2026

Magister helps you understand code by sending it to an AI model and returning an explanation. We try to collect as little as possible and to be clear about what happens to the data you give us. This policy explains what we collect, why, who it is shared with, how long it is kept, and the choices you have. Magister does not have user accounts today; where a clause below applies only once accounts are added, that is called out directly.

What is collected

  • The code you paste. When you submit a snippet, it is sent to Groq to generate a response. Magister does not store the code you paste today.
  • Privacy friendly usage analytics through Vercel Web Analytics. These measure aggregate traffic and contain no personal identifiers.
  • Error diagnostics through Sentry, collected when something fails so we can find and fix the problem.
  • When accounts are added, an email address or authentication identifier and your saved history will also be collected so you can sign in and return to past work.

Why it is collected

We collect this information to operate the service, to debug problems when they occur, and to prevent abuse of the service. We do not use it to build advertising profiles.

Who it is shared with

Your data is shared only with the providers that run Magister:

  • Groq, which runs the AI inference on the code you submit.
  • Vercel, which provides hosting and usage analytics.
  • Sentry, which provides error monitoring.
  • Supabase, which will store accounts and saved history once accounts are added.

It is shared with no one else, and your data is not sold.

Retention

  • Pasted code is processed transiently to produce a response and is not retained by Magister today.
  • Analytics and error data are kept according to the retention windows of the providers that hold them (Vercel and Sentry).
  • When accounts are added, saved history is kept until you delete it.

Your rights

Magister has no user accounts and keeps no database of personal information about you. The code you submit is processed transiently and not retained, analytics are aggregate and cookieless, error diagnostics are technical and held only by our monitoring provider, and the only value kept for rate limiting is a one-way hash of your IP address that expires daily and cannot be traced back to you. Because there is no identity-linked record we can look up, there is nothing for us to retrieve, change, or delete on an individual request. If you have any questions about privacy, you can reach us at privacy@magister.app.

EU and UK users

To the extent the GDPR or UK GDPR applies, the rights of access and erasure concern personal data a controller holds about you. As described above, Magister retains no such data, so in practice there is nothing to access or erase. Questions are welcome at privacy@magister.app.

California users

The CCPA rights to know and to delete likewise concern personal information a business holds about you. Magister holds none that identifies you, so there is nothing to disclose or delete. Questions are welcome at privacy@magister.app.