What we hold, and what never leaves your disk.

Context is made by RTCH Foundry ("we", "us"). This policy covers the Context desktop application for macOS and Windows, the service behind it, and this website.

Threads, context cards, screenshots, recordings, transcripts and chat history are written to a local database and local files in your user folder. We do not receive a copy and cannot read them.

Deleting a thread deletes its cards and its audio from your disk. Archives you have already exported are yours to keep or remove.

• Account details: an email address and sign-in credentials, so the app knows who you are.
• Usage: how many minutes have been recorded and which models handled them, so usage can be counted against your plan and shown back to you.
• Billing: the details needed to take payment, handled by our payment processor rather than held by us.
• Call audio and thread content: passed through our service to be transcribed and to generate coaching, for as long as that request takes.
• Support correspondence, if you write to us.

We process this to provide the service, to bill for it, to keep it working and to answer you when you get in touch.

Transcription and coaching run on third-party models. Audio and the thread content you include are sent to those providers through our service so they can return a transcript or a suggestion. They act as processors on our instructions.

Your content is not used to train models, ours or theirs. We will keep a current list of these providers available and will tell you if it changes materially.

Audio and thread content are processed to answer a request and are not retained by us as a durable copy afterwards. The transcript comes back to your machine and lives there.

Account, usage and billing records are kept while your account is open and for as long afterwards as tax and accounting rules require. Close your account and we delete what we are not obliged to keep.

Context can record both sides of a call. Nothing records on its own: you start a recording, and the application shows while one is running.

Where a recording captures someone else, you are the one deciding to record them, and the obligation to have any consent the law requires sits with you rather than with us. Laws differ by country and by state.

You do not hold model provider keys, so there are none for you to lose. Any credential the application does store locally, such as a Google Drive token for backups, is encrypted using your operating system's secure storage and is never transmitted to us.

This site does not set advertising or tracking cookies and does not profile visitors. Your theme choice is kept in your own browser's local storage and never sent anywhere. Our hosting provider processes standard server request logs, including IP addresses, to serve pages and defend against abuse.

Because your threads stay on your machine, you already hold them directly and can read, export or delete them yourself at any time. For the account, usage and billing records we do hold, you can ask for access, correction, export or erasure, and you can object to processing. Write to us and we will respond.

Context is not directed at children and we do not knowingly collect personal data from them.

If this policy changes in a way that matters, we will update the date at the top of this page and tell you directly where the change affects how your data is handled.

Questions about privacy go to info@rtchfoundry.com. For how this works in practice, and where each file lives, see Security and data handling.