Sibylline Platform Terms of Service

Document control

These Terms are a contract between Sibylline Labs Limited and the organisation that uses the Services. They are written for businesses. Read them before you connect a Linear workspace or run eris login.

1. Who we are and how to contact us

1.1 We are Sibylline Labs Limited ("Sibylline", "we", "us"), a company registered in England and Wales with company number 14632125. Our registered office is at 9 Cwrt-Y-Coed, Brackla, Bridgend, Wales, CF31 2ST. We were previously named Sibylline Advisory Ltd. Our VAT registration number is GB 439854253.

1.2 Support: contact@sibylline.group. Privacy: contact@sibylline.group. Legal notices: contact@sibylline.group, with a copy by post to our registered office marked "Legal".

2. These Terms and how they apply

2.1 These Terms govern access to and use of the Sibylline platform: the Portal, the API, the Services and each Product described in a Schedule. Schedule 1 covers Eris Yaks. If a Schedule conflicts with the main body of these Terms, the Schedule prevails for that Product.

2.2 The Privacy Policy and the Data Processing Agreement ("DPA") form part of these Terms. On data protection matters the DPA prevails over the rest of these Terms.

2.3 You accept these Terms when you do any of the following: connect a Linear workspace to the platform; install a Sibylline app in Linear; sign in to the Portal; run eris login; or submit data to the API using a credential issued to your Organisation. If you do not agree to these Terms, do none of these things.

2.4 The contract is between Sibylline and the Organisation: the company or other legal entity that owns or controls the Linear Workspace connected to the platform ("you"). The individual who accepts confirms that they have authority to bind the Organisation. If you connect a workspace that belongs to a client, you confirm that the client has authorised you to accept these Terms on its behalf.

2.5 The Services are provided for use in the course of business. We do not offer them to consumers. By accepting these Terms you confirm that you are not acting as a consumer. Nothing in these Terms limits rights that cannot be excluded by law.

2.6 The contract is concluded in English by the steps in clause 2.3. We do not file the concluded contract separately. The current Terms are always available at the Portal, and we will send you the version you accepted on request to contact@sibylline.group.

3. Definitions

In these Terms:

• Account Data means information about the Organisation, its Users and its billing: names, email addresses, Linear identifiers, roles, subscription state and invoices.
• Administrator means a User who is an admin of the Linear Workspace, or whom the Organisation otherwise designates as an administrator in the Portal.
• Agent means software, such as a coding agent, that submits Reports on behalf of a User or the Organisation.
• API means api.sibylline.group and any other endpoint we designate.
• Billing Administrator means the Administrator who first installs a paid Product, or whoever the Organisation later designates in the Portal.
• CLI means the eris command-line tool published at github.com/sibylline-labs/eris and on npm as @sibylline-labs/eris.
• Customer Data means data submitted to the Services by or on behalf of the Organisation, including Reports and their contents, and the Organisation's configuration. It excludes Account Data and Usage Data.
• Documentation means the CLI README, eris --help, the Portal help pages and the install page.
• Fees means the amounts payable under a Schedule.
• Linear means the issue-tracking service operated by Linear Orbit, Inc. Linear Workspace means the Organisation's workspace in Linear.
• Organisation has the meaning in clause 2.4, and includes the tenant record we keep for it.
• Portal means dash.sibylline.group, yak.sibylline.group and any successor sites.
• Privacy Policy means the Sibylline Platform Privacy Policy.
• Product means a service described in a Schedule to these Terms.
• Report means a submission to the Services from the CLI, an Agent or the API. In Eris Yaks a Report is called a yak.
• Seat has the meaning given in the applicable Schedule.
• Service Token means a credential issued by an Administrator for automated or headless use that is not bound to an individual User.
• Services means the platform, the Portal, the API, the Products and the Documentation. It excludes the CLI (clause 6) and Third-Party Services.
• Subscription Period means each monthly billing period.
• Third-Party Services means services we do not provide that interoperate with the Services, including Linear and Stripe.
• Trial has the meaning in clause 8.
• Usage Data means technical and statistical data about the operation and use of the Services: logs, metrics and audit events made up of references, counts and hashes. It excludes the body of any Report.
• User means an individual the Organisation permits to use the Services, including through the CLI or an Agent run by that individual.
• Vendor Report means a Report routed to Sibylline under Schedule 1.

