simse Terms of Service

Effective date: 20 September 2026

Revised 29 September 2026 — Section 10 no longer says our in-cluster copy of the backups is unencrypted: it now sits on its own encrypted volume.

Revised 28 September 2026 — deleting your account now cancels a paid subscription immediately, before our record of it is erased, so the summary under "At a glance" and Sections 15.1, 15.2 and 16.4 no longer tell you to cancel first; a renewal charged after a deletion made before this date is refunded on request.

Revised 27 September 2026 — deleting your account does not cancel a paid subscription, so the summary under "At a glance" and Sections 15.1, 15.2, 15.5 and 16.4 now tell you to cancel before you delete, state that a renewal falling after deletion is still charged, and commit us to cancel that subscription and refund such a renewal in full when you tell us. Sections 4.1 and 4.2 now state that the included allowance and the extra-usage spending cap reset weekly, at 00:00 UTC each Monday, separately from the billing period; Sections 4.7 and 15.3, that after a failed payment the paid features stop when our payment processor ends its retries and cancels the subscription, not on a fixed day; and Section 4.8, that we do not currently add tax to a charge. Sections 2.4 and 7.4 now state that scribe's approval prompt is on by default and can be relaxed, and that a command sent from the web dashboard to scribe running as a remote daemon runs without it. Section 16.3 no longer says we hold no commercial API key: we hold one, unfunded and unused.

These terms are the contract between you and us for simse — the app at simse.dev, the developer portal at platform.simse.dev, the API at api.simse.dev, and the scribe command-line tool.

Read Section 4 for money. Read Section 5 for who owns what. Read Section 12 and 13 for the limits on what you can claim from us.

Schedule A — Entity particulars

These are the only blanks in this document. Everything else is decided. Fill them in at publication and delete the bracket markers.

Wherever these terms say "we", "us", "our" or "simse", they mean the entity named at A-1. simse is a product of Telor.

At a glance

• You get a licence to use simse. You keep everything you put in and everything the model writes for you (Section 5).
• Plans renew automatically until you cancel. Cancelling takes effect at the end of the period you have already paid for (Section 4). Deleting your account cancels a paid plan at once, and the rest of the period is not refunded (Section 16.4).
• Subscription fees and credits are not refundable, except where the law says otherwise (Section 4.6).
• The output is generated by an AI model and is often wrong. Check it before you rely on it. We do not warrant it (Sections 7 and 12).
• Break the Acceptable Use Policy and we can suspend or close your account (Sections 6 and 15).
• Close your account and we delete your data across our live systems. Billing records, the security audit trail, our email suppression list and backups outlive that; Section 16.3 lists what survives and for how long.

1. The agreement, and how it is formed

1.1 These terms take effect when you create an account, sign in, or use any part of simse — whichever happens first. If you do not accept them, do not use simse.

1.2 These terms, the Acceptable Use Policy, the Privacy Policy, the AI Transparency Notice, the published pricing page, and — where you process other people's personal data through simse — the Data Processing Agreement, are one agreement. If they conflict, the order of precedence is: the Data Processing Agreement for the processing of your end users' personal data, then these terms, then the other documents.

1.3 If you accept these terms for a company or other organisation, you confirm you are authorised to bind it, and "you" means that organisation.

1.4 We sell self-serve. There is no negotiated form of this agreement, no per-customer variation, no enterprise tier, no team or per-seat plan, and no customer-specific service-level agreement. Anyone who tells you otherwise is not speaking for us.

2. What simse is

2.1 simse is an AI project manager. It plans work, delegates it to AI models, and keeps large projects consistent. You reach it through:

• the web app at simse.dev — chat, group rooms, projects and tasks, a knowledge library, scheduled work, notifications, account and billing settings;
• scribe, the command-line client, which runs on your own machine;
• the API at api.simse.dev, which is wire-compatible with the Anthropic Messages API, plus the TypeScript, Python and Rust client libraries; and
• the developer portal at platform.simse.dev, including the documentation and the published API specification.

2.2 The service includes generation and token counting, model listing, sessions, agents, stored memories, connectors, plugins, schedules, workflows, files, the knowledge library, artifacts, and read access to your usage and billing records.

2.3 The models are not ours. Generation is served by third-party models under named tiers — rye, zoysia (the default), bermuda and fescue. Everything you send on a generation request is transmitted to the model provider, unredacted: your messages, the whole conversation history, the system prompt including any memories recalled for you, tool definitions, tool results, and any document or image you attached. Section 3 of the AI Transparency Notice and Section 5 of the Privacy Policy set this out in full. Embeddings are computed on our own hardware and are not sent to the provider.

