EN
NaviCube · Antho
Antho Privacy Policy
1. Scope and our commitments
This policy covers the Antho browser extension and standalone navigation pages it generates. It explains how information is handled when you use their features. NaviCube, the Antho developer ("we", "us"), is the personal-information handler. Antho requires no account and provides no developer-operated workspace cloud sync.
We do not sell or rent user data or use it for advertising, profiling, credit decisions, or purposes unrelated to your selected features. The extension contains no tracking SDKs or behavioral analytics. Workspace and session records stay on your device by default; only the network features described below transmit the information they need.
2. Information we process and why
2.1 Workspace content and settings
To provide navigation, editing, search, display, and backups, Antho stores pages, categories, site names and URLs, icons, widgets, notes, tasks, appearance, search and export settings, consent records, caches, and task state in extension-local storage. Images and wallpapers use a separate local image store. Widget editors in the side panel share this data with the new-tab page and do not automatically read the adjacent webpage.
2.2 Bookmarks and quick-add
Clicking toolbar quick-add reads the current tab title and URL. When you initiate bookmark import and grant permission, Antho reads titles, URLs, and folders from the current browser profile and converts them into local records. It does not modify bookmarks or continuously read them in the background.
2.3 Open tabs and saved sessions
After you grant optional tabs access, Antho reads tab titles, full URLs, window membership, order, and pinned state in normal, non-incognito windows while the Current tabs list is open and the page is visible, for display, organization, and manual saving. Automatic snapshots are off on new installations; permission alone does not enable them. If you enable them separately, the extension reads this information in the background at your chosen interval and browser startup, saving changed sessions and timestamps. Existing or imported preferences may remain, but reading still requires permission. Snapshots and Later items stay in extension-local storage within the same browser profile; they are not sent to the developer or AI or browser-cloud-synced.
Antho does not request browser history permission or read page bodies, forms, cookies, or website storage. Incognito windows, browser-internal pages, and extension pages are excluded from session records. Full URLs may contain query parameters or sensitive information. Session records are not encrypted by the Security password; review backups before sharing them. Session icons use the browser favicon service with a built-in fallback; these URLs are not sent to a third-party icon service.
2.4 AI configuration and requests
AI is off by default. If you choose to use it, Antho stores the provider type, HTTPS endpoint, model, API key, and connection capability information encrypted locally. Saving new configuration or testing a connection sends small test prompts and credentials to the selected endpoint. Smart organization sends locally cleaned titles, hostnames, path keywords, source folders, and limited title evidence; content generation sends your topic and details. Requests go directly to your configured service without an Antho relay. The provider may retain and use this data under its policy.
2.5 Location and weather
Weather requests device location only after you choose Use current location or Relocate and consent. It does not perform continuous or background location monitoring. Coordinates are rounded to two decimals before storage or transmission. A place label, time zone, and weather cache are stored locally; accuracy, altitude, speed, and movement history are not retained. Open-Meteo receives coordinates for forecasts. BigDataCloud receives only newly acquired coordinates for a city label, never automatic requests for saved or imported coordinates. Once Weather is enabled, saved coordinates may be used to refresh forecasts; the cache is normally refreshed after two hours.
Antho does not request names, health, financial, payment, or personal-communication information. If you choose to enter it in notes, tasks, URLs, searches, or AI prompts, it is handled as part of that content. Provide only information needed for the feature.
3. Data transfers and recipients
Requests go directly from your device to the addresses below, without a workspace-sync or AI relay server. Features run after their in-product consent and required permissions are obtained. Once enabled, they may continue catalogue checks, weather updates, or wallpaper rotation you configured. Turning a feature off stops its updates; revoking origin access blocks requests that need it. Search and opening sites are browser navigation.
| Recipient / feature | Data sent | When and why |
|---|---|---|
asd.li recommendations | Ordinary transport metadata; not saved links, searches, or usage records | After recommendations are enabled, to update catalogue and icons; later checks are at most every three days |
favicon.im, a.favicon.im | The public hostname from the link you entered and transport metadata; intranet, local, loopback and private IP addresses are not sent | When you actively choose an online icon, to download and cache it locally |
picsum.photos, fastly.picsum.photos | Wallpaper seed, requested size, transport metadata | When you select or rotate a Picsum wallpaper |
uapis.cn | Date, resolution, transport metadata | When you select Bing daily wallpaper |
api.open-meteo.com | Two-decimal coordinates, forecast parameters, transport metadata | To fetch weather when adding or refreshing Weather |
api.bigdatacloud.net | Newly acquired two-decimal coordinates and transport metadata | Once after location, to obtain an approximate city name; never automatically for stored coordinates |
| Selected search service | Your submitted search query and transport metadata | When you submit a search or invoke a configured search shortcut |
| Your configured AI HTTPS endpoint | API key, model, and text required by the requested task | When saving/testing configuration or actively running an AI task |
| A site you start checking | The request for its full URL and transport metadata | After confirmation, limited HEAD and, if required, GET checks; page content is not parsed. Intranet and local addresses are not checked and are marked as not checked |
| Your chosen HTTPS image server | Full image URL and transport metadata | Downloads the icon when saving a custom image; no request while typing |
| asd.li: exported default wallpaper | Image request and transport metadata | When a standalone exported page using the default wallpaper opens; the extension’s first-run default wallpaper is packaged locally |
Transport metadata can include public IP address, receipt time, request host and path, response status, and browser/OS headers such as User-Agent, Accept, Accept-Language, Origin, and Sec-Fetch-*. Extension-managed data requests use credentials: omit and referrerPolicy: no-referrer, so it does not attach browser cookies, HTTP credentials, or a referrer. An AI authorization header contains only the credential you configured. Third parties process data under their own policies and may be outside your country; review their terms before enabling a feature.
Custom image URL: HTTPS only. No request is made while typing. Saving contacts that image server with the full image URL to download and store the icon locally, without cookies or referrer.
Online-icon consent is requested once, with the same disclosure in the toolbar and sidebar, and is shared by both. Once granted, selecting online icons downloads them directly while browser permission remains granted.
4. Browser permissions and consent
Some permissions are declared at installation; optional permissions are requested when you use the relevant feature. Refusing or revoking optional access prevents dependent features from working but does not itself delete existing local data. Declaring location permission does not start location automatically.
- Optional
tabs: reads titles and URLs in normal windows to manage and save sessions; automatic collection is enabled separately. favicon: displays icons for Current tabs, snapshots, and Later through the browser’s favicon service. Loading failures use a built-in icon. Antho does not send these URLs to a third-party icon service.alarms: schedules automatic snapshots only when enabled and tabs access is granted, and hourly local expiry cleanup even when automatic snapshots are off. Cleanup does not read open tabs or send network requests.storage: saves workspace, settings, caches, and AI configuration locally.activeTab: after you click the extension button, reads the current tab title and URL to quick-add it.sidePanel: opens widget editors without reading the adjacent page.geolocation: provides weather only when you choose current location; it does not continuously locate you.search: passes a query to the browser default provider only when you submit it.- Optional
bookmarks: reads bookmarks only when you initiate an import. - Optional
http://*/*andhttps://*/*: requested at runtime only for an exact origin needed by a network feature, a configured AI endpoint, or a user-started link check.
5. Retention and deletion
Workspace content and settings normally remain until you edit, delete, reset, clear extension storage, or uninstall. Manual snapshots and Later items remain until deleted. Automatic snapshots are kept for 30 days by default; you can change this in settings. Safety snapshots created before restoration also have retention and count limits. Turning automatic snapshots off or revoking tabs access stops future automatic collection, but does not immediately delete all existing records. Expiry cleanup continues without reading current tabs or making network requests. Insufficient space may pause automatic collection or prevent additions.
Turning off recommendations stops catalog refresh and revokes its consent and origin access; cached data can remain until removed. Locking local protection clears the session master key but retains the encrypted AI record for the next unlock; removing AI configuration deletes that encrypted record. Wallpaper cache keeps only current and previous copies within a size limit. Third-party retention is governed by each recipient.
6. Information security
AI configuration and API keys are encrypted locally with AES-GCM. The Security password is neither stored nor transmitted; it protects the local encryption key. After unlocking, the key remains only in access-restricted browser session storage and is cleared on locking or fully closing the browser. Setting a Security password does not encrypt all other workspace data, session records, images, or backups. Protect your device, browser profile, and exported files.
Executable code is packaged with the extension; it does not execute remote code. Network services and configured AI, image, and search endpoints use HTTPS. Sites you explicitly save with HTTP still use HTTP when opened or checked and are not protected by HTTPS. Access restrictions, input validation, request timeouts, and response limits reduce risks but cannot remove risks from malware, loss of device control, or third-party services.
7. Your choices and rights
You can view, edit, export, or delete workspace data in Antho, disable network features, remove AI configuration, or manage optional bookmark, tab, and site access in browser settings. Revoking tabs access switches automatic snapshots off. Snapshots and Later lists can be deleted or cleared separately; resetting a navigation page does not clear global sessions. Uninstalling or clearing all extension storage removes local data, but not exported files or information already received by third parties.
Complete JSON backups include session records and settings, but exclude AI configuration and API keys. Exported navigation pages and backups may contain your content and full URLs; review them before sharing. Opening or restoring a website may send normal browser requests and existing cookies to that site. The cookie-omission and no-referrer measures in this policy apply only to extension-managed data requests.
If you contact us, we receive and use your email address, submitted content, and attachments to respond to your support request. We do not hold the workspace or session data on your device and normally cannot retrieve or delete it remotely. Contact us below for guidance or privacy questions.
Minors must use Antho with a guardian. A guardian must review notices and provide required consent before a child under 14 enables location, AI, or other network features.
8. Limits on information use
We use information received through browser extension APIs only to provide or improve Antho's disclosed single purpose: a local-first new-tab navigation workspace and its user-facing organization, search, display, backup, weather, optional AI, and link-maintenance features. We transfer user data only when necessary for a feature the user invokes and only to the recipient disclosed in section 3. We do not use or transfer it for personalized, retargeted, or interest-based advertising; data brokerage or resale; creditworthiness or lending; or any unrelated purpose.
No developer-operated server receives workspace or AI data, so our personnel cannot read it. If a user voluntarily includes specific data in a support request, people may read only that submitted data as necessary to provide the requested support, protect security, or comply with law.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
9. Changes and contact
We update this policy when features, permissions, recipients, or law change and provide prominent notice where required. New processing that needs consent starts only after consent. Personal-information handler: NaviCube (Antho developer).
Privacy, support, and security contact: snodgrassmupzbm@gmail.com
This policy applies together with the Antho User Agreement.