ShedTerms of Service

Terms of Service

Effective date: August 1, 2026

Last updated: August 28, 2026

Summary

Here's the short version, in plain language. It's a summary, not the contract — the numbered sections below are what actually binds us both.

  • What this covers. Everything Shed offers: the site, the CLI, the API, and the build and hosting service.
  • Who can use it. Anyone 16 or older who can enter into a contract. If you're signing up for a company, you need the authority to commit that company.
  • Your code stays yours. We don't take ownership of anything you upload, build, or deploy. We only get the rights we need to actually run it for you and serve it to your users.
  • Your app is your responsibility. What it does, who uses it, what it stores, and whether it's legal — that's on you, not us.
  • Acceptable Use. No illegal activity, malware, spam, fraud, crypto mining, breaking into other people's systems, evading limits, or infringing anyone's rights. Section 7 is the full policy.
  • Things break. Builds fail, deployments restart, services go down. There's no uptime guarantee. Keep your own copies of anything you'd hate to lose.
  • Paid plans renew automatically at the price shown when you bought them, until you cancel. You can cancel any time from your account.
  • Our liability is capped — see Section 17 for the number.
  • If we ever disagree, English law applies and the English courts hear it. If you're a consumer you can also sue where you live, and nothing here removes the rights your local law gives you.

1. This agreement

These Terms of Service (the "Terms") are a contract between you and REDRESS SPACE LTD, a company registered in England and Wales with its registered office at Level 30, The Leadenhall Building, 122 Leadenhall Street, City of London, London EC3V 4AB, United Kingdom, trading as Shed. When we say "Shed," "we," "us," or "our," we mean that company.

They cover everything we offer: the website, the command-line tools, the APIs, the software, the build and hosting service, the documentation, and anything related. We call all of that the "Service."

You agree to these Terms, including the Acceptable Use Policy in Section 7, and to our Privacy Policy when you create an account or use the Service. If you don't agree, you can't use it.

Signing up for a company? Then you're confirming you have the authority to commit that company, and "you" means the company as well as you personally.

If you've signed a separate agreement with us, that one wins wherever the two conflict.

2. Words we use

"Affiliate" — any entity that controls a party, is controlled by it, or sits under the same control. Control means owning more than 50% of the voting interests or having the power to direct management.

"Authorized User" — anyone, or any automated agent or tool, you let into the Service through your account or credentials. It doesn't matter whether you set up that access deliberately.

"Customer Material" — defined in Section 6.

"End User" — anyone, or anything, that uses an application you build, deploy, or run on Shed.

"Third-Party Service" — defined in Section 9.

"Usage Data" — operational and telemetry data we generate from running the Service: performance metrics, build and request timings, error rates, resource consumption, feature usage, and abuse signals. Usage Data describes how the Service is behaving. It isn't your code, your configuration, your application data, or the contents of your logs.

3. Who can use Shed

You need to be at least 16 and legally able to enter a contract. If your local law sets a higher minimum, that one applies. If you're under the age of majority where you live, a parent or guardian has to agree to these Terms for you.

You also can't use Shed if the law says we can't serve you, including trade sanctions and export-control rules. By using the Service you're confirming that you aren't located in, resident in, or organised under the laws of a country or territory under comprehensive sanctions, and that you don't appear on a UK, UN, EU, or US restricted-party or sanctions list.

Children

We don't knowingly collect personal information from anyone under 16. If you're under 16, please don't sign up, use the Service, or send us personal information. If we find out we're holding information from someone under 16 without a valid basis, we'll delete it. If you think a child has given us personal information, email support@shed.codes.

4. Your account

Some parts of Shed need an account. Keep the information on it accurate and up to date.

You're responsible for:

  • keeping your passwords, tokens, API keys, and deployment credentials safe;
  • everything done through your account, including by Authorized Users and automated agents, whether or not you specifically approved the action; and
  • telling us at support@shed.codes as soon as you think your account or credentials have been compromised.

Don't share, sell, or hand off your account in a way that hides who's really using it, and don't get into anyone else's account without their permission.

Connecting other accounts

