Privacy Policy
Local processing. No AnyServ servers.
AQR (Advanced QR Generator) processes your QR codes and scans on your device. We do not receive your generated content, scan results, or form data on AnyServ servers. This document covers the AQR Chrome extension and, in a separate section, the anyserv.eu website and API.
Last updated: May 23, 2026 · Version 1.1.1 · Manifest V3
Quick summary
AQR extension only (not the website/API – see section 10):
| Topic | Status |
|---|---|
| Data sent to AnyServ servers | NO |
| Analytics / telemetry in extension | NO |
| User account / login / newsletter | NO |
| Personal data sold to third parties | NO |
| Extension cookies | NO |
| Content scripts / background page reading | NO |
| Local storage on your device | YES |
| Chrome settings sync (via Google) | OPTIONAL |
| Active tab URL/title (user action) | LIMITED |
| Fetch image for context-menu scan | LIMITED |
Scope & data controller
Data controller: AnyServ (anyserv.eu), contact: anyserv.eu/contact.
This policy applies to the AQR – Advanced QR Generator browser extension distributed via the Chrome Web Store. It does not replace the general Privacy Policy for anyserv.eu, which covers the website, cookies, and other services.
The extension generates and scans QR codes entirely in your browser using local libraries (jsQR, QR
generator). Verified in source code: the extension makes no calls to
anyserv.eu/api endpoints.
Data you enter
Depending on the QR mode you choose, you may enter data such as:
- URLs, plain text, email addresses, phone numbers
- SMS and WhatsApp message content
- WiFi network name (SSID) and password
- vCard contact fields (name, phone, email, organization, etc.)
- Results of scanned QR codes
- Optional logo image (PNG/SVG converted to a data URL for QR styling)
This content is processed locally to render or decode QR codes. It is not uploaded to AnyServ. Because you may enter sensitive information (e.g. WiFi passwords), we recommend using the extension only on devices you trust.
There is no registration, login, newsletter signup, or in-extension contact form – only optional links that open external pages in your browser.
Local storage
AQR stores data in Chrome extension storage and, for color presets, in extension-origin
localStorage. Nothing is written to a database on AnyServ servers.
| Storage | Key / area | Contents |
|---|---|---|
chrome.storage.sync |
qrSettings |
Theme, language, default QR options, toggles (history, session persistence, context menu, etc.). If Chrome sync is enabled, Google may sync these settings across your signed-in devices – this uses Google's infrastructure, not AnyServ servers. |
chrome.storage.local |
qrHistory |
Up to 10 recent entries: QR text, type, thumbnail (data URL), timestamp – device only. |
chrome.storage.local |
qrSession |
When "Persist popup session" is enabled: full popup state (text, presets, WiFi/vCard fields, colors/logo options) – device only. |
chrome.storage.session |
Context menu handoff | Short-lived: contextMenuText (selected text or link) and contextMenuScanUrl (image URL for scan). Cleared after use. |
localStorage |
aqrRecentColors:dark / :light |
Up to 6 recent custom colors per theme field – extension origin only. |
System clipboard: When you copy a QR image or scan result, the Clipboard API writes to your OS clipboard locally. No server involved.
Deletion:
- Clear history from the extension UI.
- Disable history or session persistence in settings.
- Uninstall the extension – removes all extension
chrome.storagedata for AQR.
Browser permissions
AQR uses Manifest V3 with no content scripts and no broad host permissions. The extension does not read page DOM or track browsing in the background.
| Permission | Why it is needed |
|---|---|
storage |
Save settings, optional history, optional session state, and context-menu handoff data. |
contextMenus |
"Generate QR for selection/link" and "Scan QR from image" – only after you use the context menu. |
activeTab + tabs |
Read the URL and title of the active tab when you open the popup or click "Current page" (chrome.tabs.query). Used only on user action. |
AQR does not request cookies, scripting, alarms, or
<all_urls> host access.
Network & third parties
No AnyServ backend: The extension does not send your QR content, scans, or settings to AnyServ. There is no analytics, advertising, or error-reporting SDK in the extension code.
Context-menu image scan
When you choose "Scan QR from image" on a web image, the extension may fetch that
image URL in your browser, decode it locally with jsQR, and discard the fetch result. The image is
not uploaded to AnyServ. The fetch may fail due to CORS or site policies – in that case
scanning may not work for that image.
Links you open (standard browser navigation)
Clicking these leaves the extension; their privacy policies then apply:
- anyserv.eu (landing, tools, contact)
- ko-fi.com/anyserv
- Other AnyServ tools linked from the "More Tools" tab
- URLs decoded from scanned QR codes (
window.open)
Open-source libraries
Bundled at build time and run offline in your browser:
- qrcode – QR code generation (SVG/PNG)
- jsQR – QR decoding from images
- React – popup UI
These libraries do not phone home or connect to their authors at runtime.
Your rights & control
Under GDPR and similar laws, you may have rights to access, rectify, or delete personal data. For AQR:
- Access / export: View history and settings inside the extension; data stays on your device.
- Delete: Clear history, turn off persistence options, or uninstall the extension.
- Object / restrict: Do not use optional features (history, session save, context menu).
We do not hold a copy of your extension data on our servers, so there is nothing for us to delete on the backend. For questions, contact us (see Contact).
We do not sell or share your personal data with third parties for marketing.
Google & Chrome Web Store
Installing and updating the extension through the Chrome Web Store is handled by Google. If you use Chrome
sync, Google may synchronize chrome.storage.sync settings across devices according to
Google's Privacy Policy.
AnyServ does not receive that sync data.
anyserv.eu website & API
Important: The AQR extension works offline and does not use AnyServ APIs. Web tools on anyserv.eu are separate. If you use online QR or WiFi generators at anyserv.eu, different processing applies.
API endpoints
Server routes such as /api/qr/* and /api/wifi accept parameters in the query
string (e.g. data, ssid, password) to generate QR images server-side.
Those values may appear in web server or proxy access logs (along with IP address,
User-Agent, timestamp). The API code does not persist them in an application database, but hosting logs
may retain them for a limited time depending on infrastructure configuration.
Rate limiting
API requests are rate-limited by IP address (approximately 30 requests per minute; IP held in server memory for about one minute). This is abuse prevention, not user profiling.
Website cookies & hosting logs
The anyserv.eu website may set cookies (e.g. consent, analytics, CDN) and generate standard access logs (IP, date/time, URL, referrer, User-Agent). Details are in the site Privacy Policy and Cookie Policy.
Children
AQR is a general-purpose utility, not directed at children under 13 (COPPA) or under 16 where GDPR-K applies. We do not knowingly collect personal data from children through the extension.
Contact & changes
Privacy questions → anyserv.eu/contact
We may update this policy. The "Last updated" date at the top will change; material changes may also be noted in the Chrome Web Store listing or extension release notes.