Privacy policy

Account information includes your name, email address, profile image, and sign-in information. We also process conversations, instructions, files you upload, and content you create or change in Weaver.

With your authorization, we access email subjects, bodies, senders, recipients, timestamps, conversation relationships, labels or folders, and attachments. We store the credentials needed to maintain a connection. With your authorization, we access calendar events and may create, change, or delete them when you instruct or confirm an action.

Weaver may turn connected content into events, summaries, to-dos, reply drafts, and personal memories. Those results can still contain personal information from the source. We also collect the limited device, network, usage, and diagnostic data described below.

We access a connected account only after you authorize it. You can decline a permission, but features that require it may not work.

We use information to provide email search and analysis, summaries, events, to-dos, memories, reply drafts, and calendar actions. Connecting an email account alone does not authorize Weaver to send mail; we send, reply to, or forward email only after you explicitly instruct or confirm it.

We also use limited information to maintain your account, respond to support requests, troubleshoot the service, protect it against abuse, and meet legal duties. Controlled automated evaluation of summaries, classifications, and replies is used only to improve user-facing Weaver features.

We do not sell your emails, calendar data, chats, attachments, or derived content. We do not use them for advertising, credit decisions, training or fine-tuning models shared with other users, or human labeling.

Personnel may access specific content only when you explicitly authorize it for support, when it is necessary for a security investigation, or when law requires it. Access is limited to the purpose involved.

DigitalOcean hosts Weaver's app, business and analytics databases, cache, object storage, and logs. Our internal analysis and diagnostics platform, RSI, may process Weaver usage events, logs, and traces. The main production resources and data storage are in DigitalOcean's San Francisco region in the United States.

Clerk provides identity and session services. Cloudflare provides site security and network delivery. Tavily supports research search. Google and Microsoft process requests when you connect their email or calendar services.

Weaver's main hosted data is stored in the United States. To provide identity, security, AI, and search functions, service providers may process necessary data in other regions where they operate. We impose purpose, security, and deletion limits on these providers.

When you instruct Weaver to send an email, create a calendar invitation, or take another external action, the relevant content goes to the recipient or service you specify. We may also disclose information when required by law or necessary to handle a security incident, subject to applicable limits on Google data.

We send AI requests through OpenRouter, an AI routing service. Requests are served by Anthropic Claude Sonnet and Haiku models, which may run on Anthropic, Claude Platform on AWS, Amazon Bedrock, Google Cloud Vertex AI, or Microsoft Azure, and by the open-weight DeepSeek model, which runs on cloud inference providers such as DeepInfra, CoreWeave, and Inference.net, never on DeepSeek's own hosted API. Search embeddings use an OpenAI embedding model. We may also run models in environments we control.

A request to a cloud AI processor may include your instruction, relevant email or attachments, necessary context, and generated results. We send only what is needed for the feature you use.

We configure OpenRouter to route requests only to providers that do not use request content to train models. OpenRouter and these providers may use request content only to complete the request and for necessary safety and abuse monitoring, and may not train or fine-tune any model on inference inputs or outputs. Providers may keep request content for up to 30 days for those purposes; content flagged for a safety violation, or that the law requires them to keep, may be kept longer.

If we run a model in an environment we control, its requests, logs, and caches stay in that environment and are not added to any shared training set. We do not use human labeling or routine human quality review of user content.

Data obtained from Google APIs, including content derived from it, is used only for clearly presented user-facing features. It is not transferred for advertising, resale, unrelated analysis, or model training for other users. The applicable Google Workspace user data rules also apply. Other parts of this policy do not expand the permitted use of Google data.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Read Google's policy

Disconnecting Gmail or Outlook stops future access and sync and revokes the stored connection credentials. It does not automatically delete previously imported content. We explain that distinction before you disconnect and provide a separate way to request deletion.

You can ask to delete imported email originals and attachments while keeping the events, summaries, and to-dos derived from them; delete the email together with the events, summaries, and to-dos derived from it; or delete your entire Weaver account. Kept derived content may still contain personal information, and we explain that before you choose it.

For an event with several sources, we remove the information within the requested deletion scope and update affected summaries, to-dos, and indexes while preserving unrelated content. Deletion also covers applicable business data, attachments, search indexes, chat history, analytics copies, and background work. We prevent reconnections or delayed jobs from silently restoring deleted content.

After verifying your identity, we complete deletion from production systems within 30 days and clear backup copies within 90 days. The relationship and deletion-prevention records described below and limited records law requires us to keep are retained separately. You can request deletion through Weaver or by email and receive the result.

Deleting data from Weaver does not delete the original email from your mailbox or delete your Google or Microsoft account. After a verified deletion request, we stop using the data being deleted for normal service while the deletion is completed.

To prevent unauthorized deletion, we may ask you to verify your identity and the scope of your request. After account deletion, we keep the name, email address, and phone number you provided for your account, along with account dates and status, indefinitely for relationship management and possible future contact. Name and contact fields are encrypted under a system key that remains after account deletion. We also keep minimal identifiers and keyed erasure locators to prevent deleted accounts from being recreated and to retry content removal.

We use Clerk sign-in and session cookies, Cloudflare security cookies, and functional cookies for language, time zone, and the return path after sign-in. Language and time zone preferences remain for at most 1 year; the sign-in return path remains for at most 10 minutes.

A first-party device identifier in browser local storage distinguishes usage sessions and rotates within 90 days. We do not use advertising cookies or cross-site advertising trackers.

First-party telemetry records page and feature use, performance, errors, security events, and the device or browser details needed to operate, troubleshoot, and improve Weaver. The optional "Help improve Weaver" setting is explained separately from telemetry needed to run the service.

Routine usage events, diagnostic logs, and operational traces do not record email bodies, attachments, chat text, AI prompts or outputs, OAuth tokens, or full URLs that could reveal that content. Content processed for controlled automated quality evaluation is handled separately under the data-use limits above.

We delete or irreversibly de-identify identifiable telemetry, including copies in analytics databases, logs, traces, and backups, within 90 days of collection. Limited records needed for a specific security incident or a legal retention duty are used only for that purpose and removed when no longer needed.

We encrypt user data and derived content in transit and at rest. Email OAuth credentials have separate protection and controlled key management. Personnel and services use least-privilege access, user data is isolated across accounts, and sensitive-content access requires a stated reason and an audit record.

We limit sensitive content in logs and traces, review vendors, code, and dependencies, and maintain an incident response and legally required notification process. These protections also apply to processors of Google data. No online service can guarantee absolute security.

Depending on the law in your state, you may have rights to know about, access, obtain a copy of, correct, or delete your personal information, and to limit or opt out of certain processing.

You can send a request to the privacy address below. We verify requests and respond within the time required by applicable law. We do not discriminate against you for exercising a privacy right protected by law.

You can withdraw a connected account authorization to stop future access. Previously imported data is handled through the deletion process above. You can also change your language, time zone, and the optional "Help improve Weaver" setting in Weaver.

Weaver is not offered to anyone under 18. If we learn that a person under 18 created an account, we will stop providing the service to that person and handle the related data as required by law. You can report such an account to the privacy address below.

We may update this policy as Weaver or our data practices change and publish a revised date. We will notify you of material changes as required by law. If a change requires renewed consent, including a new use of Google user data, we will obtain it before starting that processing.

For privacy questions or data rights requests, email [email protected].