YOUR INFORMATION
Privacy policy
Last updated: 14 October 2026
Turnwise AI is owned and operated by Indriya Research Labs, Inc. This policy explains how we handle information in its invited-team application and public website. Which features and sign-in methods you can use depends on your account and the features enabled for it.
Sign-in and account access
When you choose Google sign-in, Turnwise uses your Google account identifier, email address and verification information to establish your identity and check your approved access. Your name and profile information may be provided by Google. Turnwise does not receive your Google password.
Google sign-in alone does not authorize Turnwise to read your Gmail, Google Drive or Calendar. The current sign-in flow requests identity information, not access to those services. We use Google sign-in information for authentication, account access and attribution of your work, not advertising.
Our identity and access services verify identity and account membership, including sign-in by email link where enabled. Turnwise connects that verified identity to its application session. Signing in does not automatically enroll you in another team's account.
Optional Gmail connection
Connecting Gmail is a separate, optional consent step in the administrative console. The Gmail connection requests read-only access to messages, message headers, threads and attachments so you can browse permitted correspondence, select an invoice attachment and retain relevant clarification with your work. It does not request permission to send, modify or delete your mail. Google’s read-only permission covers the connected mailbox; an address filter in the application does not narrow that Google permission.
The connection service stores encrypted credentials and checks the current user, organization and mailbox permissions. Turnwise additionally checks the selected workspace, project and client. Connecting a personal mailbox does not automatically share its contents with colleagues. Selected copies and derived information remain private unless you explicitly authorize an available sharing action. Attachments are quarantined and inspected before a sanitized copy becomes eligible for document processing.
When enabled and requested by you, document extraction uses the selected attachment and, if selected, its accompanying clarification. The document processing service prepares the document, and the AI orchestration service routes the extraction request to the configured model service. Google user data, including Gmail messages, attachments and information derived from them, must never be used for model training. This prohibition applies to us and to service providers processing that data for us.
Turnwise AI’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. We use this information only for the user-facing features described here. We do not sell it, use it for advertising, or transfer it for unrelated purposes. Service-provider processing is limited to delivering those features with your consent, necessary security work, or applicable legal obligations. Human access to specific mailbox information requires your affirmative agreement unless necessary for security or applicable law, or permitted internal operations involving aggregated data under Google’s policy.
You can revoke the Gmail connection in the administrative console or your Google account’s third-party access settings. Revocation stops subsequent authorized mailbox retrieval; it does not erase copies you previously imported. Imported originals, inspected copies, clarification and review records are retained for the configured workflow. Contact the privacy address below to request deletion of those copies and connection information; we verify the requester’s authority and explain any required shared-record, backup or legal retention. Revoking Turnwise access does not delete messages in Gmail.
Conversations and work you save
Turnwise stores the meeting recordings, transcripts, speaker labels, review contributions, requirements and other content supplied to your workspace. It also stores questions, generated answers, evidence references and associated history so you can return to your work.
Original meeting content is separate from your subsequent AI question-and-answer conversations. When voice recording is enabled, your spoken questions and generated spoken answers can be recorded and saved for later playback. Use voice only when you are comfortable with this processing, and obtain appropriate permission before supplying recordings or information about other people.
Access follows the meeting and account permissions in the application. Shared review contributions can be visible to authorized collaborators. Personal Q&A recordings are currently restricted to the reviewer who created them and still require current access to the underlying meeting.
Services that process information
Google Firebase hosts the application and provides application authentication, shared review storage and protected meeting playback. Amazon Web Services hosts Turnwise's backend and private Q&A recording archive. The identity and access services verify permissions; the AI orchestration service routes AI requests.
When you ask an AI question, the question and relevant conversation context are processed through the AI orchestration service and its configured model service, currently OpenAI's Codex service. When enabled, ElevenLabs processes voice audio, speech recognition, spoken responses and voice conversation records. These service providers process the information necessary to deliver those features; their applicable service terms and privacy policies also govern their processing.
These are cloud services. This policy does not promise that processing stays in your country, that no provider temporarily retains data, or that the application is suitable for every category of regulated information. Contact us before using Turnwise for a workflow with specific confidentiality or residency requirements.
Retention and deletion
Meeting content, contributions and saved conversations are retained so authorized users can revisit them. The current Q&A archive has no automatic expiry. ElevenLabs is configured with a 30-day recording and transcript retention buffer; transferring a recording to the AWS archive does not delete that archive when the provider's retention period ends.
Signing out or losing workspace access does not delete previously saved work. To request access to, correction of, or deletion of your information, contact the address below and identify the relevant account or conversation. We may need to verify your identity and coordinate with the account administrator, particularly where records also belong to other participants. We will explain any applicable limitations, including shared records, backups and operational or legal retention needs.
Sessions and safeguards
The application uses browser session storage, authentication tokens and, where enabled, secure session cookies to keep you signed in. Backend session credentials are encrypted. Private recordings require authenticated access; possession of a public marketing or workspace address does not grant access to their content.
Operational records can include account and request identifiers, timestamps, errors and security events used to run the service and investigate failures. The public marketing page has no advertising trackers or third-party analytics scripts. Hosting providers may still process ordinary connection information when you visit.
Contact and updates
For privacy requests, legal notices and Google sign-in support, contact Indriya Research Labs, Inc. at abhi@indriyai.com.
We will update this page as data handling changes and show the revision date above. Material changes to the provider or processing arrangements will be communicated before they apply, with renewed agreement or consent where required. Read the pilot terms of service alongside this policy.