Ask about your documents.
Compare PDFs and go straight to the cited passage. We read and store your originals in Canada.
For EU customers
That recognition covers Canadian businesses like us. Your conversations and files are stored on hardware we own in Canada, and you choose how much any outside model sees.
Claude received: both files, with [ORGANIZATION_1], [PERSON_1] and [LOCATION_1] in place of company names, personal names and addresses.
1 · Supplier proposal.pdfProposed delivery: November 17.
2 · Project brief.pdfRequired delivery: November 10.
Compare PDFs and go straight to the cited passage. We read and store your originals in Canada.
Every model is labelled with who runs it, where it’s processed and what the provider keeps. Our AI is available in Private.
Redact replaces names, addresses and IDs before an outside model receives the request. Consistent placeholders preserve connections across documents.
Answers from your documents cite the passage behind them.
For businesses covered by PIPEDA, like us.
The European Commission has decided that Canadian businesses subject to PIPEDA, Canada’s federal private-sector privacy law, protect EU personal data to an adequate level. This is called an adequacy decision. The Commission’s 2024 review confirmed it (opens in a new tab).
For transfers within that scope, adequacy is a recognized transfer mechanism. It is not a certification of an AI product. Your other GDPR obligations and any onward transfers still need to be assessed. The European Data Protection Board explains adequacy (opens in a new tab).
We store your conversations and files in Canada, not in the EU. If your requirements call for EU-only storage or processing, that is a different requirement from adequacy.
Your stored conversations and files are on hardware we own, rather than rented from a foreign cloud.
The US CLOUD Act can require providers subject to US jurisdiction to disclose data they control, regardless of its location. The US Department of Justice’s explanation (PDF, opens in a new tab) makes jurisdiction and control the relevant questions.
Owning our storage hardware avoids placing your stored conversations and files in a US cloud provider’s custody just to host our service. It does not make data immune from lawful requests. Choosing an outside model brings that provider and its legal obligations into the processing path.
See Where your data goes for the services that are ours and the ones that are not.
No. The outside model still receives the redacted text and the rest of the request. The model label tells you where it is processed. Redaction reduces identifying details; it does not settle the legal treatment of every request.
Yes. Choose Private and our AI handles your messages and files on our hardware in Canada. External tools have their own boundaries, explained on Where your data goes.
Review the processing purpose, provider arrangements, safeguards and any onward transfers for the workflow you want to use. Start with our Trust Centre and security explanation; have the appropriate privacy or legal reviewer assess your requirements.
Choose how much each model sees.
Private
Our AI answers here, and no outside AI provider receives your messages or documents.
Redact
Use an outside model with names, addresses and IDs replaced first. We put the original details back into the answer.
Direct
Your request goes to the model you choose, as written. Its label shows who handles it and what they keep.
Redaction isn't perfect, but you can always preview before sending. Outside models and tools have their own boundaries. Where your data goes
Wherever the day takes you
Apps for iPhone and Android are on the way.
Try one document in Private. Our AI answers on our hardware in Canada.
Every model and all three privacy modes are available on every plan.
Did you scroll all the way down here looking for the cookie consent banner? You won't find tracking cookies on this site.