Terms of Service & Acceptable Use

Version 2.2 · effective 2026-07-27 · in force

These Terms of Service & Acceptable Use (the "Terms") are the agreement between you and RunMyB, Inc. governing your use of the RunMyB platform. By creating an account, accepting these Terms in the console, or using the platform, you agree to them. The following documents are incorporated into these Terms by reference and are available in the platform's legal documents section: the "Privacy Policy", the "Data Processing Addendum", the "Platform Rules — Content-Safety Taxonomy", the "Refunds, Cancellation & Complaints" policy, the "Notice-and-Action & Contact Points (DSA)" policy, the "Copyright / DMCA Policy", and the "Cookie & Tracker Notice".

1. Who you are contracting with

The RunMyB platform is operated by RunMyB, Inc., a Delaware corporation ("RunMyB", "we", "us"). RunMyB, Inc. is the contracting party under these Terms and, for the platform's own account, billing, and ledger data, the data controller (see the Privacy Policy).

We may assign these Terms, in whole or in part, in connection with a merger, acquisition, corporate reorganisation, or transfer of all or substantially all of the business or assets to which they relate; the successor assumes our rights and obligations, and a change of contracting party will be notified to you. You may not assign or transfer your rights or obligations under these Terms without our prior written consent.

2. Definitions

• Account (or tenant) — the workspace opened for a customer on the platform; the account holder is the customer and the single contracting party under these Terms.
• Administrator and member — the two membership roles within an account (Section 9).
• Venture — a project workspace within an account, in which assistants and people work toward a business or product.
• Product — an application or other work product built or operated through the platform within a venture.
• Credits — the prepaid units in which paid platform usage is denominated (Section 14).
• Your Content — everything you (or your members) submit to or create through the platform: descriptions, instructions, conversations, files and attachments, imported code and data, ventures, products, and the output attributed to you under Section 11.
• The service (or the platform) — the RunMyB console, assistants, build and verification machinery, storage, and the related surfaces we operate.

3. Eligibility

You must be at least 18 years old (or the age of majority in your jurisdiction, if higher) to use the platform. If you accept these Terms on behalf of a company or another legal entity, you represent that you have the authority to bind that entity, and "you" then means the entity. The platform is not directed at children and may not be used by them.

4. Your account and its security

You agree to provide accurate account information and to keep it current. Each identity on the platform is personal: it belongs to one person and may not be shared. You are responsible for safeguarding the credentials used to access your account and for the activity that occurs under it. If you become aware of unauthorised access to or use of your account, notify us promptly at hello@runmyb.com; after notice we will take reasonable steps to secure the account, and our liability remains as stated in Section 19.

5. The service; early access

RunMyB lets you describe software and have AI assistants build and verify it, and — where the platform offers hosting for your product — run it. You are responsible for what you build, for the lawfulness of your apps and their content, and for any classification or compliance obligations (including under the EU AI Act) that attach to what you create.

Early access. The platform is under active development. Features may change, be added, or be withdrawn; interfaces, limits, and behaviours evolve. We do not promise uninterrupted or error-free availability, we offer no service-level agreement and no uptime warranty, and maintenance may interrupt the service. Anything labelled beta, preview, or experimental is provided for evaluation and may be modified or discontinued at any time. Keep your own copies of anything you cannot afford to lose; export paths (including the git export in Section 12) exist for that purpose. Nothing in this section limits the non-waivable rights consumers have under applicable law (Section 23).

6. Acceptable Use Policy (AUP)

You may not use RunMyB to build, host, or operate anything that:

• is illegal, infringing, or facilitates illegality;
• targets, harasses, exploits, or endangers minors, or produces CSAM;
• deploys malware, phishing, spam, or credential-harvesting;
• infringes intellectual property or misappropriates trade secrets;
• attacks, overloads, or attempts to circumvent the platform's controls, quotas, or isolation;
• violates the privacy of, or unlawfully processes the personal data of, third parties;
• generates disallowed content of the categories the platform rules enumerate.

