Teasynaer

// legal

Acceptable Use Policy

Draft — pending review

Allotment Technology Ltd · Version 2026-07-03 · Not yet in effect — see draft notice above

This Acceptable Use Policy ("Policy") sets out the rules for using the Teasynaer website at teasynaer.dev and the Teasynaer live demo. By using the site or the demo, you agree to this Policy. If you do not agree, do not use them.

1. Who we are and what this covers

Teasynaer is operated by Allotment Technology Ltd, a company registered in England and Wales (company number 16925574), registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ. ICO registration: ZC092549. In this Policy, "we", "us" and "our" mean Allotment Technology Ltd, and "you" means anyone who visits the site or uses the demo.

You must be 18 or over to use the demo. This matches the eligibility requirement in our Terms of Use.

This Policy applies only to:

  • The site — the public marketing and documentation website at teasynaer.dev; and
  • The live demo — the hosted instance of the Teasynaer application that we run on our own infrastructure so that you can try it out.

This Policy does not apply to the self-hosted software. Teasynaer is open-source software licensed under the MIT licence. If you download, install and run Teasynaer on your own machine or servers, your use is governed by that licence, not by this Policy, and we do not process your data — it stays on your own systems.

2. The demo is shared, anonymous, and temporary

Please understand how the demo works before you use it:

  • No account, anonymous. The demo does not require sign-up, and sessions are anonymous. There is no sign-in or sign-out.
  • Shared. The demo is a single, shared instance. QA runs, uploads and other content you create may be visible to other people using the demo at the same time.
  • Wiped nightly. The demo is reset every night without notice. All QA runs, screenshots, recordings and other content are permanently deleted on reset. There is no backup, export or recovery.
  • No privacy or persistence. You should have no expectation of privacy, confidentiality or persistence when using the demo. Treat anything you put into it as public and disposable.

The demo exists to show what Teasynaer does. It is not a place to store anything you care about.

3. Do not upload real or sensitive data

Teasynaer lets you attach evidence to a QA run — screenshots and a screen recording — captured through your browser.

  • Capture is manual and permission-gated. Screen and screenshot capture only happens when you actively start it and grant your browser's permission. Nothing is captured automatically or in the background. You choose what is on screen when you capture.
  • There is no redaction. The demo cannot blur, mask or pixel-redact captured images or recordings. Whatever is visible when you capture is stored as-is.

Because the demo is shared and wiped nightly, and because captured media cannot be redacted, you must not upload, capture or enter real personal data or sensitive information into the demo. This includes, without limitation: other people's personal data; your own or others' credentials, passwords, API keys or tokens; financial, health or other special-category data; confidential business information; and anything covered by a duty of confidence or a non-disclosure agreement.

Use only dummy, synthetic or clearly non-sensitive test data. If in doubt, leave it out.

4. Acceptable use — what you must not do

When using the site or the demo, you must not:

  • Break the law or harm others. Use the site or demo for any unlawful, fraudulent, abusive, harassing, defamatory or otherwise harmful purpose, or in breach of any applicable law or regulation.
  • Upload prohibited content. Upload, capture, submit or link to content that is illegal, that infringes intellectual property or other rights, that is obscene, or that you do not have the right to share.
  • Upload real or sensitive personal data. As set out in section 3.
  • Test targets you are not authorised to test. Use the demo to run QA against, capture, scan, probe or record any website, system or service that you do not own or do not have explicit permission to test. The demo is for testing your own or authorised targets only — not for scanning, capturing or recording third-party sites without authorisation.
  • Attack or overload the instance. Attempt to gain unauthorised access to the demo, its infrastructure, the underlying systems or other users' sessions; break, bypass or test its isolation, authentication or security boundaries; probe for vulnerabilities without our written permission; or interfere with, disrupt, degrade or overload the service.
  • Exceed limits or automate abuse. Circumvent or exceed rate limits, quotas or other technical restrictions; or use bots, scrapers, scripts or other automated means to generate abusive traffic or load.
  • Misuse the service generally. Use the site or demo in any way that could damage, disable or impair it, or that is otherwise inconsistent with this Policy.

This list is not exhaustive. We may treat conduct as a breach even where it is not specifically listed, if it is plainly abusive or harmful.

5. Enforcement

The demo is a shared resource offered in good faith, and we protect it actively. To keep it available and safe, we may, at our discretion and without notice or liability:

  • reset the demo, or delete any session, QA run or uploaded content, at any time (this happens nightly in any case, and may happen sooner);
  • rate-limit, throttle, suspend or block access, including by blocking IP addresses or ranges;
  • remove or disable access to any content that breaches this Policy; and
  • withdraw, restrict or change the demo, in whole or in part.

Where we reasonably believe unlawful activity has taken place, we may preserve relevant logs and report it to, and cooperate with, law-enforcement or other authorities. We do not have to warn you before taking any of these steps.

6. Availability — the demo is provided "as is"

The site and the demo are provided "as is" and "as available", without warranties of any kind, whether express or implied, including any warranty of uninterrupted operation, availability, or fitness for a particular purpose. We may change, rate-limit, suspend or withdraw the demo at any time without notice. We do not guarantee that the demo will be available, that content will persist (it will not — see section 2), or that it will be free of faults. To the maximum extent permitted by law, we are not liable for any loss arising from your use of, or inability to use, the site or demo, or from the deletion of anything you put into it. Nothing in this Policy limits any liability that cannot be limited under applicable law, including your rights under mandatory UK consumer protections where they apply.

7. Reporting abuse

If you see something in the demo that breaches this Policy, or you believe your data has ended up in the demo, contact us at the address in section 9 (Contact). Because the demo is wiped nightly, the fastest remedy for unwanted content is usually the next reset, but we will act sooner where appropriate.

8. How this fits with our other policies

  • Our Privacy Notice explains what limited data we process through the site and demo, and your rights under UK GDPR.
  • Our Cookie Notice explains that we set strictly-necessary cookies only (such as the demo session) and set no advertising or third-party tracking cookies. Product analytics is planned but not yet live; when it launches it will use PostHog (EU region) as a third-party sub-processor on a cookie-based, consent-banner model.
  • The MIT licence in the Teasynaer repository governs the self-hosted software (see section 1).

We may also publish separate Terms for teasynaer.dev. If we do, and they conflict with this Policy, the Terms prevail for the matters they cover.

9. Contact

Allotment Technology Ltd 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ hello@allotmentology.tech

10. Governing law

This Policy is governed by the laws of England and Wales, without prejudice to mandatory consumer protections where applicable.

11. Changes to this policy

We may update this Policy. Material updates will be reflected by a new version, effective date, and changelog entry.