Effective Date: September 14, 2026

Privacy Policy

How Chorebot and Kavana Labs, LLC handle, protect, and process your data across our web and mobile applications.

Your data and your choices

Chorebot uses the information you share and the accounts you connect to carry out your requests. Relevant content is processed by our AI and service providers. You choose which Google permissions to grant and can disconnect accounts, delete conversations, and delete your Chorebot account from the web or mobile app.

1. Introduction & Scope

This Privacy Policy applies to the Chorebot application (the "Application" or "Service"), available via web at chorebot.co and mobile devices, created and operated by Kavana Labs, LLC ("Service Provider", "we", "us", or "our").

Chorebot helps with browser tasks, email, calendars, contacts, and other connected services. This policy also covers conversations through supported SMS, WhatsApp, and iMessage channels.

2. Information Collection and Categories of Data

The Application collects information when you access, register for, or interact with the Service. This information includes:

  • Account & Identity Information: Your email address, profile identifier, and authentication tokens provided via our authentication provider (Auth0 by Okta).
  • Conversations, Preferences & Memory: Messages, conversation histories, task instructions, feedback, settings, and saved personal memory used to personalize your requests.
  • Attachments & Uploaded Documents: Files, PDFs, images, or receipts you upload into conversation threads to provide context for chores.
  • Encrypted Vault Credentials: Website URLs, domain labels, usernames, and encrypted copies of passwords you explicitly save in your Password vault. Passwords are stored encrypted, not as readable text. When you unlock the vault, Chorebot can temporarily decrypt them to perform your requested tasks.
  • Messaging & Location: Phone numbers, message content, delivery information, and messaging consent records when you use a messaging channel. If you choose to share a location, we process the location text or coordinates to answer your request; this does not enable continuous location tracking.
  • System & Diagnostic Data: Technical request information, errors, usage information, and, when tracing is enabled, conversation and tool activity used to diagnose service problems.

The Service Provider may use your contact information to communicate important service notices, security updates, or required transactional messages.

Messages, Content & Human Access

Messages and Content: We store your messages, attachments, and task results to provide conversation history and carry out your requests. We do not permit service providers to use this content to train generalized AI models. We share content with service providers only as needed to operate the features you use, subject to this policy's restrictions.

Model Training: We may use your conversations, feedback, and task results to train and improve Chorebot's AI models. We take reasonable steps to exclude passwords and authentication tokens, but sensitive information you enter directly into chat may be included in training. We exclude data obtained through Google APIs, including content derived from that data, from training.

Restricted Human Access: Human access to your content is restricted to specifically authorized personnel who need it to resolve a support request, investigate a security incident, or comply with law. Access is limited to the minimum information necessary. For Google user data, we require your explicit permission for troubleshooting unless access is required by law.

3. Browser Tasks & AI Processing

When you direct Chorebot to perform an automated task on the web (such as downloading a utility statement, checking a balance, or scheduling an appointment), the Application interacts with third-party websites in an automated browser environment:

  • Viewport Screen Capture & Visual Context: To understand dynamic DOM layouts and interactive elements, Chorebot captures full viewport screenshots and element coordinate maps. Rendered screenshots—which may contain visible account balances, statement summaries, or order details from third-party sites—are sent to Google Gemini to understand the page and carry out your request.
  • Screenshot Receipts: Verified completion snapshots and downloaded PDF receipts are saved to your account attachments for your records.
  • Domain Reconnaissance & Structural Knowledge: Non-personal structural routing patterns (such as public URL endpoints and login form selector maps) may be cached across chore runs to improve navigation speed without storing user credentials or session data.

Google Accounts & Permissions

When you connect Google, we receive account identity information and access tokens. The permissions you grant determine which of the following features are available:

  • Gmail: Search and read email content and message details to answer your requests. With send permission, send messages you approve. Email drafts are prepared in the Chorebot conversation, not saved as Gmail drafts.
  • Calendar: List your calendars and their access levels, read events across accessible calendars to answer scheduling questions, and, with the relevant permission, create appointments on calendars you own after your approval. Google’s owned-event permission also permits editing and deleting events, but Chorebot’s Calendar tools currently only read and create.
  • Contacts: Look up names, email addresses, and other contact details to help identify the people you ask about.

Relevant Google content and tool results are sent to Google Gemini as context for your request. Results and summaries may be saved in your conversations or personal memory and, when diagnostic tracing is enabled, in traces. Access tokens are stored encrypted so Chorebot can use the connection without requiring sign-in for every request.

Connecting Google is not blanket permission to send messages or change your accounts. Chorebot requires your explicit approval for consequential actions. Google data is subject to the restrictions below, including when processed by service providers.

Google API Services User Data Policy Compliance

Chorebot's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

  • Limited Use: We only use Google data to provide user-facing features prominent in the application interface.
  • No AI/ML Training: We exclude data obtained through Google APIs, including content derived from that data, from model training and fine-tuning.
  • No Human Review: Humans are prohibited from reading your Google user data unless explicitly permitted by you for troubleshooting or required by law.
  • No Advertising: Google user data is never sold, leased, or transferred to third parties for advertising purposes.

4. Password vault Security

