← Visualese

Privacy Policy

Effective August 5, 2026.

Visualese describes a visual that you explicitly select in the browser. It has no Visualese account, advertising system, analytics service, or developer-owned backend.

Data Visualese handles

Visualese does not collect browsing history, page text, form entries, cookies, precise location, financial information, health information, or contacts.

How data is used

Data is used only to return the descriptors you request. Visualese does not sell data, use it for advertising, build profiles, or allow humans to read selected visuals or prompts.

Storage and retention

Selected visuals and generated descriptors exist only in memory for the current page session. Model choice and the optional prompt are stored in chrome.storage.local. API keys are encrypted with AES-GCM using a 256-bit key derived from the user's passphrase with PBKDF2-SHA-256 before they are stored there. The passphrase is not stored. Decrypted keys remain only in trusted-context chrome.storage.session memory while Visualese is unlocked. Websites cannot access either storage area. Users can clear or forget a saved key in Settings; removing the extension deletes its Chrome-managed storage.

Limited Use

Visualese's use of information received from browser permissions complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the extension's single purpose: describing the visual selected by the user.

Changes and contact

Material privacy changes will be disclosed in the extension and this policy before changed handling begins. Email questions to aakankshamirdha@gmail.com or use the public issue tracker, without including API keys or private image content.