Search history on this device
Unless enabled, queries live only in the current tab’s memory and disappear when it is closed or reloaded. This setting concerns browser storage only and does not allow server-side analytics or personalization.
Once enabled, the browser keeps up to 10 non-sensitive queries for no longer than 30 days. Queries that look like personal or sensitive information are not added to the history.
Persistent storage is not allowed; tab-memory mode is in effect.
Analytics: what is collected
Only after consent are the cookies pz_v and pz_s created. Viewed paths and the referrer without query/fragment, active time, search and click events, approximate country and city, device type, browser, OS and coarse editor events may be linked to them. Feed reactions and the feed profile belong to the separate personalization category. UTM source/medium/campaign are stored only when they exactly match pre-approved separate allowlists; otherwise the value stored is NULL. The raw IP address and the full User-Agent string are not stored in product analytics; some technical logs may use a time-limited IP hash.
Analytics: why and for whom
The data is needed to diagnose the search, evaluate sources and measure usage. This category by itself does not build a recommendation profile and does not load Yandex Metrica. Metrica requires a third permission and is available only after the legal release flag is enabled. Google Fonts are not loaded: the interface uses the device’s system fonts.
Personalization: a separate profile
Only after separate consent is the httpOnly cookie pz_pv created. Feed impressions and clicks, likes/dislikes, saved models and current model preferences may be stored under this identifier. By default search history exists only in the tab’s memory; storing it permanently requires a separate local setting and by itself does not enable personalization. Local search-history and saved-model terms may be passed in memory to compute a response, but are not stored as a separate hint. Without consent the API uses a shared non-personalized profile, accepts no feed events and reads no local hints; explicitly chosen topics remain ordinary filters.
What revoking Metrica means
After revocation no new connections to Metrica are made, and the JavaScript-accessible Metrica cookies and local keys on the Polyzon domain are cleared. This does not delete data already sent to Yandex or cookies on Yandex domains, which Polyzon cannot access; such requests are handled under the recipient’s rules. Metrica, first-party analytics and personalization are enabled and disabled only by these switches.
Search and external sources
To perform the search you requested, the server may pass the query text to Google Translate, OpenRouter (when enabled), Thingiverse, Cults3D, Printables, MakerWorld, 3DToday and Creality Cloud. These transfers are made to deliver results, not for optional analytics. Do not enter personal or confidential information into the search.
Feedback
The form accepts the message text and a mandatory email only to review the message and reply. Separate consent is required before sending. Its terms are available in a separate document.
Retention period
Analytics records linked to the pseudonymous browser identifier are deleted automatically within 90 days. The recommendation profile uses the same first-party limit. The choice cookies pz_analytics, pz_personalization and pz_metrica are kept for up to one year and contain an independent decision, the text version and the time of the choice. The identifiers pz_v/pz_s and pz_pv are not interchangeable. With the local setting enabled, the browser stores at most 10 queries for up to 30 days; the setting’s version itself is re-confirmed at least once a year.
What the server-side button deletes
The general server-side button sets all three optional categories to declined. Under the current pz_v identifier, analytics page views, searches, clicks and technical events are deleted or unlinked; under the separate pz_pv identifier, feed events, reactions, saved models and preferences are deleted. The cookies pz_v, pz_s and pz_pv are deleted, the Metrica cookies available to the server are cleared, and its tag is no longer loaded. If the identifier has already been cleared, earlier records cannot be found automatically for this browser.
What the server-side button does not delete
It does not delete your account, the account’s collections, local storage, messages sent to support, data held by external recipients, or technical and search caches that are not linked to pz_v/pz_pv. This button is not an account deletion and not a request to delete data held by Yandex. Consent to the processing of a message sent to support can be withdrawn through the operator contact specified in the consent text.
Collections: views and respects
For collections shared by link or published, the number of unique views is counted using a truncated hash of “collection + request network”, without cookies and without an account. The raw IP address is not stored; the deduplication hashes are deleted automatically within 90 days — only the number remains. The author’s own views are not counted. Respects are stored with the account of the person who gave them, are deleted together with it and are included in the data export; the collection’s author sees only the counter, not a list of people.
Local browser data
A separate button clears the local profile cache, the theme, locally saved models, search history, filters, feed settings and reactions, feature-onboarding state and the cache of immutable assets. The service worker does not store HTML pages. The exact list of keys: pz_account, polyzon_theme, polyzon_favorites, polyzon_search_history, polyzon_search_history_setting, polyzon_free, polyzon_sources, polyzon_sources_known, polyzon_feed_reactions_v1, polyzon_feed_survey_v1, polyzon_feed_cats, polyzon_feed_free, polyzon_feed_onboarded, polyzon_pwa_dismissed, polyzon_pwa_engagement, polyzon_tg_dismissed. This button does not end the server session and does not delete your account or server-side analytics.
Browser settings
The service does not process the Do Not Track and Global Privacy Control headers: under Article 9 of Russian Federal Law No. 152-FZ, consent must be specific and substantive, and withdrawal must come from the data subject, whereas a single browser setting applies to all sites at once. Only the switches on this page decide, and the recorded choice works in any browser mode, including a private window. This does not prevent you from blocking and deleting cookies in your browser.
Operator, contact and choice
- Operator: Individual Entrepreneur Artem Andreevich Nikulin (Russia)
- INN 434547133957, OGRNIP 326430000048653
- Registered on 30 July 2026 by the Federal Tax Service Directorate for the Kirov Region
- Postal address for requests: 109 Lenina St., office 1022, Kirov, Russia
Consent can be withdrawn at any time without losing access to the main search. For questions about processing, access, correction or deletion of data, write to privacy@polyzon.org. The policies of external services are available from Yandex, Google, OpenRouter and Telegram.
