QuietSeat Privacy Policy
Last updated: 2026-10-25
QuietSeat is a meeting assistant operated by Panda Frank (MyAgentHubs), based in Japan ("we", "us"). This policy explains what data QuietSeat handles, why, who else processes it, how long it is kept, and how you can stop it or have it deleted.
- Website: https://quietseat.myagenthubs.com
- App: https://app.quietseat.myagenthubs.com
- Privacy questions and requests: privacy@myagenthubs.com
- General support: support@myagenthubs.com
1. What QuietSeat does
You sign in with your Google account and approve the permissions listed in section 4. If you turn on automatic listening, QuietSeat looks at the Google Calendar events that you own and that have a Google Meet link. For those meetings it adds the QuietSeat assistant as an attendee. The assistant is an ordinary Google account with the display name "QuietSeat Notetaker". It joins the Meet as a visible participant (the host can decline to admit it), turns the speech into a live transcript, produces a meeting summary about every 60 seconds, and writes the transcript and summary into a Google Doc in your own Google Drive.
Where speech recognition is not yet certain, the transcript marks the passage as "unconfirmed". Unconfirmed text is not presented as final.
QuietSeat does not require a browser extension, tab sharing, or uploading recordings.
2. Who can use it, and where
- QuietSeat is currently a free beta that requires an invitation code.
- It is offered to users in Asia-Pacific and the United States. It is not offered to users in the European Union or European Economic Area, the United Kingdom, or mainland China. Please do not use QuietSeat if you are in one of those places.
- You must be at least 18 years old. QuietSeat is not directed to children.
3. Data we handle
| Data | Where it comes from | Why we need it |
|---|---|---|
| Google account identifier and verified email address | Google sign-in (openid, email) | To identify your account, to check that it is allowed in the beta, and to show it to you |
| Calendar event details for events you own: title, start and end time, time zone, Google Meet link, attendee list | Google Calendar API (calendar.events.owned) | To find the Meet meetings the assistant should join and to add the assistant as an attendee |
| Meeting audio, as heard by the assistant | The Google Meet meeting it joined | To produce the transcript. Raw audio is not stored (section 5) |
| Transcript text and meeting summary (topic, decisions, action items, open questions) | Generated from the audio | To show you the content live and to write it into your Google Doc |
| Link to the Google Doc QuietSeat created | Google Drive / Docs API (drive.file) | To keep updating the same Doc and to let you open it |
| OAuth access and refresh tokens | Google OAuth | To call Google APIs on your behalf until you disconnect |
| Usage counters (minutes used this month, meeting count) | Generated by QuietSeat | To enforce the monthly limits in the Terms of Service |
| A session cookie | Set when you sign in | To keep you signed in. It is strictly necessary; we do not use advertising or tracking cookies |
Meeting titles and calendar descriptions are treated only as data. They are never treated as instructions.
4. Google permissions and how each is used
QuietSeat requests four scopes and no others:
openidandemail: identify the signed-in account.https://www.googleapis.com/auth/calendar.events.owned:- Read: events that you own, in a window from about 1 hour ago to 7 days ahead, to find those with a Google Meet link. We do not process meetings that are not yours.
- Write: when automatic listening is on, add the assistant account as an attendee of those events with
sendUpdates=none(no email is sent). When you turn it off, disconnect, or the meeting is cancelled before it starts, the assistant is removed in the same way. We change only the attendee list and no other field of the event.
https://www.googleapis.com/auth/drive.file: create Google Docs that QuietSeat itself creates (or that you select) and write the transcript and summary into them. This scope does not let QuietSeat read or change your other Drive files. QuietSeat does not change sharing settings.
5. Meeting audio
- We do not store raw meeting audio. Audio is used live while the meeting is in progress and is not written to disk.
- While the meeting is in progress, the audio is streamed to Alibaba Cloud Model Studio (Singapore) for speech recognition, which returns text.
- The assistant only receives what it hears as a participant in the meeting. It does not access your microphone, camera, screen or system sound.
6. Who else processes data (subprocessors)
| Subprocessor | Purpose | Location |
|---|---|---|
| Alibaba Cloud (Model Studio) | Speech-to-text of the meeting audio | Singapore |
| Google (Gemini API, paid tier) | Generating the meeting summary from transcript text (and the previous summary); Google sign-in, Calendar and Drive APIs | Determined by Google |
| VPS hosting provider: Alibaba Cloud (Virginia, United States) | Runs the QuietSeat service and stores its data | United States |
| Cloudflare | DNS, email forwarding for our contact addresses, and hosting of the static website | Global |
Only transcript text and the previous summary are sent to Gemini. Meeting titles and attendee lists are not. We use the paid tier of the Gemini API, under which Google states that submitted content is not used to improve its products. Besides the parties above, we do not share meeting content with anyone.
Our commitments:
- We do not sell user data.
- We do not use user data for advertising.
- We do not use user data to train general-purpose AI or machine-learning models, ours or anyone else's.
7. Where data is stored and for how long
- Data is stored on our server in the United States. Speech recognition happens in Singapore, and summaries are generated by Google's Gemini API. By using QuietSeat you understand that your data is processed in these places.
- OAuth tokens are encrypted at rest and kept until you disconnect.
- Transcript and summary copies on our server are deleted 7 days after the meeting ends. Meeting audio is not stored.
- The Google Doc belongs to you. Content written to your Doc is yours and stays in your Drive. We never share it or add anyone to it. We do not delete it when you disconnect.
- When you disconnect Google or delete your account, we immediately delete your tokens and your server-side data.
- Backups of our server are kept for at most 30 days on a rolling basis. Deleted data may therefore remain in backups for up to 30 days and is then overwritten.
8. Other participants in your meetings
The assistant is visible to other participants as a named attendee. Meeting audio can contain other people's voices and words; we process it only to produce the transcript and summary for the user who invited the assistant. QuietSeat shows a notice when you turn automatic listening on. You are responsible for telling the other participants and for obtaining any permission required by the laws of the place where the meeting is held and by your organization (see the Terms of Service).
Some organizations' Google Meet settings block external participants. In that case the assistant cannot join, and nothing is recorded.
9. Your choices and requests
- You can turn automatic listening off at any time.
- You can disconnect Google in the app. We then stop our work, ask Google to revoke the token, and immediately delete your tokens and server-side data. You can also remove QuietSeat's access in your Google Account settings (Security, then third-party access).
- You can ask for access to, correction of, or deletion of your personal data at privacy@myagenthubs.com. We complete deletion requests within 30 days.
- If you are in Japan, we handle personal information in line with the Act on the Protection of Personal Information. The operator's full name and address are provided promptly on request to privacy@myagenthubs.com.
10. Google API Services User Data Policy
QuietSeat'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 the features described in this policy.
11. Security
- OAuth tokens are encrypted at rest and are never sent to the web page. Server-side API keys are never exposed to the Meet page or the front end.
- Access to the app requires signing in with Google, and during the beta only invited accounts are accepted.
- Error messages do not expose tokens, raw vendor errors or file paths.
- No system is perfectly secure.
12. Changes to this policy
We may update this policy. We will change the "Last updated" date above. For material changes, we will notify users in the app or by email before the change takes effect.
13. Contact
Panda Frank (MyAgentHubs), Japan Privacy: privacy@myagenthubs.com Support: support@myagenthubs.com