Skip to main content
Railyard
DocsLearnAPI reference

Terms of Service

Version 2026-10-16 · Effective date: 16 October 2026

1. Who these terms are between

These Terms of Service (the "Terms") are an agreement between the company that supplies Railyard at railyard.sh ("we", "us", "our") and the person or organisation that opens an account or uses the Service ("you", "your", the "Customer").

Railyard is a trading name of Railyard Tech Ltd, a company registered in England and Wales under company number 17525277, whose registered office is 24 Elizabeth Road, Wokingham, England, RG40 1UB.

By creating an account, signing in, or otherwise using Railyard (the "Service"), you agree to these Terms and confirm that you have read our Privacy Policy. If you are agreeing on behalf of an organisation, you confirm you have authority to bind it, and "you" means that organisation. If you do not agree, do not use the Service.

Before a new account can use the Service we ask you to accept these Terms expressly, and we ask again when you subscribe to a paid plan or buy a Project Pass. We keep a record of each acceptance: the version you accepted, the version of the Privacy Policy you were shown, and when.

We keep dated copies of earlier versions of these Terms. The version and effective date above identify the version that applies to you; see section 25.

2. The Service

Railyard is a tool for designing and documenting data-centre estates — custom spaces, racks, devices, power and cabling — and for exporting that design in a range of formats. It is a design and documentation aid that produces data you import elsewhere; it is not a monitoring, control or management system for live infrastructure.

Features may change as we improve the Service. We will give you reasonable notice when a change materially reduces how you access or export your data.

Changes to plans. If we remove a paid feature from a plan you are paying for, or materially reduce one — for example by withdrawing a deliverable or lowering a limit — we will give you at least 30 days' notice by email before the change applies to you. The change does not apply to a period you have already paid for, or to a Project Pass you have already bought, before it ends. If you do not accept the change, you may cancel before it applies and we will refund the unused part of any period you have paid for, or of a Project Pass pro rata by day. Changes that only add features or raise limits can take effect straight away. We will never remove the free design and raw Project JSON export described in section 5.1.

3. Accounts and eligibility

You must be at least 16 years old and able to form a binding contract. Sign-in is passwordless: you authenticate with a one-time sign-in code sent to your email address, or through a single sign-on provider you choose (such as Google or GitHub). You are responsible for the security of the inbox and identity provider you sign in with, and for activity under your account.

Within an organisation, access is governed by roles (owner, editor and viewer). The organisation's owners are responsible for managing membership and for the conduct of the people they invite. An organisation owner can restore their own administrator access to a private project inside their organisation, including one they were removed from; that action is recorded in the organisation's audit trail. If you store something in an organisation you do not own, assume its owners can reach it.

4. Business and consumer customers

Railyard is built for trade, business and professional use, and most of our customers buy it in the course of a business. Where these Terms say a section applies to "business customers", it applies to you if you are acting wholly or mainly for purposes relating to your trade, business, craft or profession.

You can also buy the Pro plan or a Project Pass as a consumer — as an individual acting wholly or mainly outside any business. If you do:

  • section 6 gives you a 14-day right to cancel, and explains when you lose it for a Project Pass;
  • sections 12.3, 13.3, 13.4 and 14 do not apply to you, and nothing in these Terms affects your statutory rights under the Consumer Rights Act 2015 — including that the Service must be supplied with reasonable care and skill; and
  • section 26 preserves the protections of your local law and courts.

You tell us which you are at checkout. If you are not sure, treat yourself as a consumer: it gives you more rights, not fewer.

5. Plans, trial, prices and billing

5.1 What every plan includes, and what is paid

On every plan, including the free Community plan, you can design without a time limit: create as many estates as you like with no limit on devices, model racks, cabling and power, keep version history and restore earlier versions, and export the complete design as the raw Project JSON described in section 17.3. Designing and the raw Project JSON export are free on every plan, and always will be.

