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.
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.
Your data is shared only with the providers that run Magister:
It is shared with no one else, and your data is not sold.
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.
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.
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.