2.4 Agent actions. simse can run tools — read and write files, run commands, fetch URLs, search the web. Where scribe runs on your machine, by default it asks for your approval before it writes a file or runs a command. You can relax that: one mode lets it edit files in your project without asking, another stops it asking at all, and a rule you save can allow a tool without asking. An unattended invocation refuses a call that would need approval rather than proceeding without one, with one exception: a command sent from the web dashboard to scribe running as a remote daemon on your machine runs as issued, with no approval prompt. Where we run an agent for you on our servers, tool calls are not approval-gated: they execute and you see the result afterwards. Scope what you give a server-side run accordingly.

2.5 Which features are available to you depends on your plan and on feature flags we control. We turn features on and off, including turning a feature off for everyone.

3. Your account and eligibility

3.1 Sign-in is passwordless. You sign in with a single-use email link or with Google. A sign-in link is valid for 15 minutes and can be used once. Anyone holding that link during the window can sign in as you, so treat the email that carries it as a credential.

3.2 You must be at least 16 years old to use simse. If the law where you live sets a higher age for consenting to online services without a parent, you must meet that age instead. simse is not built for children and we do not knowingly serve them. If we learn an account belongs to someone under age, we close it.

3.3 One account is one person. Accounts are individual; there are no team accounts and no shared seats. Do not share your account, your sign-in link, or your API keys.

3.4 You are responsible for everything done through your account, including by an API key you minted and by any agent, script or application you point at simse.

3.5 Keep your account email address current. It is how we reach you, and Section 19 makes notice to it effective.

3.6 You may not use simse if you are located in, ordinarily resident in, or acting on behalf of someone in a country or region subject to comprehensive trade sanctions, or if you appear on a prohibited-party list.

4. Plans, billing, renewal and cancellation

4.1 Plans

Plans are individual. There is no team plan, no per-seat plan and no enterprise tier. At publication the plans are Free (US$0), Plus (US$8 per month), Pro (US$20 per month) and Max (US$100 per month). Not every plan appears on the public pricing page.

Each plan carries an included weekly allowance (Section 4.2). The price and allowance that apply to you are the ones shown in your billing settings when you subscribe, and on the pricing page — those, not this Section, are the authoritative statement of both.

4.2 Usage beyond your plan, and credits

Your plan includes a weekly allowance. Beyond it, work is charged against prepaid credits you buy in advance at face value — pay US$20, get US$20 of credit — in amounts between US$5 and US$1,000 per purchase.

• The allowance and the spending cap are weekly. Both reset at 00:00 UTC every Monday. Unused allowance does not carry over to the next week. The week is separate from your billing period: your plan is charged for each billing period under Section 4.3, and a new billing period does not reset the allowance or the cap.
• Extra usage is controlled by two settings in your billing preferences: a switch that turns extra usage on or off, and a weekly spending cap on extra usage. You set both.
• Where a charge cannot be taken for work that was already served — no credit, cap reached, or extra usage switched off — we record it and do not bill you for it.
• A generation request is checked before it runs; served work is metered after. Where the week's included usage is spent and extra usage is switched off, where the week's spending cap has been reached, or where there is no credit to charge, the request is refused before the model runs rather than served and recorded as unbilled. The refusal names which of the three it was and what to change.
• The check never blocks you because of our outage. It asks our usage service, and where that service cannot answer in time the request is SERVED rather than refused. The same is true where your plan cannot be read.
• A cap is still not an exact ceiling. Usage for work that is served is metered after the response, and requests already in flight are not recalled, so a small amount of work can be served past a cap.
• Credits do not expire while your account is open. They are not transferable, have no cash value, and are not exchangeable for money except as Section 4.6 provides.

4.3 Renewal

Paid plans renew automatically at the end of each billing period, at the then-current price, until you cancel. Your saved payment method is charged on each renewal.

4.4 Changing plans

You can change plan at any time. A change takes effect immediately and is prorated — you are credited for the unused part of the old plan and charged for the remainder of the period on the new one.

4.5 Cancelling

You can cancel at any time from your billing settings. Cancellation takes effect at the end of the period you have already paid for. You keep access until then, and you are not charged again. You can undo a pending cancellation before the period ends.