The documents and import bundles we generate from a design (the "deliverables") are paid features. They are:

  • Build pack PDF
  • Cable schedule
  • Cable and rack labels
  • Power schedule
  • Power report
  • NetBox bulk-import bundle
  • Nautobot bulk-import bundle

The Nautobot bundle includes the Design Builder YAML file. Deliverables are included in the Pro, Team and Partner plans, in a Project Pass for the estate it covers (section 5.7), and in plans agreed under a separate written agreement. On the Community plan you can generate a watermarked preview of the build pack, one rack at a time.

Branches, merge requests (review and approval) and live collaboration are included from the Team plan upwards. Each plan's price, editor places and limits are on our pricing page and are shown again before you buy.

5.2 Limits

Each plan limits the number of racks in any one estate (Community: 25; Project Pass: 100; Pro: 100; Team: 500; Partner: 1,000) and the number of editors. A limit only ever stops growth. If an estate already has more racks than its plan allows — for example after a paid plan ends — it stays editable, you can remove racks from it, and you can export it as raw Project JSON, but you cannot add racks to it until it is back within the limit or you move to a plan with a higher one. In the same way, an organisation with more editors than its plan includes keeps them but cannot add more. Deliverables can be generated only for an estate that is within its plan's rack limit.

We may also apply reasonable technical and abuse-prevention limits in addition to the published plan limits.

5.3 Community

The Community plan is free of charge and has no expiry date. It includes 1 editor and up to 25 racks in each estate, with no limit on the number of estates or devices. We intend to keep a free plan available. We may change its limits, and we would give you at least 30 days' notice before a change to the plan you are on reduces what you can do, so you can export or move up. That does not extend to the free design and raw Project JSON export in section 5.1, which we will not withdraw.

5.4 Team trial

An organisation can run a 14-day Team trial once. Each person gets one trial across the organisations they create; organisations you create later start on Community. No payment method is needed to start a trial and nothing is charged when it ends. At the end of the trial, unless an owner has subscribed, the organisation moves to the Community plan's rules. Nothing is deleted and nothing becomes read-only: its members can still open, edit and export its designs as raw Project JSON, within the limits in section 5.2. The Team features — deliverables, creating branches and merge requests, and live collaboration — stop until an owner subscribes, which restores them straight away.

5.5 Prices and VAT

Prices published on our pricing page are stated excluding VAT. Any VAT or other sales tax that applies to your purchase is calculated and shown at checkout before you pay, based on the location and tax status you give us. If you are buying as a consumer, the total you will be charged — including VAT — is shown before you confirm the purchase.

We may change published prices with reasonable advance notice. A change never alters a period you have already paid for, or the price of a Project Pass you have already bought.

5.6 Paid subscriptions and renewal

We charge you only when you choose a paid plan or buy a Project Pass and provide a payment method. The checkout page shows the price, the billing interval, taxes where applicable and the renewal terms before you buy, and we email you confirmation of the contract afterwards. The Pro plan is for a personal space and the Team plan for a shared organisation. Paid subscriptions renew automatically for the interval you chose until cancelled.

The Team price includes 5 editor places; each further person with owner or editor access is charged at the additional-editor price shown when you buy. Viewer access and read-only review do not use a paid editor place. The Partner plan is arranged with us directly rather than at checkout. Self-hosted licences and enterprise identity, private-deployment, uptime and support commitments are available only under a separate written annual agreement; nothing on the public pricing page promises those capabilities outside such an agreement.

5.7 Project Pass

A Project Pass is a one-off purchase, not a subscription: you pay once, it does not renew, and nothing further is charged. It is available in a personal space, for an estate whose plan does not already include deliverables.

  • It covers one estate — the one you buy it for. It cannot be moved to another estate or transferred to another person.
  • For 6 months from purchase it gives that estate every deliverable in section 5.1 and a limit of 100 racks. It does not include branches, merge requests or live collaboration, and adds no editor places.
  • When it ends, the estate stays as it is: editable within its plan's limits and exportable as raw Project JSON. Deliverables you have already downloaded are yours to keep, and you can buy another pass.
  • If we refund a Project Pass — for any reason, including a cancellation under section 6 — the pass ends when the refund is made.
  • If the estate is permanently deleted, the pass ends with it. Except where the law requires otherwise, a pass is not refunded because the estate was deleted.

