Cookie Policy
Effective date:
Public website application
Digital Magnet Corporation operates the public website at https://securityfuse.com.
The current public-site application sets no cookies and uses no analytics, advertising pixels or visitor-tracking integrations. Browsers may still hold old _ga and _ga_* analytics cookies on the parent domain from the retired website until they expire or are cleared; the current website and app do not use them.
The public-site application does not load the product authentication widget.
The beta-access email link opens your email client instead of submitting a form to a site backend.
Delivery infrastructure and logs
IONOS hosts securityfuse.com in the United States; Cloudflare provides DNS. Our hosting providers can process connection and diagnostic information separately from the website itself.
The current public-site application sets no cookies. Product and provider authentication storage is described separately below; existing cookies in a browser are not necessarily set by the current page.
Our website host keeps standard access logs (IP address, requested page, browser details and time) for up to 30 days. The app does not keep visitor access logs on our servers. Server logs are kept for up to 30 days; some service logs rotate by size, and the owner deletes them manually when no longer needed.
Appearance preference
System follows your device’s appearance; an explicit Light or Dark choice is remembered in localStorage under the single key sf-theme.
This display preference uses no cookie, is not transmitted to a server and is cleared by choosing System or clearing site data.
This functional, local-only appearance preference is used only to remember appearance.
Separate product sign-in storage
Clerk is the selected authentication provider for invitation-beta sign-in, separate from the public website.
In an owner-observed signed-in session, Clerk used script-readable cookies named __session, __session_<suffix>, __client_uat, __client_uat_<suffix> and clerk_active_context on app.securityfuse.com. Clerk also uses authentication cookies on clerk.app.securityfuse.com, including HttpOnly cookies that scripts cannot read. This is not a complete list of their attributes or lifetimes.
Clerk uses localStorage keys __clerk_environment for its environment and __clerk_protect_pid and __clerk_protect_st for bot protection. Cookie availability, expiry and storage behavior depend on the configured authentication session; inspect your browser’s storage controls for its current state.
User controls and consent
Browser settings allow control of cookies and site data; the effect on product sign-in depends on the enabled storage categories and configuration.
We obtain separately required consent for storage or changed processing under the applicable rules for the selected deployment.
The absence of analytics is not a blanket consent exemption, and accepting Terms is not consent to all browser storage.
Questions and changes
Contact hello@securityfuse.com with storage questions or privacy requests.
Material changes follow the notice process in the Terms and Privacy Policy, with separate consent where required.