Privacy Policy
Last updated: 17 November 2026
1. Who we are
Audiominutes is a public webcasting service provided by Comquat Ltd ("we", "us", "our"), a company registered in England and Wales (company no. 08437490). We are the data controller for personal data processed through this website and, where applicable, a data processor acting on behalf of our clients (typically local authorities and councils) for meeting recordings.
2. What this policy covers
This policy explains how we handle personal data collected through the Audiominutes website (www.audiominutes.com), our webcasting service and the Audiominutes app. We process personal data in accordance with the UK GDPR and the Data Protection Act 2018.
3. Information we collect
Contact details you provide when you enquire, request a quote, or become a client, such as your name, organisation, email address and phone number.
Webcast content: audio and video recordings of public meetings we stream and archive on behalf of client authorities. These may capture the voices and, for video, images of meeting participants.
Technical data: limited information collected automatically when you use the site, such as IP address, browser type and pages viewed, used to keep the service secure and working.
4. How we use your information
We use your information to respond to enquiries and provide quotes; to deliver, host and archive the webcasting service our clients pay for; to operate, secure and improve our website and service; and to meet legal, accounting and regulatory obligations.
5. Lawful basis for processing
We rely on legitimate interests (to run and promote our service and respond to enquiries), contract (to provide services to clients), and legal obligation (for example, keeping financial records). Public meeting recordings are processed on behalf of the relevant authority, which determines the lawful basis for making those meetings public.
6. Sharing your information
We do not sell your personal data. We share it only where necessary with service providers that help us operate our hosting and streaming infrastructure, and where we publish links to your content management system at your request. All such providers are bound to protect your data and use it only for the purposes we specify. We may also disclose data where required by law.
7. How long we keep it
We keep enquiry and client data for as long as needed to provide our service and to meet legal obligations, after which it is deleted or anonymised. Meeting recordings are hosted for the duration of our agreement with the client authority, for at least the minimum period stated in your plan, and are retained until that authority asks us to remove them. Each authority remains responsible for its own retention policy and for telling us when a recording should be deleted; we will action deletion requests from the authority promptly.
8. Your rights
Under UK data protection law you have the right to access your personal data, to have it corrected or erased, to restrict or object to its processing, and to data portability. To exercise any of these rights, contact us using the details below. For personal data within a public meeting recording, please contact the relevant authority, as they control that content.
9. Cookies
Our website uses only essential cookies needed for it to function. You can control cookies through your browser settings.
10. Data security
We use appropriate technical and organisational measures, including real-time data verification and back-up, to protect personal data against loss, misuse or unauthorised access. How we protect what we hold for a YouTube channel is described in section 12.
11. Contact and complaints
Questions about this policy or your data can be sent to hello@audiominutes.com or +44 (0) 1223 944305. If you are not satisfied with our response, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk (opens in a new tab).
12. YouTube
Audiominutes uses YouTube API Services. An authority can connect its YouTube channel to Audiominutes, and then choose, meeting by meeting, to stream the meeting live to that channel, to upload the recording there with its agenda chapters, or both. When a meeting has been streamed live to YouTube, we make that live video private once the edited recording is uploaded.
To do this we store the access Google grants us to the channel, the channel's name and ID, and the IDs and settings of the live streams and videos we create on it. We also read the status of those videos and live streams, such as whether they are still processing and who can see them. We do not read the channel's other videos, comments, ratings, captions or analytics, and we do not make aggregated or anonymised data from anything we receive from Google. We use them only for the purposes above, and we do not read or change anything else on the channel. We do not use any of this for advertising, and we do not use it to train artificial intelligence or machine learning models. When an authority chooses YouTube for a meeting, we send that meeting's stream and recording to YouTube, which publishes them under the YouTube Terms of Service (opens in a new tab). Google's use of that information is described in the Google Privacy Policy (opens in a new tab). Our hosting provider stores this information on our behalf, as described in section 6. Apart from sending a meeting to YouTube when the authority chooses, we share none of it with anyone else, and we do not sell it. Audiominutes' use of information received from Google APIs will adhere to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.
The access Google grants is stored encrypted, with AES-256-GCM, and only our servers use it. It and the rest of this information are encrypted whenever they travel over a network.
We keep this information while the channel is connected. When an authority disconnects its channel in Audiominutes, we delete it at once. An authority can disconnect its channel in Audiominutes at any time. You can also remove our access to a channel through Google's security settings at security.google.com/settings/security/permissions (opens in a new tab). When access is removed, we delete what we stored about that channel within 30 days. You can also ask us to delete it, using the details in section 11, and we will do so within 7 days. Copies in our own backups are deleted as those backups expire, within 62 days. Videos already on the channel stay there, under the channel's control.
13. The Audiominutes app
The Audiominutes app lets people at a client authority run and manage its meetings from a phone, tablet or computer. Nobody can make an account alone: an Admin at the authority invites each person, or we set one up for the authority. This section adds to the ones above.
Your account. We hold your name, your email address, your role at the authority (Admin or Member) and when you last signed in. If you use a password, we store only a salted hash of it, never the password. An authority's Admins can see the name, email address, role and last sign-in of its people.
Invitations and password resets. We email these through Amazon Web Services. Each email carries the authority's name, a code and when the code ends: seven days for an invitation, one hour for a reset. We store only a hash of the code.
Microsoft sign-in. If you sign in with a Microsoft work or school account, we ask Microsoft only who you are. We store two identifiers, one for your organisation and one for you, to link that account to yours. We do not keep the token Microsoft gives us, and we cannot read your email, calendar or files. The Audiominutes tab in Microsoft Teams signs you in the same way, and takes nothing else from Teams about you or your meetings. Microsoft handles your sign-in under its own privacy statement (opens in a new tab).
Your devices. For each device you sign in on, we record the kind of device, the app's version, when it was last used and the device's make and model. On a Mac or Windows computer we record the computer's name instead of a make and model, which your IT team may have chosen. A sign-in ends after 30 days without use. The device keeps your sign-in in its secure storage, or in a web browser in that browser's storage, and remembers the authorities you have signed in at but not your email address.
Who changed what. When you change a recording, a transcript or the authority's list of councillors, connect the authority's YouTube channel, or send a recording to YouTube, we record your name against that change, and for most changes your email address too. The authority can see this record. Your name can also be read by anyone in the published data of a transcript or summary you changed, but your email address cannot.
Recordings from a device. With your permission, the app uses the device's microphone to send the sound of a meeting to our streaming servers as it happens, and sends its own recording afterwards when our servers need it. Both travel over encrypted connections to servers in Ireland, and become webcast content under sections 3 and 7. If an authority turns on transcription for a meeting, we send that meeting's sound to our provider Deepgram, which makes the transcript, and afterwards we send the transcript text to Deepgram, which makes the summary. Deepgram handles both in the European Union, as it offers no way to do this in the UK. For the transcript, we tell Deepgram not to keep the sound or the text and not to use them to improve its models, so it deletes them once it has sent back the transcript. It keeps only a record that each transcription request was made. We send the same instruction with the summary, but Deepgram's published information does not say that this applies to summaries, so Deepgram may keep the transcript text it summarises and use it to improve its models, which it may do outside the European Union. Section 12 says what happens when someone sends a recording to YouTube.
The copy on your device. The app installed on a phone, tablet or computer keeps a recording of each meeting on the device, in its own storage, so that nothing is lost if the connection drops. It does not encrypt these recordings itself. It removes each one 30 days after the later of the recording's end and its being sent, and only once our archive has it. A recording not yet sent, or held back on the device, stays until someone deals with it. Signing out does not remove recordings: the next person to sign in at the authority can send them. Removing the app from a computer may not remove them. The app also keeps a log of what the device did.
Logs sent to support. The app sends us a device's log only when someone presses "Send this device's log to support". It says what the device did, with the authority's short name, meeting numbers, the name of the sound input and, from a computer, its network names and addresses and our number for the person who pressed the button; passwords and sign-ins are struck out first. It goes to our own server, filed against the account of whoever is signed in when it is sent, and we use it only to look into a problem. We delete each log 90 days after it arrives.
Terms of use. Before you use the app, it asks you to accept our terms of use, and asks again when they change. We record that you accepted them: your name, email address and authority, the date of the terms, when you accepted, and how you signed in (a password, an invitation code, Microsoft, or a sign-in by Audiominutes support). We keep this to show who accepted which terms, and to know when to ask you again. Nobody at the authority can see it in the app.
Reports. You can report a transcript line, a summary, a recording, or a person at your authority, to Audiominutes support from the app. We keep each report: your name, email address and authority, what you reported as the app showed it (a line's time, speaker and words, a summary, a meeting's title, or the person's name as you gave it), what you said is wrong, and when. We email it to Audiominutes support through Amazon Web Services, with your email address to reply to. Only Audiominutes support reads reports, and only to look into them and act as our terms of use say. Nobody at the authority can see a report in the app, and nothing in it tells the person reported who reported them.
How long. We keep reports and records of accepting the terms for as long as the authority uses Audiominutes, and delete them with the rest of its data when it leaves. The email that tells support about a report is kept in support's mailbox, which is not cleared on a schedule.
What the app does not do. It has no advertising, no analytics service and no crash reporting service. It asks for the microphone, and on Android for notifications. It does not ask for your camera, location or contacts.
14. Deleting your app account
You can delete your account in the app, under About Audiominutes, and it is deleted at once. If you cannot sign in, see how to delete your account: we delete it within 30 days of your asking. If you are your authority's last Admin, someone else must be made an Admin first; if that cannot be done, ask us.
An account belongs to one authority, so an account at another authority is separate. Your account record goes: your name and email address in it, your password, your Microsoft link, your sign-ins and the devices they were on, and any codes. Your email address is removed from the record of who changed what, including the record of who named each speaker in a transcript. Your name stays on the changes you made, as part of the authority's own record, and the authority's meetings and recordings are not deleted. Recordings already on a device stay there until the app removes them. If your email address is also the authority's contact address with us, it stays as that until the authority gives us another.
Some copies of your email address are not removed when your account is, and go in their own time. Our servers' logs record it when you change a transcript or the authority's list of councillors; those logs are replaced as they fill, not after a fixed time, so we cannot say when that copy goes. Our backups hold the whole account for up to about ten weeks, and longer if a night's backup fails, because nothing is removed from them until a night's backup succeeds. A log sent to support from a device stays until its 90 days are up, even if your account is deleted.
Reports you made, and your records of accepting the terms of use, keep your name and email address after your account is deleted, so that a report can still be looked into and an acceptance shown. They go when the authority leaves Audiominutes. A report that names you keeps your name in the same way.
If an Admin removes you, you can no longer sign in, but we keep your account record so that the authority can invite you back. You can ask us to delete it as above.
15. Changes to this policy
We may update this policy from time to time. Any changes will be posted on this page with a revised "last updated" date.