Privacy Policy

In short: Claude Code runs on your computer and your files stay there. Our relay passes your messages (from Telegram, Slack or the TextMyWorker app) to your computer and never writes their content to disk. We keep counts and timings, the pairing between your account and your computer, and, if you talk to the bot before joining, your short answers to its three questions. No ads, no tracking cookies, no selling data.

1. Who is responsible

TextMyWorker is operated by Eyal Baruch, Israel (“we”, “us”). We are the controller (in Israeli law, the database owner) of the personal data described here. Contact: eyal@textmyworker.com.

This policy covers the textmyworker.com website, the TextMyWorker bot on Telegram and Slack, the TextMyWorker app at app.textmyworker.com, the relay at relay.textmyworker.com, and the TextMyWorker software on your computer (the “Service”). It doesn't cover Anthropic, Telegram, Slack or other providers' own processing under your own accounts with them (see section 5).

2. What we collect

On the website

• Anonymous visit counts. When a page loads, your browser sends us the page name and a source label (for example tiktok, search or ai), based on the link's utm_source or the site that referred you. We store daily totals only, with no IP address, cookie or identifier. The source label is kept in your browser's session storage for that tab, so moving between pages doesn't reset it. It's deleted when you close the tab.
• A source tag in the Telegram link. The “Ask the bot” button opens Telegram with a short start code such as site_tt, which Telegram passes to the bot when you tap Start, so we know which channel a request came from.
• The application form, if you use it: your email, name, what you'd have your worker do, and whether you use Claude Code.

We don't use advertising pixels, third-party analytics or tracking cookies.

When you talk to the bot before you're connected

Your Telegram user id, name, username and language setting (in Slack, your Slack user and workspace ids, display name, username and language setting; for accounts from before Telegram, your phone number instead), the source tag, your answers to the bot's three questions (your name and what you build, Mac or Windows, the first task you'd give it), a fit score calculated from those answers, and our decision (approved, rejected or waitlisted). A summary is sent to us so we can review it.

When you set up and use the Service

• Pairing: your account (your Telegram or Slack account, or the phone number of an account from before Telegram), the name of your computer, when you paired, and a hash of your computer's device token (never the token itself).
• Setup progress: content-free milestones such as “setup started”, “paired” or “first message”, their times, your operating system and the type of any error, so we can help if you get stuck.
• Usage metrics: counts and types of messages, response times, approval counts (sent, approved, denied, expired), error types, online time, voice-note duration, and the lengths of messages and replies. Never their text.
• Last channel: which channel you last wrote from (Telegram, Slack or the app) and when, so replies reach you there.
• The app: a hash of your app sign-in session (never the session itself), the device name it reports, and, if you turn on notifications, your browser's push subscription (an address at your browser's push service and its encryption keys).
• Operational logs: technical events with account identifiers and event types, but not message content, for running, securing and troubleshooting the relay.
• Bug reports you send us: if you start a message with “bug” (or “באג”), or tap the report button, the text of that report and any screenshot or recording you send in the next few minutes are forwarded to us.
• Messages you send to us directly, such as replies to our follow-ups.

Message content: passed through, not stored

Your messages to your worker, and its replies, pass through the relay on their way to and from your computer. The relay holds a message in memory only until your computer collects it and never writes message content to disk. For the app, the relay also keeps recent messages in memory for about 30 minutes, so a phone that reconnects can catch up; the app's history is stored on your phone. Photos and documents are fetched from Telegram when your computer asks for them and passed straight through. Photos you send from the app are held in the relay's memory for up to 6 hours, so your computer can download them even if it was off when you sent them; only your paired computer can fetch them, and they're never written to disk. In Telegram, messages also go through Telegram's servers, like any Telegram chat (bot chats aren't end-to-end encrypted). In Slack, messages also go through Slack's servers, like any Slack message. App notifications don't include the message text by default, only the tool or folder involved. Voice notes are sent to ElevenLabs for transcription and the text goes to your computer. We don't read your conversations with your worker.

What stays on your computer

Your files and projects, attachments you send (saved in your workspace), the activity log, the local audit log of your worker's actions, and your device token (in a file only your user can read). None of this is sent to us.

3. Why we use it, and our legal bases

• To provide the Service: routing messages, pairing, approvals and summaries. Basis: performing our agreement with you.
• To run the pilot: reviewing requests, following up, and helping you through setup. Basis: steps you asked for before an agreement, and our legitimate interest in running a selective pilot.
• To understand and improve the Service: counts, timings, error types and channel sources. Basis: legitimate interest. We use content-free and aggregated data for this.
• To keep the Service secure and prevent abuse, through rate limits, logs and unpairing. Basis: legitimate interest and legal obligations.
• To answer you, including bug reports and requests about your data. Basis: performing our agreement, and legitimate interest.

We don't sell personal data, use it for advertising, or use your messages to train AI models.

4. How long we keep it

5. Who we share it with

We use these service providers, who process data for us under their own terms and security commitments:

• Telegram Messenger: carries Telegram messages between you, the bot and your worker, if you use the Telegram channel.
• Slack (Slack Technologies, a Salesforce company): carries Slack messages if you use the Slack channel.
• Web push services (Apple, Google, Mozilla or Microsoft, depending on your device and browser): deliver the app's notifications. The notification content is encrypted for your device.
• Fly.io: hosts the relay, in Frankfurt, Germany.
• Netlify: hosts the website and stores form submissions.
• ElevenLabs: transcribes voice notes.
• Google Fonts: serves the website's fonts, which means your browser connects to Google.

Anthropic receives your prompts and the parts of your files Claude reads, but under your own Claude account and Anthropic's terms with you, not as our provider. The same applies to any other tools you connect to Claude Code yourself.

We may also disclose data if the law requires it, to protect rights and safety, or as part of a reorganisation, merger or sale of the Service, subject to this policy.

6. International transfers

We operate from Israel, the relay runs in Germany, and our providers may process data in the United States and other countries. Where the law requires it, we rely on adequacy decisions (the EU recognises Israel as adequate) or on safeguards such as the EU Standard Contractual Clauses offered by our providers.

7. Security

The relay checks Telegram's secret token and Slack's request signature on every delivery, routes each message only to the computer paired with the sending account, stores only a hash of device tokens, limits request rates, and keeps no message content on disk. Your computer connects out to the relay, so nothing on it is opened to the internet. No system is perfectly secure. If you think your phone or pairing is compromised, disconnect right away (see the Terms) and tell us.

8. Your rights

You can ask to access, correct or delete your personal data, and, where the law gives these rights (for example under the EU GDPR), to restrict or object to processing, or to receive your data in a portable format. Israeli residents have rights of access and correction under the Protection of Privacy Law. Email eyal@textmyworker.com from, or mentioning, the Telegram or Slack account, phone number or email involved. We'll verify the request and reply within the time the law requires, normally 30 days.

You can also complain to a supervisory authority: in Israel, the Privacy Protection Authority. In the EU, the data protection authority where you live.

To stop using the Service, send /disconnect to the bot or run textmyworker disconnect. That removes your pairing, and you can then ask us to delete the rest.

9. Children

The Service is for people aged 18 and over. We don't knowingly collect data from children. If you believe a child has used it, contact us and we'll delete the data.

10. Changes to this policy

We'll post any update here with its effective date. For material changes, we'll let you know in advance in the chat or by email where we can.

11. Contact

Privacy questions and requests: eyal@textmyworker.com. More on how the Service works: How it works & your data.