Terms of Service

These terms are the agreement between Intracia Ltd. — registered in the Bailiwick of Guernsey, company number 124060 — and you, for use of Intracia (the "Service"). It sits alongside our Privacy Policy, Acceptable Use Policy and Data Processing Agreement.

These terms describe the deal as we intend it, in plain English. If something here doesn't work for your organisation, tell us. We read these ourselves, and we can discuss changes.

1. Agreeing to these terms

You agree to these terms by creating an account or by using the Service. If you're doing that for a company or other organisation, you confirm you're authorised to bind it, and "you" means that organisation.

This agreement brings in 2 other documents. The Acceptable Use Policy sets out what you may not use the Service for, and counts as part of these terms. The Data Processing Agreement governs our handling of personal data inside your content.

The Privacy Policy isn't part of this agreement — it describes what we do with personal data, rather than being a promise you're making to us.

If these terms conflict with the DPA on anything to do with personal data, the DPA wins. If they conflict with the Acceptable Use Policy on anything else, these terms win.

2. What the Service is

Intracia is a content management system for websites whose content lives in a Git repository. It lets you and the people you invite edit structured content, preview it, and publish it by writing commits to your repository and triggering deployments on your hosting.

Intracia is in early access. That means:

• We may change features, replace them, or withdraw them.
• We promise nothing about availability. There's no service level agreement, no uptime figure, and no support response time. We'll do our best, and our best isn't yet a contractual promise.
• We charge nothing during this period. Section 10 covers what happens when that changes.

If you need guarantees rather than good intentions, early access isn't the moment to depend on us for something critical. Tell us what you need before you build on it, and we'll say whether we can promise it yet.

3. Your account

You're responsible for the accuracy of what you tell us, for keeping your sign-in credentials secure, and for everything done through your account.

You're responsible for the people you invite. What they publish and what they can see is your responsibility. Organisation membership reaches every site in that organisation, and an organisation administrator holds administrator rights across all of them. So an invitation can grant considerably more than it appears to. The Privacy Policy sets out exactly what one person can see about another.

Accounts are for people, not for roles. Please don't share one.

4. Your content

Your content is yours. Nothing in these terms transfers ownership of anything you create, upload or connect.

To run the Service we need a licence to handle it, limited to exactly that. You grant us a non-exclusive, worldwide, royalty-free licence to host, store, copy, transmit, modify and display your content, for the sole purpose of providing the Service to you. Modifying covers only what the Service's own features require — resizing an image, writing a commit. It ends when the content is deleted or the agreement ends, except for copies in backups, which age out on their normal cycle.

We don't train models on your content, and we don't use it for marketing, for research, or for anything that isn't operating the Service for you. Where a feature sends content to a third party — the AI features in section 8 — the Privacy Policy says so, and we choose providers whose terms exclude training on it.

You're responsible for your content: for having the right to publish it, for it not infringing anyone else's rights, and for its compliance with the Acceptable Use Policy.

5. Our intellectual property

The Service, its software, and everything we put into it are ours and remain ours. These terms grant you a right to use it while the agreement lasts, and nothing more. Don't resell it, copy it, or take it apart in order to build a competing product.

6. Feedback

If you tell us how to make the Service better, we may act on it freely and without owing you anything. This isn't us taking your ideas — it's avoiding a situation where a helpful suggestion in a support thread creates an ownership question about a feature.

7. Git, hosting, and the services you connect

This is where responsibility divides, so it's the section that decides who carries what.

The Service works by writing to your Git repository and triggering builds on your hosting. That's deliberate: your content stays somewhere you control, and if we vanished tomorrow your site would keep working. It also means:

• You're responsible for the repositories, buckets and deployment targets you connect, for having the right to connect them, and for the credentials you give us. Use the narrowest credential that works.
• We aren't responsible for those third-party services, their availability, or their terms. Their acceptable-use terms apply to your content in addition to ours, and they can act on their own account without reference to us.
• A failed push, a merge conflict, a broken build or a bad deployment on your infrastructure isn't a failure of the Service — though we'll help you work out what happened.

Where we host it for you. For customers whose sites we built, the repository may sit in our GitHub organisation and the storage bucket in our Cloudflare account. Where that's so it's recorded in your agreement with us. At the end of the engagement, or whenever you ask, we'll transfer the repository to an organisation you nominate and copy the objects into a bucket in your own account. You don't have to give a reason.

Preview links are bearer tokens. Anyone holding the link can see the draft, without signing in. That's what makes them useful; treat them accordingly.

8. The AI features

The alt-text and template assistance features send data to third-party models, as the Privacy Policy describes. They run only when you invoke them.

A model's output is a suggestion, not a fact. We don't warrant that it's accurate, appropriate, or free of anyone else's rights. What you publish is yours and you're responsible for it, whether you wrote it or accepted it.

9. Acceptable use, and suspension

