Privacy Policy
Updated 19 November 2026
This policy
This policy tells you how personal data is collected, processed, and used when you use the Services. By using the Services, you agree to this policy together with the Terms of Service. It is the notice required by Article 8 of Taiwan’s Personal Data Protection Act when we collect personal data from you.
Who is responsible
Rick Weng, an individual in Taiwan, decides the purposes and means of using personal data to provide the Services. Contact hello@eisoptric.com.
Rick Weng owns the intellectual property and operates, maintains, and develops the Services.
What we collect
The categories follow the classification published for the Personal Data Protection Act. Identification data is category C001, which includes name, job title, and email address. Conversations, tool-call arguments, and files you choose to send may contain other categories. Which categories those are depends on what you submit.
The website at https://eisoptric.com has no forms and does not ask you for personal data. The page language is part of the address. The website does not use advertising cookies or a separate analytics product.
On the MCP console at https://console.eisoptric.com and the MCP backend at https://api.eisoptric.com, we process the account and the gateway records needed to run the service:
- Identity and account data, including name, email address, organization name if you create an organization account, role, and sign-in credentials. When you sign up, we email a verification code to the address you gave. Signing in from Eisoptric Workbench uses this same account.
- What you configure: members, permissions, agents, tool sets, policies and their versions, and which MCP servers a person may connect.
- Each tool call the gateway evaluates: the agent, the tool, the arguments, the policy version, the decision, the reviewer when there is one, and whether the call was executed.
- Upstream credentials you store in the vault, sealed so the gateway can make a call you have allowed. The console does not return the secret itself.
- Cost records, if you use cost tracking.
Eisoptric Workbench runs on your computer. Until it connects to our servers, agents, files, commands, chats, and model keys stay on that computer, and we do not receive them. When you sign in and use the Eisoptric Workbench backend, that backend — a server separate from the MCP backend — processes the App data it syncs and runs: agents, conversations, tasks, scheduled wakes, memories, and the MCP servers you attach in the App.
Downloads of Eisoptric Workbench and the source code are served by GitHub. If you donate through GitHub Sponsors, GitHub collects your payment details and shares with us what its Sponsors program shows, such as your GitHub username. GitHub processes those requests under its own terms.
Purposes and legal bases
We collect and use personal data for these specific purposes, as classified for the Personal Data Protection Act: contractual and similar relationships (code 069), customer management and service (code 090), information and database management (code 136), and information security (code 137).
Collection and use stay within what those purposes require, and must be honestly and reasonably connected to them (Articles 5 and 20). As a non-government party, we collect and process personal data because we have a contract or a similar relationship with you and maintain appropriate security measures, and because you consent by using the Services (Article 19, paragraph 1, subparagraphs 2 and 5).
Period, place, recipients, and method
We keep account data, console data, MCP backend data, and Eisoptric Workbench backend data while you use the Services. When the purpose ends, or you ask us to delete the data, we delete it or stop using it. We may keep what we still need to finish a request you already made, to resolve a dispute, or to comply with law (Article 11, paragraph 3).
The console, the MCP backend, and the Eisoptric Workbench backend are hosted on Google Cloud in Taiwan (asia-east1). The website is hosted by Cloudflare. Sign-up verification codes and account emails are sent through Resend. Eisoptric Workbench downloads and donations are handled by GitHub. A tool call is sent to an upstream MCP server only when your own configuration allows it. People in your organization see what their roles allow.
We do not sell personal data. We do not use it for advertising. Cloudflare, Resend, and GitHub may process the data they handle outside Taiwan, because that is how those services deliver the website, the email, the download, or the donation. If a competent authority restricts an international transfer under Article 21, we will comply with that restriction.
Google user data
You can connect Google services to the MCP backend: Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides, Cloud Run, Cloud SQL, and Memorystore for Redis. You start each connection and approve it on Google’s own sign-in page. Eisoptric asks each service only for the access its tools need, and you can see that access on Google’s consent screen.
Through that connection, Eisoptric receives an access token and a refresh token from Google, and the data a tool returns when an agent you connected calls it, such as a message, an event, a file, or a spreadsheet range. Eisoptric reads Google data only when such a call is made. Your organization’s policies and approvers decide whether a call runs.
Eisoptric uses Google user data only to carry out the tool calls you and your organization set up: it sends the request to Google and returns the result to the agent that asked. The tokens are sealed in the credential vault with ML-KEM-1024 and AES-256-GCM. The call’s arguments and Google’s response are recorded in your organization’s audit log, encrypted, so the people your organization lets review calls can see what ran. They are kept while your organization uses the Services, and deleted when you ask us to delete them or when the account is deleted.
- We do not sell Google user data, and we do not transfer it to anyone except to provide the tool call you asked for, for security reasons, or to comply with law.
- We do not use Google user data for advertising, including personalized, retargeted, or interest-based advertising.
- We do not use Google user data to develop, improve, or train generalized or non-personalized AI or machine-learning models.
- We do not let anyone at Eisoptric read Google user data, except with your permission for a specific item, when it is needed for security, such as investigating abuse, or to comply with law.
Eisoptric’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Removing a Google connection in the console deletes the tokens Eisoptric holds for it. You can also revoke Eisoptric’s access at any time at https://myaccount.google.com/permissions. To delete the audit records of past calls, email hello@eisoptric.com.
If you do not provide data
You choose what to provide. You can browse the website without providing anything. If you do not provide account information, you cannot use the console, the MCP backend, or the parts of Eisoptric Workbench that require sign-in. Eisoptric Workbench can still be used on your computer for functions that do not connect to our servers.
Your rights
Under Article 3 of the Personal Data Protection Act, you may ask to inquire or review, to receive a copy, to supplement or correct, to stop collection, processing, or use, and to delete. These rights cannot be waived in advance. Email hello@eisoptric.com. We may need to confirm that the request is yours. We will respond within the period the Act requires.
Security
Article 27 requires appropriate security measures to prevent personal data from being stolen, altered, damaged, lost, or disclosed. Upstream credentials in the MCP backend are sealed with ML-KEM-1024 and AES-256-GCM. No method of storage or transmission is perfectly secure.
Legal capacity
The Services are not directed at anyone who lacks the legal capacity to accept the Terms of Service. If we learn that we hold personal data from such a person without the consent the Civil Code requires, we will delete it.
Changes
We may update this policy by posting a new version on this page and changing the date above. If you have an account and a change materially affects how we use personal data, we will notify you by email or in the console before it takes effect. If you continue to use the Services after that date, you accept the update. If you do not, stop using the Services and you may ask us to delete your personal data.
Contact
Rick Weng
hello@eisoptric.com