Privacy

Your email address, because it is how you sign in. A name, if you give one during setup or if it comes from Microsoft, Google or Apple when you use them to sign in. The company you work for and the domain of your work address, which is read from that address rather than asked for. What you do, meaning the kind of work you named at setup and roughly how far into your career you are. The modules you say you work in, and which of them is your main one, because answers are scoped to it. Your conversations, meaning the questions you ask and the answers you are given, so that your threads are there when you come back and on your other devices.

The setup answers are used to scope your answers, to decide which module a question belongs to, and to understand who this product is for. Your work domain is also how we recognise that several people from the same firm are using Propfessor, so we can deal with that firm once rather than as separate strangers.

Alongside those: which account you belong to and your role in it, how many sign-in providers you have linked, the date your session was last used, and any module you registered interest in from the sign-up picker. Those are the mechanics of signing in and of asking for something we do not sell yet, and each one is a row we would otherwise be describing without naming.

That is the whole list. There is no tracking of you around the internet, no advertising identifiers, no profile built from your behaviour, and nothing is sold or shared for marketing by anyone.

A short-lived count of how many questions you have asked, held in your own browser, so the free trial can end.

On our side there are two small counters, and they are keyed on the network address your request arrives from rather than on you. One counts how many questions have come from that address in the last minute and in the last day, which is how the free trial and the rate limit work at all. The other records that address once, on a day when the daily limit is passed, because somebody reading the whole of our material through the question box looks exactly like that and we want to be able to see it. Neither carries your name, your email or anything you typed, and neither is shown to anyone: the internal console counts them and cannot display an address.

We are asked to keep the questions people ask, so we can decide what this trainer learns next. That only happens if you tick the box, and if you do, the question is stored with no name, no account and no token of any kind against it. Email addresses and phone numbers typed into a question are stripped before it is stored. The answers themselves are not stored in that log.

You can withdraw at any time, and nothing further is logged from then on. Be aware of what that can and cannot do: because a logged question carries no identifier at all, not even a token, there is nothing that could find the ones already logged. They cannot be identified, retrieved or removed, by us or by anybody, and that is the same property that stops them being tied back to you. This wording was corrected on 2 September 2026: it previously said nothing was kept after a withdrawal, which the storage cannot do and never could.

Separately, and regardless of that choice, we count how many questions were asked in each module each day. That count contains nothing about anybody.

When the trainer cannot answer something, you can send that question on for a person to answer. If you do, the question is kept, with email addresses and phone numbers stripped out of it the same way the question log strips them. If you leave an address so you can be told the answer, that address is kept with it and is used for nothing else. A person reads the question, and the answer they write may become part of the material this trainer is taught from, so that nobody has to ask it again.

A sign-in cookie so you stay signed in, and a random participant token used only for the consent choice above. Two short-lived cookies exist during a Google or Microsoft sign-in to protect that exchange, and are deleted the moment it finishes. There are no advertising or analytics cookies.

The database is Neon, in Frankfurt. Hosting is Vercel. Sign-in emails are delivered by Resend, in Ireland. Answers are generated by language models reached through OpenRouter, and the search over our own material uses Voyage AI. Payment, when it arrives, will be handled by Creem, and card details will never reach us.

Your questions and answers are sent to a model provider in order to be answered. They are not used by us to train a public model.

Your account and threads stay until you remove them. You can delete any thread in the product, and it is gone. Sign-in codes expire in ten minutes, sessions in ninety days. Consent records are kept as a dated ledger, because a record of permission has to survive being checked.

The two counters described above are swept automatically. The question counters are deleted two days after the window they count closes, and a record that the daily limit was passed is deleted after ninety days. A question sent to a practitioner, and any address left with it, stays until the question is answered or withdrawn, and you can ask for it to be removed at any point.

A copy of what is held about you, a correction, or deletion of the whole account and everything in it. Write to admin@propfessor.com and it will be done. If you are in the UK or the EU, this is your right under the GDPR and you may also complain to your national data protection authority.

Propfessor is a professional tool and is not intended for anyone under 18.

If this page changes materially, the date at the top changes and anyone with an account is told by email before it takes effect.

Propfessor LLC, of 30 N Gould St, Ste N, Sheridan, WY 82801, USA, is the controller of the data described here. Every request above, and every question about this page, goes to the same place: admin@propfessor.com. A person reads it, and you will get an answer.