Updated October 30, 2026. Cadence is a meeting recording and transcription service operated by NYASB LLC. This notice applies to the Cadence apps, cadencemeets.com, the legacy cadence.nyasb.com address, and their testing environments.
We process your account identifier, email address and available profile information; recordings you capture or import; meeting titles, projects, timestamps and recording markers; generated transcripts, summaries and speaker labels; your corrections; and search queries. If you connect a calendar, we also process the calendar information described below. Conversations may include personal or sensitive information about you and other participants. Record and upload only conversations you are entitled to share, and obtain the required permissions and consent.
Microphone access enables recording. Supported desktop capture can also record computer audio with your permission. Cadence keeps recoverable local recordings on supported native clients and uploads audio for server processing. It does not require GPS or precise device location. Servers and authentication services may process IP addresses and technical request information to operate and secure the service.
We use this information to authenticate you, store and play recordings, generate transcripts and summaries, organize meetings, provide search, troubleshoot problems and respond to support requests. Cadence does not display targeted advertising or sell recordings, transcripts or calendar information.
These are cloud processing features, not on-device-only transcription or end-to-end encrypted storage. Providers may process information in countries different from yours. Their processing is also subject to their applicable terms and privacy notices: Google, Apple, NanoGPT, OpenRouter, Turbopuffer, RevenueCat and Stripe. AI transcripts, summaries, timestamps and speaker labels can be inaccurate; consult the original recording when accuracy matters.
Connecting a calendar is optional. If you connect Google Calendar, Cadence asks Google for read-only access to your list of calendars and to their events, plus your Google account email address to label the connection. Cadence cannot create, change or delete anything in your calendar, and it never starts a recording because of a calendar event.
Cadence uses this information only for features you can see in the app: showing upcoming meetings, naming a recording and choosing its project from the meeting you link it to, showing who was invited, suggesting invitees when you name speakers, reminding you before meetings on your devices, preparing for a meeting with its agenda and your notes, and drafting a follow-up email that you send yourself.
Cadence stores an encrypted access token, the names and colours of your calendars, and events from the past day through the next seven days: title, time, attendees' names, email addresses and responses, organizer, meeting link and the invite description. When you link a recording to a meeting, Cadence keeps the meeting's title, time, calendar name and colour and attendees with that conversation; it does not keep the invite description. Disconnecting a calendar deletes the stored events and token and asks Google to revoke Cadence's access; meeting details already attached to conversations remain until you unlink or delete those conversations. Deleting your account removes all of it.
Cadence does not sell, rent or trade Google user data, does not use it for advertising, and does not use it to train AI models. Google user data is disclosed only:
Google user data is not sent to our transcription (NanoGPT), summary (OpenRouter), search (Turbopuffer), sign-in and crash reporting (Google Firebase), billing (RevenueCat, Stripe) or analytics and advertising measurement (Umami, Google Analytics, Meta) providers. People at NYASB do not read it unless you ask us to for support, it is needed for security or to comply with the law, or it has been aggregated and anonymized for internal operations.
On Mac and iPhone you can instead let Cadence read calendars already on your device; that information stays on your device unless you link it to a recording. Microsoft calendars, when available, are handled the same way as Google Calendar.
Cadence's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
If you choose to connect your Cadence account to an assistant such as ChatGPT or Claude, the assistant may use read-only Cadence tools in response to your requests. Those tools can return meeting titles and dates, project names, linked calendar event titles, times and invitees, search results, transcript passages, speaker labels, timestamps, and links to the cited moment from meetings your account can access. The assistant provider receives the information returned by the tools and handles it under its own terms and privacy policy. Cadence does not give this connection permission to edit or delete meetings, send messages, or change projects.
To stop new access through a Cadence grant, disconnect Cadence in the assistant and contact Cadence support if you need the authorization revoked. Revoking a grant does not erase transcript content already returned to an assistant or included in an assistant conversation. Review the assistant provider’s controls for managing that content. Cadence recordings remain private; this connection does not publish audio or make a meeting accessible to people outside your Cadence account.
Cadence records private account-level milestones, including verified account creation, recording uploads, transcript completion and viewing, repeat use, search, playback, assistant-tool use, notifications and subscription activity, to understand adoption and improve the service. This private ledger is associated with your Cadence account and is removed when that account is deleted. We also use self-hosted Umami for aggregate website, mobile screen/action and server milestone counts. Server exports contain fixed event names, coarse app platform/version and explicit campaign tags; assistant events can include a fixed tool name and transport. They do not contain account identifiers, emails, meeting identifiers, titles, audio, transcripts, calendar information, search text or assistant arguments. Backend requests do not forward your device IP address. Direct website/mobile analytics requests expose their source IP and coarse browser/app information to Umami for its visitor/session statistics. These statistics do not match an app installation to your Cadence account. Website controls and the mobile Account App usage analytics switch control their respective Umami collection; the mobile switch does not disable the private server ledger or its aggregate export. Account deletion removes pending server exports, but previously delivered aggregate counts cannot be linked back to an account for removal.
If you open Cadence from a creator's link, the website keeps that creator's handle as a campaign tag and adds it to App Store and Google Play links. Tapping a store link there also copies the creator's link. When a new account first opens the iPhone app, Cadence checks whether the clipboard holds a link and, only then, asks iOS to read it. The Android app reads the referrer Google Play passes to new installs. You can also enter a creator code in Account. Cadence keeps only the creator handle with your account, to learn which creators bring people to Cadence; nothing about your device is used to match you, and the handle is removed when the account is deleted.
If you install the iPhone app after tapping a Cadence ad in App Store search results, a new account's app asks Apple's AdServices framework for a one-time attribution token and sends it to Cadence. Our server sends that token to Apple, which replies whether the install came from our ad and, if so, the campaign, ad group and keyword identifiers. Cadence keeps only those identifiers with your account, to learn which ads bring people who use Cadence, and uses them as the campaign tag on the aggregate counts described above. The token is not stored, no advertising identifier or tracking permission is used, and the identifiers are removed when the account is deleted. Apple does not supply ad details if you have turned off Personalized Ads.
Our public website uses a Google tag (Google Tag Manager and Google Analytics) to measure visits and campaigns, and our download page tells Google Ads when someone clicks a download button, so we can measure our Google ads. The public website and the Cadence web app also use the Meta Pixel, and the iPhone and Android apps use Meta App Events, to measure our advertising, including app installs and opens and when a recording of at least five minutes finishes uploading, which Meta receives as an event name only. Unlike Umami, these services are run by Google and Meta, which receive information directly from your browser or device: your IP address, browser or device information, the page address and referrer, including any campaign tags, and cookies or similar identifiers. In the web app, the page address sent to Meta can include a meeting or project identifier or the code from a shared link. They do not receive audio, transcripts, summaries, meeting titles or calendar information. Google and Meta handle this information under their own terms and privacy policies (Google, Meta), and it may be used to measure and improve advertising.
The website’s site-analytics control and Do Not Track apply to Umami only; they do not stop the Google tag or the Meta Pixel, and the mobile App usage analytics switch does not stop Meta App Events. You can block the website tools with your browser’s privacy settings or a content blocker, and manage ad preferences in your Google and Meta accounts.
Your library remains stored until you delete meetings or request account deletion. Deleting a meeting hides it from your library immediately and schedules removal of server audio, processing files and search-index entries. Cleanup can take additional time if a service is unavailable. Server deletion does not erase recording copies retained on your own devices.
Private recovery backups can contain earlier recordings, transcripts and calendar information. Cadence automatically expires managed backup copies within 30 days. Deleted data is not used to restore an account or rebuild its search index. We retain minimal deletion records to prevent deleted accounts from being restored. Limited records may need to be retained for security or legal obligations; we will explain any applicable exception when handling your request.
You can stop recording, revoke microphone or computer-audio permissions in device settings, disconnect calendars in Account → Calendars, correct transcripts and delete individual meetings. You can also remove Cadence's access from your Google Account. To request access, correction, account deletion or deletion of associated data, email nyasb.devs@gmail.com or use our contact form. Use the subject “Cadence privacy request” and identify your account email. We may ask you to verify account ownership; do not send passwords. You can also request account deletion from Account settings in the Cadence app.
Contact messages and the information you include are used to respond to your request. If you send an Enterprise enquiry from our website, Cadence stores your name, work email, company, team size, the features you select, your message and any campaign tags on the page you came from, and emails them to our team through Resend so we can reply. We do not add you to a mailing list. Please avoid attaching private recordings unless they are necessary and requested. Applicable privacy rights and general NYASB contact information are in the NYASB privacy policy.