Reshi privacy policy
Effective October 26, 2026
This policy explains what Reshi handles, what it keeps, and why. Reshi is operated by Justen Thongkhanh.
The short version
- Your files and messages stay in your own storage. Reshi’s hosted connector forwards approved requests between your computer and your AI provider. It does not store that content.
- Reshi keeps small operational records to route requests, protect the service, fix failures and give support.
- The Reshi panel sends a few anonymous usage events to help improve Reshi. They carry no content and no identity, and you can turn them off.
- Reshi does not sell your data or use your Room content to train AI models.
1. Room content
Room content means:
- files stored in a Room, and Room and file names;
- handoffs and messages between the members of a Room;
- prompts, instructions and responses saved in the Room; and
- reviews and their artifacts.
Room content stays in the storage service you chose (today, your Dropbox). Reshi’s hosted connector does not collect or store it.
When you approve an AI action, the hosted connector processes the request and the answer only long enough to pass them between your computer and the AI provider. It does not write that content to its database, logs, analytics or backups.
2. Reshi on your computer
Reshi installs a small program on your computer. It reads and writes your Room in your storage service on your behalf, and keeps on your computer the sign-ins it needs: your storage sign-in, and an open-model key if you add one. These stay on your computer, protected by Windows; Reshi does not send them to its hosted connector.
3. Operational records
Reshi keeps the smallest practical set of records needed to run the hosted connector. These may include:
- the time of a request;
- connector, request and connection identifiers;
- the name of the Reshi tool called;
- whether the request succeeded or failed;
- the number of bytes sent and returned;
- a salted hash standing in for the Room, never its name or raw id;
- one-way digests of the access tokens the connector issues;
- which AI vendor a sign-in belongs to (Claude, ChatGPT or Gemini);
- rate-limit, duplicate-request and security events; and
- a support reference when an error occurs.
Network providers may briefly process information such as an IP address to deliver and protect a request. Operational records never contain Room content.
4. Anonymous usage events
The Reshi panel sends a short list of anonymous usage events, so that we can see whether setup works and where people get stuck. The full list is shown in the panel’s settings, next to the switch that turns them off:
- the panel was opened (and whether you had opened it before);
- this computer was approved;
- storage was connected (which service);
- a Room became ready (new or existing);
- an AI was added (which AI and which job);
- an AI was connected (which AI and how);
- a handoff was sent or received;
- setup stopped (which kind of stop); and
- usage events were turned off (the last event sent).
Each event carries only a random install id (made on your computer, which you can reset in settings), the extension version and the time to the minute. No Room or file names, no message text, no email, no account, and no device fingerprint. The events travel from the panel to Reshi on your computer, then to Reshi’s hosted connector, which records them in the same operational log as section 3.
Usage events are on by default. Turn them off at any time in the panel’s settings.
5. Connection and security records
To keep a computer linked, Reshi stores a connector record and one-way digests used to check connection secrets and tokens. A digest can be compared but not turned back into the original. Reshi’s hosted connector does not store your AI or storage account passwords or keys.
6. Why Reshi uses this information
Reshi uses operational records and usage events only to:
- deliver and route the actions you request;
- prevent duplicate, abusive or runaway requests;
- apply security and usage limits;
- diagnose errors and outages;
- answer support requests; and
- understand, in aggregate, whether setup works and how reliable the service is.
Reshi does not use any of it for advertising, does not sell or rent it, and does not use Room content to train AI models.
7. How long Reshi keeps it
- Operational records and usage events: no more than 14 days, then deleted.
- Records linked to an open support request: while the request is open.
- Security records: longer when reasonably needed to investigate abuse or protect users.
- Connector records: while the computer stays linked.
- Token digests: only for the token’s life, then deleted on expiry, on disconnect or when the computer is unlinked.
- Payment and business records: as required for accounting, tax, fraud prevention and legal duties.
Reshi will announce a material change before keeping anything longer for a new purpose.
8. Other companies
The AI and storage services you connect receive the information needed to do what you ask; their own terms and privacy policies apply. Reshi does not control whether an AI provider keeps what you send it.
Reshi uses infrastructure providers to host, secure and monitor its connector. They may process operational records only to provide those services.
Reshi may disclose information when the law requires it, to protect users or the service from a serious threat, or as part of a business transfer. If ownership changes, this policy keeps applying unless users get clear notice of a change for the future.
9. Your choices
You can:
- disconnect any AI, or this computer, from the Reshi panel;
- turn off usage events in the panel’s settings, and reset the install id;
- delete Room content through your storage service;
- ask what operational records Reshi links to your connector; and
- ask Reshi to delete operational records it is not required to keep.
Disconnecting an AI does not delete what that AI already received; ask that provider about its deletion options.
10. Security
Reshi uses access controls, short-lived and narrowly scoped credentials, rate limits and limited retention to reduce risk. No system can promise perfect security. If a breach requires notice, Reshi will notify affected users as the law requires.
11. Children
Reshi is not directed to children under 13 and does not knowingly collect their personal information. If you believe a child gave Reshi personal information, contact us and we will remove it.
12. Changes and contact
Reshi may update this policy as the product changes. Material changes will be posted here with a new effective date and apply going forward.
Contact: support@getreshi.com, Justen Thongkhanh.
Reshi is offered in worldwide.