Terms of service
Version 2026-11-13
reproo helps software teams receive the problems their testers report: the agent investigates every report with data from the app and the code in the connected repositories, and writes a report the team reviews. These terms apply between Wavy AS ("we") and the organization using the service ("the customer").
1. Who we are
Wavy AS, org. no. 928 635 015, Herman Foss' gate 21, 0171 Oslo. E-mail: lasse@wavy.no.
2. The agreement
The agreement consists of these terms, the data processing agreement and the price accepted when a project is ordered or activated (see "Price and billing"). How personal data is processed is described in the privacy statement and the data processing agreement; for the processing of personal data, the data processing agreement takes precedence over these terms.
Whoever accepts the terms on behalf of the customer – an owner or admin of the organization – confirms that they are authorized to do so. Who accepted which version, and when, is recorded.
The service is for businesses. Consumer legislation, such as the Norwegian Consumer Purchases Act and Cancellation Act, does not apply.
3. Organization and users
The customer is the organization created in the service. Owners and admins can create projects, connect repositories, order and activate projects, invite users and change billing details. Testers need no account.
The customer is responsible for who is given access, for the content submitted and for its users following the terms. The customer is the controller of the data about its testers and must inform them about the processing; the report form can link to the customer's own privacy notice.
4. Projects and fair use
A project is one software product with up to five repositories of that product (for example a web app, an iOS app and a backend).
Each project has a fair-use limit of 3,000 AI investigations per month, and daily limits on AI investigations that protect against abuse. Beyond these limits, reports are still received, without AI investigation and follow-up questions.
In addition, each app key receives at most 1,000 and each project at most 5,000 reports per day, and as many crash reports. Beyond that, new reports are refused until the next day.
A project that requires a repository receives no new reports while none is connected.
5. Price and billing
The price is per active project and month, excluding VAT, as shown and accepted before the project is activated. Billing starts when the project is activated. Creating and setting up a project is free.
A new customer's first order is checked and approved by Wavy AS before the project is activated. The customer accepts the price and the agreements when the order is sent; the project is activated when the order is approved, and billing starts then. Until then the project receives no reports. If we do not approve the order, the project is not activated and nothing is billed. Once the customer is approved, new projects are activated at once. If the customer changes the organization number it is invoiced to, it is checked and approved in the same way before the next project is activated – an archived project taken up again included; projects already active continue as before.
The project is billed per started calendar month, including the month it is activated and the month it is archived in – no proration. Months are counted in Norwegian time. A project activated on 28 November is thus billed for all of November and then for every month it is active; a project archived on 3 March is billed for all of March and not after.
We invoice monthly from the accounting system Fiken, by e-mail to the invoice e-mail address.
We may change the price with at least 30 days' written notice to the organization's owners. The new price applies from the first full calendar month after the notice period, and the customer may archive the project before then.
6. Payment, late payment and holds
The due date is stated on the invoice and is normally 14 days after the invoice date. For late payment we may charge interest under the Norwegian Late Payment Interest Act.
If an invoice is still not registered as paid 14 days after its due date, the service stops automatically for the whole organization: new reports are not received, and AI investigations and repository indexing stop. The data can still be read, and nothing is deleted. The owners are e-mailed the day after the due date and when the service stops.
The service starts again by itself once we have registered the payment – so pay a few working days before the deadline. If the invoice is paid but not registered, the customer can contact us and we will register the payment.
A hold is not a termination: the subscriptions continue and are billed as before. A customer who wants to end them archives the projects (see "Term and termination").
We may also put the customer on hold for material breach or misuse, or when it is necessary to protect the service or other customers. We say why in the dashboard and by e-mail, in advance where possible.
7. Access to code and the customer's data
Repositories are connected read-only through a GitHub App. The code is used only to investigate reported problems – it is never changed, and the service does not review the code otherwise. A repository's index is deleted when the repository is disconnected.
The customer keeps all rights to its code and data, and grants us the right to process them as far as needed to provide the service. We do not use them for any other purpose, and neither we nor the AI provider use them to train AI models.
The customer is responsible for having the right to give us access to the repositories and to the data submitted.
8. The agent's reports (AI)
The agent's questions, explanations and reports are produced by an AI model and may contain errors or omissions. They are suggestions the customer's team reviews. No issue is created or changed in the customer's issue tracker unless a person in the team decides so.
To find duplicates, the service automatically searches the issue tracker the customer has connected with a few keywords from each report, and reads the title, description and status of the matching issues. The status of issues the reports are linked to is read from there too.
Testers are told in the report form that the questions are asked by an AI assistant.
9. Confidentiality
Each party shall keep the other party's confidential information secret – for the customer, in particular source code, reports and business matters – and use it only to perform the agreement. The obligation continues after the agreement has ended.
The obligation does not cover information that is public, that the party already had without a duty of confidentiality, or that must be disclosed by law or by order of an authority. The sub-processors are bound by confidentiality under the data processing agreement.
10. Availability and changes to the service
We operate the service with due care and aim for high availability, but give no uptime guarantee. Maintenance is scheduled, as far as possible, when it disturbs least.
We develop the service and may change features. If we remove a feature in a way that materially weakens the service the customer pays for, we give at least 30 days' notice.
11. Liability
We are not liable for indirect losses, such as lost profit, lost data, losses from interruptions to the customer's business or claims from third parties.
Our total liability under the agreement is limited to what the customer has paid for the service in the twelve months before the event giving rise to the claim.
The limitations do not apply in the case of gross negligence or intent.
Neither party is liable for circumstances beyond its control that it could not reasonably foresee or avoid (force majeure).
Claims must be made in writing within a reasonable time after the customer became or should have become aware of the matter.
12. Term and termination
The agreement runs until terminated. The customer may archive a project at any time: it then receives no new reports and is not billed from the following month. The month the project is archived in is billed in full.
The customer terminates the agreement by archiving all projects and asking us in writing to end the customer relationship. We may terminate the agreement with three months' written notice, and with immediate effect for material breach.
After termination we delete or return the customer's data as described in the data processing agreement. Information we must keep under the Norwegian Bookkeeping Act is kept for as long as the law requires.
13. Changes to the terms
We may change the terms, the privacy statement and the data processing agreement. Each version has a date, and who accepted which version is recorded.
Material changes are notified to the organization's owners and admins at least 30 days before they take effect, by e-mail or in the dashboard, where they are asked to accept the new version. If the customer continues to use the service after that, the new version applies. A customer who does not accept the change may terminate the agreement before it takes effect and is not billed for the months after.
Changes required by law or by an authority, or that only benefit the customer, may apply from publication. New sub-processors are notified under the data processing agreement.
14. Governing law and disputes
The agreement is governed by Norwegian law. The parties shall first try to resolve disagreements through negotiation. Failing that, the dispute is settled by the ordinary courts, with Oslo District Court as the agreed venue.