Privacy Policy — RavionX DevKit

RavionX DevKit processes developer payloads locally in your browser. The extension does not upload tool inputs, outputs, page text, history, or preferences to RavionX or third parties. It includes no analytics, advertising, tracking, authentication, or remote executable code.

Website and Web Tools Lite

This policy describes the extension below. Web Tools Lite runs a smaller set of tools locally on this website. It does not save payload history or use extension permissions, session handoffs, or page capture. Inputs and outputs remain in page memory until cleared or the page is closed; browser form restoration may restore text. The site includes no analytics, tracking scripts, or automatic tool-payload uploads. Hosting providers receive ordinary page requests and may retain standard connection/access logs; visiting the site is distinct from processing tool payloads. Clipboard copies remain under your control.

Data you choose to process

The tools access text you enter, files you choose to import, and text you explicitly select for the context-menu formatter. Outputs can contain the same confidential information as inputs. Copy and download actions write the chosen output to your clipboard or a local file; the extension does not read your clipboard.

Optional local history

History is off by default and requires opt-in in Settings. When enabled, history stores the tool name, action title, full input, full output, a random identifier, and a timestamp in chrome.storage.local. History is limited to 50 entries, 64 KiB per entry, and 1 MiB in total; older entries are removed as limits are reached. Entries have no time-based expiration.

Both inputs and outputs are checked for common sensitive fields and values before saving. Detection is best-effort, can miss sensitive information, and is not a guarantee. Keep history off for confidential work. Large entries are not saved. Turning history off deletes saved history and prevents future history writes. You can also delete individual entries or clear all history in Settings. Upgrades from the earlier automatic-history policy delete legacy history and require fresh opt-in.

Context-menu actions and temporary data

No page text is captured on ordinary right-clicks. After you choose “Format with RavionX DevKit,” Chrome supplies your selection. If no selection is available, an action-time script can read selected text in a permitted text control, a JSON-looking active text control, a single code block, or a JSON response body. Password fields and controls identified as sensitive are excluded from this fallback. Arbitrary page bodies are not read for this action.

Chrome does not provide the clicked DOM element for an action-time script. Select code/text before choosing the menu item for reliable capture; an unselected nearby code block in a mixed-content page is not captured. Restricted Chrome pages may require copying and pasting manually.

Context payloads are limited to 1,000,000 characters and transferred using opaque random IDs, never payload-bearing URLs. They are stored only in chrome.storage.session, accessible to trusted extension contexts. They expire after two minutes, are removed after one consumption or a failed open, and expired/abandoned payloads are cleaned on access, worker startup, and a periodic alarm. Physical deletion can be delayed while Chrome is suspended. Session storage is cleared when the browser session ends or the extension is reloaded, updated, or disabled. At most four pending payloads and a 4 MiB serialized payload budget are retained.

Optional JSON-page detection and website access

JSON-page detection is off by default. Enabling it requests optional access to HTTP and HTTPS websites. On subsequent page loads, the local helper inspects JSON response pages or pages containing a single code block, up to 1,000,000 characters and bounded nesting. It offers user-triggered beautification or opening in the formatter. No network transmission is performed. Disabling it unregisters future injection, removes existing helpers, and removes that optional website access. Browser restrictions may prevent injection on some pages.

Other storage and permissions

Preferences and welcome state are stored locally, without browser synchronization. Storage is not application-level encrypted. The extension uses contextMenus for the explicit formatter action, activeTab and scripting for action-time capture and the optional helper, sidePanel for the tool UI, storage for local preferences/history and session handoff, and alarms for expired-payload cleanup. The extension does not read cookies or browsing history.

External links and recipients

Feedback, homepage and support links open RavionX websites. Those sites receive normal navigation requests and apply their own policies. The extension does not automatically attach tool payloads to those requests. Do not include secrets or customer data in feedback. There are no automatic third-party recipients of tool data.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the disclosed local developer-tool functionality; it is not sold or used for advertising, creditworthiness, or unrelated purposes.

Deletion and contact

Use Settings or individual history controls to delete history. Uninstalling removes extension storage. Downloaded files and clipboard copies are under your control and are not deleted by clearing extension history. For privacy questions contact [email protected] or use the support page.

Last updated: November 1, 2026.