You may be able to sign in through, or deploy from, another service such as a source-code host. When you connect one, you're giving us permission to access, store, and use whatever information and permissions that account exposes so the features you've turned on can work. You decide how much access that is through the other service's own settings, and you can revoke it there whenever you like — though parts of Shed may stop working if you do. That service's own terms and privacy practices still apply to your use of it.

Messages from us

We'll send you things like confirmations, invoices, security alerts, incident notices, deprecation warnings, and changes to these Terms. These come with the Service and you can't turn them off while your account is open, though you're free to close the account. Marketing email is separate and you can unsubscribe from it any time. If you opt into text messages, your carrier's rates are on you.

5. What Shed does, and what it doesn't promise

Shed helps people and software agents prepare, build, deploy, run, and share software. That can include project configuration, moving source code around, build systems, runtime environments, generated domains, logs, storage, databases, scheduled jobs, and hooks into third-party infrastructure.

We'll add, change, limit, and retire features over time. If we're about to make a change we expect will substantially cut the core functionality of something you're paying for, we'll give you at least 30 days' notice — unless a security, legal, or operational emergency makes that impossible. If a change like that genuinely hurts you, you can cancel the affected paid Service and we'll refund the unused part of what you've prepaid.

Preview, alpha, beta, and early-access features are exactly what they sound like: unfinished. They can change without notice, break, or lose data. They come with no commitments at all and you use them at your own risk.

We can't promise any given deployment will build, stay up, hit a particular level of performance, or work with every project, dependency, agent, cloud, or runtime.

Uptime

There's no uptime commitment, no SLA, and no service credits. We work hard to keep Shed up and to tell you what's going on during incidents, but we don't guarantee any level of availability. Nothing on our website, status page, or docs creates an availability commitment unless we've signed something separate saying so.

6. Your code and data

You own it

The source code, configuration, applications, databases, files, text, images, prompts, secrets, logs, and everything else you or your Authorized Users put into Shed is yours. We call all of it "Customer Material."

Nothing in these Terms transfers ownership of it to us.

The licence we need to run it

To actually operate the Service you have to let us handle your material. So you give us a worldwide, non-exclusive, royalty-free licence to host, copy, cache, transmit, reproduce, modify for technical reasons, build, execute, display, distribute, and otherwise process Customer Material — and to let service and infrastructure providers do the same — but only as far as reasonably necessary to:

  • run, secure, maintain, and support the Service;
  • build, deploy, run, and serve your applications to your End Users as you direct;
  • deal with technical, security, fraud, or abuse problems;
  • comply with the law and enforce these Terms; and
  • do things you've specifically asked us to do.

That licence runs as long as your material is on Shed, plus a reasonable tail where residual copies sit in backups, logs, or systems we keep for security and legal reasons.

We don't sell it or hand it around

We won't sell, license, or disclose your Customer Material to anyone else, with four exceptions: service providers working for us under written confidentiality obligations, things you tell us to do, things the law requires, and anything you've separately opted into.

Usage Data is different

Usage Data — the operational telemetry described in Section 2 — is ours, and we use it to monitor, debug, secure, and improve the Service, to plan capacity, and to detect abuse. We may also publish aggregated statistics drawn from it, provided they don't identify you or reveal anything about your code or your applications.

Usage Data is deliberately narrow. It doesn't include your source code, your configuration, your secrets, your application data, or the contents of your build and runtime logs. Those are Customer Material and the rest of this Section governs them.

Public deployments

Make something publicly accessible and you're instructing us to serve it to the public. Choosing the right access controls is on you, and once something is public it can be read, copied, indexed, and passed around by anyone.

What you're promising us

By using Shed you're confirming that:

  • you have the rights and permissions you need for everything you put on it;
  • your material and your applications don't break the law, these Terms, or anyone else's rights;
  • you've given every notice and collected every consent required for personal data your applications handle, and you're the controller of that data;
  • you'll keep your applications and data reasonably secure; and
  • you won't leave secrets or sensitive information sitting in public repositories, public build output, public logs, or anywhere else public.

Building or hosting your app on Shed doesn't make us its publisher, developer, seller, or operator. The app is yours, and so is the relationship with the people who use it.

