Privacy Policy

Last updated: 21 July 2026 · Effective date: 10 July 2026

This privacy policy describes how the browser extension AI Companion for Google Tasks ("the Extension", "we", "us") accesses, uses, stores, and shares data — including Google user data, the web content you choose to attach, and the way AI processing works — when you use it. The Extension is published by ozeo (Jean-Sébastien Mancebo), 14 avenue de l'Europe, 77144 Montévrain, France. Contact: contact@ozeo.io.

The Extension is a third-party tool. It is not affiliated with, endorsed by, or sponsored by Google LLC or Anthropic PBC. Google Tasks™ is a trademark of Google LLC; Claude is a trademark of Anthropic.

1. What the Extension does

AI Companion for Google Tasks turns a Google Task into a chat with context. It lets you:

• View and manage your Google Tasks from a side panel, and pick a task to work on.
• Attach context to a task — for example, capture the web page you are currently viewing and convert it to clean text (markdown). This context is stored locally on your device.
• Chat with an AI assistant (Anthropic's Claude or Google Gemini) about the task, which reads the task and the context you attached to help you summarize, draft replies, extract information, or plan next steps.

2. Google user data we access (Data Accessed)

With your authorization, the Extension uses the Google Tasks API (https://www.googleapis.com/auth/tasks) to access:

• Your task lists — names and identifiers, to show them and let you choose one.
• Your tasks — title, notes, due date, status, completion date — to display and manage them.
• Create, edit, and complete permissions — to update tasks you choose to change.
• The email address of the Google account you authorize — from the email / openid scope, used only to build correct ?authuser= deep links for multi-account users and to derive a coarse account domain for anonymous analytics (section 5). The email itself is never transmitted to ozeo in BYOK mode and never used for advertising.
• Your basic Google profile — from the profile scope: your display name, first and last name, profile picture, and language/locale. This is read only in Managed mode / when you sign in to your ozeo account (see section 4), to personalize your account (show your name and avatar) and to serve the interface in your language. It is not accessed or stored in BYOK mode, and is never used for advertising, profiling, or to train AI/ML models.

3. Web content you attach (context)

When you explicitly click "Attach current page" (or a similar action), the Extension reads the content of the page you are currently viewing, converts it to text/markdown, and saves it as a context node locally on your device (in your browser's IndexedDB storage). This happens only on your explicit action, only for the tab you invoke it on, and only for pages you already have open.

• The Extension does not read, collect, or transmit the content of pages you merely browse. There is no background scraping of your browsing history.
• Captured context is stored only on your device and is never sent to ozeo's servers in BYOK mode.
• Context is sent to an AI provider only when you send a chat message, and only as described in section 4.

4. How we use your data (Data Usage) — including AI processing

We use the Google user data described in section 2 only to provide the Extension's features to you:

• Displaying and managing your tasks — your task lists and tasks (title, notes, due date, status) are used to show them in the side panel and to create, edit, or complete the tasks you choose to change.
• Building the AI request — when you send a chat message, the selected task's title and notes (Google user data) are included in the request sent to the AI model, so the assistant can reason about that task.
• Deep links & anonymous analytics — the authorized account's email is used only to build ?authuser= deep links and to derive a coarse account domain for opt-out analytics (section 5). We do not use any Google user data for advertising, profiling, or to train AI/ML models.

When you send a message in the task chat, the Extension composes a request containing your message, the task's title/notes, and the context you attached, and sends it to an AI model to generate a response. There are two modes, and you choose which one you use:

• Bring Your Own Key (BYOK) — default. You provide your own API key for the provider you pick (Anthropic Claude, api.anthropic.com, or Google Gemini, generativelanguage.googleapis.com). Requests go directly from your browser to that provider; they do not pass through ozeo, and ozeo never receives your task data, attached context, or chat messages. Your use of the provider is governed by its own privacy policy / terms. Your API key is stored locally in your browser (chrome.storage.local), is never synced, and is never sent to ozeo.
• Managed mode — optional, off by default. If you turn it on and connect your Google account, the Extension sends your chat message, the attached context, and the task's title/notes to ozeo's EU-hosted server (eu-west-3), which forwards them to the AI provider using ozeo's key and streams the reply back. In this mode ozeo receives that content (solely to generate the reply) and stores, per account, your Google email, your basic Google profile (name, first/last name, profile picture, locale — section 2), your monthly message count, and per-message token counts — used only to identify your account, personalize the interface, enforce your quota and, for a Paid Plan, to bill you. Content of prompts and replies is not retained after the reply is generated, and is never used to train models. Managed mode is entirely optional; BYOK never sends anything to ozeo.

AI-generated responses can be inaccurate. You are responsible for reviewing them before relying on or acting upon them.

5. How we share data (Data Sharing)

• Google Tasks API (googleapis.com) — your task data stays in your own Google account, governed by Google's privacy policy. It is never sent to ozeo.
• AI provider (BYOK) — Anthropic (api.anthropic.com) or Google Gemini (generativelanguage.googleapis.com). When, and only when, you send a chat message, the provider you selected receives your message, the attached context, and the selected task's title and notes (which are Google user data), sent directly from your browser using your own API key. This transfer happens solely to generate the reply you requested and is not used to train models. No other Google user data (e.g. your email, other task lists, or tasks you did not open) is sent.
• ozeo managed server (EU, eu-west-3) — only if you opt into Managed mode. It receives your chat message, attached context, and task title/notes to generate the reply (not retained afterwards, not used for training), and stores your Google email, basic Google profile (name, picture, locale), and monthly message/token counts to identify your account and enforce your quota and billing. Not used in BYOK mode.
• Payments (Stripe) — if you subscribe to a Paid Plan, payments are processed by Stripe (Stripe's privacy policy). ozeo stores your subscription status and Stripe customer/subscription identifiers to manage your plan.
• Anonymous analytics — to understand usage and improve the Extension, ozeo may collect anonymous, opt-out usage events on its own EU-hosted endpoint (not a third-party analytics provider). Each event contains only a locally-generated random install identifier, the event name and extension version, and a coarse account-email domain. It never includes your tasks, notes, attached content, chat messages, full URLs, or your email address. No advertising, no third-party trackers, no cookies. Turn it off any time in Settings.

ozeo never sells, rents, or shares your Google user data or attached content with any third party beyond the providers strictly needed to deliver the features you use, as described above.

6. How we store and protect data (Data Storage & Protection)

• Your tasks live on Google's servers, inside your own account.
• Attached context, task–context links, and chat history are stored only on your device in your browser's IndexedDB. They are not copied to any ozeo server.
• Your BYOK API key is stored in chrome.storage.local on your device only, never synced, never sent to ozeo. It is not encrypted at rest in this version; treat your browser profile as you would any credential store.
• Managed mode (if you opt in) — ozeo stores, on its EU server, only your Google email, basic Google profile (name, first/last name, profile picture, locale), monthly message count, per-message token counts, plan status, and Stripe identifiers. Prompt/reply content is processed transiently to generate the reply and is not retained. This data is kept while your account is active and is automatically deleted after 12 months without a sign-in (an inactivity time-to-live refreshed on every connection); you can also disconnect Managed mode in Settings or email us to delete it sooner. Usage ledger rows auto-expire after 180 days. Operational server logs of Managed-mode activity (which may include your account identifier, email, name, and the name of your last action — never prompt or task content) are retained for at most 90 days and then deleted.
• Preferences (chosen AI mode and model) are stored locally. An OAuth access token is managed by Chrome's identity API for the duration of a session.
• All network communication uses HTTPS. You can revoke the Extension's Google access any time from your Google Account permissions page. Uninstalling the Extension removes its local storage from your device.

7. Requesting minimum scopes

OAuth scopes requested: https://www.googleapis.com/auth/tasks plus openid, email, and profile. The Tasks scope is the minimum required to read and manage the tasks you chat about; Google offers no narrower Tasks scope. The openid/email/profile scopes are Google's standard, non-sensitive sign-in scopes: they identify your account and provide your email plus basic profile (name, picture, locale) to run your ozeo account. The Extension requests no Gmail, Drive, Contacts, or other sensitive scopes — email/ticket context is read from pages you already have open, never via those APIs.

8. Browser permissions, justified

9. Data retention & deletion

In BYOK mode (default), ozeo retains no Google user data, because none of your task data or attached content reaches our systems — AI requests go directly from your browser to the provider with your own key. The only data ozeo receives is the anonymous, opt-out analytics described in section 5. In Managed mode (optional), ozeo receives prompt/context content transiently to generate the reply (not retained) and stores your email + message/token counts and subscription status for quota and billing, as described in sections 4 and 6.

• Google user data (task lists, tasks, and the account email) is never stored by ozeo; it lives in your Google account and is only read into memory on your device to display and manage your tasks. Delete or export it any time from Google Tasks, and revoke the Extension's access from your Google Account permissions page.
• Data stored on your device (attached context, task–context links, chat history, preferences, and your BYOK key) is kept locally until you delete it. You can remove individual context nodes and chats from the Extension, and uninstalling the Extension permanently deletes all of its local data from your browser.
• Managed account data (email, basic Google profile, plan/usage counters, Stripe identifiers) is kept while your account is active and is automatically deleted after 12 months without a sign-in. Disconnect Managed mode in Settings or email contact@ozeo.io to have it deleted sooner; usage ledger rows auto-expire after 180 days.
• Anonymous analytics are retained for at most 90 days on ozeo's EU-hosted endpoint, then automatically deleted. As they contain no personal identifier (only a random install ID), you can stop them any time in Settings.

10. Paid features

We offer optional paid features (the "Paid Plan"). Any Paid Plan is opt-in. If you subscribe, you connect your Google account in Managed mode (sharing your email and basic profile — name, picture, locale), payments are handled by Stripe (Stripe's privacy policy), and we store your email, basic profile, subscription status, Stripe identifiers, and aggregate usage counters in our EU-hosted database. You can cancel any time from the self-service billing portal.

11. Your rights under GDPR (RGPD)

As an EU/EEA user you have the right to access, rectify, erase, restrict or object to processing, data portability, and to lodge a complaint with a data protection authority (in France: CNIL). For the free/BYOK Extension, because we do not store your data, these rights are exercised directly with Google and your AI provider. For Managed mode / the Paid Plan, contact contact@ozeo.io.

12. Children

The Extension is not directed at children under 16 and does not knowingly collect data from them.

13. Changes to this policy

We may update this policy from time to time. Material changes will be communicated through the Chrome Web Store listing and via this page. The "Last updated" date reflects the most recent change.

14. Compliance with Google API Services User Data Policy

AI Companion for Google Tasks'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.

15. Contact

ozeo — 14 avenue de l'Europe, 77144 Montévrain, France
Email: contact@ozeo.io