What we log, in plain English, with the legal pages linked rather than buried

Privacy pages are usually written to be survived rather than read. Ours are linked below and you are welcome to work through them, but here is the short version first, because a policy nobody reads is not a policy.

The short version

• An account needs an identity. Your email, the organisations you belong to, the devices you have signed in from. That is what makes a sign-in work at all.
• Sessions expire. Device tokens are short-lived and re-issued, rather than one key that lives forever.
• The index and your workspace are separate systems. What our crawler reads from the public web is one thing. What you put into a workspace is another.

Where the detail lives

The trust page is the plain-English summary of how the platform handles data and who can reach it. Security covers how to report a problem to us, which we would much rather you did than not. The legal section has the actual terms and the processing detail, which is the part that matters if you are running a vendor review.

If you would rather read the argument than the policy, the research page has the essays. They are longer and less careful than a policy, which is rather the point of an essay.

The practical guide

If your question is less "what is your policy" and more "how do I use an AI tool without leaking the thing I am working on", then keeping work private with AI is the one to read. Most of it is tool-agnostic advice that applies whether or not you use us.

What we will not do

We are not going to post a compliance badge in a Reddit thread and call it an answer. Ask something specific and you will get a specific answer, here or at contact.