Privacy policy
Effective November 9, 2026
Weft is an event-planning service operated by Benji Wojin. This policy covers Weft at weftplan.com. For privacy questions, support, or data requests, email support@weftplan.com.
Information Weft handles
- Account information: your Google account identifier, verified email address, and name, used to sign you in and associate you with your projects and invitations. Signing in does not give Weft access to Gmail.
- Project information: event details, tasks, assignments, updates, comments, invitations, guest information, uploaded files, and other information you or your team add. Only add other people’s information when you have permission to do so.
- Optional Gmail information: the connected address, authorization tokens, message and thread identifiers, labels, sender, subject, message text, dates, and generated suggestions, as described below.
- Service information: sign-in cookies, browser preferences, support messages, feedback, and technical request/error information used to operate, troubleshoot, and protect the service. Hosting providers may process IP addresses and request metadata.
- Onboarding milestones: Weft uses the timestamp of your first project and records when you first add a task. The app owner can see these milestones by Weft account code to improve onboarding. This dashboard does not include your email, name, project details, or task contents. It does not use third-party analytics or tracking cookies.
- Product usage: Weft keeps daily per-account counts of app opens on Projects and workspace screens, tasks created, and tasks completed, to understand how the service is used. The app owner sees aggregate usage totals. These counts do not store page paths, project or task identifiers, or their contents, and do not use third-party analytics or tracking cookies.
- Getting started guide: If you start the guide, Weft saves which guide buttons and screens you used and which steps you completed, with timestamps and the internal ID of the project you created in the guide. This lets you resume and helps the app owner see where people need help. The funnel dashboard displays an account code and checkpoints, not names, emails, or project contents. No third-party trackers are used.
Gmail is optional
Public launch release: Gmail connections, mailbox reading, automatic email detection, and Gmail-based invitation sending are disabled. The Gmail disclosures below describe the separate email-enabled version under review and any data retained from earlier connections. Signing in does not enable these features.
You can use Weft without connecting Gmail. For imports, Weft requests read-only access to find project emails and prepare updates. The import feature never sends, modifies, or deletes messages in Gmail. Google’s read-only permission covers your mailbox; selecting projects in Weft limits how Weft uses messages, not the scope of Google’s permission.
Manual import reads messages from a Gmail label you choose. Automatic detection requires a separate opt-in and selected projects. It checks message sender, subject, and text to decide whether a message relates to those projects. This can include unrelated or personal messages before their relevance is known. A new connection starts with the previous seven days; later checks resume from saved progress. Recovery after an expired Gmail history may recheck that period. Gmail attachments are not imported or sent for this detection.
Likely matches and uncertain matches are stored privately for the connected user to review. Messages classified as unrelated are not stored as imported emails, although processing identifiers and deduplication records may be retained. AI can make mistakes. Draft summaries do not change shared tasks until you approve an update. Imported original messages remain private to your account within Weft; an approved summary or task update becomes visible to the relevant project members.
Email invitations require a separate, optional authorization requesting Gmail sending permission, configured by an authorized organizer. You may use the same Gmail address for imports and invitations or choose different addresses. Weft stores and controls these connections separately: connecting imports does not enable sending, and connecting a sender does not enable imports. Google may group previously granted permissions for the same account. Weft uses the sender connection only for invitations you request. In-app invitations do not require Gmail sending access.
AI processing and service providers
With your automatic-detection consent, Weft sends email sender, subject, and body text, together with selected project/task names, event dates, locations, and matching identifiers, to Groq to classify relevance and draft summaries. Checks can run while you are away. Attachments are excluded. The event planner also sends the event details disclosed in its separate consent to Groq when you request an AI plan.
When an organizer chooses to draft smaller steps for a task, Weft sends only the displayed task title to Groq. Notes, attachments, event details and member records are not sent for that request. The resulting draft is private to the organizer until they choose to add steps to the shared plan.
Groq processes these inputs and outputs to provide the AI service. Its published data-handling documentation describes limited retention for reliability or abuse investigations, generally up to 30 days unless legally required for longer, and retention of usage metadata. Weft does not promise zero retention by Groq.
Weft uses Vercel for hosting and private file storage, Turso for its database, Google for sign-in and optional Gmail access in the email-enabled version, Groq for the AI features above, and Resend for invitation emails. When an organizer requests an invitation email, Resend receives the recipient’s email address, organizer display name, project name, and an email-bound invitation link with its expiration date. No mailbox access is needed. Weft stores sending attempts and acceptance receipts; an accepted email is not a guarantee of inbox delivery. These providers process the information needed for their services. Processing may occur in the United States or other countries where providers operate. Opening a suggested external website is subject to that website’s own privacy practices.
Limits on Google-data use
Weft’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.
Weft does not sell Google user data, use it for advertising or credit decisions, or use it to train general-purpose AI models. It uses that information to provide the email and planning features you choose. Human access to Google-derived information is limited to your explicit permission for specific data, necessary security investigation, legal requirements, or aggregated and anonymized internal operations as allowed by Google’s policy. Sharing with service providers is limited to the disclosed service, security, and legal purposes; project sharing happens when you approve it.
Storage and security
Weft uses HTTPS, authenticated project access, and encrypted storage for Gmail authorization tokens and imported message payloads. Shared project information is accessible according to project roles. No system can guarantee absolute security. Please do not upload passwords, payment-card details, or information that is not needed for your event.
Retention, disconnecting, and deletion
Account and project records, uploaded files, imported messages, and approved updates remain stored until removed through an available app control or a verified deletion request. They do not automatically expire when an event ends. Hiding, dismissing, or archiving an item is not a promise of permanent deletion.
In this release, Account settings lets you remove previous Gmail import and sender connections. New mailbox checks are already disabled. Removing connections does not delete previously imported messages, summaries, or shared updates, and does not affect Resend invitations. In the separate Gmail-enabled version, import and sender disconnect controls operate independently. An operation already in flight may still finish. These controls do not revoke Google’s app-wide permission grant. You can remove Weft’s access in your Google account connections; revocation there can affect both reading and sending, even when connected separately. Revoking access at Google does not itself delete data already stored by Weft.
To request access, correction, or deletion of your Weft account, onboarding milestones, imported Gmail data, or other personal information, email support@weftplan.com from your account’s address and identify what you want removed. Guest-list participants can also contact this address. Do not send passwords or identity documents. Requests are handled manually; Weft may ask for information needed to verify your identity and authority over shared records.
Deletion is not instantaneous. We will explain the outcome and any information that must be retained for security, legal obligations, or another person’s rights. Provider backups and required operational records may persist under provider retention practices. Deleting Weft data does not delete the original email in Gmail or copies others have already received.
Policy changes and contact
Updates will appear on this page with a revised effective date. A materially different use of connected Gmail data will require an updated disclosure and consent before that use begins. Contact Benji Wojin at support@weftplan.com with questions about this policy or your information.