Starizon runs in your browser and can read the pages you work with. This page explains, feature by feature, where your data goes: what stays in your browser, what passes through our servers, and which other services receive it.
It is a plain-language companion to our Privacy Policy, which covers the same practices along with your rights and our company details.
1. The short version
- Pages are read when you ask. Starizon reads a page when you make a request, or when a schedule or monitor you created runs. It does not collect your browsing history.
- What you save stays in your browser. Your Knowledge Base, Spaces, chat history, replays, schedules and monitor snapshots are stored by the extension on your device.
- Our servers forward, they do not store. When a request goes through our servers, it is passed on to the service that answers it. Our servers do not keep a copy of the request content or log it.
- Included models run with zero data retention. The model provider does not train on your request and does not keep it.
- Your own key goes direct. With your own API key, requests go from your browser to your provider. The key stays in your browser.
- No selling, no advertising. We do not sell your data or use it for ads.
2. Pages and tabs
Page questions, summaries, extraction and Agent S6 read the pages involved in your request: the page you are on, the tabs you add, or pages that Agent S6 opens while it works. Agent S6 also uses screenshots and the structure of the page to decide where to click and type. The text and images a request needs are sent to the model for that request.
Tab actions such as grouping use tab titles and addresses, and the details needed for the request are sent to the model. Our servers do not store the page content sent for these tasks or keep a record of the sites you visit. The extension can keep page snapshots and task materials locally in your browser.
3. Things you save
These are stored in your browser's local storage. Our servers do not keep copies of them. Parts of them go into a request only when that request needs them.
- Knowledge Base. When you save a page, its full text is written to your browser's local database. That is how pages behind a login can be saved, and why answers can quote the version you saved after the live page changes. Search across your Knowledge Base runs in your browser, and the matching passages are sent with the request.
- Spaces and chat history. Your conversations and the material you add to a Space are kept in your browser so you can continue a project later.
- Files. Files you add are read in your browser, and their content is sent with the requests that need it.
- Bookmarks. Starizon searches titles, addresses, folders and saved dates in your Chrome bookmarks. When you ask, it can add bookmarks, create folders and move existing bookmarks to a folder you choose. It does not rename or delete existing bookmarks. Your bookmarks stay in Chrome, and the details a request needs are sent to the model.
- Replays and scheduled tasks. Saved runs, their steps and recent results are stored so a workflow can be repeated and reviewed.
- Monitors. Recent checks keep an image of the watched area, so you can see what the monitor saw when it fired.
- Settings and API keys. Keys you add are stored in your browser and are not sent to us.
You can delete saved items one at a time or in batches in the extension. There is no button to clear everything at once yet. To remove all local data, uninstall the extension or clear its data in your browser settings. We do not have a copy, so deleted data cannot be recovered.
4. AI models
- Models included with Starizon. Your request goes from the extension to our servers, then through Vercel AI Gateway to the provider that runs the model you selected. Our servers forward the request and the response without storing or logging them. The request uses zero data retention, so the provider does not train on it and does not keep it.
- Your own API key. Requests go directly from your browser to the provider or custom endpoint you set up, under your own account. They do not pass through our servers, and the provider's terms apply.
- No training. We do not use your prompts, pages, files or results to train or fine-tune models.
5. Web search and deep research
- Web search. Searches made for you go through our servers to Parallel. The search query can include details from your request.
- Deep research. A deep research task runs at Parallel. Its progress is kept partly in your browser and partly at Parallel, so the task can continue after you close the panel. Parallel states that it does not train on customer data. How long it keeps task data is set by Parallel's own policies.
- Your own search service. If you add a search provider with your own API key, searches go directly from your browser to that provider.
6. Voice input
When you dictate, your audio is sent to Soniox to be turned into text, either directly from your browser or through our servers, which forward it without storing it. Our servers do not store your audio or the transcript. Text you send in chat can be saved in your local chat history.
7. Alerts and notifications
- Browser notifications are shown on your device.
- Email alerts are passed by our servers to Resend for delivery. Our servers do not keep a copy. Your email provider keeps the message like any other email.
- Phone alerts are sent to the ntfy server you choose, either the public ntfy.sh service or your own. We do not run a push server.
- Webhooks are sent to the address you set.
Deleting a schedule or monitor does not remove alerts that were already delivered.
8. Connected apps and MCP servers
When you connect an app such as Gmail, Google Sheets or Notion, the sign-in is handled by Composio. Composio keeps the app's access tokens encrypted with AES-256-GCM, using keys held in AWS KMS, and is SOC 2 Type II attested. When you disconnect an app, its authorization is revoked.
MCP servers you add are contacted from your browser. When you ask Starizon to send something to an app or an MCP server, that is the point of connecting it, and what you send is then governed by that service's terms. Connections are optional, listed in the panel, and can be removed at any time.
9. Account, credits and purchases
- Account. Signing in creates an account record with your email address, your plan and your credit balance, stored with Supabase in the United States.
- Without an account. Anonymous use has the same limits and privacy practices as the Free plan, and our servers do not store your request content.
- Credits. We count the credits each request uses to update your balance. We do not keep a log of individual requests.
- Purchases. Payments are handled by Stripe, and we do not see your full card number. We keep purchase and refund records for six years for tax and accounting.
10. Our website
Our website uses necessary cookies to keep you signed in, and a referral cookie when you open a referral link. Google Analytics 4 runs only if you accept analytics cookies, and you can change that choice at any time using Cookie settings in the footer. We do not use advertising cookies.
11. Extension permissions
The extension requests access to all websites because an assistant that can only read some pages would fail on the rest. You decide which page it works on by asking. This access is what lets the extension read the tab in front of you when you ask, and it is not used to gather your browsing history.
You can review or remove permissions in your browser's extension settings, limit the extension to specific sites, or uninstall it at any time.
12. Changes
As features change, this page changes with them. Updates are reflected in the date at the top, and significant changes are announced as described in the Privacy Policy.
13. Contact
Questions about any of the above, including how a specific feature handles a specific kind of data:
Starizon Ltd
Email: support@starizon.ai
Website: https://starizon.ai