Backups, and getting your data out

Keep your own copies of your source code, configuration, and data. Unless we've agreed otherwise in writing, Shed is not a backup or archival service.

We'll give you reasonable tools or a documented way to export your Customer Material while your account is open, and during the retention window in Section 15.

7. Acceptable Use

This Section is our Acceptable Use Policy. It applies to the Service, including the website, and to you, your Authorized Users, and anything acting with your credentials — including coding agents.

Don't use Shed, or help anyone else use it:

  • to break the law, including sanctions and export controls;
  • to exploit or harm minors, facilitate human trafficking, or promote terrorism or violent extremism;
  • to create, host, or distribute non-consensual intimate imagery, or other content used to harass, threaten, or intimidate;
  • to infringe intellectual property, privacy, publicity, or other rights;
  • to deceive others or obtain an unauthorised benefit, including through phishing, social engineering, payment or card fraud, credential theft, impersonation, misrepresentation of affiliation, or fraudulent schemes such as Ponzi, pyramid, or advance-fee fraud;
  • to harass, threaten, defame, or defraud anyone;
  • to host, distribute, or make available copyrighted or pirated software, media, or other material without authorisation from the rights holder;
  • to get into accounts, systems, networks, or data you're not authorised to access, or to probe them without permission;
  • to build, distribute, or run malware, ransomware, botnets, denial-of-service tools, or other attack infrastructure, or to spoof network or email identities;
  • to send unsolicited bulk messages through any channel, including email and SMS, or to run spam infrastructure;
  • to mine cryptocurrency, run public proxies or anonymisation services, torrent files, or resell raw compute, unless we've approved it in writing;
  • to run bots or scrapers that violate someone else's terms of service;
  • to dodge billing, quotas, rate limits, suspensions, or other technical restrictions;
  • to interfere with the Service or dump an unreasonable load on it;
  • to scrape, crawl, reverse engineer, decompile, or otherwise dig out non-public source code or components of the Service, except where the law says we can't stop you; or
  • in any other way that creates a serious security, legal, reputational, or operational risk for us, our providers, or other users.

Don't run critical systems on this

Shed isn't designed, tested, or certified for situations where a failure could kill or injure someone or cause severe environmental or property damage. Don't use it for life-support systems, emergency services, medical devices, aircraft or air-traffic control, nuclear facilities, weapons systems, autonomous vehicles, or other critical infrastructure unless we've signed a separate agreement covering it. If you do it anyway, the risk and the liability are entirely yours.

How we enforce this

We can investigate suspected violations, and we can remove or disable Customer Material, deployments, or access. We can also apply technical limits to protect the Service and other users. You agree to cooperate with us to remedy a violation. Section 12 covers what we tell you and how to push back.

When we decide whether a violation has occurred, we may take into account your ability and willingness to comply, including the policies and processes you have in place to prevent, identify, and remove prohibited content or activity.

Not sure whether something's allowed? Ask support@shed.codes before you deploy it.

8. Agents and automation

You can point a coding agent or other automated tool at Shed. Picking it, configuring it, and supervising it are your job, and so is everything it does with your credentials — including money it spends.

Where a reasonable person would stop and check before letting an agent act, check. That means production deployments, credentials, personal data, destructive operations, and anything expensive. Setting spending limits and giving agents the narrowest credentials that will work is a good habit.

We don't control third-party agents and we're not responsible for what they output, decide, or do, or for their security or availability.

Shed doesn't generate code or any other AI output itself. If you bring output from a third-party agent to Shed, that agent stays a Third-Party Service, and the output becomes Customer Material the moment you submit it. Who owns it is a question for the law and for your agreement with the agent's provider — not for us.

9. Other people's services

Shed connects to outside platforms, infrastructure, registries, repositories, payment processors, domain providers, databases, AI tools, and more. We call these "Third-Party Services."

They belong to their providers, not to us, and they come with their own terms, fees, limits, and privacy practices. We're not responsible for them, or for outages, data loss, or security incidents they cause.

Open-source software is governed by its own licence. Where these Terms conflict with an open-source licence, that licence wins for that software.

