Privacy Policy

What meeting insights send

Your selected insights provider processes different context for each operation. With a cloud provider, this context leaves your Mac. With the on-device provider, inference stays on your Mac.

• Automatic updates and Generate. The session title, bounded conversation contributions, speaker labels, current outcomes, meeting duration, and identifiers for new contributions, plus bounded context from the selected calendar event, included reference excerpts, and a bounded excerpt of your personal notes, including preparation questions. Automatic updates can send this context while enabled. Generate also works with automatic insights off once the meeting has conversation content.
• Refined notes. The session title, whether a title should be generated, accepted visible outcomes with owner names, dates and status, included reference excerpts, and a bounded excerpt of your personal notes and preparation questions. This operation does not independently add the full transcript or calendar event snapshot.
• Ask. Your question, the session title, bounded selected conversation passages with speaker labels, included reference excerpts, and up to three previous question-and-answer pairs. Ask does not independently add the full calendar event snapshot or personal-notes field. Codex and Claude Code can also use retained session context that contains personal notes from earlier insight requests.

Titles, speaker labels, outcomes, questions, personal notes, and references may contain calendar-derived or other personal information. Personal notes and preparation questions guide the focus of insights and refined notes; when you select a cloud insights provider, those requests send the note excerpt to that provider. Long notes use an excerpt marked as partial, while the full note stays saved on your Mac. Reference excerpts come only from references marked for inclusion; that reference control does not exclude the personal-notes field.

Stenox explains provider processing when you choose an insights provider; it does not present a new consent dialog for every request. You can change the provider or turn automatic insights off. Switching to on-device processing affects future requests and does not recall earlier transfers or erase provider-held data.

Google Calendar: data access and use

Connect a calendar only if you want to browse events, select a meeting, and use its agenda and participant context. Stenox offers your primary Google calendar and additional calendar IDs you enter; it does not discover or list all calendars in your account. Access is read-only: Stenox does not create, edit, or delete events and does not request access to your mail or contacts. You can use manual meetings without connecting a calendar.

The current Google connection requests only the events permission, https://www.googleapis.com/auth/calendar.events.readonly. It does not request Google profile, email, or calendar-list permissions. Sign-in and consent occur with Google. Earlier development grants may have included broader permissions; manage those grants separately in your Google account. Earlier Outlook test connections used Microsoft basic identity, continued authorized access (offline_access), profile (User.Read), and calendar (Calendars.Read) permissions; a new Outlook connection is not currently offered.

Stenox creates a local identifier for the Google connection without retrieving the account's profile name or email. It reads calendar identifiers and titles and selected event fields: identifiers, title, agenda, dates, times, timezone, location, organizer and invitee names and emails, roles or RSVP status, meeting/event links, recurrence identifiers, and attachment metadata. Organizer and invitee details come from event data, not a Google profile lookup. These records power the event picker, meeting title and agenda, participant choices, and meeting context.

Stenox retrieves events within the browsing date window and explicitly requests the fields used by the integration. Attachment metadata can include names, file types, identifiers, and links; this connection does not download attachment contents or request Drive access. The calendar context sent to an insights provider is a smaller, bounded selection described below.

Google data: sharing, transfers, and recipients

The calendar integration connects directly from your Mac to Google's identity, authorization, token, and Calendar API services. Google receives the sign-in, token, and API requests needed to provide that connection and returns data to your Mac. GKI Software Inc. does not operate a calendar proxy or cloud sync service and does not routinely receive your Google calendar records or OAuth tokens.

• AI and model providers. Your selected cloud insights provider—OpenAI Codex, Anthropic Claude Code, or Google Antigravity—can receive Google Calendar content and derived information through the operation-specific context described above. Automatic insights can send updates without a separate action for each request. On-device insights process this context locally. Model download services distribute model files; they do not receive the calendar content processed by local inference.
• Separate speech processing. If you select cloud meeting transcription, Deepgram, AssemblyAI, or Google Gemini receives the separately captured audio. The calendar snapshot is not included in the speech request. Audio can contain personal information spoken during the meeting, including details someone reads aloud. The provider retention and training terms below apply to that audio.
• Website and payment services. The calendar integration does not send Google calendar payloads or OAuth tokens to our website hosting/analytics services, Cloudflare and PostHog, or our payment provider, Polar. Their separate website and purchase processing is described below.
• Exports, copies, and backups you choose. Meeting exports, copied text, and backups can contain calendar details or information derived from them. Files, apps, storage/backup services, and people you choose as destinations receive the information you put there. Stenox does not automatically publish those records to a shared calendar service.
• Support you request. If you voluntarily send specific Google-related information to support, GKI Software Inc. and the email-delivery, mailbox-hosting, or support-service providers handling that request receive what you include. We use it to address your request, and human access to that specific information is limited to your consent and purposes permitted by Google's Limited Use requirements. Do not send passwords, OAuth tokens, or unrelated calendar records.
• Security or legal disclosures. If we hold information you supplied, we may disclose only what is necessary to recipients assisting with a security incident or abuse investigation, or to authorities where applicable law requires it, and only as permitted by Google's user data policies. This does not give us remote access to calendar records stored only on your Mac.