Platform rules taxonomy. A detailed, categorised list of prohibited and restricted content and conduct is maintained as the "Platform Rules — Content-Safety Taxonomy", which is the operative catalog for this AUP.

7. Enforcement

Violations of these Terms or the AUP may be met with graduated actions — a refusal to run, removal or unpublishing of content or an app, suspension of an account, or termination — chosen proportionately to the violation, its severity, and any recurrence. An enforcement action against your product or your account is accompanied by a statement of reasons — for publicly-hosted content, one consistent with DSA Article 17 — and you may appeal the decision. To appeal, send the decision reference (or a description of the decision) and why you disagree to support@runmyb.com or through the contact points described in the "Notice-and-Action & Contact Points (DSA)" policy. An appeal is reviewed afresh by a human — it is never adjudicated by the automated check that produced the original decision — and we aim to respond within 14 days. Nothing here waives our right to act immediately where the law requires it or where there is an imminent risk of serious harm.

8. Content moderation transparency (DSA Article 14)

Where RunMyB hosts third-party apps publicly, it acts as a hosting intermediary. Our moderation policy is stated in plain language: we act on valid notices (see the "Notice-and-Action & Contact Points (DSA)" policy), we may act on our own initiative against AUP violations, we give statements of reasons for restrictions we impose on publicly-hosted content, and we operate a repeat-infringer policy (see the "Copyright / DMCA Policy").

9. Teams

9.1 Members act under the customer's account

