Who is responsible
Rethread is run by Nash T. Golosino, its founder, who is also responsible for privacy (the data protection officer) during the pilot. Contact: [email protected].
What Rethread reads
- Your Google account's name and email address, when you sign in with Google. Rethread never sees your Google password.
- The files in the Drive folders you choose, and only those. Rethread asks Google for read-only access to Drive. It cannot change, move, rename, share or delete any of your files, not even by mistake: Google does not give it that permission. You can leave out any file or folder, and Rethread then stops reading it and removes what it kept of it.
- The comments in those files, with their replies. The people who comment are shown by a name Rethread gives them; their real names and email addresses are never stored or shown.
Rethread does not read your email or your calendar during the pilot.
What Rethread keeps, and for how long
| What | Why | How long |
|---|---|---|
| Your name and email address | To sign you in | Until you delete your account |
| Google's access to your Drive (a token), encrypted twice | To read your folders while you are away | Until you disconnect Google or delete your account |
| The text of each file you connected, split into sections, and the version before it | To see what changed | While the file is connected; older versions after 30 days |
| What Rethread worked out from your files: summaries, projects, tasks, checkpoints, deadlines, and the short excerpts that show where progress came from | The product itself | Until you delete them or your account |
| Comments in your files, and the names Rethread gives commenters | To follow requests and questions | While the file is connected; the names until you delete your account |
| Your handoffs and recaps, your week's thread, your settings | The product itself | Until you delete your account |
| Activity: what Rethread read and did for you, with the time | Your own record | 12 months |
| A record of each AI request: which step, how many words, the cost, whether it worked. Never the content | Cost and budgets | 30 days |
| A record of each email Rethread sent you: when, and whether it arrived. Never the content | Delivery | 30 days |
| Measurements of how well progress was detected: states, identifiers and scores. Never your content | To check Rethread's own accuracy | Kept |
| Backups of the database | Recovery after a failure | 7 days |
- Your name and email address
- Why: To sign you in
- How long: Until you delete your account
- Google's access to your Drive (a token), encrypted twice
- Why: To read your folders while you are away
- How long: Until you disconnect Google or delete your account
- The text of each file you connected, split into sections, and the version before it
- Why: To see what changed
- How long: While the file is connected; older versions after 30 days
- What Rethread worked out from your files: summaries, projects, tasks, checkpoints, deadlines, and the short excerpts that show where progress came from
- Why: The product itself
- How long: Until you delete them or your account
- Comments in your files, and the names Rethread gives commenters
- Why: To follow requests and questions
- How long: While the file is connected; the names until you delete your account
- Your handoffs and recaps, your week's thread, your settings
- Why: The product itself
- How long: Until you delete your account
- Activity: what Rethread read and did for you, with the time
- Why: Your own record
- How long: 12 months
- A record of each AI request: which step, how many words, the cost, whether it worked. Never the content
- Why: Cost and budgets
- How long: 30 days
- A record of each email Rethread sent you: when, and whether it arrived. Never the content
- Why: Delivery
- How long: 30 days
- Measurements of how well progress was detected: states, identifiers and scores. Never your content
- Why: To check Rethread's own accuracy
- How long: Kept
- Backups of the database
- Why: Recovery after a failure
- How long: 7 days
Rethread's own operating logs hold identifiers, counts and error types, never the content of your files.
If you ask for an invitation on the website, Rethread keeps your email address, what you said you work on, and that you said you are 18 or older, for 90 days, or until you are invited. To slow down automated sending, the form counts requests from each network for 10 minutes, in memory only, by a scrambled fingerprint of the network's address; that count is never stored.
Cookies. Rethread sets a cookie that keeps you signed in (30 days from your last visit), and one that remembers your choice of light or dark theme if you make one. There are no advertising or tracking cookies, and no outside analytics scripts.
Measuring how Rethread is used, only with your consent
If you tick the box during setup, or turn the switch on in Settings, Rethread also counts:
- when you open a handoff or a recap;
- when you use Check progress;
- how many tasks you finish each week;
- how many questions in your Inbox you answer.
These counts are seen by the people running Rethread only as totals across at least five accounts, never as yours alone. You can see your own. You can turn this off at any time in Settings; Rethread then stops counting. Without your consent none of this is recorded. The accuracy measurements above are kept for every account, because they are how Rethread checks that it detects progress correctly; they hold no content.
Why Rethread uses your information
Only to provide what you see in Rethread: reading your files, keeping your tasks and progress, writing your handoff and recap, and, if you turn them on, emailing them to you. Your information is never sold, never used for advertising, and never shared with anyone except the services below, which Rethread needs to work. The legal basis is your consent, given when you join the pilot, and the agreement to provide the service you asked for.
The AI model
To understand your files and judge whether a change is progress, Rethread sends the relevant text to Anthropic (the company that makes Claude), through its commercial API. Anthropic's terms say that it does not use this content to train its models, and that it deletes it within 30 days, except content its safety systems flag, which it may keep for up to 2 years. Rethread sends text only to AI providers whose terms forbid training on it.
A smaller model that compares meaning runs inside Rethread's own server; no other company receives your content for it.
Where your information is processed
Rethread's servers and the services it uses are outside the Philippines. The law allows this; Rethread remains responsible for your information.
| Service | What it does | Where |
|---|---|---|
| Supabase | The database, and its backups | Singapore |
| Railway | Runs Rethread's server and its background work | Singapore |
| Anthropic | The AI model | United States |
| Resend | Sends the emails you turn on | Japan (Tokyo) |
| Cloudflare | The domain, its secure connections, and forwarding mail sent to [email protected] | Worldwide network |
| Signing in, and reading the Drive folders you choose | Worldwide |
- Supabase
- What it does: The database, and its backups
- Where: Singapore
- Railway
- What it does: Runs Rethread's server and its background work
- Where: Singapore
- Anthropic
- What it does: The AI model
- Where: United States
- Resend
- What it does: Sends the emails you turn on
- Where: Japan (Tokyo)
- Cloudflare
- What it does: The domain, its secure connections, and forwarding mail sent to [email protected]
- Where: Worldwide network
- What it does: Signing in, and reading the Drive folders you choose
- Where: Worldwide
Who can reach what Rethread keeps
No feature of Rethread lets the people who run it open your documents, tasks, progress or comments. The admin console shows only accounts, invitations, usage, costs and the health of the service. Problems are investigated with test data and logs that hold no content.
The stored text can be read by whoever holds the production database's login, as with any hosted database. That login is held by one named person, Nash T. Golosino, is used only to run the service, and is never used to open the tables that hold your content. The database provider's table editor is not used on production.
Emails
The morning handoff and the evening recap can be emailed to you; both are off until you turn them on. They contain project and task titles, deadlines and a link, and no text from your documents.
Your rights
You can, at any time, in Rethread itself:
- see what Rethread keeps, and export it as one file (Settings, Privacy and data); the export leaves out only the accuracy measurements, which hold no content of yours;
- correct anything it got wrong: rename, edit or delete projects, tasks and checkpoints, and correct progress;
- leave out any file or folder, which removes what Rethread kept of it;
- disconnect Google, which revokes Rethread's access and removes the copies of your files;
- delete your account, which removes everything Rethread keeps for you from the live service at once, and from the backups within 30 days.
You can also write to [email protected] for anything else, or complain to the National Privacy Commission (privacy.gov.ph).
If something goes wrong
If a breach puts your information at risk, Rethread will tell you and the National Privacy Commission within 72 hours of learning of it, and say what happened and what you can do.
Google user data
Rethread's use of information received from Google follows the Google API Services User Data Policy, including its Limited Use requirements: it is used only to provide the features you see, never to train general AI models, never sold or used for advertising, and not read by people except with your consent, for security, or where the law requires.
Changes
If this notice changes, the new version is posted here with its date, and you are told before it applies.