Privacy Policy
Last updated: September 2, 2026
Why we exist
Red Tape Recordings exists to make public government meetings easier to find, cite, and share. City councils, county boards, and planning commissions already publish their meetings — the problem is that a three-hour video with no transcript and no index is technically public and practically unreadable. We fetch what governments have already published and make it searchable and linkable down to the second. The content on this site is overwhelmingly public record, published by governments themselves.
This policy explains what we do with information — both the public records we republish and the much smaller amount of personal information you give us directly.
Who we are
This site is operated by How To ADU LLC, a California limited liability company doing business as Red Tape Recordings, in Napa, California.
You can reach us at ally@redtaperecordings.com for any question or request in this policy, including access and deletion requests.
What this policy covers
This policy covers redtaperecordings.com and the tools on it: the deep-link resolver, the meeting archive, search, accounts, saved-search alerts, on-demand transcription, and our update emails.
It does not cover the government websites and video platforms we link to. When you play a meeting video, it streams from the government's own source, and that provider's privacy policy applies to that playback — not ours.
Public records we republish
Most of what you see on this site is public record. We fetch and display video, captions, transcripts, agendas, agenda packets, and meeting metadata that governments publish on their own official portals.
We never re-host video. Video always plays from the government's source. We link to it and index around it.
Agenda packets and public-comment letters sometimes contain personal information that members of the public disclosed to their government — names, addresses, and sometimes more. We republish those documents as the government published them. We do not add to them, enrich them, or combine them with other sources.
If you want a document reviewed or removed, email us at ally@redtaperecordings.com. We will review each request. This is a manual process handled by a person, so we can't promise a fixed turnaround, but we do read and respond to every request.
Information we collect
What we collect depends entirely on which features you use. Most of the site works without an account and without telling us who you are.
Looking up a meeting
You don't need an account to paste a meeting URL into our tool. When you do, we log the URL you submitted and what happened when we tried to resolve it: which platform it was, whether we found video, whether we found a transcript, how many caption segments it had, the detected language, any warnings, the meeting's title, date, and jurisdiction, how long the lookup took, when we first and last saw that URL, and how many times it has been requested.
We keep this for two reasons: so a repeat lookup of the same meeting is fast, and so we can see which platforms and jurisdictions are failing and fix them.
These logs do not contain your IP address, your browser's user agent, a cookie, a session, or an account id. A resolve log records that a meeting URL was looked up — not who looked it up.
We do use your IP address to rate-limit lookups, so that one automated caller can't overwhelm us or the government site we're fetching from. That check happens in memory as the request is served and is not written to our database.
Searching
When you search the archive, we log the keyword, any jurisdiction filter, how many results came back, and the time. This tells us what people are actually looking for, so we can improve the archive's topic list and coverage.
Search logs are deliberately identity-free — no IP address, no user id, no session, no user agent. On a site built for scrutinizing local government, a search log that could be tied to a named person is something we chose not to hold.
Reporting a problem
If you use the "report a problem" control on a meeting page, we store the meeting URL, the issue type you picked, and whatever you type into the details box, plus a timestamp. We don't collect your identity with it — but please don't type anything into that box you wouldn't want kept, since we keep what you send.
Accounts
Sign-in is handled by Clerk, a third-party identity provider. Clerk holds your account email address, your name, and your login credentials. We do not store your password, and it never passes through our systems.
Our own databases store only Clerk's opaque user id (a string like user_2abc…) plus the things you saved: your saved meetings and your saved searches. No email address, no name.
See Clerk's privacy policy for how they handle the account data they hold.
Saved-search alert emails
If you save a search and turn on alerts, we email you when new meetings match it. We don't store your email address to do this — at send time we look up your account's primary email address from Clerk, send the message, and don't retain it. Delivery is through Resend, our email provider.
Every alert email carries a one-click unsubscribe link for that specific saved search. Clicking it removes that saved search from your account, with no login step, using a signed link unique to that item. Our emails also carry a sitewide unsubscribe link that opts your address out of our mailing list entirely.
On-demand transcription requests
When a meeting has no usable captions, anyone can ask us to transcribe it — no account needed. We collect your email address and store it alongside the job, because we need it to send you a confirmation link and then to tell you when the transcript is ready or that we couldn't complete it.
To be straightforward about this: we do not currently delete that email address when the job finishes. It stays attached to the job record until you ask us to remove it. Your address is never shown publicly — our job-status responses strip it out before returning anything — but it is retained.
"Get updates" signups
If you sign up for updates, we store your email address as a contact in an audience list held by Resend, our email provider. We use it to send occasional updates about new features and tools.
Every email includes an unsubscribe link. Clicking it marks your address as unsubscribed with Resend immediately, with no login or confirmation step, and we send one final confirmation that you're unsubscribed.
Analytics
We use Google Analytics on this site to understand which pages and features get used. Google Analytics sets cookies in your browser and collects standard web analytics data, including your IP address, the pages you visit, and general information about your device and browser. We also send it a small number of events about how the meeting player is used — for example that a video was played, a transcript line was clicked, or a timestamped link was copied.
We use this in aggregate to improve the site. Google's handling of this data is governed by Google's privacy policy. You can opt out of Google Analytics across all sites by installing Google's opt-out browser add-on, or by blocking analytics cookies in your browser or with an extension.
Error reporting
We use Sentry to collect reports when something breaks. An error report can include technical details about the request that failed, such as the URL being processed and a stack trace. We have not enabled Sentry's option to attach personally identifying request data, and we don't use it for performance tracking. We use these reports only to find and fix bugs.
Hosting and where data is processed
Our applications and databases run on Render, in the United States. Email is sent through Resend and identity is handled by Clerk. Your data is processed in the United States.
How we use it
- To run the service — resolving meeting URLs, serving pages, and playing back the government's video and captions.
- To make it faster, by caching what we've already resolved.
- To send you what you asked for — a confirmation link, a transcript-ready notice, a saved-search alert, or a product update.
- To find and fix problems, including which platforms and jurisdictions are failing.
- To understand what people look for, so we can improve coverage and search.
- To improve the service and build new features, including the uses described under "Data licensing and AI training" below.
- To protect the service and the government sites we fetch from, including rate limiting.
Cookies and analytics
Clerk sets session cookies when you're signed in. These are what keep you logged in; without them, accounts don't work.
Google Analytics sets analytics cookies, as described above.
We do not use advertising cookies, and we do not run ads or ad networks on this site. We don't use cookies to build a profile of you across other websites.
Who we share it with
We don't sell or rent your personal information. We share it only with the service providers that make the site work:
- Clerk — identity and sign-in.
- Resend — email delivery and our mailing list.
- Render — application and database hosting.
- Google Analytics — site analytics.
- Sentry — error reporting.
We may also disclose information if we're legally required to — for example in response to a valid subpoena or court order — or where we need to in order to protect our rights, our users, or the public. If our business is sold or transferred, information may transfer with it.
Public contributions
When you request an on-demand transcription, the transcript we generate is added to that meeting's public page. Transcripts are public and are preserved indefinitely as part of the archive — that's the point of the archive.
Transcripts are not publicly attributed to the person who requested them. Your email address is not shown on the page and is not included in the public data.
Data licensing and AI training
This section describes a deliberate choice, so we want to be plain about it.
We may use the public-meeting content we collect — transcripts, captions, agendas, and meeting metadata — to improve the service, to train and evaluate speech-to-text and other models, and to license or sell datasets derived from these public records to third parties. This is public government record, and building a usable, licensable corpus out of it is part of how this service sustains itself.
We do not sell or license our users' personal information. That means we do not sell, license, or share for money: your account information, your email address (whether you gave it to us for updates, for a transcription request, or through your account), your saved meetings, or your saved searches. None of that goes into any dataset we license, and none of it is for sale.
The distinction is between the public record, which we do commercialize, and you, which we do not.
Your choices and rights
You can ask us to access, correct, or delete the personal information we hold about you by emailing ally@redtaperecordings.com. We'll verify your request and respond.
Some things you can do directly:
- Unsubscribe from emails — use the unsubscribe link in any email we send.
- Remove a saved search or saved meeting — unsave it from your account, or use the unsubscribe link in an alert email.
- Delete your account — deleting your account through the account menu removes your saved meetings and saved searches from our databases, and removes your account and its email from Clerk.
Deleting your account does not automatically remove other information you may have given us separately — for example an email address you submitted for a transcription request, or an address on our updates list. To have those removed, email us and we'll handle it manually. There is no automated process that sweeps every system, so please ask and we'll do it.
California residents
If you're a California resident, the California Consumer Privacy Act gives you the right to know what personal information we collect about you and how we use and disclose it, the right to request deletion of that information, the right to request correction of inaccurate information, the right to opt out of the sale or sharing of your personal information, and the right not to be discriminated against for exercising any of these rights. We will not deny you service, charge you a different price, or give you a lower quality of service for making a request.
We do not sell or share your personal information, and we have not sold or shared personal information in the preceding twelve months. As described above, we may license datasets derived from public government records — that is not a sale of your personal information.
Information that is lawfully made available from federal, state, or local government records is "publicly available information" under the CCPA, and publicly available information is excluded from the CCPA's definition of personal information. The great majority of the content on this site falls into that category.
To make a request, email ally@redtaperecordings.com. You may use an authorized agent; we may ask for proof of their authority and for information sufficient to verify your identity.
Data retention and deletion
Public-meeting content — transcripts, captions, agendas, and meeting metadata — is retained indefinitely. It is an archive; keeping it is the service.
For everything else, we should be honest that we do not currently run any automatic deletion schedule. Resolve logs, search logs, problem reports, transcription job records including the requester's email address, and mailing-list contacts are retained until you ask us to delete them, or until we no longer need them. If you want your information removed, email us and we'll remove it.
Unsubscribing from emails marks your address as unsubscribed so we stop sending to it; if you want the address deleted outright rather than suppressed, tell us and we'll delete it.
Children
This service is not directed to children under 13, and we don't knowingly collect personal information from them. If you believe a child has given us personal information, email us and we'll delete it.
Security
We take reasonable measures to protect the information we hold. The site is served over HTTPS. We deliberately keep very little personal information in the first place: passwords and account emails live with Clerk rather than with us, our own account records hold only an opaque identifier, and our search and resolve logs carry no identity at all. Storing less is the most reliable protection we can offer.
That said, no method of transmission or storage is completely secure, and we can't guarantee absolute security.
Changes to this policy
We may update this policy as the service changes. When we do, we'll update the "last updated" date at the top of this page. If we make a material change to how we handle personal information, we'll note it here on the page.
Contact
Questions about this policy, or a request about your information or a document on this site: ally@redtaperecordings.com.
This page was last reviewed on September 2, 2026. It is a plain-English description of our current practices, not legal advice.