4.6 Refunds

Subscription fees and credit purchases are not refundable, and we do not refund partial periods. Three exceptions:

1. Statutory withdrawal. If you are a consumer in the EEA, the United Kingdom or Switzerland, you may withdraw from a new subscription within 14 days of starting it. Email support@telor.dev. We refund what you paid, less a proportionate amount for the period during which the service was available to you, and we refund any unused credit balance in full.
2. We end it. If we close or suspend your account for our own convenience — meaning not for a breach of this agreement or the Acceptable Use Policy, and not because the law requires it — we refund the unused part of the current subscription period and any unused credit balance.
3. Where the law requires a refund regardless of the above.

Refunds are returned through the payment processor to the payment method you used.

4.7 Failed payments

If a charge fails we email you, and we send reminders on days 1, 3, 7 and 14 after the first failure. Our payment processor retries the charge on its own schedule, and you keep your paid features while it does. If that schedule ends without the payment succeeding, the processor cancels your subscription, your account moves to the Free plan, and the paid features stop at that point. That can happen before or after the day-14 reminder: the reminders tell you what is outstanding, and none of them ends your plan. Your data is not deleted by a failed payment.

4.8 Prices and taxes

We may change prices. A change to a recurring price applies from your next renewal and we tell you before it does; if you do not want the new price, cancel before the renewal. Prices are exclusive of taxes. We do not currently add any tax to a charge. You are responsible for any sales, use, VAT, GST or similar tax that applies to what you buy, other than tax on our income.

4.9 Card data

We never see or store your card number. Card details go directly to our payment processor, Stripe, Inc., which holds them. We hold a processor customer reference, your plan and billing status, a reference to your current open invoice, and your credit and usage ledger. The invoices themselves live with the processor, under its retention rather than ours — Section 16.3.

5. Your content, our content

5.1 Definitions

Input is everything you send us: prompts, files, code, images, documents, tool results, memories, library content, plugin and agent definitions, and anything an application you build sends on behalf of its users. Output is what a model generates in response.

5.2 You own your Input

We claim no ownership of Input. As between you and us, it is yours. You are responsible for it: you confirm you have the rights to send it to us and to have it processed as described in Section 2.3.

5.3 You own the Output

As between you and us, you own the Output generated for you, and we assign to you whatever rights we may have in it. Three things you should understand about that:

• Output is produced by a statistical model. Similar prompts from other people can produce similar or identical Output, and we may generate the same or similar Output for someone else. Your ownership does not stop that.
• We make no representation that Output is original, non-infringing, or free of third-party rights. Section 12 disclaims it and Section 13 caps what you can recover.
• Output is generated by a third-party provider's model. Your use of Output is also subject to that provider's terms, which the Acceptable Use Policy carries through.

5.4 The licence we need to run the service

You grant us a worldwide, non-exclusive, royalty-free licence to host, store, copy, transmit, display, index, embed and otherwise process Input and Output for the purpose of operating, securing, supporting and troubleshooting simse for you, and to transmit Input to the model provider so the service can answer you. That licence lasts as long as we hold the content and ends when the content is deleted. It is limited to that purpose. It is not a licence to publish your content, to sell it, or to use it for anything else.

5.5 Training

We do not train models on your content unless you turn that on. The Training data setting under Account → Privacy is off unless you switch it on. Switching it off again takes one click and stops any future use. Content used with your consent is used to improve the models behind this product and for nothing else; any new purpose needs fresh consent.

Separately, and whether or not that setting is on, we keep a record of each request and response in our own systems to debug failures, measure quality, meter usage and bill you. Detected secrets and detected personal-data patterns are replaced with [REDACTED] before that record is written. That redaction is pattern-matching, not judgement, and it will not catch everything.

5.6 Feedback

If you send us suggestions about simse, we may use them without restriction and without owing you anything. We will not identify you as the source without asking.

5.7 What is ours

simse, the software, the models we train, the documentation, the brand and the design system are ours or our licensors'. We grant you a limited, revocable, non-exclusive, non-transferable licence to use simse under this agreement. Nothing here transfers ownership of it. Do not remove our notices, and do not use our name or marks except to say truthfully that you use simse.

5.8 Open-source and third-party components

simse includes open-source components. Where an open-source licence governs a component, that licence applies to that component and, to the extent it conflicts with this Section 5, it wins. Our client libraries and CLI are distributed under the licence stated in their repositories.