For incremental insights, selected Google events and previously saved Outlook events can contribute the event title (up to 500 characters), agenda (up to 6,000 characters), scheduled start/end and timezone, organizer name (up to 120 characters), and up to 100 invited participant names (up to 120 characters each). Dedicated email-address, join-link, event-URL, location, and attachment-link fields are excluded from this calendar context. Freeform agenda, names, and reference text can still contain personal information, including links or email addresses. These limits do not redact personal information from the text.

Google data: security and protection mechanisms

• Encrypted external transport. Stenox uses HTTPS with TLS for requests to Google's identity, OAuth authorization/token, and Calendar API services, including token refresh. This protects those requests in transit; it is not a claim of end-to-end encryption for all app data.
• Google-hosted sign-in. Authorization takes place in your browser with Google. Stenox uses the OAuth authorization-code flow with PKCE and state validation to protect the sign-in exchange, and a short-lived callback on your Mac to finish it. Stenox does not receive your Google account password.
• Keychain credentials. Access and refresh authorization state is stored in app- and provider-scoped macOS Keychain items with application access controls and access limited to when the Keychain is unlocked. If Keychain storage is denied or unavailable, the connection fails instead of saving tokens to a plaintext file.
• Limited access and processing. Read-only event permission, calendars you select, date-bounded retrieval, and explicit field selection limit calendar access. Insight context has separate size and field limits. These controls do not prevent the selected cloud insights provider from receiving included Google-derived context and do not guarantee removal of personal information from freeform text.
• Local storage limits. Saved meeting snapshots are stored in a local SQLite database; account/calendar choices are stored in app preferences. Stenox does not add database or file encryption to those records or to exported files. They rely on macOS account and file access controls. Device lock, FileVault disk encryption, and protected backups are operating-system choices you control; Stenox does not enable or guarantee them. Anyone able to access those files through your account, exports, or backups may be able to read them.

Google data: retention, disconnecting, and deletion

Browsed events are held in memory. Account and calendar selection metadata persist in local app preferences, and OAuth authorization state persists in Keychain. Starting a meeting with an event selected saves a snapshot with that meeting in the local database; it remains with the saved meeting until you delete it.

Disconnecting Google in Stenox removes the local connection, tokens, account/calendar choices, and browsing state. It does not revoke the permission grant at Google, delete snapshots already saved in meetings, or sign you out of your browser. Revoke Stenox access separately in your Google account settings and delete saved meetings separately in Stenox. Disconnecting, clearing an event, or deleting a local meeting cannot recall content already sent to a cloud insights provider. Provider-held records, exports, backups, and shared copies must be managed at their destinations.

If you sent calendar information to GKI Software Inc. for support, contact privacy@stenox.app to request access, correction, or deletion of information we hold. We retain support information as needed to resolve requests and meet applicable legal obligations; this does not give us the ability to delete files held only on your Mac or at your chosen destinations.

Google API data and Limited Use

We use Google API data for the calendar picker and meeting features you choose. GKI Software Inc. does not sell it, use it for advertising, or use it to train or fine-tune AI models. On-device inference uses an existing model to produce insights; it does not train that model. Cloud-provider retention and model-improvement practices are separate and depend on the service and account, as described below.

Stenox can send included Google-derived context to your selected cloud insights provider. A session title, speaker label, accepted outcome, or reference can retain Google-derived information after the selected event is cleared. Refined notes and Ask can therefore include derived information even without a full event snapshot. Selecting on-device insights changes future processing; it does not erase those saved records or earlier transfers.

Stenox's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data policy. Provider account settings do not authorize uses prohibited by those requirements.

Website downloads, optional email, and support

When you start a website download, we record a random download reference, app version, button location, tier, time, and approved advertising campaign tags in a separate Cloudflare database. Campaign tags identify the advertising source, medium, campaign, and creative. We use them for attribution in this browser tab for up to 24 hours so navigation does not lose attribution. Expired stored tags are removed the next time attribution is read, or when the tab closes. Unknown campaign tags are discarded. We also record when the server begins serving the requested file; that does not confirm a completed transfer. These records measure download starts, not completed downloads or installations. Closing the email window continues the download without requiring an email.

Providing your email and clicking Download gives the team permission to send occasional product updates and check-ins, as explained beside the button. Email is optional, and no account is created. We store your submitted email with the download record, permission date, and the version of the wording you saw. Earlier choices and opt-outs remain unchanged. No spam. You can unsubscribe anytime by contacting support@stenox.app, or ask us to remove your email from these records. We keep these records until they are no longer needed for download analysis, permitted communications, or handling your requests.

Your email stays out of our custom PostHog event, page URLs, and application request logs. The email form is excluded from automatic interaction capture and session replay. Access to the Cloudflare download records is limited to authorized operators; there is no public email list or lookup.

The website uses Cloudflare for hosting and PostHog for product analytics. They may process page URLs, browser/device information, network information, approximate location, interactions, and technical errors. Our custom download event records app version, a random download reference, button location, tier, and the same approved campaign tags; it does not include recordings, transcripts, calendar events, API keys, or OAuth tokens.

Optional app crash reporting is controlled separately in app settings. Support and privacy messages contain the information you choose to send us. Avoid including passwords, tokens, or unrelated meeting/calendar content. We retain support and purchase information as needed to handle requests, maintain records, and meet legal obligations; provider records follow their applicable retention rules. Contact us for access, correction, or deletion requests involving information we hold.