Terms and conditions
The terms prewire is provided on.
These terms govern the use of prewire. The parts worth reading before the boilerplate are section 4, on what prewire may do to a calendar, and section 5, on what a pre-read is and who is accountable for acting on one.
Section 1
The agreement
These terms set out the basis on which prewire is provided to the organisation that subscribes to it. Where a signed order form or master agreement covers the same subject, that document takes precedence over these terms; where it is silent, these terms apply, and the order form names the contracting parties and the law that governs them.
Signing in, connecting a calendar or using the service is acceptance of these terms by the person doing it, on behalf of the organisation they are acting for.
Section 2
What the service is
prewire monitors the recurring meetings a customer chooses to enrol, gathers the material each meeting refers to, produces a pre-read with a citation against every factual claim, collects responses from participants, and recommends whether a meeting should be shortened, cancelled or held as scheduled. It reports afterwards on what was recovered.
A series is prepared only once it is enrolled. Detecting and classifying a series from calendar metadata is not enrolment, and prewire reads nothing about an unenrolled meeting beyond that metadata.
Section 3
Accounts and access
The customer decides who may sign in and who holds administrator rights. The customer is responsible for its users’ actions, for keeping its Google accounts secure, and for removing access when someone leaves.
An organiser may grant a delegate the ability to act for them. The delegate acts inside a context that is displayed for as long as it lasts, and the resulting action is recorded against both identities. A grant is revocable at any time by the organiser or an administrator, and revocation takes effect immediately.
Section 4
What prewire may do to your calendar
prewire holds no standing authority to change a calendar. It cannot create, edit or delete an event on its own initiative, on a schedule, or as a consequence of its own recommendation. The automated part of the service is built so that it structurally cannot hold a permission that would let it.
A calendar is modified in exactly one circumstance: an organiser, or a delegate they have authorised to act, confirms a specific recommendation for a specific meeting. That edit runs under the organiser’s own Google identity, applies only the change shown in the confirmation, and is refused if the event has changed since prewire last read it. Every such edit is recorded with the identity that made it.
Permission to make that edit is requested the first time it is needed and never at connection time. A customer that never acts on a recommendation never grants it.
Section 5
Generated content, and who is accountable
A pre-read is produced by a language model from the material prewire was able to gather. Every factual claim in it carries at least one citation to the source it came from, and a claim that cannot be supported by a source is dropped rather than published. This makes a pre-read checkable. It does not make it correct.
prewire does not warrant that a pre-read is accurate or complete, and it is not advice. Where the available material is too thin to support a conclusion, the service is designed to say so or to abstain rather than guess — but a reader who acts on a claim without following its citation is relying on an unverified statement, and should not.
A recommendation to shorten or cancel is a recommendation. The decision is the organiser’s, is taken by confirming it, and its consequences are theirs. The customer remains accountable for its meetings, for what is decided in them, and for what is decided instead of them.
As between the parties, the customer owns its calendar data, the material prewire reads, the responses its people write, and the pre-reads produced for it.
Section 6
Acceptable use
The service may not be used to:
Not permitted
- Reach further than you can
- Use prewire to obtain material you are not entitled to see, or to work around an access control in a connected system.
- Connect what is not yours
- Connect a calendar or workspace without the authority of the person or organisation it belongs to.
- Interfere with the service
- Probe, disrupt or attempt to gain unauthorised access to prewire or its infrastructure, or circumvent a limit placed on an account. Reporting a vulnerability in good faith is welcome and is not a breach of this clause.
- Resell or reverse engineer
- Resell access, or reproduce the service by decompiling it, except where that restriction is unenforceable by law.
- Feed a competing model
- Use the output of the service to train a competing machine learning system.
Access may be suspended where use of the service threatens its security or the data of another customer. Where suspension is not an emergency, notice is given first and the customer is given a chance to correct the problem.
Section 7
Third-party services
prewire works through Google Calendar, Google Docs, Sheets and Slides, and Slack. Those services are operated by their providers under their own terms, and prewire has no control over their availability, their rate limits or their changes in behaviour. Where one of them is unavailable or a permission is withdrawn, prewire degrades visibly rather than pretending: a participant who cannot be reached is reported as unreachable and not as someone who did not reply.
Section 8
Fees
Fees, the billing period and the currency are those stated in the order form. Fees are payable in advance and are not refundable for a period already begun, except where these terms say otherwise. Fees are exclusive of tax, which is added where it applies. A fee change takes effect at the next renewal and is notified at least 30 days before it.
Section 9
Term, and ending the agreement
The agreement runs for the period in the order form and renews for equivalent periods unless either party gives notice before the renewal date. Either party may end it immediately if the other commits a material breach and has not fixed it within 30 days of being told about it.
What happens when it ends
- Access
- Sign-in and all processing stop on the termination date.
- Export
- The customer may export its pre-reads, decisions and reports for 30 days after termination.
- Deletion
- Customer data is deleted within 90 days of the end of that export window, except where a law requires it to be kept. Backups age out on their own cycle.
- Tokens
- Stored Google and Slack credentials are revoked and destroyed on termination, and can be revoked by the customer at any time before it.
Section 10
Confidentiality
Each party will keep the other’s confidential information confidential, use it only to perform this agreement, and protect it at least as carefully as its own. This does not cover information that is public through no fault of the recipient, was already known to them, or must be disclosed by law — and where the law requires disclosure, the other party is told first unless telling them is itself prohibited.
Section 11
Warranties and disclaimer
prewire warrants that it will provide the service with reasonable skill and care, and that it will not materially reduce the security protections described in the privacy policy during a paid term.
Beyond that, the service is provided as it is. prewire does not warrant that it will be uninterrupted, that it will find every recurring meeting, that a pre-read will be accurate, or that a recommendation will be the right call. All other warranties, to the extent the law allows them to be excluded, are excluded.
Section 12
Liability
Neither party excludes liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be excluded.
Subject to that, neither party is liable for indirect or consequential loss, lost profit or lost opportunity, and each party’s total liability under this agreement is limited to the fees paid or payable in the 12 months before the claim arose. A meeting that was cancelled, or held when it should not have been, falls inside this limit.
This limit does not apply to the customer’s obligation to pay fees, or to either party’s breach of section 10.
Section 13
Data protection
The handling of personal data is described in the privacy policy and governed by the data processing agreement, which forms part of this agreement and prevails over these terms where the two conflict on data protection.
Section 14
Changes to these terms
These terms may be updated. A material change is notified at least 30 days before it takes effect, and a customer that does not accept it may end the agreement before that date without penalty and receive a refund of the unused portion of any prepaid fee.
Section 15
General
Neither party may assign this agreement without the other’s consent, except to a successor of its business. Neither is liable for a failure caused by something outside its reasonable control. If a clause is unenforceable, the rest survives. A right not exercised is not a right waived. This agreement, with the order form and the data processing agreement, is the whole of what has been agreed.
The governing law and the courts with jurisdiction over a dispute are those named in the order form or master agreement between the parties.