Cookie Policy
Last updated: 2026-04-12
Contact: hello@attach-corezone.one
Back to top1. Categories
We use essential cookies for navigation, security, and consent storage. Analytics cookies, when allowed, help us understand aggregate traffic patterns. Preference cookies remember UI choices such as theme where you opt in. We do not use advertising cookies on this property. Categories are reviewed quarterly. You may withdraw consent except for strictly necessary cookies required for basic functionality or security hardening.
2. Third Parties
Embedded content from partners may set their own cookies; we list known providers when feasible. Subprocessors bound by data processing terms may read technical logs correlated with consent flags. We prohibit behavioral ad networks on pages we control. If a partner changes practices, we update this table. You should review linked policies before submitting personal data externally. We terminate integrations that repeatedly breach contractual cookie limits.
3. Preferences
Theme preferences may be stored locally with your confirmation. Language selections default to English for this locale. You can reset preferences by clearing site storage or using controls we provide. Preference cookies do not track across unrelated sites. We avoid fingerprinting. If conflicts arise between browser settings and our banner, the stricter protection applies. Enterprise deployments may override certain UI defaults contractually.
4. Consent
On first visit, we present a consent card with accept and reject options for non-essential cookies. Rejecting does not block informational browsing. You may reopen settings via the footer link when available. Consent logs store a timestamp and choice for accountability. We re-prompt when material changes occur. Employees testing internally use separate guidance. Consent records are retained according to the Privacy Policy retention schedule.
5. Contact
Questions about cookies may be sent to hello@attach-corezone.one with the subject Cookie Inquiry. Include your browser type if troubleshooting. We respond within a reasonable period. For formal policy correspondence, reference this policy version date. Enterprise customers may route requests through their success lead. We document recurring issues to improve clarity. Please avoid sending sensitive attachments unless we provide a secure upload link.
6. What Are Cookies
Cookies are small text files stored on your device to remember state between requests. Similar technologies include local storage entries we use for theme and consent when you approve. They can be session-based or persistent. You can delete them through browser settings. Blocking all cookies may degrade features such as remembering consent choices. We minimize identifiers and avoid storing secrets in cookies.
7. Cookie Table
mh_consent: records analytics opt-in, duration twelve months, MetricHarbor. mh_theme: stores light or dark preference when enabled, duration twelve months, MetricHarbor. session_route: balances load, session, hosting provider. csrftoken where applicable protects forms, session, MetricHarbor. Analytics identifiers, if enabled, rotate quarterly and are aggregated. Durations may adjust with browser automatic cleanup policies.
8. Managing Cookies
Use browser controls to block or delete cookies. Guides differ by vendor; consult official documentation for Chrome, Firefox, Safari, or Edge. You may also use opt-out tools provided by analytics vendors when applicable. Disabling essential cookies may prevent form submission or security checks. Mobile browsers offer similar toggles. Corporate device policies may supersede individual settings; contact your IT team if features fail unexpectedly.
9. Impact of Disabling
If analytics cookies are off, we lose aggregate insight but core pages remain usable. If essential cookies are blocked, consent banners may repeat and forms may error. Theme memory may reset each visit. Embedded partner widgets could fail when third-party cookies are globally blocked. We surface inline notices when we detect incompatible settings. Support can suggest workarounds for accessibility needs without weakening security.
10. Updates
We update this policy when vendors or regulations change. Material updates receive a new date and may trigger a fresh consent prompt. Continued use after notice indicates acceptance of non-essential adjustments you previously approved unless you opt out. Archived versions are retained internally. Translation delays will not postpone enforcement of materially stricter protections. Notify us if discrepancies appear across language copies.
11. Liability and Cookies
We are not liable for issues arising solely from user-side cookie blockers except where non-waivable consumer law applies. Partners remain responsible for their own tracking compliance. If a breach involves cookie data, we follow incident procedures in the Privacy Policy. You agree to cooperate with reasonable investigations. Nothing here limits statutory penalties assigned by competent authorities to the appropriate party.