What prewire reads, and what it keeps.

prewire reads your calendar to find recurring meetings, gathers the material a meeting refers to shortly before it happens, writes a pre-read from that material with a citation against every claim, and then deletes the gathered material within 24 hours. What survives is the pre-read, the decisions recorded in it, and the references needed to follow a citation back to its source.

It holds no standing permission to change anything. The single action that modifies a calendar — shortening or cancelling a meeting — runs under the organiser’s own Google identity, at the moment they confirm it, and is recorded in an audit log.

Your content is never used to train a model. That is a contractual term with every model provider prewire uses, not a setting, and the provider bound to your organisation is recorded so the claim can be audited.

Where prewire is used inside an organisation, that organisation is the controller of the meeting data in its workspace and decides who may connect a calendar and what is enrolled. prewire operates the service as a processor on its instructions, and is the controller for the account data it needs to run the service itself — sign-in identity, billing, and security logs.

Privacy requests reach prewire through your organisation’s administrator, who can raise them from the product, or through the channel named in your organisation’s data processing agreement. An administrator can export or delete an account’s data without needing to ask anyone.

Access is granted in stages, and each stage is asked for separately at the moment it is needed. Connecting a calendar never grants the ability to write to it.

From your calendar, prewire stores the structure of a meeting rather than its substance: the series and its recurrence, the title, the start and end times with the series’ timezone, the organiser, and the participant list. Until a series is enrolled, that is all there is — meetings are detected and classified from this metadata alone, and nothing about an unenrolled meeting’s content is read.

You can withdraw any of these permissions at any time, from prewire’s connection settings or from your Google account. Withdrawing calendar access stops the service for that calendar immediately.

The Slack app installed for your workspace can send messages, open direct messages with participants, read its own direct-message history, and look up user names and email addresses so a calendar participant can be matched to a Slack account. It cannot read your channels.

Anything that reads organisational content is a permission you grant individually, for your own account, and it is used only to draft answers for you to review before they are sent. Participants who have not granted it are not disadvantaged silently: their draft is built from their earlier responses in prewire alone, and the pre-read says so.

Raw source material is deliberately short-lived. It is gathered to write one pre-read, and it is deleted by two independent mechanisms — immediately once the pre-read is sent, and again by a nightly sweep that catches anything the first missed, because the failure paths that skip the first are exactly when data lingers.

Each organisation’s data is isolated in the database itself. Every query runs under a tenant identity enforced by the database, using an application role that cannot bypass that rule; a query that arrives without one fails rather than returning everything. There is no shared index and no cross-organisation search.

Within an organisation, access to source material is checked per reference, per reader, at the moment of reading, against the permissions that reader already holds. prewire does not crawl your systems, does not build a shared index of them, and does not hold a privileged account that can read documents on everyone’s behalf.

A pre-read is assembled as the organiser, from what the organiser can see, and it says so in its footer. That means it can show a participant something they could not have reached themselves — which is the organiser sharing it, disclosed on the document. It never widens anyone’s standing access to any system.

If an organiser has granted a delegate the ability to act for them, the delegate’s context is shown persistently while they are in it, and every action they take is recorded against both identities.

Access tokens are encrypted with a key held in a managed key service, decrypted only in memory for the length of a single request, cleared afterwards, and every decryption is logged. Keys are rotatable without re-consent.

The component that runs the automated loop is structurally incapable of writing to a calendar: the write client cannot be imported into it, and that restriction is verified on every change rather than kept by convention. A calendar edit checks the event has not changed since prewire last read it, so a concurrent human edit is refused rather than overwritten.

Writing a pre-read means sending the gathered material to a language model provider. Every provider prewire binds is contractually required to retain nothing and to train on nothing; a provider unwilling to commit to that in writing is not eligible, whatever it costs. The provider bound to your organisation is recorded against each call, so the claim can be checked rather than trusted.

The other processors prewire relies on are its cloud hosting and database provider, its workflow orchestration service, and its email delivery provider. The current list, with each processor’s role and location, is available on request and is an annex to the data processing agreement.

prewire’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Section 3 lists every Google permission prewire requests and when each is asked for; this section states what is done with what those permissions return.

prewire requests no restricted scope. Reading what is attached to a meeting uses three per-application permissions — Docs, Sheets and Slides — rather than access to your whole Drive, so the data reaching prewire is limited at the point of access and not only by this promise about what happens afterwards.

Each organisation is pinned to a region and its data is processed in that region. Where data must cross a border to reach a processor, it does so under the transfer mechanism named in the data processing agreement.

You can ask for a copy of the personal data prewire holds about you, ask for it to be corrected or deleted, object to a particular use, or ask for it in a portable form. Where your organisation is the controller, ask your administrator and they will instruct prewire; where prewire is the controller, raise it through the same channel. Requests are answered within one month.

Disconnecting your calendar stops all processing for it immediately, and you can do that yourself without asking anyone. If you believe prewire has handled your data wrongly, you can complain to the data protection authority for the country you live or work in.

prewire sets one cookie: the session cookie that keeps you signed in after you authenticate with Google. It is required for the product to work, carries no advertising identifier, and is not shared. There is no analytics or advertising cookie, and so there is nothing here to consent to or opt out of.

prewire is a workplace tool, sold to organisations and not directed at children. It is not intentionally used to collect data from anyone under 16.

When this policy changes materially, the change is announced in the product before it takes effect, and the date above moves in the same change as the words. Continuing to use prewire after that date is acceptance of the revised policy.

The terms and conditions govern the use of the service itself.