Terms of use for cmsspot
Last updated October 3, 2026
cmsspot is a tool for editing the content of websites you own or have the right to edit. By creating an account and connecting a website, you accept these terms.
1. Use at your own risk
You use cmsspot at your own risk. cmsspot writes the changes you make straight to the server you connect. You are responsible for the content of your changes and for having the right to edit the website you connect.
cmsspot is provided "as is", without any warranty that the tool is error-free, always available or fit for a particular purpose. cmsspot is not liable for loss of data, lost income, downtime or any other direct or indirect loss arising from its use. You are encouraged to keep a working backup of your website.
2. Sensitive files must be excluded
To edit your website, cmsspot pulls a copy of the relevant files onto its own server. It is your responsibility to make sure that files with passwords, database credentials, API keys or other sensitive or personal data are not pulled in.
When you connect a site, use the "Files cmsspot must never fetch, show or edit"
field to list the files or folders to keep out. You should do this when you
connect the site. cmsspot never fetches the listed files, never shows them and
never writes to them. Hidden files such as .env and
.htpasswd are always excluded automatically.
The strongest protection is to connect with a user that has no access to the sensitive files at all. The exclusion list is an extra layer on top of that. If you fail to exclude a sensitive file, that is at your own risk.
3. Your account and access
Login happens through a one-time link to your email, with no password. You are responsible for access to your own inbox. If you give colleagues access to a site, you are responsible for who you invite and for what they do on that site.
4. Your data and your website
You own your website and your content. cmsspot creates nothing on your server beyond the files you edit or upload yourself, and the backups of the edited files that are kept on cmsspot's own server. If you delete a connection, the local copy at cmsspot is removed.
5. AI access and tokens
You can give an AI assistant access to a site by creating a token. A token is like a key: anyone who holds it can do what the token allows until you revoke it. You are responsible for keeping tokens secret, for the level of access you choose, and for what the assistant does with it. Review changes made through AI access as you would review a colleague's. Hide files you do not want an assistant to see, and revoke tokens you no longer use. cmsspot logs every call made with a token.
6. The build guide
The public build guide at /build is documentation delivered through an MCP server. It is free to use, provided "as is", and may change or be withdrawn at any time. Code you create by following it is yours, and so is the responsibility for it. Automated use is limited per address so the service stays available to everyone.
7. Responsible use
You may not use cmsspot to edit websites you have no right to, or to store or distribute illegal content. You may not try to reach other users' sites or data, probe the service for weaknesses without telling us, or flood it with automated requests. cmsspot may close an account that is used in breach of these terms.
If you find a security issue, write to us before you publish it. We take reports seriously and reply quickly.
8. Changes to the terms
These terms may change. Significant changes will be announced on this page. Continued use after a change counts as acceptance of the updated terms.
9. Contact
Questions about the terms can be sent to contact@cmsspot.com.