Terms

Last updated 8 August 2026

Part A. This website

A1. Agreement

By using this website you agree to these terms. If you do not, please do not use it. "Vivere", "we" and "us" mean Vivere.

A2. What this site is

A pre-launch marketing site. Vivere is not generally available and has no customers. Product data shown on this site is sample data and is labelled as such wherever it appears. Nothing here is an offer, a price quote, or a commitment to ship a particular feature on a particular date.

A3. The waitlist

Joining the waitlist costs nothing and obliges neither side to anything. It does not reserve capacity, guarantee access, or lock in a price. We may close the waitlist, change how it works, or contact you about availability. You can leave at any time.

A4. Acceptable use

• Do not attempt to gain unauthorised access to this site or its infrastructure.
• Do not scrape it in a way that degrades it for other people.
• Do not use it to distribute malware or to break the law.

Good-faith security research is welcome. Please follow the disclosure process on the security page.

A5. Intellectual property

The content, design and code of this site belong to us. You may link to it and quote it with attribution. You may not present it as your own.

Part B. The service

This part describes the terms intended to govern Vivere once it is available. It does not apply to anyone yet, because nobody is using the service. It is published early because the way Vivere works raises questions that should be answered before you sign up, not after.

B1. What the service does

Vivere connects to a customer's landing page codebase and analytics, reasons about how visitors behave, and makes changes to that codebase intended to improve conversion. Changes are ordinary commits, deployed by the pipeline once its checks have passed.

B2. Autonomous deployment

There is no pre-deploy human approval gate. Changes go live once every automated check has passed, and the customer is notified afterwards with a summary of what changed and why. This is the central design decision of the product, and by using the service the customer accepts it. Customers who require a sign-off step before production changes should not use Vivere.

B3. Customer responsibilities

• Restrictive zones. Marking components or files as off-limits is the customer's responsibility. We honour those boundaries. We cannot infer them.
• Backups and version control. The customer keeps their own repository history and backups. Rollback relies on it.
• Access. The customer grants and revokes access, and is responsible for keeping their own credentials secure.
• Compliance of their own page. The customer remains responsible for what their website says and does, including any regulated claims.

B4. Rollback

Every change is revertable with a standard version control revert. We do not lock rollback behind our own tooling, and a customer can undo any change without our involvement.

B5. Intellectual property in generated code

Code that Vivere writes into a customer's repository belongs to that customer. We claim no ownership of it and no licence to reuse it. We retain ownership of the Vivere system itself, including the pipeline, agents and models used to produce that code.

B6. No guarantee of results

Vivere makes changes intended to improve conversion. It does not guarantee that conversion will improve, that any individual change will help, or that results will hold over time. Conversion depends on traffic quality, offer, pricing, seasonality, and much else outside the page. The service is provided on an "as is" basis without warranties of any kind, to the extent the law allows.

B7. Traffic requirement

The service needs roughly 10,000 monthly visitors per page to reach statistical confidence in a reasonable window. Below that, the pipeline will frequently halt rather than act, which is correct behaviour and also a poor experience. We state this before purchase rather than after.

B8. Limitation of liability

To the maximum extent permitted by law, neither party is liable for indirect, incidental, special or consequential damages, or for lost profits or lost revenue, arising from the service. Our total liability for any claim is limited to the fees paid for the service in the twelve months before the claim arose. Nothing here limits liability that cannot lawfully be limited.

B9. Suspension and termination

A customer may stop the service at any time, and revoking access is sufficient to stop it. We may suspend the service for non-payment, for misuse, or where continuing would create a security or legal risk. On termination, we stop processing and delete or return data as set out in the privacy policy.

B10. Changes to these terms

We will update the date at the top when these change. For material changes affecting an active customer, we will give notice before they take effect.

B11. Governing law

Governing law and jurisdiction will be stated here before the service becomes available. This is a placeholder in an unreviewed pre-launch document, not an omission we intend to keep.

B12. Contact

Questions about these terms: legal@vivere.example.