SQD Intelligence Briefing

1.0 General Data Isolation

This service operates on a data-isolation baseline: no accounts, no user profiles, no behavioral datasets. The only data processed server-side are basic access parameters — request paths, timestamps, response codes, and originating IP addresses — retained solely for technical validation and security parsing: diagnosing faults, measuring load, and detecting abusive traffic.

2.0 Local Storage & Preferences

Interface preferences such as the Light/Dark UI mode, and your Saved Articles list, are stored exclusively in your browser's localStorage. Both are device-local: there is no account, this data is never transmitted to our servers, and it can be cleared at any time through your browser settings.

3.0 Analytics

Where enabled, this service uses Google Analytics to measure aggregate traffic. A short banner shown on your first visit asks for consent before any analytics storage or cookies are set; declining keeps analytics storage denied under Google's Consent Mode. Your choice is remembered in your browser and can be changed at any time through Manage Cookies in the footer. Google's handling of any data this collects is governed by Google's own privacy policy.

4.0 Advertising

Where enabled, this service displays ad units served by Google AdSense on browsing and article pages — never on this page or the About, FAQ, Terms, or Contact pages. Ad-related storage and personalization are gated by the same Google-certified consent management platform described above, and default to denied until you consent; declining, or later reopening your choice through Manage Cookies in the footer, keeps ads non-personalized. When permitted, AdSense may use cookies or device identifiers to select and measure ads, per Google's own advertising and privacy policies. We do not control, and are not privy to, the data Google collects through those ad units.

5.0 Contact Form Verification

Where enabled, the contact terminal uses Google reCAPTCHA to screen automated submissions. Completing the challenge sends data to Google for verification, governed by Google's own privacy policy; this only runs at submission time and is not used for tracking elsewhere on the service.

6.0 Contact Submissions

Messages sent through the contact terminal (sender designation, inquiry domain, and message body) are relayed to our inbox by email and logged for triage and follow-up only. They are not shared with third parties beyond that transmission.