The short version
- Treadle is an app that runs on your Mac. There is no Treadle account. Once a day it checks your membership with gettreadle.com, and that check carries only your membership key and Treadle's version number. Twice a day it also asks gettreadle.com whether a newer version of Treadle exists, and that question carries nothing about you.
- Your board is kept in a private folder on your Mac. It is never sent to me.
- To read your work, Treadle asks Claude (or Codex, if you choose it) through your own account. Short excerpts of your work go to Anthropic or OpenAI under your agreement with them.
- Treadle has no analytics, no tracking, no ads and no crash reporting. On its own, it sends only that daily membership check and the question about a newer version, and nothing about your work.
- I only receive what you choose to send: your purchase, through Stripe, your emails and problem reports, and your email address if you sign up for the Sunday email.
- You can switch off any source, and delete everything by deleting one folder (two, if Treadle keeps a copy of your code from GitHub).
Who is responsible
Treadle is sold by 18202729 Canada Inc., a federal corporation, at 505-2019 rue Moreau, Montréal, Québec H1W 2M1, Canada. Yael Ezerzer owns and runs it, and makes Treadle. In this policy, “I” and “me” mean 18202729 Canada Inc., speaking through me, Yael, and “Treadle” means the app and this website.
I am the person in charge of the protection of personal information for Treadle. You can reach me about anything in this policy at yael@gettreadle.com.
This policy covers the Treadle app for Mac, the website gettreadle.com, your purchase, and any support you ask me for.
What Treadle reads on your Mac
Treadle keeps your board up to date by reading the work you already do. It reads only the sources below, and only what each row says. Every source has a switch, or is read only when you add it.
| Source | What it reads | How to control it |
|---|---|---|
| Claude Code sessions | Each session's title, when it happened, and short excerpts of your own messages (not Claude's replies). | Integrations → Claude Code. On by default. |
| Claude Cowork sessions | Each session's title (or the first line of your first message), its timing, and the folders you chose for it. Scheduled runs are ignored. | The same Claude Code switch. |
| Claude app sessions | Only after you press Start on a task to open it in Claude Code: the new session's record and first message, to check it opened in the right folder. This check runs even when the Claude Code switch is off. | Happens only when you press Start. |
| Codex | The list of your Codex sessions (title, folder, branch, timing) and short excerpts of your own messages. | Integrations → Codex. On by default when Codex is installed. |
| ChatGPT and Claude chats | Only chats you hand over: an export you add, or a ChatGPT chat you send to Codex. From each, the chat's title and your own messages, not the replies. From an export's .zip, only the conversations file is taken out; its pictures and other files are left alone. | Integrations → Add an export. Chats sent to Codex follow the Codex switch. |
| Git repositories | In the folders you add: the branch, how many files are changed, and the last 30 days of commits (identifier, subject line, author name, date). Each commit's author email too, used only on your Mac to tell your commits from other people's: when the repository says which email is yours, other people's commits are left out. The email is never written to your board or sent anywhere. A commit's full details only when you open it. | Only folders you add or watch. Hide a folder to exclude it. |
| GitHub | Only if you connect it, with a read-only token you make on GitHub. The repositories that token can see and that changed in the last month: their names, and the last 30 days of commits (identifier, subject line, author name, date) on each one's main branch and on its claude/ branches, the ones Claude Code's cloud sessions push. Only your own commits and your agents' are kept; other people's are left out. Each commit's author email is read only to tell them apart, on your Mac, and is never written to your board or sent anywhere. To tell whether a branch's work is already merged, the names of the files in the main branch and in the branch's changes, with a fingerprint of each, not what the files contain. For a goal whose code is only on GitHub, the code itself: Treadle keeps a read-only copy of that repository's main branch on your Mac so agents working on that goal can read it (see below). Your GitHub user name, to check the token. | Integrations → GitHub. Off until you connect it. Disconnect deletes the token. |
| Notion | In databases you share with your own Notion integration: each row's title, status, date and link. A short excerpt of a page only when you open it. Meeting-note transcripts are never read. | Only if you create a Notion integration and save its secret. |
| Your calendars | From the private calendar links you paste: each event's title, start and end time, and whether it repeats. Not its location, description or guests. | Integrations → Calendar. Only links you add. |
| Your Mac account name | Your full name, used only on your Mac so that your own name isn't mistaken for a project when matching meeting titles. Never stored or sent. | Not optional, never leaves your Mac. |
Treadle doesn't read your chats on claude.ai or chatgpt.com unless you add an export of them or send one to Codex. It doesn't read your email, your messages, your photos, or your browser history.
What it keeps, and where
Everything Treadle keeps is in one folder in your home folder: ~/.treadle-app, apart from the copies of code described below. The folder can be opened only by your own macOS user. Its files are readable only by you.
- Your board: goals, tasks, plans, notes, the conversations you have with your agents, your settings, and the evidence behind each update (session titles, commit subjects, short quotes of your words). It is kept as a plain file you can open in a text editor, with one backup copy refreshed each time Treadle opens.
- What agents made for you: drafts and files, and before-and-after pictures of changes.
- Chat exports you add: the conversations file from each, one per app. Adding a newer export replaces the older one.
- Sign-ins and links: your private calendar links, your Notion secret if you saved one, and your GitHub token if you connected GitHub. Each in its own private file that only you can read, never in the board, never shown on screen, and never sent to gettreadle.com. Treadle keeps no Claude sign-in: Claude Code keeps its own, in your Mac's Keychain, and Treadle never sees it.
- An error log, so problems can be explained. It can contain short pieces of text from a failed step.
- Measurements of your own pace, such as how long your sessions ran on a given day, so Treadle can size your plan realistically. This is worked out and kept on your Mac. It is never sent to me, and nothing about you is decided from it.
Three things are kept outside that folder. If a goal's code is only on GitHub, Treadle keeps a read-only copy of that repository beside its own folder, in ~/.treadle-app-copies, which, like it, can be opened only by your own macOS user. It is the latest version of the repository's main branch, refreshed with your GitHub token before each use, so it holds only code that token can already read. If you install the /treadle command for Claude Code, its instructions are saved in ~/.claude/skills/treadle. And Claude Code itself keeps a record of every run Treadle makes through it, in ~/.claude/projects, as it does for any use of Claude Code. The support page shows how to delete all of it.
What leaves your Mac, and where it goes
Your board is never sent to me. The only thing Treadle sends to gettreadle.com is the membership check below. These are the only places anything goes, and only for the reason given.
| Recipient | What is sent | When |
|---|---|---|
| gettreadle.com, for the membership check (run by Cloudflare) | Your membership key and Treadle's version number, over an encrypted connection (HTTPS). Nothing else: not your board, not your project names, not how you use Treadle. | About once a day. |
| gettreadle.com, to see whether a newer Treadle exists (run by Cloudflare) | Nothing about you: the app asks for one public file, the same one anyone can open, over an encrypted connection (HTTPS). The new version downloads only when you press Update and restart, and Treadle checks it is signed by me before installing it. | About twice a day, and when you press Check for updates. |
| Anthropic, through your own Claude account | Project names; goal and task titles; commit subject lines; session titles; up to 40 short excerpts (400 characters each) of your own messages per project; sentences from your messages that mention a date; titles of last week's meetings for your weekly summary; your own messages from the chats you added or sent to Codex (up to 6,000 characters each time they're read: when you press Read my chats, and when a goal they mention is planned); to sort a new step, its title and notes, the start of its goal's spec, your agents' descriptions, and your choices and recent corrections about who does what; and, when you ask for help on a goal, its text and what you type. | Once a day when you open Treadle, if Check in on its own is on (it is by default). Once you have allowed agents, also a minute or two after a new step appears, to sort it as the team's or yours, while Check in on its own or unattended work is on. Otherwise only when you press a button that asks Claude, or when an agent works (see Agents). |
| OpenAI, through your own Codex sign-in | The same as above, instead of Anthropic. | Only if you choose Codex as Treadle's engine. |
| Notion | Requests to read the databases and pages you shared, signed with your secret. | About every 15 minutes during your working hours, and when you open a Notion item. |
| GitHub | Requests to read the repositories your token can see, as listed above, signed with your token, over an encrypted connection (HTTPS). | Only if you connected GitHub: about every 15 minutes while Treadle is open, when you open Integrations, and, for a goal whose code is only on GitHub, before an agent works on one of its steps, to refresh Treadle's copy of it. |
| A Claude Code cloud session, in Anthropic's cloud, through your own Claude account | The step, its notes, its goal and up to 3,000 characters of the goal's spec, to start the session. The session then works on your repository on GitHub, in Anthropic's cloud rather than on your Mac, and pushes its own branch there for you to review. | Only when you press Run it in the cloud on a step whose goal's code is only on GitHub, or hand off such a step while Agents work in the cloud is on (Integrations → GitHub, off by default). |
| Your repository's remote (such as GitHub) | A change's branch and its commits, sent with your own git sign-in. | Only when you press Push branch on a change waiting for your review. |
| Your calendar provider (Google, Microsoft or other) | A request for your calendar feed. | At most once an hour. |
| The app you open with Start | The task you started, so the app opens ready: Claude, ChatGPT, your email app, Notion or Notion Calendar. For Google Calendar on the web, the task's title is part of the web address. | Only when you press Start. |
The membership check asks Stripe whether your membership is paid, then answers with a signed reply, so Treadle can tell the answer is genuine. The check stores nothing: your membership lives in Stripe. Cloudflare, which hosts gettreadle.com and runs the check, keeps standard request logs (your IP address, the time and the page), as it does for any web page.
What Anthropic and OpenAI do with what they receive is governed by your own agreement with them, including whether your conversations may be used to train their models. You can change that in your Claude or ChatGPT privacy settings. Treadle sends your requests to them the same way you would by typing in their apps.
Agents
When you send an agent to work on a step, it runs Claude Code (or Codex) on your Mac, in a separate copy of your project or an empty folder, unless you run the step in the cloud (below). It sends the step, its goal, the goal's plan and your conversation with it to Anthropic (or OpenAI), along with whatever files it opens to understand your project. An agent can read files on your Mac, and what it reads is sent to the model like anything else it works with. For a goal whose code is only on GitHub, that includes Treadle's copy of the code. While it works, it can change files only inside its own copy.
Agents work when you send them, and also without a press in cases you turn on. With unattended work on (Settings → Your team, off by default), the team picks up the steps sorted as its own, and prepares the kinds of steps set to Prepare it for me in Who does what, whether you chose that or Treadle learned it from your past choices. When you ask your Reviewer agent (Reed) to check a change, it works the same way, on its own copy of that change, and may add a test to it.
What an agent can reach beyond that is your choice, in Settings → Your team, or with one press when an agent asks. With the web on, it can search the web and open pages through Claude Code, and what it finds is sent to the model like anything else it reads. With one of your apps on, it reads that app through the connection you set up in Claude, under your own Claude account, and what it reads is sent to the model. Agents read your apps, and change things in them only as you choose for each app: after your yes, word for word, or on their own. Anything an app marks as deleting always waits for your yes. An agent can never read the places where your Mac and common tools keep passwords, keys and tokens: your Keychain, your SSH and signing keys, the sign-ins of common developer and cloud tools, 1Password, and the data of Safari, Chrome, Firefox, Edge, Brave and Arc. It can't read your shell history, Mail, Messages or Treadle's own folder either. It can read the settings files (.env) of the project it works on, which often hold that project's keys, and what it reads is sent to the model like anything else. While a step is allowed to open web pages, install packages or change one of your apps without asking you, Treadle seals those files too. Treadle keeps a list of what each step reached, on your Mac only.
Planning a goal works the same way once you have allowed agents: the planner may open files in that goal's project folder to see what is already there, and what it reads is sent to the model. It can't change anything.
If a goal's code is only on GitHub, you can run one of its steps in a Claude Code cloud session instead: by pressing Run it in the cloud, or by handing it off while Agents work in the cloud is on. That session runs in Anthropic's cloud, not on your Mac, under your own Claude account. Treadle sends it the step, its goal and the goal's spec. The session works on your repository there and pushes its own branch to GitHub for you to review, and it is told not to merge it. What happens in that session is governed by your agreement with Anthropic. Treadle starts one only when you press a button.
When a change is ready, Treadle may run your project on your Mac, the way your project says to run itself, to take before-and-after pictures for you. The founding version asks your permission once before any agent works.
What I receive
- Your purchase. Payments are processed by Stripe through its Link service, which acts as the merchant of record for payment and sales tax. I remain the seller. Stripe and Link handle your payment details under their own privacy policies (Stripe's is here, and Link's is linked at checkout). Your card number never reaches me. I see your name, email address, country, what you bought, and whether your subscription is active.
- Your emails to me, and anything you attach.
- Problem reports you choose to send. A report holds Treadle's version, your macOS version, how many items each source found (never their titles), and the last lines of the error log with personal text removed. You see every line before it's sent, and it's sent from your own email app.
- The Sunday email, if you sign up for it on the Before you rebuild page. You tick a box to say yes, then press Confirm in the email that follows. Until you press it, nothing is kept. Once you confirm, Resend, which sends the email, keeps your email address, the language you chose and when you confirmed. They are used only to send you that email, at most once a week, and are not linked to a membership. Every email has a link to unsubscribe.
That is all. The app itself contacts gettreadle.com only for the daily membership check and the update check described above. Nothing from it is kept, apart from Cloudflare's standard request logs.
This website
gettreadle.com sets no cookies and runs no analytics or ads. Its typeface is served from gettreadle.com itself, so no font request goes to Google or anyone else. Cloudflare, which hosts the site, keeps standard server logs (your IP address, the page and the time) for security. The site also runs the membership check, the welcome page that shows your membership key after checkout, and the Resend my key form on the support page. That form uses the email address you type only to find your membership in Stripe and send you its key, and its answer is the same whether or not that address has a membership. To limit how often a key can be emailed, the form keeps the times a key was asked for in Cloudflare's cache for up to a day, filed under two scrambled codes: one made from the address, and one from the address together with your IP address. Each is made with a secret key, so it reveals nothing about either without that key. The form doesn't keep the address or your IP address themselves. The sign-up form for the Sunday email sends one email with a Confirm link to the address you type, and keeps nothing until you press Confirm. It limits how often that email can be sent in the same way, under codes of its own. When you press a payment button, you go to Stripe's checkout page, where Stripe's policy applies.
What I never do
- Sell or rent your personal information, or share it for advertising.
- Track you across apps or websites.
- Train AI models on your work.
- Read your board. I can't: it isn't sent to me.
Why, and on what basis
I handle the little personal information I receive only for these reasons:
- To provide what you paid for: your membership, the download, updates and support. This is necessary for our contract. Without your name, email and payment, I can't sell you a membership. Using Treadle sends me nothing about your work: its daily membership check carries only your membership key and Treadle's version number, to confirm the membership you paid for.
- To keep records the law requires, such as sales and tax records.
- To answer you when you write, and to fix what you report. This is in both our interests, and you started it.
- To ask how Treadle is going, once, by email, about ten days after you join. Answering is up to you, and if you reply stop I won't ask again. This is in both our interests: it's how Treadle gets better. I quote what you write on gettreadle.com only with your written yes, with your first name and what you do, once you've seen the exact words, and a quote comes down whenever you ask.
- To tell you about important changes to Treadle, this policy or the terms. I will never add you to a marketing list without asking.
- To send the Sunday email you asked for, with your consent. You can withdraw it any time with the unsubscribe link in every email.
Where the law asks for your consent, I ask for it, and you can withdraw it at any time.
How long things are kept
- On your Mac: until you delete it. Treadle keeps no copies anywhere else. Deleting a goal removes it from your board. A copy remains in the one backup file until Treadle next opens.
- Purchase records: six years after the year of the sale, as Canadian and Québec tax law requires.
- Emails and problem reports: as long as needed to help you, and no more than two years after our last exchange. Sooner if you ask.
- A quote and your written yes: as long as the quote is on gettreadle.com. After that, like any other email.
- The Sunday email: until you unsubscribe. After that, Resend keeps your address marked as unsubscribed so the email is never sent to it again. Ask me and I'll delete it completely.
Where data is processed
Your board stays on your Mac, wherever you are. The personal information I receive could be communicated outside Québec: it is held by the services I use, which may store it in the United States or elsewhere. Those are Stripe and Link for payments, Microsoft for email, Resend for the welcome email after you buy, the key emails sent from the support page and the Sunday email, Cloudflare, a US company, for the website and the membership check, and my phone provider. Before using a service outside Québec, I assess whether it protects personal information adequately, and I rely on a written agreement with it. Information held in another country may be accessible to that country's courts and authorities. Anthropic, OpenAI, GitHub, Notion and your calendar provider receive data from your Mac under your own agreements with them.
Your rights
Wherever you live, you can ask me to:
- tell you what personal information I hold about you, and give you a copy;
- correct it if it's wrong or incomplete;
- delete it, or stop using it;
- give it to you in a structured, commonly used format, or send it to someone else;
- treat a consent you gave as withdrawn.
Email yael@gettreadle.com. I answer within 30 days and never charge for a reasonable request. I may need to confirm it's you before I act. For anything on your Mac, you are in control directly: it's your folder.
You can also ask who has access to your information (only me), how long I keep it, and how to reach me as the person in charge of protecting it.
Complaints
To complain about how I handle your personal information, email me with “Privacy complaint” in the subject. I acknowledge it within five business days, look into it, and answer in writing within 30 days.
If you're unhappy with my answer, you can complain to the Commission d'accès à l'information du Québec (cai.gouv.qc.ca), the Office of the Privacy Commissioner of Canada (priv.gc.ca), or, in the European Union or United Kingdom, your local data protection authority.
Security
- Treadle's folder, its copies of your code, and their files can be opened only by your own macOS user.
- Secrets (your Notion secret, your GitHub token and your calendar links) are kept in separate private files, are never written into your board, and are never placed where other programs on your Mac could read them while in use. Your Claude sign-in stays with Claude Code.
- Agents on your Mac work in a separate copy of your project, with their file changes confined to it. A step you run in the cloud works on its own branch on GitHub instead.
- Treadle is signed by its developer and checked by Apple.
No system is perfectly secure. Keeping your Mac up to date, locked and backed up protects Treadle's folder along with everything else.
If something goes wrong
If personal information I hold is ever lost, accessed or disclosed without authorization, I will act quickly to limit the harm. Where there is a risk of serious injury, I will notify you and the Commission d'accès à l'information du Québec, and, where the law requires it, the Office of the Privacy Commissioner of Canada. I keep a record of every incident, however small, for at least five years.
Age
Treadle is for adults. It requires a paid Claude plan, which Anthropic offers only to people 18 and older. I don't knowingly collect information from anyone younger.
Changes to this policy
If Treadle starts reading, keeping or sending anything new, this policy changes first. The date at the top always shows the last update. For any significant change, I will email members before it takes effect.
Contact
Yael Ezerzer, Treadle, Montréal, Québec, Canada.
yael@gettreadle.com