Version 1, effective August 26, 2026 · Part of the Sqemes Terms and Conditions
This policy says what you may not do with Sqemes. It applies to everything you store, generate, publish or distribute through the service.
1. Content
You may not store, generate or distribute content that infringes copyright, trademark, trade secrets or any other third-party right · is unlawful or promotes unlawful acts · depicts the sexual abuse or exploitation of minors · harasses, threatens or defames a person, or incites violence or hatred against a group · is designed to deceive about its origin, impersonating a person or organisation or presenting fabricated records as genuine · violates the usage policies of the AI provider your request is routed to. Those policies apply to your request even though your contract for that key is with them and not with us.
2. Personal data belonging to other people
Sqemes is where a team keeps its working knowledge, and that knowledge often touches people. You are responsible for having a legal basis for whatever personal data you put into your workspace, including data in the files you upload.
You may not use Sqemes to profile individuals, to infer sensitive characteristics about them, or to make decisions with legal or similarly significant effects for a person without meaningful human review.
3. Skills, scripts and the marketplace
A skill is a folder, and it may contain executable files. Sqemes stores, versions and distributes them; your client runs them. That division of labour is deliberate, and it is why this section exists.
When you publish to the marketplace, you may not include:
- code that damages, disables or gains unauthorised access to any system;
- code that exfiltrates data — including anything that sends a workspace’s context, keys or file contents to a third party;
- code that fetches and executes further code from a remote address at run time. A skill must be what it appears to be when it is reviewed. Pulling an unpinned script at run time defeats review by design, and it is the most dangerous pattern this format allows;
- material you do not hold the rights to publish.
What review is and is not. Listings are reviewed before they appear, and we may decline or remove one. Review is not a security audit, and nothing about it should be read as one. Treat a downloaded skill the way you would treat any third-party code: read it before you run it.
Withdrawing a listing stops further distribution. It does not reach into copies other people have already taken.
4. The service itself
You may not resell, sublicense or provide Sqemes Cloud to third parties as a service of your own · circumvent quotas, credit limits, access controls or the subscription gate, or attempt to · access another workspace’s data or probe for a way to · automate the interface to a degree that degrades the service for others, or scrape it in bulk · use the service to build a competing product from our material.
Security research is welcome and is not covered by the two clauses above — report what you find to ufuk@neorebels.com and give us reasonable time to fix it before publishing.
5. Self-hosted instances
This policy governs Sqemes Cloud. If you run your own instance we have no contract with you about it and no access to it — the rules for its users are yours to set, and the responsibilities of an operator are yours to carry.
6. What happens if you breach this
We will normally contact you first and say what the problem is.
For a serious breach — malicious code, unlawful content, or an attack on the service — we may suspend access immediately and without prior notice, and remove the material. We will tell you what we did and why.
Suspension is not deletion. Your data remains available for export, on the terms in the subscription agreement.
7. Reporting
To report content or a listing that breaches this policy, write to support@sqemes.com. Tell us what you saw and where. We respond to every report; we do not promise a particular outcome.