Disputes with other people

Whatever happens between you and your End Users, other Shed customers, or a Third-Party Service provider is between you and them. We're not obliged to get involved. As far as the law allows, you release Shed and its Affiliates, officers, employees, contractors, and agents from claims and damages of every kind arising out of those disputes.

If you're in California, you're also waiving California Civil Code section 1542, which says a general release doesn't cover claims you didn't know about at the time and which would have changed your mind had you known. You waive equivalent rules elsewhere too. None of this releases a claim that can't legally be released, and none of it releases claims against us for something we ourselves did.

10. Paying for Shed

Some of Shed is free and some isn't. Prices, included usage, usage rates, billing intervals, spending limits, and the rest are on the pricing or checkout page.

When you buy something, you're agreeing to:

  • pay the fees and the taxes;
  • give us accurate billing information;
  • let us and our payment provider charge your payment method; and
  • pay usage charges run up through your account, including by automated activity you authorised.

Fees are in pounds sterling (£) unless shown otherwise. Prices shown to consumers include VAT. Prices quoted to business customers exclude VAT and any other applicable tax, which we add at the rate in force. Taxes on our own income are ours. Tax on your own activity is also yours — including anything you owe on what you charge your End Users. We're not your tax agent and we don't file for you.

Renewals

Unless checkout says otherwise, subscriptions renew automatically for the same length of period, at the price in effect at the time, and we charge your payment method each time — until you cancel. To cancel, email support@shed.codes — we'll action it and confirm. Cancellation takes effect at the end of the period you've paid for, and we won't ask you to justify it or route you through a retention call. California residents: see Section 21 for extra notices.

Refunds

Unless the law says otherwise, fees aren't refundable. Unused credits have no cash value, can't be transferred, and expire when we say they do or when your account ends. Section 5 gives you a limited refund right if we cut a paid feature.

If you're a consumer, you have a statutory right to cancel within 14 days of buying, without giving a reason. But if you ask us to start providing the Service straight away — which is what happens when you deploy something — you're acknowledging that you lose that right once we've fully performed, and that you'll pay for what you've used up to the point you cancel. Email support@shed.codes to cancel. This paragraph doesn't limit any stronger right your local law gives you.

Price changes, and what happens if you don't pay

We can change prices going forward. For subscriptions, you'll get at least 30 days' notice of an increase, and the new price kicks in at the renewal after that. Usage-based prices change as stated on the pricing page.

If a payment is late or fails, we may limit or suspend paid features, deployments, or the account — with notice where that's practical. Overdue amounts can accrue interest at the lower of 1.5% a month and the maximum the law allows.

11. Who owns what

Apart from your Customer Material and third-party material, Shed and its licensors own the Service: the software, the design, the branding, the documentation, and the intellectual-property rights in all of it.

We give you a limited, non-exclusive, non-transferable, non-sublicensable, revocable right to use the Service to develop, build, deploy, operate, and ship your applications — including making them available to your End Users and to the public if that's what you want.

Our name, logos, and product names are trademarks. These Terms don't give you the right to use them, other than to describe your own product accurately.

The licence above covers our command-line tools too. You can install and use them on your own machines while your account is open, for the purpose of working with the Service. Any open-source components they include are governed by their own licences, which win over this Section for those components.

If you provide suggestions, ideas, or feedback, we get a worldwide, perpetual, irrevocable, royalty-free right to use it however we like, with no compensation owed. That doesn't give us any rights in your Customer Material.

12. Reporting content

Telling us about a problem

Anyone can report material or an application on Shed they believe is illegal or breaks these Terms. Email support@shed.codes with where the material is, why you think there's a problem, and how to reach you. We'll confirm we got it and handle it promptly, objectively, and without being arbitrary about it.

Report suspected infringement the same way, and tell us: what work you say was infringed, where the infringing material is in enough detail that we can find it, your contact details, that you believe in good faith the use isn't authorised, and that you're the owner or authorised to act for them.

