Terms of Service.
What you get, and what we do not promise.
These terms govern the RERUN desktop runtime and the licence control plane that issues its entitlements. They are written to be read: short sentences, real limits, and an explicit account of what the Service does not do.
1. Who we are and what this covers
RERUN is supplied by Registered company name — to be completed , Legal form — to be completed , of Registered address — to be completed , tax identification number CIF/NIF — to be completed , registered at Commercial registry entry — to be completed . In these terms, "we" and "RERUN" mean that company, and "you" means the organization that registers an account, activates a device or buys a licence.
The Service has two parts, and the split matters throughout this document.
- The desktop runtime. A local-first application for macOS on Apple silicon. It records browser journeys inside its own embedded browser, replays them with Playwright, and keeps flows, session state and run evidence on the machine that runs the test. There is no RERUN-hosted execution backend.
- The licence control plane. The web service you are reading this on. It owns accounts, organizations, annual subscriptions, device activation, signed device entitlements and release metadata. It has no endpoint for browser URLs, cookies, DOM, screenshots, flows, AI prompts, provider keys or run evidence.
You accept these terms when you create an account, activate a device or buy a licence — whichever happens first. If you are accepting on behalf of an organization, you confirm you are authorised to bind it.
RERUN is sold to organizations for their internal business use, and these terms are written for that relationship; we do not market the Service to consumers. If you nevertheless contract as a consumer — outside any trade, business or profession — the mandatory rules of Spanish and EU consumer law apply to you whatever these terms say, and nothing here waives them. Among them is the fourteen-day right of withdrawal under Real Decreto Legislativo 1/2007, which for digital content and services supplied immediately is lost only once supply has begun with your express prior consent and your acknowledgement that the right is lost. Ask us before you buy if you are unsure which side of that line you are on.
These terms do not govern the third-party services involved in using RERUN. Your payment is processed by Stripe under Stripe's terms. If you enable an AI step, your model provider's terms apply to that request. Section 4 and section 6 explain both.
Enterprise licences are agreed separately by contract. Where a signed Enterprise agreement exists, it prevails over these terms for the customer that signed it.
2. The licence we grant
For as long as your licence is current, we grant you a non-exclusive, non-transferable, non-sublicensable right to install and run the RERUN desktop runtime for your own internal business purposes. The licence is bound to named seats and to registered devices. It is not a sale: we keep all intellectual property in RERUN, and nothing here transfers it.
The limits are the ones the licence service actually enforces:
- Professional — 1 seat, 2 devices per seat. The organization may hold 2 active device activations at a time.
- Team — 5 seats, 2 devices per seat. The organization may hold 10 active device activations at a time.
The device ceiling is enforced as an organization-wide count of active installations — seats multiplied by devices per seat — not as a per-person quota. When that count is reached, the next activation is refused until you deactivate a device from your account page. Deactivating a device frees its slot immediately.
Seats are named, not floating. A Team seat belongs to a person you invite by email; the invitation is signed, expires after seven days and can only be accepted by the invited address. A pending invitation reserves its seat. Removing a member frees the seat and revokes that member's devices and licence leases. Sharing one seat between several people, or sharing account credentials, is not a permitted use of the licence.
Under this licence you may not:
- resell, sublicense, rent, lease or run RERUN as a service for third parties;
- circumvent, disable or tamper with licence checks, device activation, the signed entitlement or its expiry;
- reverse engineer, decompile or disassemble the software, except to the extent that applicable law expressly permits it despite this restriction;
- remove or alter our notices, or use our name or marks without permission.
Everything you produce with RERUN — your flows, your runs, your evidence — is yours. We claim no rights in it, and, as section 9 explains, we do not receive it.
3. Evaluation and purchase
Each organization gets one seven-day evaluation. It does not start when you sign up. It starts when you verify your email address and then activate your first device: the service stamps the trial at that moment and ends it seven days later. Registering an account and never activating a device leaves the evaluation unused rather than silently burning it.
When the evaluation ends, the runtime stops issuing entitlements for recording and replay. Continuing requires an explicit purchase.
Licences are annual. There is no monthly plan, no execution meter and no usage credits. You buy a year of Professional or a year of Team through Stripe Checkout, and the subscription renews annually until you cancel it. You cancel from the billing section of your account, which opens the Stripe billing portal.
Cancelling stops the next renewal. Your licence runs to the end of the period you already paid for. If a renewal payment fails instead, we do not cut you off on the same day: the licence moves into a grace state — currently fourteen days — and stops when that window closes.
A full refund ends the licence. A chargeback or payment dispute revokes it immediately, with no grace window.
Refunds. Cancelling stops the next renewal; it does not refund the term you are already in. An annual licence is paid for the year and is not refunded pro rata when you stop using it. Where we have charged you in error, or where a licence could not be issued at all, we refund the amount concerned. Anything beyond that is at our discretion, and a refund we do grant ends the licence on the day it is issued. A consumer's statutory right of withdrawal, where it applies, is honoured in full and is unaffected by this paragraph. Refunds are returned through Stripe to the payment method used.
4. Payment
Payments are handled by Stripe. Checkout and the billing portal are Stripe-hosted pages. RERUN never sees or stores your card number. What we store is the Stripe customer and subscription identifier, the plan, the price identifier, the current period end and the resulting licence state — enough to know whether your licence is valid, and nothing more.
Prices are the ones displayed at checkout, in the currency shown there, and they exclude VAT. Tax is calculated and applied by Stripe Tax at checkout, and Stripe collects your VAT or tax identification number where it applies. Any tax shown is therefore Stripe's determination for your billing address, not a tax opinion from us.
Stripe's own terms and privacy policy govern the payment itself. Invoices and receipts are available from the Stripe billing portal linked in your account.
Invoices are issued by Registered company name — to be completed under tax identification number CIF/NIF — to be completed . The tax treatment of your purchase is determined at checkout by Stripe Tax, from your billing address and from the VAT or tax identification number you enter there — including the reverse charge on cross-border business sales inside the EU, where it applies. The invoice Stripe issues states the treatment that was applied. Enter a valid VAT number at checkout if your organization has one; a tax determination cannot be changed by re-issuing the invoice afterwards.
If a renewal payment fails, Stripe retries it and the licence enters the fourteen-day grace state described in section 3. If payment has not succeeded when that window closes, the licence stops and the subscription is treated as ended; you can start a new one at any time. We charge no late-payment interest, collection fee or reactivation fee on a failed card payment. Where an invoice is agreed outside Stripe and is paid late, the statutory late-payment interest under Spanish Law 3/2004 applies by operation of law, and nothing here waives it.
5. What you are responsible for
RERUN drives a real browser against whatever address you give it. It does not know whether you own that system, and it does not check. That responsibility is yours.
- The systems you test. You confirm you have the right to test every application, environment and endpoint you point RERUN at — including third-party services your application depends on, which the browser will also contact during a run.
- The credentials you load. RERUN can import an explicitly selected cookie export into its isolated browser profile, and can store an API key for a model provider. It never reads your Chrome profile, password store, history, cards or extensions. You choose what to load, you confirm each import, and you are responsible for having the right to use those accounts and for what happens with them.
- Your account. Keep your password and account access secure, keep your member list current, and deactivate devices you no longer control — a lost or wiped Mac keeps its activation slot until you deactivate it.
- Lawful use. Do not use RERUN against systems you are not authorised to test, to defeat another party's access controls, or to generate load intended to disrupt a service.
RERUN produces evidence about a run. It does not certify anything. Deciding what a passing or failing run means for your release, your audit or your regulator is your judgement, not ours.
6. AI steps and your model provider
AI is off unless you turn it on for a specific step. A flow with no AI step makes no model request at all; deterministic recording, replay and evidence never require model egress. AI assertions are an experimental feature.
When you do add an AI step, it runs on your provider account — your OpenAI API key, or an already-authenticated Claude CLI on your machine. The request is made under your contract with that provider, billed to you, and governed by their terms, their privacy policy and their data retention. We are not a party to that relationship and we do not control it. If your provider changes its terms or its handling of data, that is between you and them.
What leaves the machine on a commercial AI step is bounded and redacted: the step's instruction,
a sanitized URL and page title, bounded visible text and candidate metadata. OpenAI requests are
sent with store: false and receive no screenshot; the Claude path uses the same
text-only boundary. The development-only Codex executor can receive a DOM-masked screenshot, and
when it does, it says so in the local egress receipt. Every AI step writes that receipt locally:
provider, model, field categories, redaction policy and latency.
Redaction is defence in depth, not a guarantee. RERUN cannot know that a particular page contains nothing sensitive. You decide which steps may send page context to a third party, and you carry the responsibility for that decision — including any duty to inform or obtain consent from the people whose data appears on the page.
7. Service limits and no warranty
The Service has limits, and we would rather state them here than let you discover them later. Concretely:
- We hold no compliance certification — no ISO 27001, no SOC 2, no HIPAA attestation — and we claim none. Do not represent RERUN as certified to your auditor.
- We make no uptime commitment for the control plane and offer no SLA. The desktop app carries a signed offline lease of up to thirty days, so a short outage does not stop your work, but that is a design property, not a promise of availability.
- RERUN does not claim air-gap support, Zero Data Retention, encrypted evidence storage or tamper-proof artifacts. Evidence on your machine is protected by redaction and owner-only file permissions, and otherwise relies on your operating system and disk encryption.
- Several capabilities are outside the scope of the Service and are not supplied under these terms, including CAPTCHA handling, automatic selector healing, managed secret vaults, scheduled runs, team sync, signed reports, MDM packaging and client-certificate (mTLS) targets. Nothing in our materials should be read as offering them.
To the fullest extent permitted by law, the Service is provided "as is" and "as available", without warranties of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose or non-infringement. We do not warrant that the software is free of defects, that a run will detect every defect in your application, that a recorded flow will keep working when your application changes, or that the control plane will be available when you need it.
This section is read subject to the rights you hold by law. Spanish and EU law give the recipient of digital content and services rights of conformity that cannot be excluded or limited by contract, including — for consumers — the remedies in Real Decreto Legislativo 1/2007 where the software does not conform to what was described. To the extent an exclusion above conflicts with a right you hold that cannot be waived, that right prevails and the rest of this section continues to apply.
Support. Support is provided by email at Support email — to be completed , in English and Spanish, on ordinary business days. We read every message and aim to answer promptly, but these terms commit to no response time, no resolution time and no availability target. A signed Enterprise agreement may set different support terms for the customer that signed it.
8. Limitation of liability
To the fullest extent permitted by law, neither party is liable for indirect or consequential loss, nor for loss of profit, revenue, business, goodwill, data or anticipated savings, nor for the cost of substitute services — even where the possibility was known in advance. In particular, we are not liable for a defect your tests did not catch, for a release you shipped on the strength of a passing run, or for what a third-party service you tested against did in response to that run.
Our total aggregate liability arising out of or in connection with these terms, whether in contract, tort or otherwise, is limited to Liability cap — to be completed .
That limit reflects the practical allocation this product creates: your flows, credentials, session state and run evidence never reach us, so we can neither lose them nor recover them, and any AI request is made under your own provider account. Our involvement is limited to identity, billing and entitlement, and the price of the licence is set on that basis.
Nothing in these terms limits liability that cannot be limited by law: liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for wilful misconduct or gross negligence, for a party's infringement of the other's intellectual property, and any other liability applicable law does not permit to be excluded or restricted — including a consumer's non-waivable statutory rights — all stand outside the limits above. So does your obligation to pay the fees due.
9. Termination and what happens to data
You can stop at any time: cancel the subscription from the Stripe billing portal, deactivate your devices from your account page, and remove members you no longer want to hold seats. The portal does not currently offer self-service account deletion; request account closure at the address in section 12.
We may suspend or terminate a licence for non-payment after the grace window, for a chargeback or payment dispute, or for a material breach of these terms — in particular the use restrictions in section 2 and the responsibilities in section 5.
When a licence ends, the control plane stops issuing entitlements. The desktop app keeps working only until its current signed lease expires or is revoked; it then fails closed. A revoked licence takes effect at the next refresh rather than instantly on every machine.
What we hold, and can therefore delete:
- identity — your name, email address and hashed password;
- organization, membership and invitation records;
- subscription, billing identifiers and entitlement state;
- device activation records — installation identifier, device public-key hash, device name, platform, app version and timestamps;
- licence lease metadata, audit events and release metadata.
What we do not hold, and therefore cannot delete or return:
- your flows, the URLs you tested, DOM snapshots, screenshots, cookies, session state, run evidence and AI provider keys.
All of that lives on your Mac and nowhere else. There is no hosted copy and no backup on our side. If you want it gone, delete it locally; if you lose the machine, we cannot restore it for you. That is the trade you make for a local-first runtime, and it is deliberate.
After termination we delete the account, organization, membership, entitlement, device activation and audit records listed above within 30 days from termination. Billing, invoice and tax records are the exception: we keep those for the statutory retention period for accounting records, because the law requires it, and they remain protected for as long as we hold them. The Privacy Policy sets out each period in detail.
A data processing addendum covering the control-plane data is offered, and is published as the RERUN Data Processing Addendum. It forms part of these terms and applies from the moment you accept them, with no separate signature needed. If your procurement process requires a counter-signed copy, ask at Legal contact email — to be completed and we will execute one.
The sections that by their nature survive termination — the licence restrictions, the warranty disclaimer, the limitation of liability, and governing law — continue to apply after it.
10. Governing law and venue
These terms, and any dispute arising out of or in connection with them, are governed by the law of Spain, excluding its conflict-of-law rules and the United Nations Convention on Contracts for the International Sale of Goods. The competent courts are Competent courts — to be completed , and both parties submit to them.
Where you contract as a consumer, that clause does not displace the mandatory rules that let you sue, and be sued, in the courts of your own place of residence. We do not require mediation or arbitration before you go to court, and we are not currently a member of an out-of-court consumer dispute resolution scheme. Write to us first if you can: most disputes are settled faster by email than in front of a judge.
11. Changes to these terms
We may update these terms — for example when the product changes, when a processor changes, or when the law requires it. The current version always carries a date at the top of this page.
For material changes, we will notify the account owner by email at the address on the account at least 30 days before the change takes effect. A material change that reduces what you receive, or increases what you owe, does not apply during a term you have already paid for: it takes effect at your next renewal, and you can cancel before that renewal if you do not accept it. Changes required by law, and changes that only clarify existing wording, take effect on the date stated in the notice.
If you keep using the Service after a change takes effect, you accept the updated terms. If you do not accept them, stop using the Service and cancel your subscription; section 3 explains what happens to the period you already paid for.
12. Contact
Legal notices under these terms must be sent in writing to Registered address — to be completed , and copied by email to Legal contact email — to be completed .
For everyday questions about billing, seats or devices, write to Support email — to be completed .
Questions about personal data are answered in our Privacy Policy, which names the processors we use and how to exercise your rights.
13. Language of these terms
These terms are published in English and in Spanish. Both versions state the same agreement, and neither is a summary of the other. Where a discrepancy between them changes the meaning of a provision, the version that prevails is Prevailing language — to be completed , and the other is read as a translation of it. This clause settles a discrepancy between two texts; it does not take away any right the law of your own country gives you, including the right to be addressed in your own language where that law requires it.