5.8 Cancelling a paid plan

An owner cancels through Manage billing in the billing settings of the personal space (Pro) or organisation (Team) that pays. Cancelling stops the next renewal: paid access continues until the end of the period you have already paid for, and we do not refund the unused part of that period unless the law requires it or section 6 applies. The space or organisation then moves to the Community plan's rules, as section 15 describes: nothing is deleted or made read-only, and you can export your data as raw Project JSON at any point before or after.

5.9 Deleting an account or organisation

Deleting your account or an organisation does not cancel its subscription for you. While a subscription is set to renew, the account or organisation cannot be deleted: cancel it through Manage billing first, then delete. If you delete before the paid period ends, the remainder of that period is lost, and deleting an estate covered by a Project Pass ends the pass (section 5.7). If you believe you have been charged after deleting an account or organisation, contact [email protected] and we will cancel the subscription and refund any charge taken after deletion. Invoices and payment records are kept to meet accounting and tax obligations (see our Privacy Policy).

6. Your right to cancel if you are a consumer

This section applies only to consumers (see section 4). It gives you the information required by the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013.

You have the right to cancel a paid subscription or a Project Pass within 14 days of the day the contract is concluded — the day you complete checkout — without giving any reason, subject to what this section says about a Project Pass.

How to cancel. Tell us clearly, before the 14 days are up, that you are cancelling. Email [email protected] or use the form below. You can also cancel renewal at any time through Manage billing, but to exercise this 14-day right please tell us in writing so we have a record of the date. We will confirm receipt without delay.

Starting a subscription during the cancellation period. Access begins as soon as you subscribe, which is before the 14 days are up. At checkout we ask you to confirm you want the Service to start straight away. If you then cancel, you keep the right to cancel but you must pay a proportionate amount for the Service actually supplied up to the moment you told us — calculated on the subscription price for the period, pro rata by day. If you would rather not pay anything, ask us at checkout to delay the start until the 14 days have passed.

A Project Pass is digital content. A Project Pass (section 5.7) is supplied as digital content that is not on a tangible medium. At checkout we ask you to request that it is made available straight away and to acknowledge that you will lose your right to cancel once you start using it, and we confirm both in the email confirming your purchase. If you gave that request and acknowledgement, you lose the right to cancel the pass when you first generate a deliverable with it. Until then — or at any time within the 14 days if you did not give them — you can cancel the pass and we will refund it in full. Losing the right to cancel does not affect your rights if the digital content is faulty.

Refunds. We refund everything you have paid, less any proportionate amount due for a subscription under the paragraphs above, within 14 days of the day you tell us you are cancelling, using the same payment method you used to pay. A refunded Project Pass ends when the refund is made.

Cancelling within the 14 days does not delete your data. You can export it first, and we handle it afterwards as described in section 17 and our Privacy Policy.

Model cancellation form — you do not have to use this form, but you may.

To Railyard Tech Ltd, [email protected]:

I/We hereby give notice that I/we cancel my/our contract of sale for the supply of the following service: [the Railyard subscription / the Railyard Project Pass]

Ordered on: [date] / Received on: [date]

Name of consumer(s): [your name]

Address of consumer(s): [your address]

Signature of consumer(s): [only if sent on paper]

Date: [date]

Complaints. If something has gone wrong, email [email protected] and we will reply. If we cannot resolve it between us, you can take the matter to the courts described in section 26; nothing here requires you to arbitrate or to give up any statutory remedy.

7. Acceptable use

