Privacy
Closive helps you remember important open loops and prepare useful steps toward completing them. This policy explains how we use your data to do that.
Effective 7 October 2026
Who we are
Closive, Inc. builds and operates the Closive assistant. You can reach us at manpreet@closive.ai about anything on this page.
Connecting your account
Sign-in verifies your Google identity. Gmail, Calendar and Drive reading are optional. You can let Closive find open loops in email, which needs Gmail access, or start by sharing what you want to track in Chat or voice. Calendar and Drive remain optional when you choose email discovery. Returning sign-in keeps access you already granted without requesting missing permissions. You can enable more from Google access in the account menu or when a task needs it in Chat. Calendar helps discover upcoming meetings and follow-ups. Drive helps read relevant files; Google grants broader Drive read access. Sending email, changing calendar events and writing Google documents are offered when needed. We use Google sign-in; you do not give Closive your Google password. If you are not yet invited, signing in saves your name, email address and account identity so we can contact you about access. You can register interest without granting mail access. We do not sync your connected accounts before you are invited.
Granting access does not itself send an email, change an event or write a document. Emails to other people, Calendar changes and Google document writes require your approval of the exact draft. If you explicitly ask Closive to email results to yourself, that request authorizes delivery to your verified account address without another draft approval.
Your choice about AI processing
Before background reading or AI processing starts, we ask you to explicitly accept our data-sharing disclosure. This also applies to existing accounts. In Account and privacy, you can decline or withdraw acceptance to pause processing without deleting your saved history. Signing in or granting Google permissions alone does not provide this acceptance.
What the application collects
- Your account information. Your Google account identity, email address and display name, so we can recognise your Closive account.
- Mail and attachments, when enabled. Message content, senders, recipients, subjects, dates, conversation history and readable attachment content needed for your work.
- Calendar information, when enabled. Event titles, times, attendees and descriptions, and event changes you approve.
- Drive files, when enabled. Content from specific files linked in your email conversations when relevant to your work. You can also ask Closive to search for files, explore a selected folder, read a file, or attach an existing file to an email draft. These reads are bounded to your request; we do not automatically index or synchronize your whole Drive.
- What you share. Chat messages, tracking instructions, answers, corrections, meeting notes and voice recordings you choose to make. Voice is processed into text.
- What Closive prepares and remembers. Tracked outcomes, preferences, reminders, drafts, guides, meeting preparation and summaries, along with supporting context, their updates and records of actions you approve.
- Usage and service records. Information needed to manage your sign-in, diagnose problems and measure AI usage and estimated cost. Cost records contain usage measurements, not copies of your messages or the answers you receive.
Emailing results to yourself
For accounts with scheduled email delivery enabled, choosing email for a task sends its completed results from Closive through Resend. Resend processes your verified account email, the subject and the report body, which may include information from connected sources. We do not send your Google credentials to Resend. Chat requests such as “email me this” send through your connected Gmail and need Gmail sending access. Scheduled notification delivery does not. Reports are also kept in Closive. Delivery providers and recipient mailboxes retain their own copies under their applicable terms and controls; deleting Closive data does not recall sent mail.
iPhone notifications
The signed-in iPhone app registers a device push token and installation identifier with Closive and stores your notification preferences. Alerts are sent only after you allow notifications. Apple processes the device token, alert text and app navigation identifiers to deliver them. Scheduled task alerts include the task title and completion or attention status, which may appear on your lock screen. Other alerts use generic text. Payloads do not include task instructions, result bodies, email bodies, question text or prepared work. You can turn notifications off in Closive or iPhone Settings.
You can also select existing Gmail attachments for a new email or reply, and existing Drive files when that capability is available. Closive saves private copies for seven days and sends the exact selected files only after draft approval. Attachment metadata and approval history remain with your drafts; paused cleanup and recovery copies follow our retention policy. Formatted original-email previews block external images and active content. Preparing a forwarded email saves a copy of the selected original message, including its formatting and attachments, with your draft. Closive sends that original only after you approve the draft and included attachment.
Google document writing
With your optional permission, Closive can create Google Docs and Sheets and prepare supported changes to files created by Closive. You review and approve the exact proposed change before anything is written. Document writing uses Google’s drive.file permission. Reading a file or providing its URL does not grant editing access. Editing other existing files requires explicit Google file selection, which is not available in this rollout.
Proposed content and bounded snapshots needed to prepare an edit may be processed by our AI provider. Closive saves drafts, approval and execution records, and links to completed files. Files remain in Google Drive and follow their existing sharing settings; Closive does not change sharing.
How Closive finds relevant information
Connecting Gmail and choosing what Closive should monitor are separate decisions. With Gmail connected, Closive can investigate a request, watch email about topics you ask it to track, or read email for a scheduled task. A one-time lookup does not start ongoing monitoring. You can separately enable finding new work in email: Closive analyzes recent emails for commitments and follow-ups and keeps checking new email. You can stop that discovery while keeping updates for work already being tracked.
Google’s Gmail permission covers your mailbox; it is not restricted to a single task or topic. Closive limits its reads to your requests and tracking choices. Search results can include senders, subjects and short previews of unrelated messages. Closive uses these to judge relevance and keeps search records, but does not open unrelated conversations further.
When establishing an outcome or preparing its next step, Closive can search related conversations and inspect relevant sources. It saves useful context and private records of its searches and source reads to support follow-through and diagnose reported misses. Private diagnostic records also contain brief AI-written explanations of decisions, including supporting facts, assumptions and uncertainty. These can include personal information from the task context. They do not contain hidden model reasoning. Searching does not automatically track every result.
If you enable Calendar access, Closive also reviews events for useful attendance, preparation or follow-through. You can tell Closive what to track, change or stop at any time.
How your information is used and shared
We use your information to remember what matters to you, answer questions, prepare useful work and reassess next steps as conversations change or follow-up times arrive. This work can continue in the background while you are away.
Third-party AI providers process relevant messages, source content and instructions to produce answers, judgments and prepared work. Third-party speech providers process recordings for transcription and text for voice playback. That text may include information from your connected accounts. Third-party hosting, authentication and communication providers help us operate the service and respond to you. The providers we use may change over time.
When you approve sending an email or creating, updating or canceling an event with invitations, the approved information is shared with the recipients or attendees. We may also disclose information with your consent or when required by law.
We do not sell your data or use it for advertising.
Providers may retain information under their applicable service terms and data controls, including for security and abuse prevention. Deleting data from Closive does not necessarily delete provider records immediately. Our data retention policy explains this distinction. Contact us if you need details about the providers and controls currently used for your account.
AI and speech providers
Third-party cloud providers process relevant connected content, instructions and conversation context for AI assistance to understand requests and prepare answers and work. Speech providers process recorded audio for transcription and text for spoken playback. Before capture starts, voice explains that audio streams to a provider before you submit your transcript. You can use typed chat instead. These providers have separate retention controls; we do not promise universal zero retention.
Live voice calls
When live calls are available and you choose to start one, your microphone stays open until you mute it or end the call. Live audio goes directly to OpenAI, together with relevant conversation context and, when requested, your Daily Brief. Nearby people or television may also be captured. The microphone notice appears before your first call; use a private space or typed Chat if you do not want continuous audio processing.
Closive saves call transcripts and task results with your conversation. Call text may also be processed by the AI providers used for task reasoning and Memory. Closive does not retain raw call audio and requests that OpenAI session storage be disabled. This does not establish zero provider retention; provider records remain subject to applicable terms and account controls. Ending or interrupting a call does not cancel work already accepted by Closive. Actions requiring approval still require approval on screen.
Email writing style
Closive can learn how you write from a small sample of sent messages in conversations it is already permitted to review. The configured cloud AI provider processes these samples to personalize future email drafts. This does not scan unrelated email or train a generalized model. The learned description is visible in Memory, where it follows the same account-history and deletion rules as other remembered preferences.
You can ask Closive to correct the description, turn learning off, reset it or learn it again. Turning learning off or resetting it does not erase historical records or recovery copies. Your current instructions override inferred habits, and sending keeps its existing approval requirements.
Reading document images
When reading selected documents, Closive may send embedded images and rendered PDF pages to its AI provider alongside extracted text. This includes images in Google Docs tabs, Word documents and Sheets or Excel worksheets, and scanned or mixed-content PDFs from permitted Drive files, selected email attachments or public links. Reads are bounded, and the assistant reports unread content and material uncertainty. Reading a file does not authorize changing it or sending it to email recipients.
Temporary Google image links retrieve the permitted image but are not sent to the AI model or saved in Closive history. Image-server requests do not send Google credentials or account cookies. Images stay in memory for the reading task; saved findings and citations follow our data retention policy.
Public web research
When public information can help answer your request or prepare a useful next step or meeting brief, Closive uses a third-party public search provider. Minimal public search terms, such as a person or company name, go to that provider. The assistant is instructed to exclude private message bodies, document text, credentials and confidential details from queries. Relevant public passages go to our AI provider and may be cited in your saved answers. Search queries and results are subject to the search provider’s service terms and retention controls.
Closive can also read public pages and follow relevant public links. Each visited website receives the public URL, our service network address and a reader identifier. We do not send your Google credentials, account cookies, private message bodies or the assistant's explanation of why it is reading the page. Publicly published Google spreadsheets may be read through their public export. Relevant extracted text, rendered public PDF pages and links go to our AI provider and may be cited in saved answers. The assistant is instructed not to open private links, access tokens, unsubscribe links or other links that perform an action. This does not use your signed-in browser sessions.
Google user data
Closive’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide and improve the user-facing features described here. It is transferred only as needed to provide those features, with your consent, or as permitted by that policy for security or legal reasons. It is never used for advertising.
These use and transfer restrictions apply to raw Google user data and data derived from it, including summaries, prepared work, and any aggregated or anonymised data. Aggregating or anonymising Google data does not allow us to use or share it for unrelated purposes.
We do not use raw or derived Google Workspace data, including aggregated or anonymised data, to develop, improve or train generalized or non-personalized AI or machine-learning models. We do not permit our AI or speech providers to use that data for those purposes. Transfers to these providers are for the user-facing assistance described above, subject to the Limited Use restrictions.
We do not read your mail as a matter of course. Human access is limited to your consent for specific information, security investigations, legal obligations, or permitted internal operations using aggregated and anonymised data. If diagnosing a reported problem requires looking at a specific record, we will ask you first.
How information is protected
Connections to the hosted application use HTTPS. The server checks the signed-in account before allowing access to its stored work. Google access credentials remain on the server in account-specific files with restricted filesystem permissions; they are not sent to the browser or included in AI conversations. Our Security and data page explains these protections and account controls.
How long information is kept
We keep the source information and Closive history needed to remember and follow through while your account remains active. Completing an item or stopping tracking does not erase its history. You can disconnect Google and keep your Closive history, or request deletion of your account and its stored data. Account data is removed from our remaining recovery backups within 90 days of account deletion. See the data retention policy for details.
What this website collects
This marketing site runs no analytics or advertising trackers and sets no cookies. Sign-in and early-access interest are handled by the Closive application. The application uses sign-in cookies or secure device storage to keep you signed in and device storage for settings and unfinished meeting notes. Support emails are kept until we no longer need them.
Your choices
- Review or enable optional access in Closive, or revoke access through your Google account permissions. Signing out of Closive does not disconnect Google. After disconnect, we retain the names of previously enabled capabilities so you can choose which to restore. These preferences grant no access; reconnect requires new Google authorization. They are removed with account deletion.
- Tell Closive to change or stop tracking an item or topic. This changes future tracking; it does not delete information already retained.
- Open Account and privacy in the web or iPhone app to disconnect Google, pause AI processing or request account deletion. We stop processing and sign-ins immediately on deletion request, complete active-data cleanup and confirm by email within 7 days, and remove recovery copies within 90 days of the request. Email manpreet@closive.ai from your account address for a data export or help.
Children
Closive is not intended for anyone under 18.
Changes
We update the effective date when this policy changes and notify invited users by email about material changes to how their data is handled.