Saved passwords and notes are encrypted at rest using keys derived from your master passphrase. Website names, labels, and username hints are stored unencrypted to help identify saved logins. When you unlock the vault, Chorebot can decrypt credentials in server memory and enter them into the websites you ask it to use. This is not end-to-end encryption that prevents the service from accessing credentials during an authorized task.

The vault locks when you lock it manually or after 15 minutes of vault inactivity. Locking prevents further vault decryption until you unlock it.

We cannot recover your master passphrase. If you forget it, saved credentials cannot be recovered through that passphrase.

5. Third-Party Infrastructure Providers

We use the following providers for the features described here. The information they receive depends on the features you use. Our Google data commitments apply to transfers of Google data to these providers.

Auth0 by Okta

Identity management, single sign-on, and authentication token security.

Google Gemini

Processes relevant messages, attachments, screenshots, and connected-service results to generate answers and carry out tasks.

Steel

Provides cloud browsers that process the pages, session information, and inputs needed for browser tasks.

Apple App Store & Google Play

Mobile application binary distribution and platform update services.

Twilio

Processes phone numbers and verification messages for SMS sign-in and two-factor authentication.

Sendblue

Processes phone numbers, message content, attachments, and delivery information for iMessage and SMS/MMS conversations.

Langfuse

When tracing is enabled, processes diagnostic traces that can include conversation text, tool inputs and results, account identifiers, and model outputs. Traces are not limited to anonymous usage counts.

6. Disclosure of Information & SMS Privacy

Subject to the Google data restrictions above and the SMS restrictions below, we may disclose information:

  • As required by law, such as to comply with a subpoena, court order, or valid legal process;
  • When we believe in good faith that disclosure is necessary to protect our rights, protect your safety or the safety of others, investigate fraud, or respond to a valid government request;
  • With trusted technical service providers who work on our behalf under binding confidentiality and data protection agreements.

SMS / Text Messaging & Opt-In Consent Privacy

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not sold or shared for third-party marketing. Messaging service providers process the information needed to deliver the messaging service on our behalf.

If you opt in to receive SMS notifications or conversational chore updates from Chorebot, your phone number and consent records are used strictly to provide the requested service and essential account communications. You can cancel text communications at any time by replying STOP, or text HELP for assistance.

7. Data Retention & User Deletion Rights

Conversation history, attachments, saved memory, and vault entries are retained to provide your account features until deleted. Connected-account tokens are retained while the connection remains active. We do not currently promise a single fixed retention period for all diagnostic logs, backups, or records held by service providers.

  • Delete your account: Use Delete Account in account settings on the web or mobile app. This removes your account and associated records from our active application database and starts cleanup of your uploaded files and browser data. File or provider cleanup can fail or take longer; account deletion does not guarantee immediate erasure of every copy.
  • Manage individual data: Delete conversations and vault entries using their controls. Review or clear saved personal memory separately; deleting a conversation does not by itself clear memory derived from it.
  • Disconnect Google: Use Connections to remove the integration. Chorebot deletes the stored connection and attempts to revoke its Google token. You can also revoke access directly in your Google Account connections.
  • Previously stored data: Disconnecting Google does not delete Google-derived content already saved in conversations or memory. Delete that content separately or delete your Chorebot account. It also does not delete messages or events in Google itself.
  • Other copies and assistance: Account deletion does not automatically erase diagnostic traces, backups, messages held by recipients, or every record held by identity and messaging providers. Contact privacy@chorebot.co for help with deletion, access, or records outside the application database. Legal obligations may require retention of some records.

8. Regional Privacy Rights (California & European Residents)

Depending on your location, you may have specific statutory rights under data protection frameworks such as the California Consumer Privacy Act (CCPA/CPRA) or the General Data Protection Regulation (GDPR):

  • Right of Access & Portability: You may request a copy of the personal information we maintain about you.
  • Right to Rectification & Deletion: You may request correction of inaccurate data or complete erasure of your personal data.
  • No Sale of Personal Information: We do NOT sell, rent, or monetize your personal information or vault secrets to data brokers or third parties.
  • Non-Discrimination: We will never discriminate against you for exercising your lawful privacy rights.

To exercise any of these rights, submit a Data Subject Access Request to privacy@chorebot.co.

9. Children's Privacy

The Application does not address and is not intended for anyone under the age of 13. The Service Provider does not knowingly collect personally identifiable information from children under 13 years of age.

If we discover that a child under 13 has provided us with personal information, we will immediately delete such data from our servers. If you are a parent or guardian and become aware that your child has provided us with personal data, please contact us at privacy@chorebot.co.

10. Security Safeguards

We maintain physical, electronic, and procedural safeguards to protect information processed by the Application. While we implement industry-standard encryption, tokenized authentication, and sandboxed browser environments, no electronic transmission or storage system is 100% secure. We encourage users to use strong master passphrases and safeguard their credentials.

11. Changes to This Privacy Policy

We will update this page and its effective date when our practices change. We will provide notice of material changes through the app or an account communication. If we propose a new use of Google data beyond what you previously authorized, we will seek your consent before using it for that purpose.

12. Contact Us

If you have any questions or concerns regarding privacy practices while using Chorebot, or if you wish to exercise your data protection rights, please contact the Service Provider:

Kavana Labs, LLC

Email: privacy@chorebot.co