Last Updated: September 23, 2026
This Privacy Policy describes how Parnassah AI LLC, operating as Parnassah.ai (“Company”, “we”, “us”, or “our”), collects, uses, and protects your information.
We use data to provide the features you request, generate AI responses, maintain security, and improve service reliability, subject to the specific connected-data restrictions below. Optional integrations require the relevant authorization.
Your data may be processed by AI systems and third-party providers to generate responses, analyze documents, and process audio.
Financial data is processed solely to provide organization and insights. We do not provide financial advice.
When you enable Meeting Secretary, we process meeting audio, provider participant identifiers, transcripts, summaries, decisions, and action items to provide live guidance and meeting follow-through. Depending on how you connect, Twilio, Zoom, Supabase, OpenAI, and other subprocessors may process the data needed to provide the feature.
Before capture, the organizer must separately confirm that every participant received clear notice of recording, transcription, and AI analysis; that every participant affirmatively consented; and that the feature is not prohibited in any applicable jurisdiction. The Service records the checklist version and confirmation times as consent evidence. Supported phone flows also play an audible notice, but that notice does not replace affirmative participant consent.
Reusable voice identity is optional and separate from recording consent. The current self-enrollment flow may create a biometric voice signature only for the signed-in user's own voice. It blocks enrollment of another participant unless a direct, documented subject-consent flow is made available. The signed-in user may withdraw consent and delete the sample and signature independently.
We do not sell your data. We may share data with service providers or when required by law.
Meeting retention is configurable. Raw recordings default to deletion after 30 days; you may choose 1, 7, 30, 90, or 365 days, or retain them until deletion. Transcripts may be retained for 7, 30, 90, or 365 days, or until deletion. Voice samples and signatures are retained only after separate opt-in and can be deleted independently.
Deletion jobs remove referenced storage objects and meeting records and preserve a limited audit record showing that deletion occurred. We may retain limited security, billing, legal, or deletion-audit records when reasonably necessary or legally required; those records do not contain the deleted meeting recording or transcript.
We implement reasonable safeguards but cannot guarantee absolute security.
The Service is not intended for children under 13.
Users may delete an individual meeting, its recording, its transcript and generated meeting data, or its voice-identity data from inside Meeting Secretary. Users may also request deletion of their account and associated data from inside the app.
To delete your account, sign in to Parnassah.ai, go to Profile, scroll to Delete account, type DELETE to confirm, and select Delete my account.
When an account is deleted, we delete the user’s account, chats, files, memory, images, profile data, and other associated app data. Limited billing, transaction, audit, security, or legal records may be retained only where required for legal, tax, fraud prevention, dispute resolution, security, or compliance purposes.
Users who cannot access their account may request deletion by contacting [email protected] from the email address associated with their account.
We may update this policy and will provide notice of material changes as required by applicable law.
Connecting Gmail, Outlook, or another supported account is optional. We receive the account identifiers, granted permissions, and authorization tokens needed to maintain the connection. Personal email features access message headers, recipients, subjects, snippets, and message bodies to search, read, summarize, prepare, and send the messages you request. OAuth authorization permits access; it does not itself approve sending an email. The personal assistant requires approval of the prepared send action.
Relevant email content and your instructions may be processed by AI providers to fulfill a request; a phone response also passes through our voice and telephone providers. Authorized sends disclose the approved message to its recipients and their email providers. We store encrypted connection credentials and task payloads/results, together with account labels, permission records, task summaries, approval evidence, status, and diagnostics. Task summaries can include message content; encryption of credentials does not mean that every operational field has separate application-level encryption.
You can disconnect personal email on the Phone assistant page and revoke access in Google or Microsoft account settings. Disconnecting stops future use of that connection; it does not recall messages already sent or automatically erase prior task history. Account deletion and privacy requests are described above. Organization integrations have separate workspace permissions and may access authorized files, calendars, tasks, and records for the features enabled by that organization.
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace user data policy. These restrictions also apply to derived data and take precedence over broader language about service improvement in this policy.
Google data is used for the user-facing features you authorize. It is not sold, used for advertising or credit decisions, or used to train general-purpose AI models. Transfers are limited to providing those features with consent, security, legal obligations, or an eligible business transfer with prior express consent. Human access is limited to your documented permission for specific data, necessary security or legal purposes, or legally permitted aggregated, anonymized internal operations. These restrictions apply to our personnel and service providers.
The phone assistant collects your enrolled number, verification status, a protected PIN hash, call and stream identifiers, timestamps, task instructions, approval events, and usage/cost records. Twilio processes calls and verification codes; OpenAI processes live conversational audio and relevant task context. Speech may be transcribed to understand and execute requests. Separately, browser dictation may use your browser or platform’s speech-recognition service; other voice or media-upload features send audio to server transcription providers according to the feature you use. The current phone pilot does not save a complete call recording or full transcript in its own call-history feature; task records may retain instructions, email content, summaries, and results. Providers may retain information under their applicable service terms.
Phone enrollment does not enroll a biometric voice identity. That is a separate Meeting Secretary feature with separate consent. Disable phone access from the Phone assistant page if your number is lost, reassigned, or no longer under your control. Disabling phone access does not disconnect email accounts or cancel the subscription. Do not include another person in a call without informing them of the AI and audio processing and obtaining any required consent.
Browser tasks use a hosted browser, currently Browserbase. The browser and websites visited receive the requests, form submissions, and account information necessary for the task. Page text, links, observations, and relevant task context can be sent to the selected AI provider and separate safety/review providers. We retain task history, action and approval records, results, and, where available, masked and reviewed preview snapshots. Masking reduces exposure but cannot guarantee that every sensitive item on a page is detected.
Secure sign-in fields send credentials to the intended website through the hosted browser. The dedicated input flow uses encrypted, one-use input and erases it after consumption or cleanup. Optional saved website connections store encrypted cookies rather than reusable passwords and expire after 30 days. Disconnecting a saved connection removes its reuse by the Service; use the website’s own account controls to revoke that website’s sessions. Our browser configuration disables hosted session recording and logs, but this does not promise zero retention by every provider or visited website.
Executive Suite and Company Brain process authorized company records, documents, notes, relationships, imported communications, proposed updates, review decisions, citations, and audit history. Information may be available to other members according to company, project, and role permissions. The organization controls its workspace membership and authorized sharing. Personal mailbox connections are not automatically company-wide connections.
Uploaded and generated files may be stored for later retrieval, converted, indexed, extracted with OCR, analyzed in a computing environment, and rendered or validated by our workers or hosted providers. This can include document text, spreadsheet cells and calculations, images, audio, filenames, source references, and generated previews. Deleting one chat or disconnecting one source does not necessarily remove separately saved files, workspace records, or content already shared with others.
Depending on the feature and configuration, providers include OpenAI, Anthropic, Google, and xAI, alongside Supabase and hosting, payment, communications, search, and browser services. Selecting a primary model does not mean every operation stays with that provider: safety checks, search, OCR, file generation, and other specialist operations can use additional providers. Provider prompt caching may temporarily retain context to reduce repeated processing. Progress and diagnostics may include task status, source references, usage, and errors; an activity display is not a disclosure of private model reasoning.
We retain information for the feature you use, continuity of your account or workspace, security, accounting, and applicable obligations. The phone recovery worker removes completed, failed, and cancelled personal-assistant jobs older than 30 days when it runs successfully. Uncertain actions, call history, approvals, and billing records can remain longer for investigation and reconciliation. This is not a 30-day deletion promise for all phone or connected-account data. Provider copies, delivered messages, backups, and organization records can have different retention periods.
We use authentication/session cookies and similar local storage to keep you signed in and retain settings. Requests to external websites or providers can reveal network and device information. Where a location-dependent feature is used, the location supplied or permitted by you is used for that request. You may manage browser storage and permissions; disabling required storage can prevent features from working.
Depending on your location and applicable law, you may have rights to access, correct, delete, or obtain a copy of your information, withdraw consent, or object to or restrict processing. Contact [email protected] to make a request; we may verify identity and applicable workspace authority. Where applicable, you may complain to your data protection authority. Withdrawing consent does not undo processing already lawfully performed.
Where applicable, processing relies on performing our contract, your consent for optional features, legitimate interests such as security and service reliability, or legal obligations. Providers may process information in the United States or other countries. We apply safeguards required for applicable international transfers. We will provide legally required notice of material changes rather than treating this policy as permission for undisclosed new uses.