You agree not to, and not to permit anyone else to:

  • use the Service unlawfully, or to store or transmit unlawful, infringing or malicious content;
  • attempt to gain unauthorised access to the Service, other customers' data, or the underlying infrastructure, or probe, scan or test the vulnerability of any system except under the responsible-disclosure process on our Security page;
  • interfere with or disrupt the integrity or performance of the Service, including by circumventing rate limits, editor limits, rack limits or other technical restrictions;
  • get round the limits of your plan — for example by using a Project Pass for an estate it does not cover, or by removing the watermark from a build-pack preview;
  • reverse engineer, decompile or copy the Service except to the extent this restriction is prohibited by law; or
  • resell, sublicense or provide the Service to third parties except as expressly permitted by your plan.

8. Your data and ownership

As between you and us, you own all the designs, models, device data, labels, comments and other content you create or upload in the Service ("Customer Data"). We do not claim ownership of Customer Data.

You grant us a worldwide, non-exclusive, royalty-free licence to host, store, process, transmit, display and back up Customer Data solely as needed to provide and support the Service, to keep it secure, and as otherwise instructed by you. This licence ends when the relevant data is permanently deleted or you close your account, except for copies held in backups until they age out of our backup retention period, or where we must keep something by law. A deleted organisation or project stays restorable in the Service for 30 days and is then permanently deleted; you can delete it permanently sooner from Recently deleted. You are responsible for having the rights necessary to submit Customer Data and for its accuracy.

Where Customer Data contains personal data, you are the controller of it and we process it on your instructions under our Data Processing Agreement, which forms part of these Terms.

You can export your design data as the raw Project JSON from within the Service at any time, on every plan and free of charge. Section 17 describes what is exportable, in what formats, and for how long after your plan ends.

9. Our intellectual property

The Service itself — the software, its user interface, and the Railyard name and logo — is owned by us or our licensors and is protected by intellectual property laws. Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable right to access and use the Service for your internal purposes while we make it available to you. We reserve all rights not expressly granted.

The bundled device library is not ours. The built-in device-type library is a curated, transformed subset of the netbox-community/devicetype-library, published under CC0 1.0 Universal. We claim no ownership of it or of the manufacturers' names and model designations it contains, and nothing in these Terms restricts your use of that upstream data. Third-party notices for everything we ship are at /licenses.txt.

If you send us feedback or suggestions, you agree we may use them to improve the Service without obligation to you. We do not ask for ownership of anything else you send us.

10. Integrations and clients you connect

You can connect things to your Railyard data: personal access tokens, AI assistants and other clients through our connector interface, and importers or plugins for systems such as NetBox. You decide what to connect, and:

  • a client you authorise acts with your access. What it reads, writes or sends onward is your responsibility, including anything it sends to an AI provider you have chosen — that provider's handling of your data is governed by your agreement with them, not by these Terms;
  • you are responsible for reviewing and revoking tokens and connected clients you no longer use. Account settings lets you list and revoke them individually or all at once;
  • tools that write into your other systems can change or remove data there. Take a backup of the destination system before a first sync, and run any available preview first; and
  • we are not responsible for third-party services, and we do not warrant that an integration will keep working if the third party changes its interface.

11. Availability and maintenance

We aim to keep the Service available and reliable, but except where a separate written service-level agreement applies, the Service is provided without an uptime commitment. We carry out maintenance, and we may need to suspend the Service to protect its security or integrity. Where practical we give notice of planned downtime.

12. Our responsibility for the Service

12.1 We will supply the Service with reasonable care and skill.

12.2 Railyard is a design and documentation aid. It does not verify that a design is safe, buildable or compliant, and you remain responsible for checking a plan — particularly power, capacity and cabling calculations — before relying on it operationally or building from it.

12.3 Business customers only. To the fullest extent permitted by law, and except as stated in 12.1, the Service is provided "as is" and "as available", and we disclaim all other warranties, conditions and representations, whether express or implied, including implied terms as to satisfactory quality, fitness for a particular purpose and non-infringement. We do not warrant that the Service will be uninterrupted or error-free, or that it will meet your specific requirements.