The Acceptable Use Policy sets out what the Service may not be used for and what we do about a violation, including when we suspend or terminate an account. It forms part of this agreement and that document governs.

Where we suspend rather than terminate, your content stays where it's while the matter is resolved.

10. Fees

The Service is free during early access. There's no charge, no card on file, and no payment processor involved.

When we introduce charges we'll give you at least 30 days' notice before any fee applies to your account, tell you the price, and let you close your account instead, without penalty. Nothing you have used for free becomes chargeable retrospectively. These terms will be updated to cover invoicing, taxes, late payment and renewal before that happens rather than after.

11. Ending the agreement

You may stop at any time, by closing your account or by not using the Service any more. You don't need a reason, and you don't need to send us anything.

We may end it by giving you 30 days' written notice, or immediately where the Acceptable Use Policy allows.

When the agreement ends:

• Your content in your own repositories and buckets is unaffected — it was never ours to take away, which is rather the point of the arrangement.
• Your editing setup lives only in our database — schemas, templates, area definitions, queries and media attributes. Your site doesn't need it to run, but rebuilding it does take work. Ask and we will send you a copy; the DPA gives you 30 days. We don't export unpublished drafts: publish one, or copy the Markdown out.
• Where we host the repository or bucket for you, section 7 applies and we transfer it out.
• We delete the personal data we hold as controller on the timetable in the Privacy Policy, and the content we hold as processor on the timetable in the DPA.
• Anything either of us already owes the other survives, along with sections 4, 12, 13, 14 and 15.

12. Warranties, and what we don't promise

The Service is provided "as is". To the fullest extent the law allows, we exclude all implied warranties, including fitness for a particular purpose, satisfactory quality, and non-infringement.

We don't warrant that the Service will be uninterrupted, error-free, or that it will meet your requirements. During early access, see section 2: we promise nothing about availability at all.

Nothing in these terms excludes or limits liability that can't lawfully be excluded — including liability for death or personal injury caused by negligence, for fraud, or for fraudulent misrepresentation.

13. Liability

Subject to section 12, and to the fullest extent the law allows:

• Neither of us is liable to the other for indirect or consequential loss, loss of profits, loss of business, loss of goodwill, or loss of anticipated savings.
• We aren't liable for loss of your content, because the architecture is built so that we don't have to be: your content lives in your own Git repository, and keeping your own backups of the repositories, buckets and deployments you connect is your responsibility.
• Our total liability arising out of this agreement is limited to the greater of the fees you paid us in the 12 months before the claim and £500.

That cap is deliberately modest and reflects a free product at an early stage. If you need a different allocation of risk, that's a conversation to have before you depend on us rather than after.

14. Indemnity — if someone sues us over what you did

To indemnify someone is to stand behind them financially: if a third party comes after us because of something you did, you carry the cost rather than us.

You'll indemnify us against claims, losses and reasonable costs arising from your content, from your use of the Service in breach of these terms or the Acceptable Use Policy, or from your infringement of anyone else's rights.

We'll tell you promptly about any such claim, let you control its defence, and not settle it without your agreement.

15. Confidentiality

Each of us will keep the other's non-public information confidential, use it only for this agreement, and protect it as carefully as our own. That doesn't apply to information which is public, already known, independently developed, or required by law to be disclosed. Where the law requires it, we'll tell you first if we're permitted to.

16. Publicity

We won't name you as a customer, or use your logo, without asking first. If you say yes and later change your mind, tell us and we'll remove it.

17. Changes to these terms

We'll update these terms as the Service and the law change, and revise the date at the top.

Where a change is material — anything affecting your rights, our liability, or what you pay — we'll tell you at least 30 days beforehand, at the address on your account. It takes effect on the date we give. If you would rather not accept it, close your account before then and it won't apply to you.

We won't treat mere continued use as agreement to a change that matters. For minor corrections and clarifications, the date at the top is the notice.

18. General

Assignment. You may not assign this agreement without our consent. We may assign it to a company that acquires our business, having told you first, as the Privacy Policy describes.

Entire agreement. These terms, with the Acceptable Use Policy and the DPA, are the whole agreement between us about the Service, and replace anything said beforehand.

Severability. If any part is unenforceable, the rest continues.

Waiver. Not enforcing something once doesn't mean giving it up.

Events outside our control. Neither of us is liable for a failure caused by something genuinely outside our control. Lawyers call this force majeure.

Notices. We write to the email address on your account; you write to hello@intracia.com.

No partnership. Nothing here makes us partners, or either of us the other's agent.

19. Governing law

These terms, and any dispute arising out of them, are governed by the law of the Bailiwick of Guernsey, and the courts of Guernsey have exclusive jurisdiction.

Nothing here deprives you of the protection of any mandatory consumer law of the country you live in, where that law applies to you.

20. How to reach us

You can also use the contact form, which reaches the same people.

Intracia Ltd.
Ohana
La Route du Coutanchez
St Peter Port
GY1 2TX
Guernsey