Privacy Policy
NotebookMeeting Privacy Policy
This policy explains how the NotebookMeeting application handles personal data, including information obtained from Google APIs. NotebookMeeting is a personal application used by João Vytor Sobreira, not a service offered to the general public.
1. Who is responsible
The controller of the data processed by this application is João Vytor Sobreira, in Brazil. Contact: joaovytor123@icloud.com. This website: https://joaosobreira.io/.
2. What the application does
NotebookMeeting is a Windows program that:
- records the audio of remote meetings held on the owner's notebook (system sound and microphone) when the owner decides to capture the meeting;
- reads decision and status files from a folder in the owner's personal Google Drive;
- uploads the audio file to a folder in the same Drive;
- notifies the owner's personal assistants (including Grok Bot) so the audio can be transcribed;
- allows the transcript to be written back to the owner's Google Drive.
The application has no advertising, does not sell data, and is not distributed as a commercial product to third parties.
3. Data accessed from Google APIs, and why
To sign in to the Google account, the application uses installed-app OAuth 2.0 with a local redirect and PKCE. The requested scope is:
https://www.googleapis.com/auth/drive
This scope grants access to files in the authorized Google Drive account (read, create, update, and delete). It is used because the application must:
- read decision and status JSON files that another client creates in a folder in the owner's Drive (the “Notebook Meeting” folder); a scope limited only to files created by this application cannot reach those files;
- upload recordings to an existing folder created by the owner (the audio inbox folder), and write related metadata.
In practice, the application is designed to operate in those folders and not to change sharing permissions on the files it uploads: the file remains restricted, under the control of the owner's Google account. The technical scope is nevertheless broad (the authorized account's Drive), which is disclosed here.
Typical data obtained or written in Drive includes: the meeting audio file, file name and identifiers, the destination folder, technical metadata (for example a hash and a source identifier), and the decision, status, and heartbeat JSON files the application needs to work. The application does not use Drive to send messages, does not read account content for any other purpose, and does not publish the files.
The Google access token and refresh token stay only on the owner's computer, in the Windows Credential Manager (or, if a secret exceeds the size of one credential, in a local file encrypted with DPAPI). They are not embedded in the program and are not sent to this website.
4. Limited Use statement
NotebookMeeting'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, such data:
- is used only to provide and improve the user-facing features described in this policy (recording, uploading to Drive, and enabling the transcription requested by the owner);
- is not used for advertising, including personalized advertising;
- is not sold;
- is not transferred to third parties except to operate those features (the processors listed below), to comply with law, or at the owner's direction;
- is not used to train machine-learning models of the operator of this application;
- is read by a human only when the owner asks, when needed for security or to operate the service, or when required by law.
5. Other data we process
In addition to Google Drive data, the application processes:
- Meeting audio captured on the notebook (call sound and microphone). This may include the owner's voice and the voices of other people in the meeting. The owner is responsible for recording only when there is a legal basis to do so, including informing participants when the law or good faith requires it.
- Local configuration, such as Drive folder identifiers and the start-with-Windows preference, stored in the Windows profile, with no secrets in the configuration file.
- Credentials for the OAuth client, the Google token, and the notification (webhook) key, in the Windows Credential Manager.
- Technical logs on the owner's computer, containing identifiers, durations, end reasons, and error types, without the meeting title and without the contents of the audio or the transcript.
6. Where data is stored
- The owner's computer: temporary recordings, configuration, logs, and credentials, in the Windows profile.
- The authorized Google Drive account: uploaded audio, returned transcripts, and decision and status files. These files belong to the owner's Google account and follow Google's settings and terms.
- The owner's personal assistant computers: operational copies of the audio and transcript, used to transcribe and return the text to the owner.
- Modal: audio may be sent to Modal for transcription with Whisper on a GPU. Modal acts as a processor solely for that task.
If the owner later asks for notes or a summary based on the transcripts, that text may be processed by an AI provider chosen by the owner. If this is done with Anthropic, retention on the API in use may be up to 30 days, according to that provider's rules. That step is later than, and distinct from, the application's OAuth access to Google Drive.
7. Processors and sharing
NotebookMeeting does not sell personal data and does not share it with advertisers. Recipients are limited to:
- Google, for authentication and storage in the authorized Drive account;
- the owner's personal computers and assistants (including Grok Bot), to receive the notification, download the authorized audio, and return the transcript;
- Modal, for Whisper transcription on a GPU, when that path is used;
- AI providers later used, at the owner's request, to produce personal notes from an existing transcript;
- public authorities, if required by law.
Some of these processors may operate outside Brazil (for example in the United States). Processing takes place because the owner authorizes the application and requests the transcription service. This website is hosted on Cloudflare and serves only the public pages; it does not receive the audio, the Google token, or Drive content.
8. Retention
- Local recordings on the notebook are deleted 7 days after the notification to the personal assistants is confirmed. A recording that has not yet been uploaded to Drive is not deleted automatically.
- Local logs are kept for 30 days.
- Files in Google Drive remain until the owner (or anyone with access to the account) deletes them, or until the Google account's own retention applies.
- Operational copies on the assistant computers and processing on Modal exist to complete the requested transcription; they are not used for any other purpose of this application.
9. Deletion and revocation
The owner may, at any time:
- revoke NotebookMeeting's access to the Google account at https://myaccount.google.com/permissions. After revocation, the application can no longer read from or write to Drive until consent is given again;
- delete uploaded files and transcripts in Google Drive itself;
- delete the application's local folders on Windows (
%LOCALAPPDATA%\NotebookMeeting\and the installation folder) and remove the corresponding generic credentials from Credential Manager; - request deletion of any operational copies that still exist in the owner's systems by writing to the contact email below.
If a recording has already been notified to the personal assistants, automatic recall of that path may not be possible; in that case, a deletion request should be made through the contact below and by deleting the files in Drive.
10. Your rights
Under Brazil's Law No. 13,709/2018 (LGPD), you may request confirmation of processing, access, correction, anonymization, blocking or deletion, portability, information about sharing, information about the option not to consent and its consequences, and withdrawal of consent. To exercise these rights, write to joaovytor123@icloud.com.
The primary basis for access to the Google account is consent, given on the OAuth screen. Audio is processed to perform the service the owner requested by recording and transcribing the meeting. This application is not directed at children.
If you believe the processing violated the LGPD, you may also contact the Brazilian National Data Protection Authority (ANPD).
11. Security
The application communicates with Google over HTTPS. Secrets are not stored in the program code or on this website. The token remains on the owner's computer, protected by Windows mechanisms. No system is perfect: the owner should protect the Windows session and the Google account (preferably with two-step verification) and may use a dedicated Google account with access only to the necessary folders, to reduce the impact of an incident.
12. Contact and changes
Contact: joaovytor123@icloud.com.
If this policy changes in a material way, the effective date on this page will be updated. Continued use of the application after the new version is published, while consent remains valid, means the updated text has been made available. If a change requires new consent, that consent will be requested.