6. Acceptable use

Your use of simse is governed by the Acceptable Use Policy, which is part of this agreement. If you build an application on simse, you are responsible for your users' compliance with it as if it were your own.

7. What you must not skip about the AI

7.1 You are interacting with an AI system. Every answer simse gives you is written by a model, not a person.

7.2 The output is often wrong. Models state false things confidently, invent citations, APIs and file paths, and write code that compiles and does the wrong thing. Read generated code before you merge it, test it before you ship it, and verify facts before you repeat them.

7.3 You decide what to accept. Nothing simse produces is professional advice — not legal, not medical, not financial, not tax. Do not use simse as the sole basis for a decision that carries legal or similarly significant effect for a person.

7.4 Agents act. Where you let an agent run tools, it will do what it decides to do inside the scope you gave it. Give it the narrowest scope that works, and read Section 2.4 for where the approval prompt sits on each surface, how you can relax it, and the one path on your machine that runs without it.

7.5 We make no automated decision about you that produces a legal or similarly significant effect. Plan limits, rate limits and fraud controls are operational rules applied to a service, not profiling of you.

8. Third-party services

8.1 simse connects to third parties on your instruction — connectors you install, plugins you add, repositories you point it at, and the web tools an agent uses. When it does, your data goes to those parties on your instruction and under their terms, not ours. We do not control them, we do not endorse them, and we are not responsible for them.

8.2 The agent's web tools transmit query text to a search provider and, where it fetches a page, the target URL and the request to whoever operates that URL. Those recipients are chosen at the moment of the request and we have no contract with them.

8.3 Our own service providers — for payments, email delivery, hosting and model inference — are listed, with the safeguards that apply to each, in the Privacy Policy and its sub-processor disclosure.

9. Privacy

What we collect, why, who receives it, and how long we keep it is in the Privacy Policy. Where you use simse to process personal data of your own end users, you are the controller and we are the processor, and the Data Processing Agreement applies to that processing. It takes effect when you accept these terms; no signature is needed.

10. Security

10.1 We take the technical and organisational measures described in the Privacy Policy. In summary: traffic between you and us is TLS, terminated at our edge provider and carried into our cluster over an authenticated tunnel. The live databases, the analytics warehouse and the object store sit on an encrypted volume whose key is sealed to the machine's security chip, our in-cluster copy of the backups sits on a second one on its own disk, and our secret store adds a second layer of encryption over service credentials. Our off-site backup copies are encrypted at rest by the provider that holds them. Internal calls between our own services are authenticated rather than encrypted — each service presents a short-lived cryptographic identity that the receiving service verifies, and network policy restricts which services can reach which. Agent tool execution runs in a sandbox with default-deny network egress. We do not claim more than that, and Section 12 is not qualified by this Section.

10.2 Report a vulnerability to security@telor.dev. We acknowledge within 2 business days and triage within 5. Section 4 of the Acceptable Use Policy sets out, in full, what you may test, the rules you must follow, and the authorisation we give research that follows them. Do not test against anyone's account but your own.

10.3 You must keep your own credentials, API keys and connector secrets secure, and tell us promptly at security@telor.dev if you believe your account has been compromised.

11. Availability and changes to the service

11.1 We commit to no uptime figure. There is no service-level agreement, on any plan. simse is provided as it is available. We do maintenance, we ship changes, and things break.

11.2 We may change, add or remove features, including features you use. Where a change removes something material and you are on a paid plan, we tell you before it takes effect where we reasonably can. Your remedy for a change you do not want is to cancel under Section 4.5.

11.3 We may set and change rate limits, concurrency limits and quotas to keep the service available for everyone.

11.4 We may discontinue simse entirely. If we do, we give you at least 30 days' notice to your account email, we stop charging you, we refund the unused part of your current subscription period and your unused credit balance, and we keep the in-product export in Section 16.1 working through the notice period. Because that export covers your account record only, we will also run the full cross-service export described in Section 16.1 for anyone who asks at privacy@telor.dev during the notice period, at no charge.

12. Warranties and disclaimers

12.1 simse is provided "as is" and "as available". To the fullest extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, title, non-infringement, and any warranty arising from a course of dealing or trade usage.

12.2 We do not warrant that simse will be uninterrupted, timely, secure or error-free; that any defect will be corrected; that Output will be accurate, complete, current, original, non-infringing or fit for any purpose; or that Output produced for you will not also be produced for someone else.