4. Accounts, sign-in and administrators

4.1 Sign in with Linear is the only way to create an Organisation and to sign in. We create one Organisation bound to one Linear Workspace. You need a Linear account and workspace to use the Services, and Linear's own terms govern those.

4.2 Admins of the Linear Workspace are Administrators. Administrators may install and uninstall Products, configure where Reports are delivered, manage Seats and Service Tokens, view and manage billing, designate the Billing Administrator and delete the Organisation. We treat an Administrator's instructions as the Organisation's instructions.

4.3 You are responsible for your Users and Agents, for their compliance with these Terms, and for everything done with credentials issued to your Organisation, whether or not you authorised the particular act. The Services are not for anyone under 18.

4.4 A credential issued by eris login is bound to one User and one device. Keep credentials secret and do not share a User's credential with anyone else. Revoke a credential in the Portal as soon as you suspect it has been exposed, and tell us at contact@sibylline.group. We store only a hash of each credential and cannot recover a lost one.

4.5 When a User is removed from or deactivated in the Linear Workspace, we revoke that User's credentials and Seat once we learn of it, through Linear's notifications or our daily reconciliation. Until then the Organisation remains responsible for use of those credentials.

4.6 Keep the Billing Administrator's contact details accurate. We send notices about the Services and billing to that address.

5. The Services

5.1 We provide the Services as described in the Documentation and the applicable Schedule. Subject to these Terms, we grant the Organisation a non-exclusive, non-transferable right, for the term of these Terms, to access and use the Services for its internal business purposes through its Users and Agents.

5.2 We may add, change or remove features of the Services. We will give at least 30 days' notice before removing a core capability of a paid Product, unless the change is needed for security, to comply with law, or because a Third-Party Service has changed.

