She Said AI

Privacy notice

She Said AI at shesaidai.com and app.shesaidai.com is operated by Magus Verma. Privacy questions or access, correction and deletion requests: magusverma@gmail.com. Updated 17 September 2026.

What we use

Account email, name, password hash, workspace content and activity support sign-in, saved work and security. Google sign-in requests openid, email and profile; we store your name, email and stable Google account ID. It grants no Gmail or Calendar access.

Storage and services

Cloudflare serves the website and routes app traffic, processing network/request information. The app currently runs on the operator's laptop using Node and SQLite. Google processes Google sign-in. Essential cookies maintain sessions; browser storage keeps preferences and setup drafts. We add no advertising trackers.

Browser speech recognition may send audio to the browser's speech service; the app saves setup text. Browser dictation and provider voice conversations are separate features.

Provider voice conversations

Provider voice currently requires an enabled workspace; xAI is configured for the owner's workspace. Starting its microphone session sends your audio through our server to xAI, together with the selected agent instructions and relevant workspace knowledge. Replies and transcripts return to your browser. The app does not store audio recordings. Final conversation transcripts are saved in workspace conversation history; interim transcription updates are displayed without being saved as final messages. Operational usage and action receipts are also retained. Workspace export and content purge cover conversation content; separate retained records and backups are described below. Do not include data you are not authorised to share. Other voice providers require separate configuration; customer telephone calling is not activated.

Optional Google Calendar connection

Calendar access is separate from Google sign-in and requires a configured integration and your explicit consent. The current connector requests permission to view and edit calendar events to create events you approve. It does not import your calendar history, read Gmail or access Google Drive. We store an encrypted refresh token, granted permissions, target calendar, connection owner and connection timestamps. Approved event details go to Google; event identifiers and action receipts are saved in your workspace.

Calendar information is used to provide your requested integration and action history, not advertising, sale or general model training. Our use of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. Human access is limited to authorised support, security, legal obligations or your explicit permission. Disconnect removes the stored workspace token but does not revoke Google's grant, remove created events or cancel requests already in progress. You can separately remove access in your Google Account connections.

Retention and your controls

Workspace settings provide export and content purge. Purge removes conversations, execution payloads and contact details; it retains account/configuration, knowledge, audit and hashed safety records. Knowledge has separate deletion. Retention preferences need the maintenance process. Account records remain until separately removed; backups and provider records require separate handling.

Email for broader requests or complaints; we may verify account ownership. Clearing browser storage removes local drafts. Disconnecting Google does not delete workspace data.

Notice scope

This describes today's service, not compliance certification. India's MeitY publishes DPDP rules and commencement notices; applicable duties need review as the service changes.