12.3 Nothing in this agreement excludes or limits liability that cannot lawfully be excluded or limited — including liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, and, where you are a consumer, your statutory rights.

13. Limitation of liability

13.1 To the fullest extent the law allows, neither party is liable for indirect, incidental, special, consequential, punitive or exemplary damages, or for lost profits, lost revenue, lost business, lost goodwill, or loss or corruption of data — even if that party was told the loss was possible.

13.2 To the fullest extent the law allows, our total liability arising out of or relating to this agreement is capped at the greater of (a) the amounts you paid us in the 12 months before the event giving rise to the claim, and (b) US$100.

13.3 The cap in 13.2 does not apply to your obligation to pay amounts due, or to your obligations under Section 14.

13.4 The exclusions and cap in this Section apply regardless of the theory of liability — contract, tort, statute or otherwise — and survive termination.

13.5 These limits are part of the bargain. The Free plan and the prices in Section 4.1 reflect them.

14. Indemnity

14.1 You will defend, indemnify and hold us harmless against any third-party claim, and any loss, liability, damage, fine, cost and reasonable legal fee arising from it, that relates to:

• your Input, or your use of Output;
• your use of simse in breach of this agreement or the Acceptable Use Policy;
• an application you build on simse, and the acts of its users;
• your infringement of anyone's intellectual property, privacy or other rights; or
• your breach of any law, including sanctions and export controls.

14.2 We will tell you about the claim promptly, let you control the defence, and cooperate at your expense. You may not settle in a way that admits fault on our behalf or imposes an obligation on us without our written consent.

14.3 We do not indemnify you. There is no intellectual-property indemnity for Output or for the service, on any plan.

15. Term, suspension and termination

15.1 This agreement runs from when it takes effect under Section 1.1 until your account is closed. Closing your account cancels any paid subscription immediately (Section 16.4).

15.2 You may stop at any time. Cancel your subscription under Section 4.5, or delete your account under Section 16, which cancels the subscription as well.

15.3 We may suspend your access — in whole or in part, with or without prior notice where the circumstances require it — if we reasonably believe that:

• you are breaching this agreement or the Acceptable Use Policy;
• your account is compromised, or is being used to attack, degrade or gain unauthorised access to anything;
• payment has failed and our payment processor's retries under Section 4.7 have ended without it succeeding; or
• the law, a court, or a regulator requires it.

We aim to make a suspension no broader and no longer than the problem requires, and to tell you what it was for.

15.4 We may terminate this agreement and close your account on 30 days' notice for convenience, or immediately for a serious or repeated breach of this agreement or the Acceptable Use Policy, for use that exposes us or another user to legal or security risk, or where the law requires it.

15.5 On termination your licence to use simse under Section 5.7 ends immediately. Sections 5.2, 5.3, 5.4 (until the content is deleted), 5.5, 5.6, the ownership statement in 5.7, 5.8, 12, 13, 14, 16, 18, 19 and 20 survive.

16. What happens to your data when this ends

16.1 Export first — and know what the button gives you. Account → Privacy → Download my data downloads a JSON file containing your account record: your profile, your sign-in identities, your platform account, your workspaces and memberships, API-key metadata (never a key itself), your preferences, your consent history, your sessions, devices and device tokens, your sign-in and token records, and your account audit trail. Credentials and secret values are never in it. It is rate-limited to three exports per day.

That file does not contain your conversations, your generated content, your memories, your uploaded or generated files, your knowledge library, your projects and tasks, your plugin grants, or your billing records. Those live in other services and none of them is in the download. To get them, email privacy@telor.dev and ask for a full export; we run it across the services that hold your data and send you the result.

Do that before you delete anything. Deletion is not reversible, we cannot restore an account, and the in-product export is not a backup of your work.

16.2 Deleting your account. Deleting your account runs our erasure workflow across every live store that holds data keyed to your account — account and preferences, chat and session history, adaptive memory, files and artifacts, the knowledge library, projects and tasks, plugins and grants, notification records, usage counters and analytics. In our analytics warehouse that same operation erases the product-analytics and audit-event records, the records of your AI exchanges that carry your account identifier or a reference to one of your conversations, and the records of the calls your installed plugins made on your behalf. It runs when you confirm it. There is no waiting period and no undo. Section 16.3 lists what it does not reach.

16.3 What survives deletion, and for how long.

The per-store detail is in Section 8 of the Privacy Policy.

