General privacy principles
This page contains product-specific disclosures for Asya Coding Software ® browser extensions. Each product has different functions and permissions. Please read the section for the extension you use.
We describe the purposes of data access, retention and sharing for each extension. We do not treat all extensions as having identical permissions or data handling practices. Information here must remain consistent with each extension's published version and its Chrome Web Store privacy declarations.
We may revise this page if an extension's functionality or data practices change. The appropriate product section will be reviewed at the same time.
Asya Clean — Privacy disclosure
Overview: Asya Clean v1.1.0 scans selected metadata and clears selected browsing data locally in Chrome, upon user action. It does not transmit scanned history, download records or cookies to Asya Coding Software servers.
1. What data is accessed?
Browsing history: History entries, including page URLs, titles, timestamps and visit counts, may be read during a user-initiated scan.
Download history: Download record fields, such as source URLs, timestamps, state and MIME type, may be read during a scan. The extension does not read downloaded file contents.
Browsing data categories: On user request, Chrome's built-in API removes the selected cache, cookies, history, download history, form data or site storage categories.
Local preferences: Language, theme, time range and selected data categories are saved using Chrome extension local storage.
2. Why is this information used?
The scanner counts accessible history and download records and estimates the size of those records' metadata. KB/MB values are metadata estimates, not actual cache size or disk space that will be recovered. Cleaning is executed only after the user selects data categories and confirms the operation.
3. Storage, transfers and sharing
Scan results are temporary within the extension popup. The current v1.1.0 does not submit scanning records, site data or cookies to developer-operated servers. No advertising trackers or external analytics are included in this version. Local preferences remain in Chrome storage until changed or removed according to the browser's behavior.
4. User controls and important limitations
Users can start a scan, select a time range and choose what to clean. Deletion cannot be undone; removing cookies may sign users out. Removing download history does not delete local files. Saved passwords are not deleted by this extension.
5. Chrome permissions
- browsingData: Clear selected browsing information through Chrome APIs.
- history: Count and estimate metadata for visited-page records.
- downloads: Count and estimate metadata for download records.
- storage: Save UI and cleaning preferences locally.
This section is based on the Asya Clean v1.1.0 implementation. Update it before releasing any version with different data behavior.
QR Atelier — Privacy disclosure status
QR Atelier lets users turn text and links into QR codes, preview designs and download the resulting codes.
Verification required: Before using this page as QR Atelier's Chrome Web Store privacy URL, review the exact published extension package to verify whether input data is retained, transmitted, or shared; whether any analytics or external assets are used; and the exact permissions requested. Those details have not been independently confirmed in this website package, so no unsupported data-collection promises are made here.
Until the audit is complete, the QR Atelier listing should retain its existing accurate policy, if any, or be updated with a verified, product-specific disclosure.