An account may be used by more than one person. The account holder — the customer — remains the single contracting party under these Terms. People the customer admits to its account (members, typically the customer's employees or contractors) act under the customer's account and on the customer's authority: their platform usage, the work products they create, and the charges their usage incurs are the customer's, and the customer is responsible for its members' compliance with these Terms and the AUP as if the acts were its own.

9.2 Membership is managed by the customer's administrators

Each account has one or more administrators (the first user of an account is its administrator). Administrators manage membership: they invite new members (an invitation is a single-use token addressed to a named e-mail address, valid for the validity period stated in the invitation; on the administrator's instruction the platform itself e-mails the invitee an acceptance link, and the inviting administrator — who is also shown the link — may convey it directly as well), assign each member a role (administrator or member), and may disable a member's access at any time. Invitation acceptance requires proof of possession of the token; nobody becomes a member of an account without an administrator's invitation and the invitee's own acceptance.

The last-administrator guarantee: an account can never be left without an administrator — an attempt to disable or demote the only remaining administrator is refused. Account-level obligations (billing, legal acts, deletion) therefore always have an accountable holder.

9.3 Acceptance is personal

These Terms and the Privacy Policy are accepted per person, not per account. Every member — administrator or not — must accept the then-current required documents before first use, and a material change requires each member's renewed acceptance before that member continues (Section 24). By accepting, a member agrees to these Terms in respect of their own use of the platform; the customer remains the contracting party for the account itself — its billing, its ventures and products, and account-level acts. The customer's acceptance does not substitute for a member's own; a member's acceptance does not bind the customer beyond that member's authorised acts (Section 9.1).

9.4 Administrator-only acts (money and legal)

The following acts are reserved to the customer's administrators; a member-role user's attempt is refused:

• billing and payments — purchasing credits, starting or cancelling a subscription, the billing portal, filing complaints, and access to billing documents;
• legal acts for the account — the withdrawal waiver, tenant-wide data-subject requests (account-wide export), and filing or cancelling account deletion (offboarding);
• credentials and connectors — storing or deleting account credentials (API keys), connector and AI settings, and enabling live (real-money or externally-visible) connector operation;
• admin-class approvals — decisions on money-class gates (spend/budget authority) and on live-enablement gates.

Ordinary venture work — describing, building, evolving, and reviewing apps — is open to every active member. Reading these Terms and accepting the required documents is never gated by role.

9.5 Attribution of member acts

Acts performed under an account are attributed to the person who performed them: approvals and decisions record the deciding member, and messages in shared venture conversations record their author. These attributions are part of the customer's account records (Section 9.6) and of the platform's audit trail.

9.6 Work products and shared records belong to the customer

Everything produced under the customer's account in the course of venture work — apps, documents, artifacts, and the conversation records of shared venture lanes, including each member's authored turns in them — are the customer's records (as between the customer and its members, subject to any arrangement between them, which is not the platform's concern). A member's personal data rights in those records are addressed in the Privacy Policy; a member's own-data export covers the member's personal data and the conversations the member owns, not the customer's shared records.

9.7 Member disable is not account termination

Disabling a member ends that person's access to the account: their sessions stop resolving, their approver authority is deactivated, and they can no longer act under the account. It does not delete the account, its ventures, or the member's past contributions (which remain the customer's records, Section 9.6). Account termination — ending the customer's account itself — is the separate, administrator-only offboarding act, with the grace window stated when the deletion request is filed and the tiered erasure described in the Privacy Policy. A disabled member remains a data subject; the Privacy Policy states what personal data of a departed member is retained, why, and for how long.

10. Your content; the licence you grant us

You own Your Content. These Terms transfer no ownership of it to us.

The operating licence. So that we can lawfully run the service on your behalf, you grant RunMyB a worldwide, non-exclusive, royalty-free licence to host, store, reproduce, transmit, back up, execute, process, display (to you and to those you authorise), and create technical copies and derivatives of Your Content, solely as needed to operate, secure, maintain, and improve the service and to run your app where you ask us to host it. Improving the service does not include training AI models on Your Content: we do not train models on it, and would not without your express opt-in. The licence ends, for a given item of Your Content, when you delete it or your account is offboarded, subject to residual copies in backups, to retention the law requires (see the Privacy Policy), and to the operational records the platform retains under Section 12.

10.1 We will not build against you

To have a product built here you must describe how your business actually works — your method, your pricing logic, your process, the judgement that makes your service worth paying for. That description is Your Content, and you own it under this Section. Ownership alone, however, does not answer the question a person is really asking when they hesitate to type it in. This subsection answers it.

The commitment. RunMyB will not use Your Content — including a method, process, ruleset, or business logic you describe to us — to develop, commission, or operate a product or service that competes with yours, and will not disclose it to a third party for that purpose. This is a restriction on us. It places no restriction on you.

What this commitment cannot say, stated so you are not misled. It does not make your idea exclusive, and it is not a promise of uniqueness. Section 11.5 stands: purely AI-generated output may not be protectable, and the same or similar output may be produced for another customer who independently describes something similar. We commit not to take what you told us and act on it; we cannot commit that nobody else will ever arrive at the same idea on their own. A platform that promises you the second thing is describing something it has no way to enforce.

10.2 Your customer relationships are yours

Where you bring your own clients, members, or buyers to a product built here — including where you introduce them while acting for them as an agency, consultant, or reseller — that relationship is yours, and the following applies in addition to Section 15.

1. We will not market to them. RunMyB will not use the contact details of your end users, or of people you introduce to the platform, to market RunMyB or any other product or service to them. Mail reaching those addresses is limited to the first-party account and transactional mail described in Section 15 and on the platform's published email page.
2. We will not solicit them away from you. We will not approach a client you introduce with an offer that bypasses you.
3. What this does not restrict. A person who finds RunMyB independently and approaches us on their own is free to do so, and this subsection does not make you their gatekeeper. It restrains what we do with an introduction you made; it does not restrain them.

10.3 Confidentiality

RunMyB treats your non-public content — your briefs and descriptions, your methods and business logic, your code, and your data — as confidential. We do not disclose it to third parties, with two exceptions only: the sub-processors needed to operate the service (the named list and its safeguards are in the Privacy Policy and the Data Processing Addendum), and disclosure required by law or legal process. This is a restriction on us, it adds nothing to what we may do with Your Content under Section 10, and it survives termination of these Terms for as long as we hold the content (including the operational records retained under Sections 10 and 12).

11. AI-assisted output (the output clause)

The following is the split for AI-assisted output, stated plainly:

1. As between you and us, you own the output your ventures produce through the platform.
2. We assign to you any rights we may have in that output, to the extent we have any.
3. The output is Your Content — the narrow operating licence in Section 10 applies to it, including running your app where you ask us to host it.
4. You must review anything you build before you rely on or ship it: AI output can be wrong, incomplete, or insecure, and you are responsible for testing and validating it before use.
5. No uniqueness and no warranty of copyrightability. Purely AI-generated output may not be protectable by copyright, the same or similar output may be produced for others, and we make no warranty that any output is original, non-infringing, or copyrightable.

12. Git-provider integration

12.1 Export and takeover — your code on your provider

You may connect your own git hosting provider (GitHub, GitLab, Bitbucket, or a self-hosted service) and export a product's code repository to it, under your provider account. The code is already yours under Sections 10–11; export changes where it lives, not who owns it. On export the platform pushes a fresh single-commit history containing the product's current committed code — the platform's internal build history does not travel. The platform retains its local copy of the repository and its full local history as an operational record (it is what the platform builds from, verifies against, and serves previews from); that copy remains covered by the operating licence in Section 10.

12.2 The continued-operation grant

While a provider connection and a product's repository binding both stand, you grant the platform the right to read from (fetch) and write to (commit and push to) the bound repository, within that connection's scope, so the platform can keep building, fixing, and evolving the product you asked it to operate. The grant's shape is deliberately narrow, and the platform's code enforces it structurally:

1. Default: proposal branches. In the default ("pr") mode the platform pushes only to its own "runmyb/…" branches in your repository and proposes changes for you to merge; it does not write to your default branch. A direct-push mode is your explicit opt-in.
2. Never force. The platform never force-pushes to any branch of yours; forced updates are only ever applied to the platform's own "runmyb/…" namespace, and only with a lease check.
3. Never discards. When the platform adopts your newer remote work, the prior local state is preserved first (under a platform-owned reference namespace); adoption never deletes your commits.
4. Revocable at any time, by disconnecting. Deleting the provider connection (or the product's binding) revokes the grant: the stored token is deleted and all remote operations stop — every bound product flips to a named "connection revoked" state rather than failing silently. The platform's local copies remain, under the Section 10 licence, as the operational record of the service you used. Stated plainly so revocation is not misunderstood: after disconnecting, the platform can no longer fetch from or push to the repositories that rode that connection, and their bindings stay in the revoked state until you act. A disconnected connection is not revived; the supported recovery is to connect the provider again (a new connection) and re-point each affected product's existing binding at it — a supported action that changes which credential authenticates, never where anything is pushed. (An expired or rotated token on a live connection is replaced in place on the Connections surface, without disconnecting.)

12.3 Import — your warranty for code you bring

When you import an existing repository, you affirm that you hold the rights needed to bring that code onto the platform and to grant the Section 10 operating licence over it, and that you take responsibility for it — including compliance with any third-party licences the imported code carries, which remain your responsibility. The platform records this affirmation at the moment of import (an append-only attestation record keeping the exact wording you saw), together with the import's provenance (where the code came from, at which commit). Imported code is Your Content under these Terms, including the AUP and the content-safety rules.

12.4 Secret scanning — a safeguard, not a warranty

Before pushing your code to a provider, the platform runs an automated secret scan over the exact content to be pushed and refuses the push when it finds likely credentials (naming the findings with masked values, so you can remove or rotate them — the platform never edits your code silently). On import, findings are reported to you but do not block the import (the content is already in your own repository; the report is so you can rotate). This scanning is a safeguard operated on a best-effort basis: the platform does not warrant that it will detect every secret, and keeping credentials out of your repositories remains your responsibility.

13. AI disclosure (AI Act Article 50)

The assistants you interact with are AI systems. Their output may be inaccurate, you must review it, and you own it subject to Section 11. This is stated again in-product where you converse with an assistant. The AI providers behind the assistants are named in the Privacy Policy's sub-processor list (Section 5.1): Anthropic PBC runs the AI assistants and build agents that process workspace content, and OpenRouter, Inc. provides auxiliary AI model routing for platform-side engine tasks where a platform role is configured to route through it.

14. Fees, credits & payments

1. Credits. Paid platform usage is denominated in prepaid credits. Credits are a means of using the service — they are not money and are not transferable, and, except for the statutory refunds described in the "Refunds, Cancellation & Complaints" policy or where the law requires, they are not redeemable for cash. Credits you purchase do not expire. Promotional or granted credits (including subscription allowances) may carry an expiry; each credit lot's expiry — or the fact that it never expires — is shown per lot in your Billing view. Credits are consumed by the work you ask the platform to perform: usage is metered as the work happens, including where the output of a given piece of work turns out imperfect — AI-assisted work does not carry an outcome warranty (Sections 11 and 18) — and if you believe a charge was wrong, the complaints route in the "Refunds, Cancellation & Complaints" policy is the named remedy. The bundles and prices in force are shown at the point of purchase, and every charge — with the rate and any margin applied — is itemised in your Billing view; changes to rates, bundles, and account-specific settings are effective-dated, prospective, and never silent or retroactive. Refunds, cancellation, your statutory withdrawal rights, and the withdrawal waiver for credits put to use are governed by the "Refunds, Cancellation & Complaints" policy.
2. The usage margin. Usage pricing includes a platform margin over raw model and infrastructure cost. The margin applied to your usage is effective-dated and itemised with each charge in your Billing view whenever it differs from the baseline; changes never apply retroactively.
3. Payment-processor choice. Where your apps take payments from your own end-users through your own payment processor, the platform takes no share of your revenue — and your account's usage margin may be set correspondingly higher. Any such setting is effective-dated, applies only prospectively, and is itemised on the charges it prices in your Billing view — never silent or retroactive. The margin in force for your account is therefore always readable from your Billing view: every charge is itemised with the margin that priced it whenever it differs from the baseline, and the absence of a margin line means the baseline applied. Changes follow point 2 — effective-dated, prospective, never retroactive.
4. Integrated payments (where offered). Where the platform offers integrated payments, you are the merchant of record for your end-user transactions, the payment provider performs onboarding and identity verification, you bear your own end-user refunds and disputes, and the platform's remuneration is a disclosed application fee shown in-product together with your earnings. When a sale is refunded, disputed, or charged back, the application fee on that sale is not returned: the fee compensates platform processing that was already completed when the sale was made.
5. Billing documents. Invoices and receipts for subscriptions and credit purchases are produced through the payment processor and surfaced in your Billing view.
6. Taxes. Stated prices are exclusive of applicable taxes unless expressly stated otherwise.

15. Hosted apps and your end users

Where the platform hosts or serves your app — in previews, or publicly where the platform offers public hosting:

1. Your app is yours to answer for. You are solely responsible for your app, its content, its lawfulness, its end users, and the notices your app owes its own users (including your own privacy notice where your app processes personal data). For your end-users' data, you — not RunMyB — are the responsible party; RunMyB is not a party to the relationship between you and your end users. Where RunMyB processes personal data on your behalf, the "Data Processing Addendum" forms part of these Terms and governs that processing.
2. Serving domains stay ours. The platform owns its serving domains and hosting infrastructure. We may reassign or reclaim subdomains, hostnames, and hosting slots on at least 7 days' notice — and immediately where security, legal compliance, or abuse requires it.
3. No app-availability warranty. We do not warrant the availability of your hosted app; Section 5's early-access terms and Section 18's disclaimer apply to hosting.
4. Child-safety reporting. Where apparent child sexual abuse material is discovered in hosted content, RunMyB preserves the material and the associated records and reports to the National Center for Missing & Exploited Children (NCMEC) as US law (18 U.S.C. § 2258A) requires. This is a legal duty, not a discretionary act, and it is not subject to appeal under Section 7.

15A. The public catalogue: listings, ranking, and reviews

The platform is beginning to operate a public catalogue of hosted products. It is new and small; the commitments below bind as it operates and are stated now so they are on the record from the start.

1. Listing is consent-based. Every published product in good standing is eligible for a catalogue listing as that surface opens. Your product is listed only with your recorded consent, which you may withdraw at any time; withdrawal removes the entry.
2. Ranking transparency. The main parameters determining how catalogue entries are ordered and presented are: recency, platform curation ("recommended" picks are editorial choices made by us), visitor ratings, and usage signals. Placement is not influenced by payment. If paid placement is ever introduced, it will be labelled as advertising.
3. Reviews and ratings. Visitor ratings are not verified purchases, and we say so where they appear. We do not suppress a rating for being negative. Removing a catalogue entry and removing a rating are separate acts, and each is recorded. Submitting, commissioning, or incentivising fake ratings or reviews violates the "Platform Rules — Content-Safety Taxonomy".
4. Contesting a decision. You may contest a ranking, a rating, a listing, or a delisting by writing to support@runmyb.com; the complaint is handled under the process described in the "Notice-and-Action & Contact Points (DSA)" policy.

16. Third-party services you connect

The platform lets you connect third-party services under your own accounts — git providers, Google services, Trello, Notion, AI providers under your own keys, and similar. Each such service is governed by its own terms and privacy policy, which you are responsible for accepting and observing. By connecting a service you authorise the data flows you initiate through that connection (described in the Privacy Policy); disconnecting stops them. RunMyB is not responsible for third-party services, their availability, their acts or omissions, or the consequences of your configuration of them.

17. Feedback

If you send us feedback, suggestions, or ideas about the platform, you grant us a perpetual, irrevocable, worldwide, royalty-free, sublicensable licence to use them for any purpose, without obligation, compensation, or attribution. Feedback is not Your Content under Section 10.

18. Disclaimer of warranties

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND ACCURACY. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, SECURE, OR ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT ANY OUTPUT WILL BE CORRECT, COMPLETE, OR FIT FOR YOUR PURPOSE.

Nothing in this section limits the warranties or conformity remedies that applicable law grants you as a consumer and that cannot be excluded or limited by agreement (Section 23).

19. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW: (a) NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUES, DATA, OR GOODWILL, EVEN IF ADVISED OF THE POSSIBILITY; AND (b) RUNMYB'S AGGREGATE LIABILITY ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICE IS CAPPED AT THE GREATER OF (i) ONE HUNDRED US DOLLARS (US$100) AND (ii) THE FEES YOU PAID TO RUNMYB IN THE TWELVE MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM.

Nothing in this section limits your indemnification obligations under Section 20 or your obligation to pay fees due.

What this clause never limits. Nothing in these Terms excludes or limits liability for intentional misconduct or gross negligence, for death or personal injury caused by negligence, or for any other liability that cannot be excluded or limited under applicable law. If you are a consumer, your statutory remedies remain unaffected to the extent they cannot be waived.

20. Indemnification

You will defend, indemnify, and hold harmless RunMyB, Inc. and its officers, directors, employees, and agents from and against third-party claims, and the resulting liabilities, damages, and reasonable costs (including reasonable attorneys' fees), to the extent arising from: (a) Your Content; (b) apps you build or direct the platform to operate, and your own end users; (c) your breach of these Terms; or (d) your violation of law or of a third party's rights. We will give you prompt notice of any such claim — a failure to notify does not relieve your obligations except to the extent you are materially prejudiced by it; you may not settle a claim in a way that imposes obligations on us without our consent, and we may participate in the defense with our own counsel at our expense. If you are a consumer, this section applies only to the extent permitted by the law of your habitual residence and only to claims caused by your breach, Your Content, or your apps.

21. Suspension & termination

1. By you. You may stop using the platform at any time, and you may terminate by filing account deletion (offboarding) from your account surface.
2. By us. We may suspend, restrict, or terminate your access for material breach of these Terms or the AUP, for legal or regulatory risk, for a security threat, or for non-payment. Enforcement is graduated where practicable (Section 7); we may act immediately where the violation, the law, or an imminent risk of serious harm requires it. We may also terminate these Terms for convenience on at least 30 days' notice — your export paths (Sections 5 and 12) remain available through the notice period — and may close accounts for inactivity only after at least 12 months without activity, and only with notice to the account's e-mail address before the closure takes effect.
3. Effect of termination. On termination your access ends. Offboarding runs a grace period whose end date is stated when you file the deletion request; during that period the deletion can still be called off — through your account surface where it remains accessible, or by contacting support@runmyb.com. After it, your data is handled as the Privacy Policy describes (tiered erasure, with the retention the law requires). Whether any amounts are refundable is governed by the "Refunds, Cancellation & Complaints" policy — which states the rule for an unspent balance at account closure — and applicable consumer law.
4. Survival. Sections 10 (for retained records, to the extent stated there), 11, 12.3, and 17 through 25 survive termination.

22. Export control & sanctions

You represent that you are not located in a jurisdiction subject to comprehensive embargo, are not on any applicable sanctions or denied-parties list, and will comply with applicable export control and sanctions laws in your use of the platform.

23. Governing law, disputes & consumer rights

1. Governing law and venue. These Terms are governed by the laws of the State of Delaware, without regard to its conflict-of-law rules. Subject to point 3 below, the state and federal courts located in Delaware have exclusive jurisdiction over disputes arising out of or relating to these Terms or the service, and both parties consent to their jurisdiction.
2. Talk to us first. We ask — without limiting your rights — that you contact us at hello@runmyb.com before filing a claim; most issues can be resolved quickly and informally.
3. If you are an EU/EEA consumer. Nothing in these Terms deprives you of the protection of the mandatory provisions of the law of your country of habitual residence, and the choice of Delaware law does not displace them. You may bring proceedings in the courts of your home Member State, and proceedings against you may be brought only there. Your withdrawal rights are described in the "Refunds, Cancellation & Complaints" policy. Where any clause of these Terms conflicts with a mandatory consumer protection that applies to you, that protection prevails.
4. Individual basis; jury waiver. To the extent permitted by applicable law, disputes will be resolved on an individual basis — neither party will participate in a class, representative, or consolidated action against the other — and both parties waive trial by jury. This point does not apply where such waivers are prohibited by law, including for EU/EEA consumers.

24. Changes to these Terms

The platform is under active development, and these documents evolve with it; by accepting these Terms you also accept this change process. We update the legal documents for stated kinds of reasons: new or changed features, legal or regulatory requirements, security, and changes to pricing mechanics.

• A material change requires your renewed acceptance before you continue using the console.
• A non-material change takes effect on posting; the new version number, its effective date, and the changelog are the notice of the change, and you are invited to review them.
• In plain language, so the split is not ours to stretch: material means a change that reduces your rights or adds an obligation on you — for example, narrowing the licence limits in Section 10, adding a new fee category, or widening what you indemnify us for; such a change fires the re-consent gate. Non-material means a new restriction on RunMyB, a disclosure, a clarification of something already true, or a change in your favour; such a change takes effect on posting.
• A change never retroactively removes value you have already paid for. Operational values — rates, bundles, margins, allowances, and similar settings — live in-product (Section 14) and change through the platform's effective-dated configuration, not through these documents.
• Every version is dated, versioned, and kept in the changelog.

25. General provisions

1. Entire agreement. These Terms, together with the documents they incorporate by reference, are the entire agreement between you and RunMyB about the service and supersede prior understandings on that subject.
2. Severability. If a provision of these Terms is held invalid or unenforceable, it is enforced to the maximum extent permissible and, where necessary, deemed modified to the minimum extent needed to make it valid — and the remaining provisions stay in full force.
3. No waiver. A failure to enforce a provision is not a waiver of it.
4. Force majeure. Neither party is liable for failure or delay caused by events beyond its reasonable control, including natural disasters, war, terrorism, labour disputes, failures of the internet or utilities, and acts of government.
5. Contact. Questions about these Terms: hello@runmyb.com.