16.4 Deleting your account cancels a paid plan immediately. The deletion cancels your subscription with our payment processor before our record of it is erased. If the processor cannot be reached, the cancellation is retried and your deletion is not completed until it succeeds; if a renewal is charged in that time, tell us at support@telor.dev and we will refund it in full. Deleting your account does not refund any part of the period you have already paid for: to use that period, cancel under Section 4.5 and delete your account when it ends. Before 28 September 2026 a deletion did not cancel the subscription. If a renewal was charged to you after you deleted your account before that date, tell us at support@telor.dev and we will refund that charge in full.

16.5 Where you were a processor-tier customer, deletion of your own end users' data is governed by the Data Processing Agreement.

17. Changes to these terms

17.1 We may change these terms. The current version is always at simse.dev/legal/terms.

17.2 For a change that is material and adverse to you, we give at least 30 days' notice by email to your account address, or in-product, before it takes effect. Other changes take effect when we publish them.

17.3 If you do not accept a change, cancel and stop using simse before it takes effect. Continuing to use simse after that is acceptance.

17.4 We will not apply a change retroactively to a dispute that has already arisen.

18. Governing law and disputes

18.1 Governing law. This agreement, and any dispute arising out of or relating to it or to simse, is governed by the law of the State of Delaware, United States, without regard to its conflict-of-law rules. The UN Convention on Contracts for the International Sale of Goods does not apply.

18.2 Talk to us first. Before filing anything, send a written description of the dispute and the relief you want to legal@telor.dev. We will do the same. Both parties will try in good faith to resolve it for 30 days from that notice. This step is a condition of filing, except for a claim seeking an injunction or brought in a small-claims court.

18.3 Courts. The state and federal courts located in New Castle County, Delaware have exclusive jurisdiction, and both parties consent to venue there.

18.4 Jury and class waivers. To the fullest extent the law allows, both parties waive trial by jury, and both agree to bring claims only in an individual capacity — not as a plaintiff or class member in any class, collective, consolidated or representative proceeding. If this paragraph is held unenforceable for a claim, it does not apply to that claim, and the rest of this Section stands.

18.5 Consumers. If you are a consumer, nothing in 18.1, 18.3 or 18.4 deprives you of the protection of the mandatory law of the country where you live, or of your right to bring proceedings in the courts of that country. Consumers in the EU may also take a dispute to a national alternative-dispute-resolution body, or to the European Consumer Centre in their country. The European Commission's online dispute resolution platform is not a route to us: Regulation (EU) 2024/3228 repealed the regulation behind it and the platform stopped operating on 20 July 2025.

18.6 Time limit. Any claim must be brought within one year after it arises, or it is barred, unless the law where you live forbids that limit.

19. Notices

19.1 To you. We give notice by email to the address on your account, or in-product. Notice by email is effective when sent. Keep the address current — a notice sent to a stale address still counts.

19.2 To us. Send legal notices to legal@telor.dev, and to the registered address at A-2. Notice is effective when we receive it.

19.3 The other addresses.

19.4 We may send you service messages — security notices, billing notices, changes to these terms — and you cannot opt out of those while you have an account. Marketing email is separate and you can turn it off.

20. General

20.1 Assignment. You may not assign this agreement without our written consent. We may assign it to an affiliate or in connection with a merger, acquisition or sale of assets.

20.2 No partnership. Nothing here creates a partnership, joint venture, employment or agency relationship.

20.3 No third-party beneficiaries. Nobody other than you and us has a right to enforce this agreement.

20.4 Entire agreement. This agreement is the whole agreement between us about simse, and it replaces anything said or written before it.

20.5 Severability. If a provision is unenforceable, it is modified to the least extent needed to make it enforceable, or struck if it cannot be, and the rest stands.

20.6 No waiver. Not enforcing a provision once does not waive it.

20.7 Force majeure. Neither party is liable for a failure caused by something outside its reasonable control — including a failure of a provider on which the service depends. This does not excuse an obligation to pay.

20.8 Export and sanctions. You will comply with applicable export-control and sanctions law, and you will not make simse available to anyone that law prohibits.

20.9 US Government users. simse is "commercial computer software" and "commercial computer software documentation". Government use, reproduction and disclosure are governed solely by this agreement.

20.10 Language. These terms are written in English. A translation is provided for convenience; the English text governs.

simse is a product of Telor. Questions about this document: legal@telor.dev.