5.3 The Services depend on Third-Party Services, in particular Linear and Stripe. We are not responsible for Third-Party Services, and your use of them is governed by their own terms. By installing a Sibylline app in your Linear Workspace you authorise us to access the Workspace with the scopes shown at install (we do not request Linear's admin scope) and to create and update issues, comments and labels there on the Organisation's behalf. You can withdraw that authorisation at any time by uninstalling the app. If our access to Linear lapses or is revoked, we hold undelivered Reports and the Product enters a disconnected state, as described in the Schedule.

5.4 Features marked early access, beta or preview, and any Product used before we switch billing on for it, may be changed or withdrawn without notice. Clause 16.3 applies to them.

5.5 We may use subcontractors to provide the Services. We remain responsible for their performance under these Terms.

6. The eris CLI and open-source software

6.1 The CLI is open-source software licensed under the Apache License, Version 2.0. That licence, not these Terms, governs copying, modifying and distributing the CLI. These Terms govern use of the CLI to access the Services.

6.2 We publish CLI releases at our discretion and may require a minimum CLI version to access the API, so older versions may stop working. We do not accept third-party contributions to the CLI repository. Support for the CLI is provided under clause 15.

6.3 The CLI and the Documentation include optional material that instructs Agents to file Reports: a Claude Code hook, and snippets for AGENTS.md and CLAUDE.md. Installing that material is your choice. Your Agents act on your behalf, you control how they are configured, and you are responsible for what they submit.

6.4 Third-party open-source components in the CLI are licensed under their own terms, listed in the CLI repository.

7. Acceptable use

7.1 You must not, and must ensure that your Users and Agents do not:

• (a) use the Services unlawfully, or submit material that is unlawful, infringes anyone's rights, contains malicious code, or that you have no right to submit;
• (b) submit credentials, secrets, access tokens, private keys, payment card data or special category personal data in Reports. The CLI and the Services apply redaction, but redaction is a safeguard, not a guarantee. You remain responsible for what is submitted;
• (c) circumvent or probe caps, rate limits, redaction, tenant isolation or authentication; share credentials; or use a credential issued to another Organisation;
• (d) interfere with the operation of the Services or their infrastructure, or run load or security testing against them without our written consent;
• (e) reverse engineer, decompile or copy the hosted Services, or scrape the Portal. This does not apply to the CLI, which is open source;
• (f) resell or sublicense the Services, or operate them for third parties, except for a client whose Linear Workspace you manage under clause 2.4;
• (g) impersonate any person or Organisation, or submit Vendor Reports that are abusive or knowingly false.

7.2 Automated submission of Reports by Agents is the intended use of the Services. You must configure Agents so that they file Reports deliberately, not on every event, and within the caps in the Schedule. We may throttle or refuse submissions that exceed those caps.

7.3 If we reasonably believe this clause has been breached, we may remove or quarantine the Customer Data concerned and suspend access under clause 19.

8. Free trial

8.1 A Product may offer a free trial ("Trial"). The length and conditions of the Trial are in the Schedule for that Product. For Eris Yaks the Trial lasts at least 14 days and no payment card is required.

8.2 During the Trial the Product is provided free of charge. If you have not started a paid subscription by the end of the Trial, we stop accepting Reports after any grace period in the Schedule, and clause 10.6 applies to Customer Data.

8.3 One Trial per Organisation. We may change or withdraw the Trial offer for new Organisations at any time. A Trial that has already started keeps its stated length.

8.4 These Terms apply in full during a Trial, including clause 16 (warranties) and clause 18 (liability).

9. Fees, Seats and payment

9.1 The Fees for each Product are set out in its Schedule and in the Portal. Fees are stated in US dollars and exclude VAT and any other applicable tax, which you must pay in addition where it applies. If law requires you to deduct or withhold any tax from a payment, you must pay an additional amount so that we receive the full Fee. Fees are payable only once we have enabled paid plans for the Organisation, which we will do on notice to the Billing Administrator (paragraph 4.3 of Schedule 1). Clauses 9.2 to 9.5 apply from then.

9.2 We bill monthly in advance for each Subscription Period, based on the number of Seats at the start of the period. A Seat added during a Subscription Period is charged pro rata from the day it is added. A Seat removed during a Subscription Period stops being charged at the end of that period. We do not refund Fees for part of a Subscription Period.

9.3 Payment is taken by Stripe using the payment method on file. Stripe holds your payment details and we do not see full card numbers. By starting a paid subscription you authorise recurring charges to that payment method until you cancel. Stripe's terms apply to the processing of payments.

9.4 We count Seats from the Organisation's Seat and credential register, which the Billing Administrator can see in the Portal, and we reconcile that count with Stripe daily. Our register is conclusive unless it is shown to be wrong.

9.5 If a charge fails, or no payment method is on file when a payment falls due, the Product enters a grace period of 7 days during which Reports are still accepted and held. After the grace period we may suspend the Product until the overdue amount is paid. We may charge interest on overdue amounts at the rate set by the Late Payment of Commercial Debts (Interest) Act 1998.

9.6 We may change the Fees for a Product by giving the Billing Administrator at least 30 days' notice. The new Fees apply from the first Subscription Period that starts after the notice period ends. If you do not accept the change, cancel before then under clause 20.2.

9.7 Promotion codes are subject to the conditions stated with them, apply once per Organisation unless stated otherwise, and may be withdrawn if misused.

9.8 If you dispute a charge, tell us within 30 days of the invoice date at contact@sibylline.group. Any undisputed part remains payable.

9.9 Invoices and receipts are issued through Stripe. The Billing Administrator can view them, update the payment method and cancel through the Stripe customer portal linked from the Portal.

10. Customer Data

10.1 Customer Data belongs to you. You keep all rights in it. We claim no rights in Customer Data other than the licence in clause 10.2.

10.2 You grant us a non-exclusive, worldwide, royalty-free licence to host, copy, process, transmit and display Customer Data as needed to provide the Services, to deliver Reports to your Linear Workspace, to detect and address security or operational problems, and to comply with law.

10.3 A Vendor Report is submitted to us for our own use and is governed by paragraph 6 of Schedule 1.

10.4 We do not use Customer Data to train or improve machine-learning or AI models, and we do not permit our sub-processors to do so. We may use Usage Data, and aggregated statistics derived from Customer Data that do not identify the Organisation or any individual, to operate, secure and improve the Services.

10.5 Customer Data is stored and processed in the United States. The Schedule for each Product states how long we keep Customer Data.

10.6 When you uninstall a Product, delete the Organisation, or these Terms end, we stop accepting Reports and delete the Customer Data for that Product within 30 days, except for the metadata the Schedule says we keep, copies in backups, which are overwritten within 30 days, and anything we must keep by law. Reports already delivered to your Linear Workspace stay there: that is your copy of record, and we do not provide a separate export.

10.7 You are responsible for the content, accuracy and legality of Customer Data, for having the rights and permissions needed to submit it, and for any notices your Users need to receive about it.

10.8 Our personnel access the body of a Report only to provide the Services, to handle a support request or Vendor Report you have made, to investigate a security or operational problem, or where the law requires. Access is logged.

11. Data protection

11.1 Each party will comply with the Data Protection Laws (as defined in the DPA) in relation to these Terms.

11.2 Where Customer Data includes personal data, we process it as your processor under the DPA.

11.3 We process Account Data and Usage Data as a controller, as described in the Privacy Policy. You must make the Privacy Policy available to your Users.

11.4 International transfers of personal data are addressed in clause 7 of the DPA.

12. Confidentiality

12.1 "Confidential Information" means information one party discloses to the other under these Terms that is marked confidential or would reasonably be regarded as confidential. Customer Data is your Confidential Information. The non-public parts of the Services, our security measures, our roadmap and any pricing offered to you individually are our Confidential Information.

12.2 Each party will keep the other's Confidential Information confidential, use it only for the purposes of these Terms, and disclose it only to its personnel, professional advisers and subcontractors who need to know it and are bound by obligations at least as protective as this clause.

12.3 Clause 12.2 does not apply to information that is or becomes public other than through a breach of these Terms, that the receiving party already held without a duty of confidence, that it develops independently, that it lawfully receives from a third party, or that it must disclose by law, by court order or to a regulator. Where the law allows, a party required to disclose will tell the other first.

12.4 This clause lasts for the term of these Terms and three years after. For trade secrets it lasts as long as they remain trade secrets.

13. Intellectual property

13.1 We and our licensors own all intellectual property rights in the Services, the Portal, the Documentation and the hosted software. Customer Data (clause 10) and the CLI (clause 6) are excluded. Nothing in these Terms transfers ownership of anything to either party; your rights in the Services are the licence in clause 5.1.

13.2 If you give us suggestions or feedback about the Services, you grant us a perpetual, irrevocable, royalty-free licence to use it for any purpose without obligation to you. Feedback does not include Customer Data.

13.3 Sibylline, Eris, Eris Yaks, Olympus and Socrates are our trade marks. You may refer to the Services by name to describe your use of them. You may not use our logos without our written consent. We may identify the Organisation as a customer by name and logo in our marketing unless you tell us not to.

14. Security

14.1 We maintain technical and organisational security measures appropriate to the risk, described in Annex 2 of the DPA. They include a separate data store for each Organisation, storage of credentials as hashes only, encryption in transit, encrypted storage of your Linear credentials, and redaction of Reports on your machine and again on our side.

14.2 You are responsible for the security of your own systems, devices, Linear Workspace, Agents and credentials; for configuring redaction and Agent behaviour appropriately; and for reviewing what your Agents submit.

14.3 We will tell the Billing Administrator without undue delay after we confirm a security incident that affects your Customer Data. Clause 8 of the DPA applies where personal data is involved.

14.4 Report suspected vulnerabilities in the Services or the CLI to contact@sibylline.group. Do not test them against the live Services without our written consent (clause 7.1(d)).

15. Support and availability

15.1 Support is provided by email to contact@sibylline.group and through Vendor Reports (eris yak --vendor). We respond during UK business hours (09:00 to 17:30 UK time, Monday to Friday, excluding bank holidays in England and Wales) and aim to give a first response within two business days. We do not commit to resolution times.

15.2 We aim to keep the Services available at all times, but we do not commit to any level of availability and do not offer service credits. We may suspend the Services for maintenance. Where practicable we will do so outside UK business hours and give notice of planned maintenance that affects the acceptance of Reports.

15.3 A Report is received only when the API returns a receipt for it. A submission that receives no receipt, for example because of a network failure, a lapsed subscription or an invalid credential, is not stored. The CLI is designed to warn rather than block your Agent in that case.

15.4 Delivery of Reports to your Linear Workspace depends on Linear. We retry failed deliveries and hold undelivered Reports. If our access to Linear is disconnected, we notify the Billing Administrator, show a notice in the Portal and in the CLI, and hold Reports until access is restored.

16. Warranties

16.1 Each party warrants that it has the authority to enter into these Terms.

16.2 We warrant that we will provide the Services with reasonable care and skill and substantially in accordance with the Documentation. If we breach this warranty, we will use reasonable efforts to correct the problem. If we cannot correct it within 30 days of your notice, you may terminate the affected Product and we will refund any Fees you have paid in advance for the period after termination. This is your only remedy for breach of this warranty.

16.3 Except as stated in clause 16.2, the Services and the CLI are provided as they are. To the extent the law allows, we exclude all other warranties, conditions and terms, express or implied, including any implied terms of satisfactory quality, fitness for a particular purpose and non-infringement. In particular, we do not warrant that the Services will be uninterrupted or error-free, that every Report will be delivered, that redaction will remove all sensitive content, that clustering, deduplication or routing will be accurate, or that the Services will meet your requirements. Early access, beta and preview features, and any Product used before billing is switched on for it, are provided without the warranty in clause 16.2.

16.4 Reports are written by your Agents and Users. We do not check their content, and decisions you take on the basis of Reports are yours.

17. Indemnities

17.1 You will indemnify us against all claims, losses, damages and costs, including reasonable legal fees, arising from: (a) Customer Data or Vendor Reports, including any claim that they infringe a third party's rights or that you had no right to submit them; (b) use of the Services by you, your Users or your Agents in breach of these Terms or of the law; and (c) your Linear Workspace or any other Third-Party Service account you connect.

17.2 We will defend you against any third-party claim that the Services, as provided by us, infringe a patent, copyright or trade mark enforceable in the United Kingdom or the European Union, and we will pay the damages finally awarded or the settlement we agree. This does not cover the CLI, Customer Data, Third-Party Services, open-source components, modifications we did not make, combinations with anything we did not supply, or use after we have told you to stop. If a claim is made or we think one is likely, we may obtain the right for you to continue, change the Services so they do not infringe, or terminate the affected Product and refund any Fees paid in advance for the period after termination. This clause is your only remedy for infringement of intellectual property rights by the Services.

17.3 A party seeking an indemnity must tell the other party promptly in writing, give it control of the defence and any settlement, and give reasonable cooperation at the indemnifying party's cost. The indemnifying party may not settle a claim in a way that admits fault on the other party's behalf without its written consent.

18. Liability

18.1 Nothing in these Terms limits or excludes either party's liability for death or personal injury caused by its negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot be limited or excluded by law. Nothing in these Terms limits your obligation to pay Fees or your indemnity under clause 17.1.

18.2 Subject to clause 18.1, neither party is liable to the other, whether in contract, tort (including negligence), breach of statutory duty or otherwise, for any indirect or consequential loss, or for any loss of profit, revenue, business, goodwill or anticipated savings, or for loss or corruption of data other than through our breach of clause 10 or the DPA, even if the loss was foreseeable.

18.3 Subject to clauses 18.1 and 18.2, each party's total liability to the other arising out of or in connection with these Terms, for all claims arising in any period of 12 months, is limited to the greater of: (a) the Fees paid by the Organisation to us in the 12 months before the first event giving rise to a claim in that period; and (b) US$1,000.

18.4 The limits in clause 18.3 apply during a Trial and to any Product for which no Fees are payable. They apply to our indemnity in clause 17.2.

18.5 The parties agree that these limits are reasonable given the level of the Fees, the nature of the Services, and the fact that every delivered Report is held in your own Linear Workspace as your copy of record.

19. Suspension

19.1 We may suspend an Organisation's or a User's access to all or part of the Services, giving notice where practicable, if: (a) Fees are overdue beyond the grace period in clause 9.5; (b) we reasonably believe there is a breach of clause 7 or a threat to the security of the Services; (c) a Third-Party Service requires it or withdraws our access; (d) the law or a regulator requires it; or (e) continued use would harm the Services, other customers or third parties.

19.2 We will limit any suspension to what is needed and lift it once the cause has been resolved. Fees remain payable during a suspension caused by your breach or non-payment.

20. Term and termination

20.1 These Terms start when you accept them under clause 2.3 and continue until terminated under this clause. A paid subscription renews automatically each Subscription Period until it is cancelled.

20.2 You may cancel a Product at any time in the Portal, through the Stripe customer portal, or by uninstalling the Sibylline app from your Linear Workspace. Cancellation takes effect at the end of the current Subscription Period. You keep access until then and we do not refund the remainder of the period. You may delete the Organisation at any time in the Portal, which ends these Terms.

20.3 Either party may terminate these Terms, or the affected Product, by notice if the other party materially breaches them and, where the breach can be remedied, does not remedy it within 30 days of a notice asking it to. We may terminate immediately for a serious breach of clause 7.

20.4 We may also terminate these Terms or a Product: (a) immediately if you become insolvent, enter administration or liquidation, make an arrangement with your creditors, or suffer anything similar in any jurisdiction; (b) immediately if a Third-Party Service we depend on withdraws access and we cannot reasonably provide the Product without it; and (c) for any other reason on 60 days' notice, in which case we will refund any Fees paid in advance for the period after termination.

20.5 On termination: your right to use the Services ends; we revoke the Organisation's credentials; we handle Customer Data under clause 10.6; and any Fees accrued remain payable. Clauses 3, 9 (as to accrued Fees), 10, 11, 12, 13, 16.3, 16.4, 17, 18, 20.5, 22 and 23 survive termination.

21. Changes to these Terms

21.1 We may update these Terms. We will post the new version in the Portal with its effective date and keep a change log at the end of the document. For a material change we will give the Billing Administrator at least 30 days' notice by email and a notice in the Portal. A change that is required by law, that clarifies the existing text, or that adds a Schedule for a Product you do not use may take effect when posted.

21.2 If you do not accept a change, cancel under clause 20.2 before it takes effect. Continued use of the Services after a change takes effect is acceptance of it.

22. General

22.1 These Terms, including the Schedules, the DPA and the Privacy Policy, are the entire agreement between the parties about the Services. Each party confirms that it has not relied on any statement not set out in them. Terms printed on a purchase order or similar document you issue have no effect.

22.2 You may not assign or transfer these Terms without our written consent, which we will not unreasonably withhold, except to a successor to the whole of your business on notice to us. We may assign or transfer these Terms to an affiliate or to a successor to our business, on notice to you.

22.3 We give notice to you by email to the Billing Administrator, and may also use a notice in the Portal or the CLI. You give notice to us by email to contact@sibylline.group, with a copy by post to our registered office for any notice of breach or termination. An email notice is treated as received on the business day it is sent if sent before 17:00 UK time, and otherwise on the next business day.

22.4 Neither party is liable for failure or delay caused by events beyond its reasonable control, including failure of a Third-Party Service, of a cloud or network provider, or of the internet, provided it tells the other party and uses reasonable efforts to resume. This does not excuse payment of Fees. If the failure continues for more than 30 days, either party may terminate the affected Product by notice.

22.5 A delay or failure to enforce any right under these Terms is not a waiver of it. If any part of these Terms is found invalid or unenforceable, the rest remains in force and the invalid part is treated as modified to the minimum extent needed to make it valid.

22.6 No one other than the parties has any right to enforce these Terms under the Contracts (Rights of Third Parties) Act 1999.

22.7 The parties are independent contractors. These Terms do not create a partnership, agency or employment relationship.

22.8 You confirm that you, your owners and your Users are not the subject of sanctions imposed by the United Kingdom, the European Union, the United Nations or the United States, and you will not use the Services in breach of applicable export control or sanctions laws.

22.9 Each party will comply with the Bribery Act 2010 and will not do anything that would cause the other to breach it.

22.10 These Terms are written in English. Any translation is for convenience only.

22.11 Headings do not affect interpretation. "Including" means including without limitation. A reference to a law includes any amendment or replacement of it.

23. Governing law and disputes

23.1 These Terms, and any non-contractual obligations arising out of or in connection with them, are governed by the law of England and Wales.

23.2 Before starting court proceedings, each party will try to resolve a dispute by discussion between a senior representative of each party for a period of 30 days from one party's written request. This does not prevent either party from seeking urgent interim relief or from recovering undisputed Fees.

23.3 The courts of England and Wales have exclusive jurisdiction over any dispute arising out of or in connection with these Terms. We may nevertheless apply to any court for an injunction or similar relief to protect our intellectual property or Confidential Information.

Schedule 1: Eris Yaks

1. The Product

1.1 Eris Yaks lets the Organisation's Users and Agents file Reports ("yaks") about friction in their coding-agent tooling with the eris yak command. We receive each Report at the API, store it in the Organisation's own data store, group related Reports into clusters, and deliver each cluster as an issue in the Organisation's Linear Workspace. Later Reports in the same cluster are added to that issue as comments and counted, so a repeated problem produces one issue, not many.

1.2 Reports carry a verb: issue, suggest or fatal. A fatal Report sets the Linear issue to Urgent priority if the Organisation has enabled that. We may add verbs.

1.3 Your Linear Workspace is the system of record for Reports. Our data store holds a Report only for as long as paragraph 7 says.

2. The Linear app and configuration

2.1 An Administrator installs the Eris Yaks app in the Linear Workspace. The app requests the Linear scopes read, write, issues:create and comments:create. It does not request Linear's admin scope.

2.2 An Administrator configures where Reports are delivered: the Linear team (required), project (optional), initial workflow state (Triage by default), labels (we create a Yak label and one label per verb, which can be remapped), the new-issue cap, and whether fatal Reports are set to Urgent. Members of the Workspace can view this configuration but not change it.

2.3 Until a destination is configured, Reports are accepted and held. The receipt returned to the CLI says so.

2.4 We create issues in Linear as the Eris Yaks app. Each Report comment is attributed to the reporting User by name ("Alice (via Eris Yaks)") or, for a Service Token, to the token's name. We do not delete issues in your Workspace, we do not reopen an issue you have closed, and we stop adding comments to a cluster whose issue you have cancelled or marked as a duplicate.

2.5 We refresh the Linear access token we hold for the Organisation. If a refresh fails or you uninstall the app, Eris Yaks enters a disconnected state: Reports are accepted and held, we notify the Billing Administrator, and a notice appears in the Portal and in the CLI. Reinstalling or re-authorising the app restores delivery.

2.6 While Eris Yaks is suspended under clause 19, or lapsed under clause 9.5 after the grace period, a submission receives an error, the CLI warns and does not block the Agent, and no Report is stored.

3. Seats and Service Tokens

3.1 A Seat is a User who holds an active credential issued by eris login for the Organisation. A User with credentials on several devices is one Seat.

3.2 The Organisation may hold up to three active Service Tokens at no charge. Each further active Service Token counts as one Seat.

3.3 A Seat is added when a credential is issued and removed when every credential for that User is revoked. Clause 9.2 governs how Seats are charged.

4. Fees and Trial

4.1 The Fee is US$3 per Seat per month.

4.2 The Trial lasts at least 14 days from the day the Organisation first installs Eris Yaks, or from the day we switch billing on for Eris Yaks if the Organisation installed it before then. No payment card is needed to start the Trial. A paid subscription is needed to continue after the Trial.

4.3 Organisations that installed Eris Yaks before we switched billing on use it free until then. We will give the Billing Administrator at least 14 days' notice before billing starts.

5. Reports, redaction and caps

5.1 A Report contains: the summary and body written by the User or Agent; any evidence the Agent attaches; and provenance, which includes the CLI version, the type of agent or harness, a device identifier, an execution identifier, the git identity configured on the machine, and the names of the repositories the Report concerns.

5.2 The CLI redacts recognised secret patterns before a Report leaves the machine, and our side applies the same rules again on receipt. Redaction is best-effort and does not catch everything. If a User disables redaction with --no-redact, the Organisation accepts the risk of what is sent.

5.3 The following caps apply, with current values published in the Documentation: a maximum size per Report, beyond which the API rejects the submission and stores nothing; a cap on new issues created per Organisation in a period; a cap on comments per cluster; and rate limits per credential and per Organisation. We may change the values with notice in the Documentation and the Portal. A submission beyond a cap is refused or held, and the CLI is told which.

5.4 A Report resubmitted with the same content, device and execution identifiers is treated as the same Report, not a new one.

5.5 If we cannot deliver a Report to Linear after repeated attempts, we mark it as failed and show it in the Portal. We may ask you to resubmit it.

6. Vendor Reports

6.1 A Report filed with eris yak --vendor, or a Report about the eris CLI itself, is a Vendor Report. It is delivered to Sibylline's own Linear workspace, not yours, and carries the Organisation's identifier and the reporting User's name. You receive a receipt and can see the status of your Vendor Reports in the Portal and with eris yak reports, but you cannot read the issue in our workspace.

6.2 You grant us a non-exclusive, perpetual, irrevocable, worldwide, royalty-free licence to use, copy, modify and act on the content of Vendor Reports to investigate, support, fix and improve the CLI and the Services, including after these Terms end. The CLI is open source, so a fix prompted by a Vendor Report may be published. Do not include in a Vendor Report anything you would not want us to hold for that purpose.

6.3 We treat Vendor Reports as your Confidential Information and will not disclose one to another customer in a form that identifies you. We are not obliged to act on any Vendor Report.

6.4 Where a Vendor Report contains personal data, we process it as a controller for the purposes in paragraph 6.2, as described in the Privacy Policy.

7. Retention, deletion and location

7.1 For a Report that has been delivered to Linear, we delete the body and evidence 30 days after delivery. We keep the metadata (identifiers, timestamps, verb, cluster, deduplication fingerprint and the Linear issue reference) for the life of the Organisation so that repeated Reports continue to be matched and counted.

7.2 We keep an undelivered Report until it is delivered or deleted under paragraph 7.3.

7.3 An Administrator can delete Reports and the Organisation's Eris Yaks data in the Portal. Uninstalling the Eris Yaks app stops acceptance of Reports and schedules deletion of the Organisation's Eris Yaks data within 30 days. We keep audit events, which contain references, counts and hashes but no Report content, for the life of the Organisation for security, billing and dispute purposes.

7.4 All Eris Yaks data, including undelivered Reports, audit events and backups, is stored in the United States. We do not offer storage in any other region.

Change log