We haven't registered a designated agent under the U.S. Digital Millennium Copyright Act and don't run a formal DMCA notice-and-counter-notice programme. We do take these reports seriously — we'll investigate, remove or disable material that appears to infringe, and close the accounts of repeat infringers where that's appropriate. We'll also reject reports that are fraudulent, abusive, or seriously misleading.

Why we did what we did

When we remove or disable material, suspend a deployment, restrict a feature, or suspend or terminate an account over content or conduct, we'll tell the affected user: what we did, how broad it is and how long it lasts, the facts behind it, which part of these Terms we relied on, whether automation was involved, and how to challenge it.

The exception is where telling you would itself be unlawful, would get in the way of a criminal investigation, or where the material is manifestly illegal and serious.

Disagreeing with a decision

If you think we got a decision wrong, write to support@shed.codes and say why. We'll look at it again, ask either side for more if we need it, and put things back where we agree we were wrong. Your right to take the matter to court under Section 20 is unaffected.

Point of contact

For regulators, authorities, and communications under this Section, use support@shed.codes. You can write in English.

13. Privacy and data protection

Our Privacy Policy covers what we do with personal data when we're the controller — your account, billing, and support data.

When we're processing data for you

When your applications handle personal data, you're the controller under the UK GDPR and the EU GDPR (the "business," under US state privacy laws) and we're your processor. We process that data on your documented instructions, as needed to provide and secure the Service, and as required by applicable law.

Data you shouldn't put here

Don't use Shed for protected health information, payment card data beyond what our published compliance posture covers, biometric identifiers, government ID numbers, children's data covered by COPPA, or other special-category or regulated data — unless the Service explicitly supports it and we've got a written agreement with you covering it.

14. Security

We keep reasonable technical and organisational measures in place to protect the Service. No service is perfectly secure, though, and we can't promise nobody will ever get past them.

What we owe you if something goes wrong

If we find out about a breach that destroys, loses, alters, or exposes Customer Material or personal data we process for you, we'll tell you without undue delay and within 72 hours of becoming aware of it. We'll give you what we've got so you can meet your own notification obligations. We won't sit on it while we finish investigating.

What's on you

Configuring your applications, dependencies, access controls, credentials, networks, and data securely is your job. Patch known vulnerabilities in your applications promptly, and tell us at support@shed.codes if you spot a security problem in the Service.

15. Stopping, suspension, and termination

You can walk away whenever you want. Email support@shed.codes to cancel a paid Service or delete your account, and we'll action it.

We can suspend, limit, or terminate your access or a deployment if:

  • you breach these Terms;
  • your use creates a security, legal, or operational risk;
  • payment is overdue;
  • we reasonably think we need to act to prevent harm;
  • a Third-Party Service forces our hand;
  • the law requires it; or
  • we're shutting the relevant Service down.

Where it's practical we'll tell you first and give you a chance to fix the problem, and we'll keep any suspension as narrow and as short as it reasonably can be. In an emergency we may act immediately. Section 12 covers the explanation you get and how to challenge it.

After it ends

Your right to use the Service stops. We'll keep your Customer Material recoverable for 30 days after termination or deletion so you can export it, then delete it within another 60 days. Copies in backups, logs, or records survive that where the law requires it or where we reasonably need them to resolve a dispute or enforce an agreement, and backups age out on our normal cycle, currently 90 days.

We may delete material immediately, with no retention window, where keeping it would be unlawful or where it's manifestly illegal content.

Sections that ought to survive the end of this agreement do survive it, including Sections 2, 6 (ownership and Usage Data), 10 (money you already owe), 11, 17, 18, 19, 21, and 23.

16. What we don't promise

Nothing here strips out warranties or rights that can't legally be excluded, including under consumer-protection law.

TO THE FULLEST EXTENT PERMITTED BY LAW, THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE." SHED AND ITS SUPPLIERS AND LICENSORS DISCLAIM ALL EXPRESS, IMPLIED, AND STATUTORY WARRANTIES, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT, AND ANY WARRANTY ARISING FROM A COURSE OF DEALING OR USAGE OF TRADE.

WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR FREE FROM HARMFUL COMPONENTS; THAT CUSTOMER MATERIAL WILL NOT BE LOST; THAT ANY DEPLOYMENT WILL BUILD OR OPERATE SUCCESSFULLY; OR THAT RESULTS OBTAINED FROM THE SERVICE WILL BE ACCURATE OR RELIABLE.

Some places don't allow these exclusions, so parts of this Section may not apply to you.

17. Limits on what we owe you

Nothing here limits liability where the law says it can't be limited — fraud, fraudulent misrepresentation, gross negligence, willful misconduct, death or personal injury caused by negligence, or anything protected by consumer law.

TO THE FULLEST EXTENT PERMITTED BY LAW, NEITHER SHED NOR ITS AFFILIATES, SUPPLIERS, LICENSORS, OFFICERS, EMPLOYEES, CONTRACTORS, OR AGENTS WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL, USE, OR DATA, ARISING OUT OF OR RELATED TO THE SERVICE, EVEN IF ADVISED THAT SUCH DAMAGE IS POSSIBLE.

TO THE FULLEST EXTENT PERMITTED BY LAW, THE TOTAL AGGREGATE LIABILITY OF SHED AND THE PARTIES LISTED ABOVE FOR ALL CLAIMS ARISING OUT OF OR RELATED TO THE SERVICE OR THESE TERMS WILL NOT EXCEED THE GREATER OF (A) THE AMOUNT YOU PAID TO SHED FOR THE SERVICE IN THE 12 MONTHS IMMEDIATELY BEFORE THE EVENT GIVING RISE TO THE CLAIM, OR (B) £100.

That cap is the total across all claims, not a fresh cap for each one. It applies whatever the legal theory, and it still applies even if some other remedy in these Terms turns out to be worthless. Both of us are treating this as a deliberate split of risk and part of the deal.

Neither of us is liable for loss the other could reasonably have avoided or reduced. Section 6 asks you to keep your own copies of your code, configuration, and data: we aren't liable for loss you would have avoided by doing that, or for loss you could have limited by telling us about a problem sooner.

Some places don't allow these limits, so parts of this Section may not apply to you.

18. When you cover us

As far as the law allows, you'll defend, indemnify, and hold harmless Shed and its Affiliates, suppliers, licensors, officers, employees, contractors, and agents against third-party claims, damages, losses, liabilities, judgments, settlements, and reasonable attorneys' fees arising out of:

  • your Customer Material or your applications;
  • your use of the Service;
  • your dealings with your End Users;
  • your breach of these Terms; or
  • your violation of the law or of someone else's rights.

We'll tell you about a covered claim within a reasonable time. If we're late, that only lets you off the hook to the extent it actually hurt your position. We keep control of the defence and any settlement, though we may let you take over the defence with counsel we're comfortable with. You can't settle anything in a way that admits fault for us, puts an obligation or a payment on us, or restricts what we can do, without our written consent. We'll expect reasonable cooperation from you, at your cost.

This Section doesn't apply where consumer law says it can't, and it doesn't cover claims arising from our own gross negligence or willful misconduct.

19. Changes to these Terms

These Terms will change as the Service and the law change. When a change is material, you'll get at least 30 days' notice in the product, by email, or some other sensible route.

The new version takes effect on the date in the notice. Changes don't apply retroactively unless the law requires it. If you don't like the new version, stop using the Service before it takes effect — keep using it afterwards and you've accepted it.

One carve-out: changes to Section 20 don't apply to a dispute either of us had already raised in writing before the change took effect.

20. If we end up in a dispute

20.1 Which law applies

These Terms, and any dispute or non-contractual obligation arising out of them or out of the Service, are governed by the law of England and Wales.

If you're a consumer, this doesn't take away the protection of any mandatory rules of the law of the country where you habitually live. Whatever this Section says, you keep every right your own consumer law gives you that can't be signed away.

20.2 Talk to us first

Before either of us starts formal proceedings, we both agree to spend 30 days trying to sort it out informally, starting when one of us writes to the other. Say what the dispute is, what you want, and how to reach you, and include the email address on your account.