If you are a consumer, 12.3 does not apply to you and your statutory rights are unaffected.

13. Limitation of liability

Each sub-clause below operates independently. If any one of them is found unenforceable, the others continue to apply.

13.1 What we never limit. Nothing in these Terms excludes or limits either party's liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for breach of the terms implied by section 12 of the Sale of Goods Act 1979 or section 2 of the Supply of Goods and Services Act 1982, or for any other liability that cannot lawfully be excluded or limited.

13.2 Consumers. If you are a consumer, we are responsible for loss or damage you suffer that is a foreseeable result of our breaking these Terms or failing to use reasonable care and skill, and nothing in 13.3, 13.4 or 14 applies to you. We do not exclude or limit anything the Consumer Rights Act 2015 says we cannot.

13.3 Business customers — excluded losses. To the fullest extent permitted by law, we are not liable to a business customer for:

  • loss of profit, revenue or anticipated savings;
  • loss of business, contracts or opportunity;
  • loss of or damage to goodwill or reputation;
  • wasted expenditure or management time; or
  • any indirect or consequential loss,

in each case whether arising in contract, tort (including negligence) or otherwise.

13.4 Business customers — loss of Customer Data. You can export your Customer Data at any time (section 17), and you are responsible for keeping your own copies of anything you could not afford to lose. To the fullest extent permitted by law, we are not liable to a business customer for loss or corruption of Customer Data to the extent that the loss could have been avoided by you keeping a reasonably recent exported copy. This exclusion does not apply to loss or corruption caused by our breach of our security obligations, our breach of the Data Processing Agreement, or our deliberate or reckless act or omission; our liability for those is limited only by 13.5.

13.5 Cap. Subject to 13.1 and 13.2, our total aggregate liability arising out of or in connection with the Service and these Terms, whether in contract, tort (including negligence), for breach of statutory duty or otherwise, will not exceed the greater of:

  • the total fees you paid us for the Service, including for any Project Pass, in the twelve (12) months immediately before the event giving rise to the liability; and
  • £5,000.

The floor means the cap is a real remedy even on a free plan, where no fees have been paid.

14. Indemnity (business customers only)

If a third party brings a claim against us because your Customer Data infringes their intellectual property rights, breaches their confidence, or is unlawful, you will indemnify us against the amounts a court awards or we reasonably agree in settlement, plus our reasonable legal costs. This does not cover any claim to the extent it arises from our own breach of these Terms, our negligence, or our processing of Customer Data otherwise than on your instructions.

If a third party claims that the Service itself (excluding Customer Data and the CC0-licensed device library described in section 9) infringes their intellectual property rights, we will indemnify you on the same basis, subject to the cap in 13.5.

Either party claiming under this section must notify the other promptly, let the indemnifying party conduct the defence and settlement, make no admission without consent, and give reasonable assistance at the indemnifying party's cost. This section does not apply to consumers, who are liable only to the extent the law makes them so.

15. Suspension

We may suspend some or all of your access — including by limiting an organisation to read-only access so you can still read and export your designs — where we reasonably believe it is necessary to protect the Service, other customers or a third party, or where the law requires it. We will tell you why, and restore access once the reason has gone. Suspension does not extend a period you have paid for, except where the suspension was our fault.

When a paid plan or a Project Pass ends. Not paying is not a reason for suspension. When a paid plan lapses, expires or is cancelled, or a Project Pass ends or is refunded, nothing is deleted, hidden or made read-only: your designs stay editable within the Community plan's limits (section 5.2) and exportable as raw Project JSON (section 17). Only the paid features stop — deliverables, creating branches and merge requests, and live collaboration — until you subscribe or buy a pass again.

16. Termination

You may stop using the Service and close your account at any time (see 5.8 and 5.9 for the billing consequences). Either party may terminate these Terms by notice if the other materially breaches them and, where the breach can be remedied, fails to remedy it within 30 days of being asked. We may terminate immediately where necessary to protect the Service or other customers, or to comply with law.

