Terms & Conditions
These Terms & Conditions (“Terms”) govern your use of YOLO Cloud (the “Service”), provided by Code Snippets B.V. (“we”, “us”, “our”), a company registered in the Netherlands. YOLO Cloud is a Code Snippets product. It includes tools to manage WordPress sites that run the YOLO plugin, and YOLO CMS, which lets an AI you connect build and run websites for you. By accessing or using the Service you agree to these Terms. If you do not agree, do not use the Service.
1. The Service and your account
Subject to these Terms and any applicable plan, we grant you a non-exclusive, non-transferable right to use YOLO Cloud to manage WordPress sites you own or operate, and to build, publish and run websites with YOLO CMS. All intellectual property in the Service remains ours or our licensors’. You are responsible for keeping your account credentials secure and for activity under your account, including by people you invite to your team.
2. Managing WordPress sites (please read)
YOLO Cloud connects to your WordPress sites through a secret token and can read and change them and, with the code or install capabilities, run code on them. You are responsible for how it is used:
- Connect only sites you control. Only connect WordPress sites you own or are authorised to manage.
- Use at your own risk and keep backups. The Service can create, modify and delete content, settings, code and files on your sites. Our snapshots, backups and recovery tools are provided to help, not as a guarantee: keep your own independent backups too.
- Your token is a credential. Tokens are scoped and revocable; keep them secret and revoke them if exposed. You are responsible for all actions taken through your tokens.
- Your AI, your output. The AI Bridge and proposed fixes can be wrong. You are responsible for reviewing their work before relying on it, especially for changes to a live site.
- Code and installs. Writing code and installing plugins or themes let the Service run arbitrary code on your site. They are offered, ticked, when you approve a site’s connection (untick them if you don’t want them) and can be switched on in the site’s wp-admin. If a site has them, you accept the additional risk that running arbitrary code entails.
- Compliance. You must use the Service lawfully and in line with your hosting provider’s and any third party’s terms.
3. Websites built with YOLO CMS
A YOLO CMS website is published on the internet under an address we provide or a domain you connect. Whoever builds it, the website is yours, and so is the responsibility for it:
- You are the publisher. You are responsible for everything on your website, including what your AI writes, the pictures it uses, and anything your visitors add to it. Check your website before you publish it, and keep it accurate and lawful.
- Your visitors’ data. You decide what your website collects from its visitors, and you are the controller of that personal data. You are responsible for telling visitors what you collect and why (a privacy notice), for having a lawful basis, for asking consent where the law requires it (for example before analytics), for answering their requests, and for choosing how long you keep their data. A privacy notice YOLO CMS drafts for you is a starting point, not legal advice.
- Your AI app. When you connect an AI app to YOLO CMS, it can read and change your websites with the access you approve. What it does through that connection is done on your behalf. Your use of that app is governed by its provider’s terms. You can see and disconnect connected apps at any time.
- Members, bookings and visitor content. If your website lets visitors make accounts, book, post listings or upload photos, you are responsible for the rules of your website, for dealing with your visitors (including cancellations and complaints), and for removing unlawful content when you become aware of it.
- Emails to visitors. Your website may email only visitors who have dealt with it (for example a booking confirmation or a password link). Mail sent through our mail service is subject to daily limits, and we may pause sending for a website whose mail bounces, is reported as unwanted, or breaks these Terms. If you connect your own email account, you are responsible for it.
- Payments. If you connect your own Stripe account to take payments, you are the seller: prices, refunds, taxes and your obligations to buyers are yours, and Stripe’s terms apply between you and Stripe. We are not a party to those payments.
- Your domain. You may connect only a domain you own or are authorised to use.
- Pictures. Stock pictures and pictures made with your own keys are subject to their providers’ licences, including any credit they require.
- Versions and backups of your website are kept to help you, not as a guarantee.
4. Personal data we process for you
Where we process personal data in your websites (your YOLO CMS websites’ visitor data, and the backups of your WordPress sites) we do so as your processor. We will: process it only to provide the Service, on your instructions as given through your use and settings of the Service; keep it confidential and limit access to people who need it; protect it with appropriate security measures; use only the sub-processors listed in our Privacy Policy, which we will update before adding new ones; help you answer your visitors’ requests and meet your own obligations, as far as the Service allows; tell you without undue delay if we become aware of a breach affecting it; and delete it when you delete it or close your account, except the backups of a deleted YOLO CMS website (including a final backup taken just before it is deleted), which we keep for 30 days so that a mistaken deletion can be undone if you ask us, and then delete, and except where the law requires us to keep it. Members’ photos and design preview pictures are deleted with the website and are not in its backups. The backups of a website deleted before 17 October 2026 are kept until you ask us to delete them. If you need a separate data processing agreement, contact us.
5. The YOLO Sentinel Hive
The YOLO Sentinel Hive helps sites recognise known attackers. Where your workspace has the hive and you switch on sharing with the hive in a site’s Sentinel settings, that site reports the addresses of visitors Sentinel judged to be attacking it. YOLO Cloud scores each address across independent site owners and sends a watch list of high-scoring addresses to the sites taking part. Your workspace’s own sites also share what they detect with each other, on a list that goes only to your workspace’s sites, and a site that moves to another workspace is sent a fresh list. An address that fewer than two checked owners have reported reaches other workspaces’ sites only if one of those owners’ workspaces has passed our trust check (through its plan or our own approval) and their site has earned enough trust, from how long it has been connected and how its reports have held up. Its score is then capped at 69, which on its own is below the scores at which Sentinel slows a visitor down or blocks them. Section 4 of our Privacy Policy says what is shared and how long it is kept.
- What you agree to. Switching sharing on for a site means you agree to share its reports of attackers with the hive, and to receive the hive’s watch list on that site.
- Tell your visitors. Your site’s own privacy notice must say that security data, such as the addresses of visitors who attack the site, may be shared with a security network.
- Honest reports only. You must not make, or cause, false or malicious reports, and you must not try to raise or lower any address’s score by other means.
- Your site, your settings. What your site does with the watch list is set by you in Sentinel: for example, asking a visitor to show they are a person, slowing them down or, only if you allow automatic blocks, blocking them for a time. You are responsible for the actions your site takes.
- Update signals. Where your site’s Sentinel settings allow it, the site also reports when a plugin or theme begins behaving in a new way soon after an update (for example contacting a new outside domain), so that we can spot a compromised update across many owners’ sites. A person on our team reviews each such alarm before anyone is told. If we confirm one, we tell the people who receive security alerts for each workspace with a site running that version (for a theme, the sites that reported it), and may tell its author and WordPress.org. An alarm is our view of a risk, not a finding that the plugin or theme or its author did anything wrong. Section 4 of our Privacy Policy says what a signal holds.
- As is. The watch list is provided as is. We do not guarantee that it is complete or accurate, or that every address on it belongs to an attacker.
- We may pause or stop it. We may pause the hive, set aside a site’s reports (quarantine them), or stop the hive for a site or for everyone, at any time.
- Switching off. If you switch sharing off for a site, or your workspace no longer has the hive, we stop collecting the site’s reports and sending it the watch list, and we delete the reports we hold from it: usually soon after, and otherwise at the daily clean-up once 7 days have passed since we last received them, and never later than 30 days after we first received them. Other hive records are kept for the periods in our Privacy Policy.
For the hive’s data, Code Snippets B.V. is the controller, not your processor, so section 4 of these Terms does not apply to it.
6. Price and payment
The Service is currently provided without charge. If we introduce paid plans, we will tell you the price and terms in advance, and you will not be charged unless you choose a paid plan. Features and limits of free use may change.
7. Acceptable use
You must not use the Service, or any website built with it, to: break the law or infringe others’ rights; publish content that is unlawful, defamatory, hateful, that sexualises minors, or that incites violence; impersonate anyone or mislead people about who you are; collect passwords, payment details or other personal data under false pretences; send spam; distribute malware or run phishing; sell goods or services that are illegal where they are offered; attack, overload, probe or gain unauthorised access to any system; resell, scrape or attempt to replicate the Service; or share credentials to circumvent plan limits. We may apply reasonable technical limits and may change them.
8. Third-party services
The Service relies on third parties, including the providers listed in our Privacy Policy (for example Anthropic and OpenAI for AI features, Cloudflare and Hetzner for infrastructure), the AI app you connect, your own WordPress hosting, and, if you connect them, your own Stripe and email accounts. Your use of those is also governed by their terms, and we are not responsible for their acts or omissions.
9. Disclaimers
The Service is provided “as is” and “as available”, without warranties of any kind, whether express or implied, to the maximum extent permitted by law. We do not warrant that the Service will be uninterrupted or error-free, that work done by AI will be correct, or that it will recover or preserve any particular data.
10. Limitation of liability
To the maximum extent permitted by law, Code Snippets B.V. is not liable for any indirect, incidental or consequential loss, or for loss of data, profits or business, arising from your use of the Service. Nothing in these Terms limits liability that cannot be limited by law.
11. Indemnity
You agree to indemnify us against claims, losses and costs arising from your misuse of the Service, the content of your websites, your breach of these Terms, or your violation of any law or third-party right.
12. Suspension and termination
You can stop using the Service and delete your websites at any time; to delete your account, contact us. We may suspend or terminate accounts that breach these Terms or that pose a security or legal risk. We may also take a website offline (showing a notice in its place), stop it from sending email, or remove content from it, if it breaches these Terms, if we receive a credible notice that it is unlawful, or to protect visitors, other customers or the Service. Where we can, we will tell you first and give you a chance to put things right.
13. Changes to these Terms
We may update these Terms; we’ll change the date above when we do and, for material changes, tell you in the app.
14. Governing law
These Terms are governed by the laws of the Netherlands.
15. Contact
Questions about these Terms? Email [email protected].