Selio for Chrome
Privacy Policy
Last updated:
This policy explains what Selio reads, what it sends to the AI service you choose, and what stays on your device.
The essentials: Selio has no developer-operated data relay or analytics service. AI requests go directly to your configured API endpoint. Settings and saved notes stay in the extension’s storage on your device.
1. Scope and developer
Selio — AI Reading Companion is a Chrome extension for translating, summarizing and explaining selected text, asking questions about the current webpage, and saving useful answers as notes. The developer responsible for Selio is zilong, reachable at zhou.zilong@qq.com.
This policy covers the extension’s data handling and this policy website. AI services, custom API endpoints, Chrome and the website hosting service may handle data under their own policies.
2. Data Selio handles
- Reading content
- The text you select; its surrounding paragraph if you choose that scope; and, when you enable webpage context, the locally extracted page title and body passages. A page’s URL and title are also used locally to track its source and navigation. Content may include personal information or communications if they appear in the material you choose to process.
- Questions and answers
- Your questions, follow-up messages, prompt instructions and AI answers. Relevant retained conversation turns may be included in later requests so the AI service can respond in context.
- Model configuration
- Your selected provider, API endpoint, model identifier, API key and generation settings. The API key is used to authenticate requests to the endpoint you configure.
- Preferences
- Interface and translation languages, theme, reading actions and custom prompts, automatic selection preferences, and allowed or disabled website lists.
- Saved notes
- The selected text, source URL and title, AI answer, your optional remarks and tags, and timestamps. Notes are saved only when you choose to save an answer.
- Local usage records
- Model and provider information, action names, request times and status, and token counts reported by the AI service. These local records do not contain API keys, source text, prompts, answers or page URLs.
Selio does not read your browser history or use tracking or advertising SDKs. It does not collect payment details or require a Selio account. Webpage extraction excludes input fields, editable areas, embedded frames, images, screenshots, and hidden or unloaded content; text you intentionally submit may still contain sensitive information.
3. When content is sent
- Selected-text actions: an AI request starts when you click the Selio selection icon, intentionally hover over it for approximately 0.8 seconds, use the selection context menu, switch to an uncached action or scope, regenerate an answer, or submit a follow-up. Selecting text by itself does not send it to an AI service.
- Webpage questions: opening the sidebar or refreshing the extracted page prepares context locally. Sending a question or choosing a suggested question sends the page title, the passages chosen for that request, context metadata, and relevant conversation history.
- General chat: when page context is off, requests contain your chat messages and applicable instructions, without automatically attaching the current page.
- Connection tests: a small test request is sent to your configured endpoint using your API key. It does not include your current webpage content.
- Notes: saving, searching, editing and exporting notes do not call the AI service.
Selected-text requests do not automatically include the page title or URL. Webpage-context requests include the page title but do not automatically include the full page URL. Text, questions or custom prompts may themselves contain URLs or other information you provide. Depending on page length and your question, webpage context may include all extracted passages or only relevant excerpts.
4. AI services and data sharing
AI requests travel directly from the extension to the API endpoint you configure. Available presets include OpenAI, Anthropic, Google Gemini, DeepSeek, Alibaba Cloud Qwen and Moonshot AI Kimi. You can also configure another compatible endpoint or a service you operate. Only the endpoint used for a request receives that request; Selio does not send it to every listed provider.
The selected endpoint receives the request content described above, your model identifier, generation settings and API key for authentication. As part of a normal network request, that service can also receive your IP address and request headers. If you configure a proxy or gateway, its operator receives the request.
The endpoint operator controls its own processing, retention, security, possible model-training use, and any onward sharing. Review that operator’s privacy policy and account settings before sending content. Selio does not operate that service or control copies it retains.
The developer does not receive the extension’s AI conversations, API keys or saved notes through a Selio backend. Selio does not sell user data, share it with advertising networks or data brokers, or use it to train developer-operated AI models. If you contact the developer for support, the developer receives the message and any information you choose to include, and uses it to respond and resolve your request.
5. Local storage and security
Settings, saved notes and local usage records are stored in Chrome extension storage on your device. Selio does not synchronize them through its own cloud service or Chrome sync. Current conversations and extracted webpage snapshots are kept in browser session memory.
By default, API keys are saved on your device in unencrypted extension storage. A person or software with sufficient access to your device or browser profile may be able to read them. You can choose session-only key storage instead; those keys do not persist across browser restarts.
Remote API endpoints must use HTTPS. HTTP is allowed only for loopback endpoints on your own computer, such as localhost. Requests do not attach the cookies from the page you are reading. Extension storage access is restricted to trusted extension contexts, and ordinary webpages cannot list your models or all saved notes.
Protect your device and API keys, and use an AI endpoint you trust. Selio does not claim that local storage is encrypted or that sending content to an AI service makes it private from that service.
6. Retention and deletion
- Settings and persistent API keys remain until you change or delete them, remove the model, or clear all Selio data.
- Conversations and page snapshots are kept for the current browser session and are removed when the associated tab is closed. Closing the floating panel keeps the current conversation available in that tab.
- Saved notes remain until you delete them or clear all Selio data. You can edit remarks and tags, delete individual notes, and export selected notes as Markdown.
- Usage records are limited to the latest 1,000 records. You can clear them on the Token usage page or by clearing all Selio data.
To clear the extension’s stored models, keys, preferences, conversations, usage and notes, open Selio Settings → Privacy & access → Clear all data and confirm. This resets the extension’s settings.
Clearing Selio data does not delete Markdown files you have already exported, support emails, or information already received by an AI endpoint. Manage exported files on your device and contact the relevant service operator for its data-deletion options. For support correspondence, the developer keeps it only as needed to respond, resolve the matter, or meet applicable obligations; you can request deletion by email.
7. Website access and your choices
Selio requests HTTP/HTTPS website access so its selection tool can appear on webpages and it can communicate with your configured API. Automatic selection on ordinary websites is enabled by default. You can turn it off, use a specified website list, disable individual sites, or limit website access in Chrome’s extension settings.
Storage supports local settings and data; scripting and active-tab access support the selection interface and page extraction; context-menu access provides a selected-text action; and side-panel access lets you keep a conversation beside a webpage. These permissions do not authorize Selio to collect unrelated browsing history or send every visited page to an AI service.
8. Chrome Web Store Limited Use
Selio’s use and transfer of user information, including information obtained through Chrome APIs, complies with the Chrome Web Store User Data Policy and its Limited Use requirements.
User information is used only to provide or improve the reading, chat and note features described in this policy. It is not sold, used for personalized advertising, or used to determine creditworthiness. Transfers are limited to providing these features and the exceptions permitted by the policy, such as applicable legal or security requirements. Selio’s developer does not allow people to read extension user data except with specific user consent or as permitted for legal or security reasons.
9. This policy website
This page includes no analytics, advertising trackers, third-party fonts, cookies or browser-storage code. Its language switch operates on this page without saving a preference.
If the page is hosted on GitHub Pages, GitHub may process standard website request information when you visit it, including your IP address. Hosting-related processing is governed by the GitHub General Privacy Statement. Clicking an external link takes you to a service governed by its own policy.
10. Changes and contact
This policy may be updated when Selio’s features or data practices change. The date above identifies the most recent revision. Changes to data use that require additional notice or consent will be disclosed as required.
For privacy questions, support or requests concerning information you have sent to the developer, contact:
zilongzhou.zilong@qq.com