Legal
Privacy policy
Aegis is designed as a client-side utility site. Most tool activity stays in the browser, but the site now supports privacy-conscious usage analytics through Pulse.
What this site collects
The toolkit itself does not require account creation and does not intentionally collect form submissions, passwords, or generated results on its own backend.
When deployed, the hosting provider may still log standard request metadata such as IP address, user agent, and request timestamps for delivery, uptime, and security purposes.
Pulse analytics
Aegis can send basic usage analytics to the Pulse collector running on the same device. Before you allow analytics, Aegis only sends anonymous page views in a strict minimal mode. After you allow analytics, Aegis may also send tool navigation and button-click events with anonymous session identifiers so workspace usage can be measured.
Aegis does not intentionally send passwords, raw tool inputs, uploaded file contents, or freeform personal text to Pulse. Tracking payloads are limited to page context, tool identifiers, coarse browser context, and interaction labels.
Local browser storage
Aegis stores your theme preference in localStorage under the key aegis-theme so the interface can remember light or dark mode between visits.
The app also stores favorites, recent tools, saved presets, and recent repeatable states on the current device using the aegis-favorite-tools, aegis-recent-tools, aegis-tool-presets, and aegis-tool-history keys.
If analytics is enabled, Aegis also stores a consent choice under aegis-pulse-consent-choice, an anonymous visitor key under aegis-pulse-visitor-key, and a session identifier in sessionStorage under aegis-pulse-session-id.
Third-party requests
The current frontend loads Google Fonts. Your browser may contact Google font servers to download those font files. If you self-host the fonts later, update this policy to match the deployed behavior.
If you enable the connection speed test, the browser will also send latency, download, and upload requests to the speed test endpoints defined in speed-test-config.json. Those endpoints may be hosted on the same domain or a separate infrastructure provider that you control.
How data is used
- Render and serve the site to visitors.
- Remember the selected theme on the current device.
- Measure high-level usage patterns such as page views, tool opens, and important clicks when Pulse analytics is enabled.
- Support routine security monitoring and operational logging by the hosting platform.
Updates
If deployment behavior changes, including analytics, forms, or additional third-party services, this page should be updated before release.