Legal
Privacy Policy
In short
- Upshot is a desktop application that runs on your own Windows computer. Your recordings, transcripts and summaries are stored there.
- AM Consulting, which makes Upshot, never receives your recordings, transcripts, summaries or Google data. Upshot sends us only update checks, crash reports if you agree to them, and feedback you choose to send (section 6).
- Audio is transcribed on your computer and is never uploaded.
- To write summaries and answer your questions, Upshot sends the text it keeps (transcripts, summaries, notes, action items and calendar details) to the AI provider you choose. If you choose a local model, nothing leaves your computer.
- If you connect Google Calendar, Upshot reads your events, on your computer, to notice and name your meetings, and sends a meeting's invitation to the AI provider you choose along with its transcript. An AI app you connect can read your calendar details when you ask it to; Upshot shares calendar data with no one else, and never with AM Consulting.
- If you connect an AI app of your own to Upshot, such as Claude Desktop, Codex or Open WebUI, that app can read your meetings and have Upshot transcribe audio and video files on your computer, when you ask it to, and sends what it reads to its own AI provider. You can turn each of these off in Upshot's settings, and see what it asked for in the app.
1. Who we are
Upshot is made by AM Consulting (“AM Consulting”, “we”, “us”), based in Israel. This policy explains how the Upshot desktop application (“Upshot” or “the app”) and this website handle information. You can reach us at upshot@amconsultingai.com.
2. How Upshot works
Upshot records your meetings on your own computer, transcribes them there, and writes a summary. It runs on your own computer and has no account system: you do not sign up with us. Where the transcript goes next is your choice, described in section 5.
The app does not send usage statistics or analytics to us or anyone else. What it does send us, and only then, is described in section 6: checks for updates, crash reports if you agree to them, and feedback you choose to send.
3. Information Upshot processes
All of the following is created and kept on your computer, in the data folder you choose and in Upshot's own folder (section 7):
- Audio recordings of your microphone and of the sound your computer plays during a meeting.
- Transcripts, produced on your computer by a speech-recognition model.
- Summaries, written by the AI provider you choose (see section 5).
- Meeting details such as the time, duration and title, and, if you connect Google Calendar, the event details described in section 4.
- Settings, including your choice of devices and providers. API keys, passwords and sign-in tokens you enter are stored in Windows Credential Manager, not in plain files.
- Meeting detection: to notice that a meeting has started, Upshot checks on your computer which application is using the microphone, the window title and whether the camera is on. This information stays on your computer.
- Notifications: Upshot's notifications, which can show a meeting's title, can stay in Windows' notification centre until you clear them or Windows removes them.
4. Google user data
Upshot can optionally connect to your Google Calendar. This section describes exactly what happens if you do. If you do not connect a Google account, Upshot accesses no Google user data.
4.1 Data we access
Upshot requests one permission (OAuth scope):
https://www.googleapis.com/auth/calendar.events.readonly: read-only access to the events in your Google Calendar.
With it, Upshot reads, for each event: the title, start and end time, the organizer and attendees (names, email addresses, whether they are optional and how they replied), the description, the location, any video-conference link, and the names and links of files attached to the event. Upshot cannot create, change or delete anything in your calendar, and it does not access your email, contacts, files or any other Google data.
4.2 How we use it
Upshot uses your calendar data only to provide these features to you:
- to know when your meetings are scheduled, so it can get ready to record them;
- to give each recorded meeting its title and time;
- to show who was invited, alongside the meeting, in your timeline;
- to send the meeting's calendar details to the AI provider you choose, so it can write the meeting's summary and answer your questions about it; and
- to let an AI app you connect to Upshot (section 5) read your meetings' calendar details and your calendar's events, when you ask it to (section 4.4).
Calendar data is not used for any other purpose.
4.3 How we store and protect it
Calendar data is fetched directly from Google to your computer. The sign-in token Google issues is stored in Windows Credential Manager. Event details are stored with the matching meeting in Upshot's database, in Upshot's own folder on your computer (section 7). AM Consulting never receives your calendar data or your token.
4.4 How we share it
Upshot sends a meeting's calendar details (the title, times, organizer, the names of the people invited, whether they are optional and whether they declined, the description, the location, and the names and links of attached files) to the AI provider you choose, directly from your computer, so that it can write the meeting's summary and answer your questions about it. You can turn this off in Settings, and if you choose a local model nothing is sent. Email addresses are never sent. If you connect an AI app of your own to Upshot (section 5), that app can read the calendar details kept with your meetings and the events in your calendar (titles, times and the names of the people invited) when you ask it to, and sends what it reads to its own AI provider; you can turn this off in Settings, under AI apps. Apart from these, Upshot does not transfer or disclose your Google calendar data to AM Consulting or to any other third party. It is not sold, and it is not used for advertising.
4.5 Retention and deletion
Event details stay with the meeting on your computer until you delete that meeting in Upshot, and in the backup copies of Upshot's database for a while after (section 7). You can disconnect Google Calendar at any time in Upshot's settings, which deletes the stored token; Upshot then stops reading your calendar. You can also revoke Upshot's access in your Google Account at myaccount.google.com/permissions. Uninstalling Upshot and deleting its data folder and its own folder (section 7) removes everything it stored, except the API keys, passwords and sign-in tokens it keeps in Windows Credential Manager, which you can remove there; disconnecting Google Calendar before you uninstall deletes the Google sign-in token.
4.6 Limited Use
Upshot'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.
In particular:
- We use Google user data only to provide and improve the user-facing features described above.
- We do not transfer Google user data to others, except as needed to provide those features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to you. The only such transfers today are the ones described in section 4.4: calendar details sent to the AI provider you choose, to write your summaries and answer your questions, and calendar details read by an AI app you connect to Upshot yourself, at your request.
- We do not use or transfer Google user data to serve advertisements, including retargeting, personalized or interest-based advertising.
- We do not sell Google user data.
- No person at AM Consulting reads your Google user data. We would only do so with your explicit consent (for example, if you send it to us for support), for security purposes such as investigating abuse, to comply with applicable law, or where it has been aggregated and anonymized for internal operations.
- We do not use Google user data to develop, improve or train generalized or non-personalized artificial-intelligence or machine-learning models.
5. Services you choose to connect
Some features work by connecting, from your computer, to a service you choose. When you use one, that service receives the data described below directly from your computer, under your own account, and handles it according to its own terms and privacy policy. AM Consulting does not receive this data.
- AI providers. To write summaries and answer your questions, Upshot sends the provider you select any of the text it keeps: meeting transcripts, summaries, notes, action items, calendar details and your instructions. The providers are: Anthropic (Claude, through the API or through Claude Code on your own subscription), OpenAI (through the API or through Codex on your own subscription) or Google (Gemini, through the API or through Antigravity on your own subscription). If you select Ollama, the summary is written by a model running on your computer and nothing is sent. Audio is never sent to these providers. If you use Antigravity on your own subscription, or ask Upshot's assistant questions through Claude Code, that program also keeps what Upshot sends it, and its answers, in its own history on your computer, under its own terms; deleting Upshot's folders does not remove that history. Upshot runs Codex, and Claude Code when writing summaries, with their option not to save the session, so those runs are not kept in that program's history on your computer; this does not change what the provider keeps on its servers.
- AI apps you connect. You can connect an AI app of your own to Upshot, such as Claude Desktop, Claude Code, Codex, Antigravity, Cursor or Open WebUI. That app can then read, when you ask it to, the text Upshot keeps: meeting transcripts, summaries, action items, the calendar details kept with your meetings and the events in your calendar. It sends what it reads to its own AI provider, under your account with that app, unless it runs a model on your computer. Upshot lists what the app asks for, under AI apps, and you can turn this off in Settings. Apps connect with a key that Upshot keeps on your computer.
- Transcribing files for other programs. A connected AI app, or another program on your computer that uses Upshot's access key, can ask Upshot to transcribe an audio or video file on your computer. The file is transcribed on your computer and never leaves it; if the program sends Upshot a copy of the file, Upshot deletes that copy once the transcript is ready, unless you set its configuration to keep it; if the transcription fails or is cancelled, the copy is kept with that transcription until you delete it or until a period you set in its configuration passes. Upshot keeps the transcript in your data folder, where it appears on the Transcriptions page until you delete it or until a period you set in its configuration passes (section 7), and returns the text to the program that asked. That program handles the text under its own terms; an AI app may send it to its AI provider, as with anything in a chat. You can turn this off in Settings ("Let other apps transcribe files").
- Email. If you set up email delivery, Upshot sends summaries through the email server and account you configure.
- Model downloads. On first use, Upshot downloads speech-recognition models from the sites that publish them, and, if you enable speaker separation, its models the same way. These downloads send no meeting data; like any web request, they reveal your IP address to the host.
- Terms of Service updates. This one is not a service you choose: about once a day, Upshot asks this website whether the Terms of Service have changed, and downloads the new version if they have, so it can show it to you. The request sends no meeting data, account details or identifier of yours; like any web request, it reveals your IP address and the app's version to the host. Which version of the Terms you accepted, and when, is recorded on your computer only.
6. What Upshot sends to AM Consulting
Upshot has no account system and does not send us your recordings, transcripts, summaries, meeting titles, calendar data or Google data. It sends us only the following, through service providers that act for us.
- Update checks. Every few hours, Upshot asks this website whether a newer version of the app is available. If one is, it downloads the installer from the service that hosts our releases, checks that it is ours, and installs it when you are not recording and no meeting is about to start (you can turn automatic installation off in Settings). The request sends no meeting data, account details or identifier of yours; like any web request, it reveals your IP address and the app's version to the services that host our website and releases. To release new versions gradually, Upshot picks a random number once and keeps it on your computer; it is never sent.
- Crash reports, only if you agree. Upshot asks once, during setup, whether to send crash reports, and you can change your answer in Settings, Privacy, where you can also see exactly what was last sent. Nothing is sent until you say yes. If you have not agreed and a meeting fails because of an error Upshot does not recognise, Upshot may ask whether to send a report on that one error. It shows you exactly what would be sent, and sends it only if you choose Send report; your answer in Settings does not change. A report says what went wrong in Upshot's code (the type of error, and the names of the parts of the program involved, with line numbers), the app's version, the kind of computer (Windows version, an approximate amount of memory, the interface language), and a random number that lets us count how many installations a problem affects; that number is not linked to you or to anything else. If the error happened while an AI provider was working on a meeting, the report also says which provider and model were used, the version of its program, the error message that program gave about itself (such as a failed sign-in), at which step and on which try the error happened, the meeting's language, and its length in broad bands (such as "under 30 minutes"). A report never contains your recordings, transcripts, summaries, meeting titles, the names or email addresses of anyone, your calendar, file names or folder paths, your account details, or what an AI provider wrote. Upshot builds each report from a fixed list of these items and removes anything that looks like your content before it is sent.
- Feedback you choose to send. If you send feedback from Upshot, we receive what you write and, only if you add them: your email address (so we can reply), technical details (the app's version, the kind of computer, and the types of recent errors), and a screenshot of Upshot's window, which you see before it is sent and which may show meeting content. If you rate a summary, we receive your rating, your comment, which AI provider wrote the summary, and the summary itself only if you choose to include it. Feedback is anonymous unless you add your email address.
Crash reports and feedback are received by an error-reporting service that processes them for us and on our instructions. Like any web request, sending them reveals your IP address to it; we have set it not to store IP addresses and not to record the location they suggest.
Crash reports and feedback you choose to send may be stored and processed in any country where we or our service providers operate, including the United States. We choose where based on convenience and may change it without notice. Where the law requires it, these transfers are covered by appropriate safeguards.
We keep crash reports only as long as we need them to find and fix problems, and feedback as long as we need it to act on it and to reply. To have feedback you sent deleted, write to us with its reference (it looks like FB-3F9A2C).
7. Storage, retention and deletion
Everything Upshot creates is stored on your computer: recordings, transcripts and summaries in your data folder, and its database, which also holds transcripts, summaries and meeting details, in Upshot's own folder (%LOCALAPPDATA%\upshot), together with backup copies of that database, which it makes about once a day and before each update. API keys, passwords and sign-in tokens are kept in Windows Credential Manager (section 8), and deleting those folders does not remove them; you can remove them in Windows Credential Manager. Apart from the copies of files that other programs send it to transcribe (section 5), the oldest entries of the record of what AI apps asked for, which keeps only recent ones, and the oldest backup copies of its database, of which it keeps the newest seven, Upshot deletes nothing on its own: recordings, transcripts and summaries are kept until you delete them. You can delete any meeting in the app at any time, set periods in Upshot's configuration after which recordings, whole meetings with their transcripts and summaries, transcripts of files and the record of what AI apps asked for are deleted automatically, or delete the data folder and Upshot's own folder entirely. Whatever is deleted from Upshot's database, by you or by a period you set, including a meeting's transcript, summary and calendar details, remains in the backup copies until seven newer ones have replaced them.
8. Security
Upshot's interface runs only on your own computer (at 127.0.0.1) and requires a per-installation key before it shows anything. API keys, passwords and sign-in tokens are kept in Windows Credential Manager. Recordings and transcripts are regular files in your data folder, so they are protected by your computer's own security; we recommend turning on full-disk encryption such as BitLocker.
9. Your choices and rights
Because your data is on your computer, you control it directly: you can open, copy and delete it at any time, disconnect any connected service, and revoke Google access as described in section 4.5. Apart from crash reports and feedback (section 6), we do not hold personal data about Upshot users, so there is normally nothing for us to access, correct or delete on your behalf. You can stop crash reports at any time in Settings, Privacy. If you contact us, we use your message and email address only to reply, and you can ask us to delete them. Depending on where you live, you may have rights under data-protection laws such as the Israeli Privacy Protection Law or the GDPR; to exercise them, contact us.
10. Recording other people
Recordings include the voices of the other people in your meetings. The laws on recording conversations differ between countries and states, and some require everyone's consent. You are responsible for informing participants and obtaining any consent the law requires. See our Terms of Service.
11. Children
Upshot is not directed at children under 16, and we do not knowingly collect personal data from them.
12. This website
This website itself sets no cookies and uses no analytics. It remembers your language choice in your browser only. It is hosted by a website-hosting service and loads fonts and style files from content-delivery services; like any website host, these services receive your IP address and browser details when you visit, under their own privacy policies. The product video is not loaded until you press play. Pressing play loads it from YouTube's privacy-enhanced mode (youtube-nocookie.com), operated by Google, which then receives your IP address and browser details and may store cookies or similar data on your device, under Google's privacy policy. If JavaScript is off, the video opens on youtube.com instead.
13. Changes to this policy
If we change this policy, we will publish the new version on this page. If a change materially affects how Upshot handles your data, and in particular Google user data, we will describe it in the app before it takes effect.
14. Contact us
AM Consulting
Email: upshot@amconsultingai.com
Website: www.amconsultingai.com