Write to us at support@shed.codes, or at REDRESS SPACE LTD, Level 30, The Leadenhall Building, 122 Leadenhall Street, City of London, London EC3V 4AB, United Kingdom. We'll write to the address on your account. Either of us can ask for a call, and we'll both turn up in good faith.

This step doesn't stop you going to court if you need to protect a deadline, and it doesn't stop either of us seeking an urgent injunction under Section 20.4.

20.3 Where a dispute gets heard

The courts of England and Wales have jurisdiction over any dispute arising out of these Terms or the Service.

If you're a consumer, you can bring proceedings in England and Wales or in the courts where you live, whichever you prefer, and we'll only bring proceedings against you in the courts where you live.

If you're a business customer — acting wholly or mainly for purposes related to your trade, business, craft, or profession — the courts of England and Wales have exclusive jurisdiction.

20.4 Injunctions and small claims

Either of us can go to court at any time for an injunction or other urgent relief to stop actual or threatened misuse of intellectual property, confidential information, or the Service, without waiting for Section 20.2.

Either of us can also bring a qualifying claim on the small claims track or an equivalent local procedure.

20.5 Time limit for business claims

If you're a business customer, any claim arising out of these Terms or the Service must be brought within one year of the date you became aware, or ought reasonably to have become aware, of the facts giving rise to it. This doesn't apply to consumers, whose statutory limitation periods are untouched.

20.6 Who else can rely on these Terms

Except as set out here, someone who isn't a party to these Terms has no right under the Contracts (Rights of Third Parties) Act 1999 to enforce any of them. Our Affiliates, officers, employees, contractors, and agents may enforce Sections 16, 18, and 19. Your End Users have no rights against us under these Terms. We don't need anyone else's consent to vary or rescind these Terms.

21. If you're in California

We're a UK company, and Section 20 governs disputes. These two notices still apply to California residents who buy a subscription from us.

Automatic renewals. Before you buy a subscription that renews on its own, we'll show you the renewal terms clearly, take your active agreement to them, and send a confirmation covering those terms and how to cancel. To cancel, email support@shed.codes. A single email is enough — we won't require a phone call or put you through a retention process, and we'll confirm once it's done. Where required, we'll warn you before a renewal and before a free trial converts to a paid rate.

Complaints. You can reach the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs at 1625 North Market Blvd., Suite N 112, Sacramento, CA 95834, or on (800) 952-5210.

22. The rest

The whole agreement

These Terms, the Privacy Policy, anything else expressly folded into them, and any order or written agreement between us are the complete agreement about the Service. They replace everything discussed beforehand.

Which document wins

If two of them conflict, in this order: (1) a signed agreement between you and Shed; (2) these Terms; (3) the Privacy Policy and other referenced policies.

Assignment

You can't assign these Terms without our written consent, except to a successor in a merger or a sale of substantially all your assets — provided they're not a competitor of ours and they take on these Terms in writing. We can assign in a merger, acquisition, reorganisation, asset sale, or by operation of law.

Not enforcing something isn't giving it up

If we don't enforce a provision, we haven't waived our right to enforce it later.

If part of this fails

An unenforceable provision gets narrowed just enough to work, or dropped if that's impossible. Everything else stands. Section 20.5 has its own severability rule, which governs there.

We're not partners

These Terms don't make us agents, partners, joint venturers, employer and employee, or franchisor and franchisee.

Things outside our control

Neither of us is on the hook for delays or failures caused by things we can't reasonably control: natural disasters, war, terrorism, labour disputes, internet or utility failures, government action, and Third-Party Service failures. That doesn't excuse paying money you owe.

How we reach you

We'll send notices to the email on your account, through the Service, or by posting them on our website. They count as delivered when sent or posted. Keep your contact details current.

Language

These Terms are written in English. If we publish a translation and the two conflict, the English version governs, unless the law says otherwise.

Headings

Headings and the summary are there to help you find things. They don't change what the Terms mean.

23. How to reach us

REDRESS SPACE LTD Level 30, The Leadenhall Building, 122 Leadenhall Street, City of London, London EC3V 4AB, United Kingdom

support@shed.codes

That address reaches us for everything — support, legal notices, security, abuse reports, copyright, and privacy.