.svg?fit=max&auto=format&n=RaTUOQa09vPhW7_D&q=85&s=368f39de7ecc6605f73c43c2017546a3){kind=logo}
.svg?fit=max&auto=format&n=RaTUOQa09vPhW7_D&q=85&s=01a6eb27b4db3af8a1d5557525c579d3){kind=logo}
Introduction
TypingMind is committed to the security of our users and their data. This policy gives security researchers clear guidelines for finding vulnerabilities in our systems and tells you how we want you to report them to us. This policy describes which systems and types of research it covers, how to send us vulnerability reports, and how long we ask you to wait before you disclose a vulnerability publicly. We encourage you to contact us to report potential vulnerabilities in our systems.Authorization
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and TypingMind will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.Guidelines
Under this policy, “research” means activities in which you:- Notify us as soon as possible after you discover a real or potential security issue.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
- Use only accounts, team workspaces, and installations that you own or have explicit permission to test. Do not access or change the data of other users.
- Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
- Do not submit a high volume of low-quality reports.
Test methods
The following test methods are not authorized:- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data. This includes automated scans that send a high volume of requests.
- Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
- Spam or abuse of features that send email or messages to other people.
Scope
This policy applies to the following systems and services:typingmind.comwww.typingmind.comcloud.typingmind.comeu.typingmind.comapi.typingmind.comapi.eu.typingmind.comcustom.typingmind.com*.typingcloud.com
- Any subdomain of
typingmind.comthat is not listed above, such as our documentation, status, trust, feedback, store, and checkout sites. Third-party vendors operate these sites. - Team workspaces on custom domains or self-hosted installations that our customers operate. Report issues in the software itself to us, but do not test against customer systems.
- Plugins, agents, MCP servers, and other content that users create and share.
- Third-party services that TypingMind connects to. Report vulnerabilities in vendor systems directly to the vendor, according to their disclosure policy (if any).
Findings we do not accept
These findings usually have no security impact. We will close them unless you show a clear exploit with real impact:- Missing security headers, or clickjacking on pages with no sensitive actions
- Missing or weak SPF, DKIM, or DMARC records
- Self-XSS, or attacks that need the victim to paste code into their own browser
- Lack of rate limiting on endpoints that do not affect security
- Software version disclosure or banner information
- Issues that affect only outdated or unsupported browsers
- Results from automated scanners without a proof of concept
- AI model output issues (such as jailbreaks or incorrect answers), unless they cause data access or actions across accounts
Reporting a vulnerability
Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely TypingMind, we may share your report with the affected vendor or with a coordinating organization such as the Cybersecurity and Infrastructure Security Agency (CISA), where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission. We accept vulnerability reports via security@typingmind.com. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days. We do not support PGP-encrypted emails. Do not include sensitive data that you found (such as other users’ data or credentials) in your report. Describe the data instead, and we will ask for more details if we need them. By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against TypingMind related to your submission.What we would like to see from you
In order to help us triage and prioritize submissions, we recommend that your reports:- Describe the location the vulnerability was discovered and the potential impact of exploitation.
- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
- Be in English, if possible.
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.- Within 3 business days, we will acknowledge that your report has been received.
- To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
- We will maintain an open dialogue to discuss issues.