SAFE INNOVATION
Cookie & storage policy
The browser storage we use, its duration and your choices.
How browser storage works
Cookies can accompany requests to the website. localStorage remains in this browser until cleared, subject to expiry checks made by the site. sessionStorage belongs to a browser tab session; browsers may restore it when restoring tabs. These are distinct from the enquiry records held on the server.
Essential catalogue access
safe_catalog_session is an HttpOnly, Secure, SameSite=Strict cookie created only after a valid access code is exchanged. It expires at the access grant’s expiry, normally 24 hours after approval, not 24 hours after code entry. Revocation or a replacement invalidates access on the server immediately; the cookie may remain until its expiry or catalogue sign-out. Private media URLs normally last 60 seconds after issuance and may remain usable during that short window. No customer account is required.
Preferences
safe-consent-v1 in localStorage records your analytics and advertising choices. The site honours a choice for 180 days, then asks again; the expired localStorage entry may remain until overwritten or you clear it. safe-motion-reduced in sessionStorage remembers the reduced-motion choice for the tab session. These preference records do not contain form text.
Optional attribution and duplicate prevention
safe-attribution-v1 in sessionStorage holds only allowlisted campaign information: analytics permission permits campaign labels, while advertising permission permits eligible Google click identifiers. First and latest eligible campaign touches are kept distinct. Withdrawing a category removes its information; rejecting both clears this attribution. safe-leads-v1 in sessionStorage keeps a bounded list of accepted-request references to avoid repeated lead measurement. It is written after a saved request even when optional measurement is rejected; references stay local and are not sent to Google. These entries last for the tab session or until browser data is cleared.
Owner authentication and other security
The restricted owner workspace uses Supabase authentication cookies named sb-…-auth-token, sometimes split into numbered chunks. The installed library gives these cookies a maximum age of 400 days, refreshed during use; server-side session expiry, sign-out or revocation can end access earlier. They are not created simply by browsing public pages. Forms use a short-lived signed anti-abuse challenge held in page memory (up to two hours), server-side rate limits and submission keys; no separate public form-security cookie is installed.
Google features are not active here
This website does not install Google Analytics or advertising cookies. Google tags remain disabled even if you select optional categories. The site can still keep consented first-party campaign information as described above. Before Google activation, its actual cookies, durations and outgoing automatic events need verification and this inventory must be reviewed. We do not list hypothetical Google cookies as currently installed. No WhatsApp/Meta scripts, widgets or cookies are loaded by this site.
Change your choice
Use Cookie settings in the footer to accept, reject or manage analytics and advertising independently. Closing the preferences dialog does not save draft changes. Forms and catalogue authentication remain available with both optional categories off. Withdrawal stops future optional collection and removes the relevant local attribution; it does not erase enquiries already submitted or data already processed. Browser settings can also remove cookies and browser storage, which can sign you out of the catalogue or reset preferences.
Contact us
For questions about your information or this policy, email management@safeinnovationdb.com.