Your clock & preferences
The clock reads your device time zone. Wallpaper, clock format, weather units, quick links and your selected weather area are stored locally in this browser. No account is required.
PRIVACY, EXPLAINED
Your trust deserves
more than a promise.
Practical controls. Clear limits. Evidence you can read. CAQA’s security direction is built around making browser boundaries easier to understand.
The website features below are available now. The desktop security controls marked as development work are still being tested and may not be included in a staff preview. CAQA does not claim to be more secure than every other browser.
Review dated test evidence →THE WEB EXPERIENCE
Know what leaves
your device.
The website and the desktop browser have different responsibilities. Here is how the web start page and local manifest reviewer handle your interactions.
Your weather
The start page can request a forecast for a city suggested from your time zone. This is an estimate, not detected location. Device location permission is requested only when you choose “Use my location”. Coordinates are rounded before forecasts are requested through CAQA’s weather service using MET Norway data. You can turn Local weather off in the web start page’s Personalise panel to stop forecast requests. Normal network requests expose your IP address to the receiving server.
Your searches & links
Submitting a web start-page search sends it to DuckDuckGo. Opening a shortcut or an official extension marketplace takes you to that provider; their terms and privacy policy apply.
Your extension manifest
The marketplace reviewer reads or parses your selected manifest in this page’s memory. It does not upload, save or install the extension. A declaration review cannot establish that extension code is safe.
Website measurement
The product pages do not include advertising or analytics scripts. Web servers still receive standard request information necessary to deliver pages and respond to requests.
THE DESKTOP SECURITY DIRECTION
Boundaries that
have a purpose.
Current security fixes
Track upstream releases and measure time to CAQA deployment. Version numbers alone cannot prove that an engine includes every security fix.
Verified updates
TUF-based update tooling checks signed metadata, expiry, integrity and rollback rules. Trusted publisher signing and public deployment tests remain required.
Extension boundaries
Development controls limit default site access and require approval in protected workspaces. An approved extension still has the powers you grant it.
Separate sessions
Client profiles keep browser sessions separate. They do not isolate you from malicious software with access to your Windows account.
Site exceptions
Filtering exceptions are scoped to a specific site and deliberately reduce filtering there. Use an exception when you understand why the site needs it.
Constrained AI
Privileged inherited AI services are disabled in development source. Ordinary AI websites receive the content you choose to submit under their own policies.
MEASURE WHAT MATTERS
Transparency
over security scores.
Our evidence page records test scope, timestamps, dependency findings and the remaining release gates. It does not award a made-up safety rating.
See security & release evidence ↗Independent assessment
An external security assessment has not yet been commissioned. Internal reviews and automated tests are not independent certification.
Production readiness
Publisher signing, clean Windows installation and verified update/recovery behaviour remain required before a public browser release.
Report responsibly
Staff testers should send a minimal reproduction to their CAQA test coordinator. Do not include passwords, client data or complete browser profiles.
What to include in a report →