On termination your right to use the Service ends, subject to the retrieval period in section 17. Terms that by their nature should survive termination — including sections 8, 9, 12, 13, 14, 17 and 26 — will do so.

17. Switching, exit and data retrieval

You are not locked in, and this section sets out that right in the contract as well as in the product. It is written to meet Articles 25 and 26 of the EU Data Act for customers to whom that regulation applies, and we apply it to every customer.

17.1 Switching on request

You may at any time ask us to help you switch to another provider, to your own infrastructure, or to stop using the Service and retrieve your data. Tell us at [email protected]. We will cooperate in good faith, keep you informed, and not create deliberate obstacles to switching.

17.2 Notice, transition and retrieval periods

  • Notice. You may terminate for the purpose of switching on a maximum notice period of two months. Cancelling a subscription through Manage billing takes effect at the end of the current paid period, which is shorter than that for monthly plans.
  • Transitional period. After notice takes effect you get a 30-day transitional period in which the Service stays available for retrieval and export. If you reasonably need longer to complete the switch, ask before the period ends and we will extend it once by up to a further 30 days.
  • Retrieval period. You then have at least a further 30 days to retrieve your data before we erase it. In practice a personal space or organisation whose paid plan has lapsed keeps every design editable and exportable as raw Project JSON for as long as the account exists, but 30 days is the minimum we commit to.

17.3 What you can export, and in what format

Your data exports as structured, machine-readable files in open formats, free of charge on every plan and without a rate penalty:

  • The raw Project JSON — the complete design in our documented format: every location, space, row, rack, device and device type, port, cable, power link, naming rule and setting in the estate, which is everything another tool needs to rebuild it. Its schema is published at schema/project.schema.json, so you or another provider can read it without our help. This is the reference format for Article 26 purposes.
  • Your account data — from User settings → Data & deletion, as a JSON file covering every category of personal data we hold about you.
  • Organisation-level lists — the shared device-type catalogue, device-role vocabulary, rack templates and naming rules, and the member and role list, through the Service and its documented API.
  • History and review records — saved versions, merge requests, review decisions and comments, through the documented API using a personal access token. A single downloadable archive of these is on our roadmap; until it ships, ask us at [email protected] and we will produce one for you at no charge.

What is not exportable: our own operational and derived data (server logs, security and abuse records, rate-limit counters, billing records held for tax purposes), the Service's software itself, and anything belonging to another customer. These are not your data and are excluded under Article 25(2)(b).

Deliverables are separate. The deliverables in section 5.1 — including the NetBox and Nautobot bulk-import bundles and the Design Builder YAML file — are documents and import files we generate from your design for the plans that include them. They are derived from the same design and hold none of your data that the raw Project JSON does not already contain, so you do not need them to retrieve your data or to switch.

17.4 Charges

We charge nothing for switching, for exporting the data described in section 17.3, or for the assistance described above, and we will not introduce such a charge. Deliverables are paid features of the plans that include them; they are not a switching or data-export charge.

17.5 Erasure after exit

Once the retrieval period ends, or as soon as you ask us to, we erase your Customer Data from the live Service. An organisation or project you delete yourself is erased 30 days after you delete it, unless you restore it, or at once if you delete it permanently from Recently deleted or close your account. Copies in encrypted backups age out within our published backup retention period, and we do not restore erased data from a backup except to recover the Service as a whole — in which case we re-apply your erasure afterwards. We will confirm erasure in writing if you ask.

18. Data protection

Our Privacy Policy explains the personal data we handle as controller — your account, billing, security and feedback data. Where Customer Data contains personal data, you are the controller and we are your processor, on the terms of our Data Processing Agreement (the "DPA"), which is incorporated into these Terms and which you accept by accepting these Terms. The DPA includes our commitment to notify you of a personal data breach, our use of sub-processors and how we tell you about changes to them, and the safeguards for international transfers. Our current sub-processors are listed at railyard.sh/subprocessors.

19. Force majeure

