Privacy
What the software does with your calls, and how that changes depending on who supplies the AI.
Last updated 13 October 2026
Pace Notes is made and sold by Genesis Web Digital LLC ("Genesis Web Digital", "we", "us"), Rockledge, Florida.
Pace Notes is a Mac app, available now, and a Chrome extension, not yet released. This page describes both, so you can see what each does with your data before the extension is released. Either one runs in one of two modes. On a bring-your-own-keys plan, or with no licence at all (the three free calls a month), you supply your own Anthropic and Deepgram keys and no server of ours is involved in a call. On a managed plan (the 7-day trial, Solo and Pro) we supply the transcription and the AI for your calls and the notes after them, and your call audio and transcripts pass through a server we run. On Pro, pre-call prep runs on our service too, and sends the record you hold for the client you prep through the same server.
The mode matters far more than the product does, so this page is organised by mode. Read the section that applies to what you bought; where the Mac app and the extension genuinely differ, it is said in place. Blurring the two modes together would make this document less useful than no document at all.
For bring-your-own-keys plans we are the controller of the small amount of personal data described here, and a processor of nothing. For managed plans we are also a processor of the call data you send us, and you are its controller; our Data Processing Agreement is the contract that governs that, and the subprocessor list names every company that touches it because we handed it to them.
What is true however you use it
Your knowledge is part of every prompt. The transcript of a live call is sent to a large language model to generate what appears on screen, and so is the relevant part of your knowledge base. Your pricing, your objection answers and your case studies are what the model reads in order to suggest something specific to your business instead of something generic. That is the product working as intended, and it means the contents of those files reach a model on every call.
How they get there differs by mode, and the difference is worth knowing. With your own keys, the relevant part is read off your machine and sent with the prompt each time, so a copy of it leaves your machine on every call. We never receive it. Anthropic receives it under your own account, and how long Anthropic keeps what it receives is set by its terms with you. On a managed plan they are uploaded once, when you activate and whenever your copy changes, and kept on our server between calls — so a call sends a check rather than the files, and we hold a copy you can have erased. Neither is more private than the other in the abstract; they are different trades, and both are described below.
The client you are on a call with is described to the model. Stored files are one thing; what the model is told is another. When you name a client at the start of a call, Pace Notes puts that client’s record into the prompt, trimmed to a size limit: whatever your notes hold on them. That can include their contact names, the work you have done for them, your next steps, open loops and “don’t promise” notes, lead details such as industry and location, short summaries of your last few calls with them, any rate you have on file for them, and any open invoices you have recorded against them, with number, amount, due date and status, and whether a balance is overdue. If a different client of yours comes up in the conversation, their record is added too, but without invoices or rate. That is how the suggestions on screen are about your actual relationship rather than a generic one. On a managed plan this reaches our server along with the transcript, as part of the call context described below.
In the extension, once it is released, stored calls are capped. A browser profile is not a disk, so the extension keeps at most 5 MB of finished calls and removes the oldest automatically once that is reached. The Mac app has no such limit: it writes call notes to a folder on your machine and nothing prunes them but you.
GoHighLevel, if you connect it. If you connect a GoHighLevel sub-account (Settings → GoHighLevel; the Mac app offers this on Pro), you do it with a Private Integration Token you create in GoHighLevel and the sub-account’s Location ID. The Mac app then reads that sub-account’s contacts, opportunities and invoices to build your client records. It needs only read access (the token should have the scopes contacts.readonly, opportunities.readonly and invoices.readonly), and the Mac app only ever sends read requests, so it writes nothing to GoHighLevel. Those requests go from your Mac to GoHighLevel under your own GoHighLevel account; we do not relay them. The token is stored encrypted with your Mac’s secure storage; the Location ID, which is an identifier and not a credential, is stored beside it in a plain file. Once synced, those records are used like any other client record in the app: during a call, client and contact names can be among the spelling hints sent to Deepgram, and on a managed plan the record for the client on the call goes through our server to Anthropic, as described below. In the Mac app, disconnecting removes the token, the Location ID and the copy of your GoHighLevel records (ghl-snapshot.json, and ghl-local.json if the app made one) from the app’s folder (Application Support/Pace Notes), and the Mac app does the same if GoHighLevel stops accepting the token (for example, because you revoked it). Versions before 0.1.9 leave that copy in the folder until you delete it. From 0.1.9, while your plan does not include GoHighLevel, the Mac app keeps the copy but does not use it. Call notes you have already saved keep what they said about each client until you delete them. Nothing is read if you do not connect it. The Chrome extension, which is not yet released, also tries to write each finished call’s notes as a note on the matching contact in your GoHighLevel account; it never creates a contact.
We do not sell or rent your data, we do not share it for advertising, and we do not use it to train any model. That is a promise about us. On a managed plan your call also reaches Deepgram and Anthropic, who handle it under their own terms, and what we have and have not agreed with each is set out under “If we supply the AI: the managed plan” below. The software contains no analytics, no telemetry, no tracking and no advertising identifiers, in either mode. On a managed plan your call data does go to the companies named on the subprocessor list, so that the service can run, and to nobody else on our initiative. Anything you connect yourself, such as GoHighLevel or Google Calendar, receives data on your instruction, not ours. A managed plan also records more than metering: the account, device and billing details, the record of each call and the knowledge history described under “What we keep” below. They exist to run and bill the service, and none of it is used to profile you, compare you with anyone else, or train anything.
If you bring your own keys
Call audio. When you start a call, Pace Notes captures the audio and streams it to Deepgram for transcription using your Deepgram API key. It is not stored by us and not sent anywhere else. The Mac app also sends Deepgram up to 50 short hints so it spells names correctly: the client name and company you typed in, client and contact names and aliases from your own records, and a short built-in list of tool names. The Chrome extension sends none.
Transcript text, your knowledge and your client records go to Anthropic using your Anthropic API key, and to nobody else. Both services process this under your own account with them, on their terms. None of it is ever sent to us.
What stays on your computer. Your knowledge files themselves, your client list, and the notes and transcript of every finished call are stored only on the machine you installed on, for as long as you keep them. We do not receive them, there is no account to sync them to, and nothing prunes them but you.
Your API keys never reach us. In the Mac app they are stored as plain text, not encrypted, in a file named .env in ~/Library/Application Support/Pace Notes. The app saves that file so that only your user account can read it. In the Chrome extension they are stored, also not encrypted, in chrome.storage.local, which is not copied to your Google account or to any other device you are signed in on. Neither app shows a saved key back to you in full: the Mac app says only whether a key is saved, and the extension shows the last four characters. To remove them, use “Remove both” on the extension’s setup page, or in the Mac app delete the two key lines from the .env file.
No server of ours is involved at all. Not at startup, not to check your licence, not ever. Your licence key is verified on your own machine using a signature check — nothing is transmitted, so we cannot see when you use it, how often, or on what.
The consequence is worth stating plainly: because there is no check-in, a licence on this plan cannot be revoked remotely, and we cannot tell whether a key is in use on one machine or several. That is a deliberate trade, and it is what lets this plan work with no account and no server.
The Mac app makes one background request the extension does not. On launch, and roughly every six hours while it is open, it asks GitHub whether a newer version has been released. That necessarily reveals your IP address and the version you are running to GitHub, which hosts our releases. It contains nothing about your calls, your clients, your knowledge, or your keys. If a newer version exists and no call is running, the app also downloads it from GitHub in the background, and installs it only when you choose to restart. We do not receive the request — GitHub does — and we do not get a list of who checked. You can turn it off in Settings → “Check for updates automatically”, and with it off, on your own keys, the app makes no network request to us or to GitHub at any point. Apart from that check, the app talks only to the services you have set up yourself: Anthropic and Deepgram during a call, on your keys, and anything you connect, such as GoHighLevel or Google Calendar.
If we supply the AI: the managed plan
On a managed plan you do not need API keys for your calls or for the notes written after them. We supply the transcription and the AI for those, on our accounts, and that changes this document more than anything else in it: on every call that runs on our service, your call audio and your transcripts pass through a server we run. Pre-call prep, on Pro, also runs through that server, as described below. Everything below applies to a managed plan. Which section describes you depends on your licence, not on whether you have keys saved. If you saved your own keys earlier (for the free calls, say), they do not switch a managed plan over to them: every call starts on our service, and everything below applies, whenever it can run there.
Your own keys are used for a call only when that call cannot start on our service, because it is unavailable or because your plan’s allowance for the month has been reached, including any extra-usage limit we have agreed with you. That call’s audio and transcript then go to Deepgram and Anthropic on your own keys, as described in the section above, and not through us. But your device has already contacted our server by then: at minimum a health check and, if our service was reachable, the knowledge check (with an upload if your copy changed) and the call-opening request that a managed call begins with, which are covered in the list below. The app tells you the first time this happens in a session, and does not repeat it for later calls in that session. A call that is already running when the allowance is reached stays on our service: transcription and the end-of-call notes carry on, and the suggestion cards pause. Only a bring-your-own-keys plan, or no licence at all, involves no contact with our server. The Mac app’s update check, described above, applies on a managed plan too.
Outside a call. Our service covers what runs during a call, the notes written after it, and, on Pro, pre-call prep. Pre-call prep goes through our server. When you press Prep, the Mac app usually looks the client up on the web, and for that it sends what Pace Notes holds about them: their name and contacts; their status and the summary and latest update in your notes on them; what you have done for them; open follow-ups; summaries and next steps from previous calls; lead details (status, industry, location, service and the reasons recorded); the subject line and an excerpt of any proposal or outreach email you saved; and, if your notes include a calendar file for today, the time, title, attendee and prep note of their entry in it. It also sends a company line: the company name you typed, or the client’s name if you typed only that, followed by the location on their lead record if there is one. It skips the lookup, and sends nothing, when a lookup for that client finished within the last day (one that failed or was cut off is tried again), or when your vault holds a note for them. Our server passes the request to Anthropic on our account, and Anthropic may run web searches to research the client. Pace Notes tells the model that the client details are background only and must never appear in a search phrase, and on your machine it strips email addresses, phone numbers and your saved contacts’ names (except a name that is part of the company line itself) from the company line first. The model writes the search phrases itself, so that is an instruction and a filter, not a guarantee; if a phrase looks like it carries private detail, Pace Notes marks it in the prep it saves, after the search has run. On a managed plan the ask box, when no call is running, answers only from the client records and notes on your computer, and does not contact our server or any AI model. The setup wizard’s first draft of your knowledge does not go through our server: it runs on the Anthropic key you have saved in the app, if you have saved one, under your own account with Anthropic, and without a saved key it falls back to its templates.
Genesis Web Digital is a processor of that data, and you are the controller of it. Our Data Processing Agreement is the contract that governs it, and the subprocessor list names every company that touches it because we handed it to them.
What we have, and have not, agreed with Deepgram and Anthropic. Anthropic’s commercial terms say it may not train its models on what we send it through the API. Deepgram’s published terms let it use submitted audio to improve its models, and its documentation puts requests in that programme unless the request opts out. Our server sends the opt-out on every request, in a setting a client cannot change. That is a setting we send, not a contract: we have not entered into a data processing agreement or Standard Contractual Clauses with Deepgram, so what Deepgram does with audio rests on that setting and on its own published terms. The subprocessor list has the detail.
What reaches our server. In the order it happens:
- Your licence key, a device label, and a random identifier your device makes up for itself, when you activate a device. The identifier is not derived from anything about your machine; we use it so that activating the same device again takes back its own slot instead of using your second one.
- Your knowledge files and proof points, on activation and whenever the copy on a device changes. They are stored encrypted, per licence. A call keeps a copy of what it started with, so a mid-call edit cannot change what that call was answering from.
- Call audio, both sides, continuously while a call runs, over an authenticated connection. Our server relays it to Deepgram on our account. The Mac app also sends up to 50 short name hints with it, described under “Call audio” above; the Chrome extension sends none.
- Transcript text, the client name and company, and the call context, continuously while a call runs: on every analysis pass, several times a minute, whether or not a card results, and again for the end-of-call write-up. Our server builds the prompt and calls Anthropic on our account.
- The text of a live web lookup, on Pro: the short search phrase Pace Notes sends when it looks something up during a call or when you type a question into the ask box during one (up to 500 characters). Email addresses, phone numbers and your saved contacts’ names are stripped from it on your machine first.
- A pre-call prep request, when you press Prep on Pro and the app looks the client up: the client details listed under “Outside a call” above, cut to 20,000 characters if they are longer, and the company line (our server refuses one longer than 500 characters). Our server passes it to Anthropic and returns the result to the app, which saves it in your notes on your machine. The request itself is not stored on our server; its usage figures are, as below.
- The opening of a long call, paraphrased, when a call is too long for its write-up to fit in one piece.
- In the Chrome extension only, once it is released: up to ten past calls’ notes and transcripts, but only when you use “Ask across your calls”. The Mac app has no such feature.
What we keep. On a managed plan, per licence:
- the email address the licence was issued to, and the licence’s plan, expiry and region;
- each device you activate: the name you gave it, a random identifier the app generates for itself, and when it last checked in;
- your subscription and billing state: the Stripe customer and subscription identifiers, plan, status and billing period, and, if we have agreed overage with you in writing, your overage settings and what we have billed;
- a record of each call: when it started and ended, which device ran it, and what it cost;
- usage rows: the operation, token counts, cost, minutes and time. That is how a plan’s included minutes are counted and how overage is billed, and they are an accounting record, so they outlive the account they came from;
- your knowledge, encrypted, with the earlier versions kept so an overwrite can be undone (the ten newest, plus up to ten more that were no more than 30 days old when we last trimmed; we trim whenever you save, list or restore), and a copy of your knowledge as it stood, kept with every call you run for as long as the licence exists;
- Stripe’s notifications to us about your subscription (a renewal, a cancellation, a chargeback): event, dispute and charge identifiers, status and dates;
- our logs. Our web server’s access log records your IP address, the time, the request line (the method and path, which carries call identifiers), the status and size of the response, and the user-agent and referrer headers. Our application’s own log lines carry identifiers (call and, in some events, licence), counts, costs, operation names and the reason for an error. Call content is not put in either, subject to the caveats under “What we do not write down” below. Logs are not part of an erasure, and we do not promise a fixed retention period for them: they roll off through the server’s own log rotation, and the system journal is capped by size, not by age.
A job that runs when our server starts and once a day cuts the licence id from any usage row older than 400 days. It does not touch the call record, so such a row can still reach the licence through the call it belongs to. Erasing a licence cuts both links for the usage rows that still carry the licence id (see “Removing it” below).
What we do not write down. Our software is written so that transcript text, knowledge content, card content, prompts, completions and client names do not go into its log lines or error reports, and request bodies are not logged. Call audio is streamed through our server’s memory to Deepgram and is not written to disk. Transcript text and knowledge also pass through memory on their way to Anthropic. That is not an absolute, so three caveats. Our web server can hold a request or response that is larger than a small buffer in a temporary file until the request ends: a long transcript sent for the write-up, or your knowledge when a device downloads it. If our server process itself crashes, the runtime prints its own error output to the system log, which we do not claim is free of content. And the logs listed above are the ordinary kind, kept outside any erasure. What we store on purpose is your knowledge, encrypted: the current copy, the earlier versions, and the copy each call starts from, because the software would otherwise have to re-upload it on every call.
Your device token, and where it lives. Activation gives your device a
token. On the Mac it is encrypted with the operating system’s secure storage, and
activation is refused outright if that storage is unavailable. In the Chrome
extension it is stored unencrypted, in chrome.storage.local, because a
browser extension has nothing equivalent to the Mac’s keychain. It is never put in
Chrome’s sync storage, so it is not copied to your Google account or to
your other machines. It is cleared when the licence changes, when you remove it, and when our
server refuses the device.
A managed licence can be revoked, and its devices counted. This is the opposite of the licence you get with your own keys, and it is worth being explicit about: because a managed device checks in with us, we can see that a licence is in use, we can tell how many devices are on it (a licence allows two), and we can stop one. A licence with your own keys does none of those things. Neither design is a secret; they are simply different, and which one applies depends on what you bought.
Removing it. Write to cole@genesisweb.org and we erase it by hand, within 30 days of the later of your request and the end of your billing, including settlement of any final overage invoice. We do not erase while a subscription is still billing, and erasure does not cancel it, so either we stop the subscription first or you cancel it first in Stripe’s customer portal, using the link in your purchase confirmation or, if you no longer have it, by asking for a sign-in link by email at billing.stripe.com with the email you bought with. A subscription cancelled at the end of its paid period stops billing then, and the 30 days run from that date if it is later than your request. We do not delete anything automatically when a subscription ends or a licence expires: until you ask, we keep it.
Erasing a managed licence deletes the knowledge we hold for it, every stored version of it, and every call’s copy of it; overwrites every device credential so none can authenticate again; and blanks the email address on the licence record and the names and identifiers of your devices. What remains is the accounting trail, and it is pseudonymised, not anonymous: the licence record (plan, dates and region, with no email); the subscription record, with its Stripe customer and subscription identifiers; a record of each call (when it ran, which device ran it and what it cost); the device records (their dates only); the usage and overage figures; the log of Stripe’s notifications about the subscription (event identifiers, types and outcomes, and the subscription identifier, with any error text cleared); and any chargeback record (Stripe’s dispute and charge identifiers, its status and the subscription identifier). The billing-period work-list rows we use to charge overage are deleted. The licence, subscription, call and device records stay linked to one another and to the licence’s identifier, which is a code derived from your licence key, not a name. The Stripe identifiers let us and Stripe tie the subscription record, and the notification and chargeback records that carry the same subscription identifier, back to you. Erasure cuts a usage row’s links to the licence and to the call record, and an overage figure’s links to the licence and to Stripe. The exception is a usage row that the 400-day job described above had already processed: erasure does not change it, and it still reaches the licence through its call record, to a licence record that no longer carries your email. We have not set a date for deleting the retained records. Stripe keeps its own records under its own policy, and erasing with us does not rewrite them. Our database host also keeps point-in-time history for seven days, so erased rows can persist in that history for up to a week; it is not individually rewritten. The logs described above are not rewritten either.
Buying a licence
The software itself has no sign-in. Buying does: that purchase goes through Stripe, which receives your email address and payment details and may send you its own receipt. Stripe does not issue your licence key: after you buy, we sign it by hand and email it, with the download link, to the address you bought with, usually within one business day. When a trial turns into Solo, or your key nears its expiry date, we send a new key the same way and you enter it in the app. The 7-day trial needs a card, which goes to Stripe, and it is a managed plan: it includes one call of up to 45 minutes on our service. We learn the email address of anyone who buys, because that is who the key was issued to. Nothing about the content of your calls or your clients is involved in the purchase, and the Pace Notes app itself never talks to Stripe. If we have agreed overage with you in writing on a managed plan, our server sends Stripe the minutes used past your allowance, in one or more line items per billing period, and the amount, so it can add them to your invoice. It sends no transcript, audio, knowledge or client name. Stripe keeps its own copy of those invoices, and erasing a licence with us does not rewrite them.
Without a licence, Pace Notes gives you three calls a month in each of the two — three in the Mac app and, once it is released, three in the Chrome extension. They keep separate counts because they keep separate storage, and neither knows the other exists. That count is kept on your own machine, is never reported anywhere, and is not tied to any identifier: for an unlicensed install we cannot tell how much you have used the software, or whether you have used it at all. A managed plan is different by necessity — see above.
Recording other people is your responsibility
Pace Notes records the other party on your call. Laws vary: some places require only your consent, and many — including Florida, California, nine other US states, and much of Europe — require the consent of everyone on the call.
Pace Notes will not start a call until you confirm you have told the other party. That confirmation is required every time and is recorded with a timestamp in that call's saved notes. It is a prompt, not legal advice, and it is not a substitute for actually telling them. Complying with the law where you and the other party are is your responsibility.
Removing your data
Removing the Chrome extension removes everything it stored. The Mac app keeps everything it stored — your keys, knowledge, call notes and transcripts, licence and tokens — in ~/Library/Application Support/Pace Notes, and moving the app to the Trash does not delete that folder. The “Open config folder” button in the app opens it; delete the folder yourself to remove everything. You can remove a single key or your licence at any time by deleting its line or file there. On a bring-your-own-keys plan the software sends us nothing, so that is all there is, apart from the email address you bought with (see “Buying a licence” above).
On a managed plan, removing the extension or deleting that folder clears what is on your machine, but not what we hold. Write to cole@genesisweb.org to have the rest erased. When we can do it, what it covers and what survives it are described under “Removing it” above; cancel the subscription first.
Terms of sale
What you are buying, what renews, and what happens when a licence expires is set out in the terms of sale.
This website
genesisweb.org, including this page, uses Google Analytics. It sets cookies in your browser and sends Google the pages you visit, your clicks on contact, email and phone links, form submissions, and standard browser, device and approximate-location details, so we can count visits and enquiries. The pages also load their typeface from Google Fonts, which tells Google your IP address. This is separate from the software: it is not in the Mac app or the Chrome extension, and it sees nothing from your calls, transcripts or knowledge. To opt out, block googletagmanager.com or use Google’s opt-out browser add-on.
Where your data is held
Pace Notes is sold to buyers in the United States only, and we offer no EU or UK region. On a managed plan, the records described above are held in the United States: our database is in Neon’s US East region (us-east-1), and our server runs in DigitalOcean’s New York data centre (nyc3). Call audio goes to Deepgram, and transcript text, your knowledge and your client records go to Anthropic. Both are US companies, but we do not choose where either of them processes a request, and we have not asked either to keep it in the United States. Anthropic may process requests outside the United States, and we do not claim otherwise; we have not agreed with Deepgram where it processes audio. The subprocessor list says what we know about each.
Your rights
You can ask us to tell you what personal data we hold about you, to correct it, to give you a copy, or to erase it, by writing to cole@genesisweb.org. We handle these by hand. We prepare a copy on request, within 30 days of your request, and we erase on the timing described under “Removing it” above. The copy is not a complete dump of everything we hold. It covers your licence, subscription and device records, a record of each call (times and charges; we store no call content), your usage records and your current knowledge. It leaves out the contents of earlier knowledge versions (we list their dates and sizes only), each call’s copy of your knowledge, the overage and billing-period records, the records of Stripe’s notifications and any chargeback, and our server logs. If you are in the EU, the UK or California you have these rights in law, and you may also complain to your data protection authority. The people on your calls are your data subjects, not ours: if one of them contacts us, we pass the request to you and help you answer it (see the Data Processing Agreement).
Contact
Questions about this policy: cole@genesisweb.org, Genesis Web Digital LLC, Rockledge, FL 32955.