Privacy Policy
Clareou — by Revvo Technology. This policy covers the demonstration website and Clareou extension version 0.3.0. Updated September 21, 2026.
Purpose
The extension generates and fills fictional form data for tests and demonstrations. Page context is processed to perform the filling requested by the user. The current version is not presented as a validated solution for clinical or other sensitive information.
Settings and API keys
Provider, model, endpoint URL, API key, instructions and preferences are stored in the browser using storage.local. We do not use storage.sync to synchronize these settings. The key is sent to the configured endpoint to authenticate requests. The extension does not add its own encryption to the locally stored key. Protect your device and browser profile.
Page data sent to AI
When you request filling, the extension reads visible editable fields and their context: labels, types, options, constraints, existing values, page title and URL, description, headings and other form context. This information and your instruction are sent to the configured provider. URLs may contain parameters. Preserving existing fields prevents overwriting their values; it does not prevent sending those values as context.
Visual capture and sensitive information
In visual capture mode, an image of the visible area of the tab is also sent. It may include names, messages, location, health or financial information and other content displayed on screen. Some sensitive field values are filtered by field type or name, but comprehensive removal is not guaranteed and screenshots are not automatically anonymized. Use fictional information and review the page before starting.
Recipients and external processing
Requests go directly from the browser to OpenAI, Anthropic, Google Gemini or the compatible endpoint you configure. The extension does not route this content through a Revvo Technology AI server. The endpoint receives the key, request content and technical connection metadata. Retention, processing locations and service data use depend on the selected provider, account settings and terms. We do not promise zero retention or no training use across all custom endpoints.
Connection security and testing
Remote endpoints must use HTTPS. HTTP is accepted only for localhost and supported loopback addresses for local services. Testing a connection sends a test instruction and credentials to the endpoint without extracting a form or capturing the tab for that test. API keys are not sent to the demonstration website.
Retention and deletion
Local settings remain until changed, cleared with extension data or removed by uninstalling. Operation data and undo state are held in memory; the extension does not maintain a persistent history of filled forms. Uninstalling does not delete content already transmitted to a provider or changes saved by a destination website. Revoke keys in the provider dashboard and contact the relevant service about retention or deletion of transmitted data.
Permissions and user control
Version 0.3.0 requests activeTab, scripting, storage, sidePanel and broad host access. Content scripts are available on HTTP/HTTPS pages; form extraction starts when filling is requested. The extension does not read the full browsing history, log keystrokes or mouse movements, or include advertising trackers. You can stop using it, restrict site access in browser settings or uninstall it.
Demonstration website
The website demo runs locally in the browser without AI requests, registration or storage of entered text. We have not installed advertising tools. To measure the audience we use Google Analytics 4 and Vercel Web Analytics, which collect aggregated browsing data such as pages visited, referrer, device type and approximate location; Google Analytics may use cookies for this, while Vercel Web Analytics works without cookies. Hosting provider Vercel may process technical access data such as IP addresses, requested URLs and logs required for delivery and security, under its policies.
Limited Use
Use and transfer of data obtained through Chrome APIs are limited to the stated purpose and requested features, in accordance with the Chrome Web Store User Data Policy, including Limited Use requirements. We do not sell this data, use it for personalized advertising or creditworthiness decisions, or transfer it for purposes unrelated to filling forms. The current version does not make form content available for a Revvo Technology team to read.
Contact and updates
Revvo Technology is the brand responsible for Clareou. For support or privacy questions, use the developer contact email displayed on the official Clareou Chrome Web Store listing when published. Do not include API keys or sensitive page content in support requests. This policy will be updated when data practices change; its date appears above.