Neither party is liable for a failure or delay in performing its obligations (other than an obligation to pay) caused by an event beyond its reasonable control — including an act of God, flood, fire, epidemic, war, civil unrest, terrorism, industrial action by third parties, a failure of public telecommunications or power networks, a government measure, or a denial-of-service attack. The affected party will tell the other as soon as practical and use reasonable efforts to mitigate. If the event continues for more than 30 days, either party may terminate on written notice, and we will refund fees paid for a period the Service was not provided (for a Project Pass, pro rata by day of its term).

20. Assignment and subcontracting

You may not assign or transfer these Terms without our written consent, except to a successor of your business that is not our competitor, on notice to us. We may assign or transfer these Terms to a group company or to a buyer of the business or assets to which they relate, provided your rights under them are not reduced; we will tell you if we do. We may use sub-processors and subcontractors to provide the Service (section 18), and we remain responsible to you for their performance.

21. Notices

We give you notice by email to the address on your account, or by a prominent message in the Service, and it takes effect when sent or displayed. You give us notice by email to [email protected], and it takes effect when we acknowledge it or on the next business day, whichever is earlier. Keep your account email address current — it is how we reach you about billing, security and changes to these Terms.

22. Entire agreement, waiver and severability

These Terms, together with the DPA and any separate written agreement we have signed with you, are the entire agreement between us about the Service, and replace any earlier understanding. Neither party relies on any statement not set out in them — though nothing here limits liability for fraudulent misrepresentation. Where a separate signed agreement conflicts with these Terms, that agreement prevails for the customer who signed it.

A delay in enforcing a right is not a waiver of it. If a provision is found invalid or unenforceable, it is modified to the minimum extent necessary or, if that is not possible, severed, and the rest of these Terms continue in force — subject to section 13, where each sub-clause stands on its own.

23. No third-party rights

These Terms are between you and us. No one else may enforce any of them under the Contracts (Rights of Third Parties) Act 1999, and we do not need anyone else's consent to vary or terminate them.

24. Export control and sanctions

You confirm that you are not, and are not owned or controlled by or acting on behalf of, a person or entity subject to UK, EU, US or UN sanctions, and that you are not located in a country or territory subject to comprehensive sanctions. You will not use the Service, or allow it to be used, in breach of applicable export control or sanctions laws. We may suspend or terminate access to comply with those laws.

25. Changes to these Terms

We may update these Terms. Each version carries a version stamp and effective date, and we keep dated copies of superseded versions — ask [email protected] for an earlier one. If a change is material we will give you reasonable notice by email or in the Service before it takes effect, and where the change materially affects your rights or obligations we will ask you to accept the new version when you next sign in or open the Service. Until you do, you cannot make changes in the Service, but you can still sign out and retrieve your data (your account data from the agreement screen, and your projects through the API), and you may terminate as described below.

If you do not agree to a material change, you may terminate before it takes effect and we will refund the unused part of any period you have paid for, or of a Project Pass pro rata by day. Changes to what a paid plan includes follow section 2. For consumers, a change does not bind you unless you accept it, and you may end the contract if we make one you have not accepted.

26. Governing law and jurisdiction

These Terms and any dispute arising out of or in connection with them are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction.

If you are a consumer, this does not deprive you of any protection given by the mandatory law of the country where you live, and you may bring proceedings in the courts of that country as well as in England and Wales. We may bring proceedings only in the courts of the country where you live.

27. Contact

Questions about these Terms, requests for an earlier version, and cancellation notices go to [email protected]. For privacy matters, use [email protected]; for security reports, see our Security page.

RailyardRack layouts, topologies, cabling and capacity — in one place.
DocsLearnAPI referenceFeedbackRoadmapTermsPrivacyDPASecurityAccessibilityContact
© 2026 Railyard Tech Ltd · Railyard · Railyard is a trading name of Railyard Tech Ltd, registered in England and Wales no. 17525277, 24 Elizabeth Road, Wokingham, England, RG40 1UB