What cookies and browser storage are
EngineersCalc uses cookies and similar browser technologies to operate the website, retain consent choices, support sessions, protect forms and, when you agree, measure website use. A cookie is a small piece of information stored in your browser and sent to a matching website. Browser localStorage and sessionStorage are separate browser storage mechanisms and do not automatically appear in a cookie list.
Whether a technology appears depends on the page visited, your browser, your sign-in status, the enabled services and your consent choices. Cookies that are strictly necessary for a service you request are distinguished from optional analytics technologies; an administrative category label alone does not determine whether consent is legally unnecessary.
Necessary cookies and security
Necessary technologies help retain your consent choices, protect forms, support authentication and preserve requested sessions. They may include CookieYes preferences, WordPress consent-state records, login/session cookies and Cloudflare security tokens such as cf_clearance. WooCommerce session or cart cookies may also occur when the corresponding functionality is used. A cookie's necessity is determined by its actual purpose, not merely by a label in the scanner.
Cloudflare Turnstile is used to defend relevant forms against automated submissions and may process request or device signals. Not every form of security processing relies on a browser cookie. Optional analytics should not be confused with essential site security.
Google Analytics and Sourcebuster
Where you consent to Analytics, EngineersCalc uses Google Analytics 4 through Google Tag Manager to measure site visits and use of available engineering tools. WordPress Consent API and Site Kit support the integration. In reviewed browser tests, _ga and _ga_B7MCH1J11W appeared after consent and were absent after Reject All.
Sourcebuster/WooCommerce may also set sbjs_* visit-attribution cookies, classified in the CookieYes register as Analytics. Their actual behaviour depends on the active components and route, and the category label alone is not a technical enforcement mechanism. Users can refuse optional analytics using CookieYes.
Calculator view-count cookies
The first-party family ec_viewed_calc_* (with a calculator identifier in place of *) helps avoid counting repeated visits to the same calculator in a 30-day period. This measure is separate from Google Analytics and is categorised as optional Analytics.
The server-side view-count endpoint checks analytics consent before setting the deduplication marker or registering an eligible view. The counter is deliberately deduplicated and does not represent all individual page visits.
Cookie register
This register summarises the main cookies and families identified in the site configuration. Storage periods are configured or observed values, and may be shortened by browser behaviour or updated settings; not every cookie is set on every visit. An asterisk denotes a variable suffix.
| Cookie / pattern | Purpose / provider | Category | Period recorded |
|---|---|---|---|
cookieyes-consent, cookieyes-* | Consent preferences — CookieYes | Necessary | Up to 1 year in register |
wp_consent_* | Consent status/preferences — WP Consent API | Necessary consent-state records; review each purpose | 1 month in register |
cf_clearance | Security challenge state — Cloudflare | Security / necessary where applicable | Varies with the security challenge and browser |
| WordPress login/session cookies | Account authentication — WordPress / Ultimate Member | Necessary for sign-in | Session / configuration dependent |
woocommerce_items_in_cart, woocommerce_cart_hash | Shopping cart continuity — WooCommerce | Necessary when cart functionality is requested | Session in register |
wp_woocommerce_session_* | Customer/cart session — WooCommerce | Necessary when cart functionality is requested | 2 days in register |
_ga, _ga_B7MCH1J11W | Site measurement — Google Analytics 4 | Analytics (consent) | Usually up to 2 years; browser or settings may shorten this |
sbjs_current, sbjs_current_add, sbjs_first, sbjs_first_add, sbjs_migrations, sbjs_udata | Visit-source attribution — Sourcebuster/WooCommerce | Analytics in CookieYes register | Session in register |
sbjs_session | Visit-source attribution — Sourcebuster/WooCommerce | Analytics in CookieYes register | 1 hour in register |
ec_viewed_calc_* | Calculator view deduplication — EngineersCalc | Analytics (consent) | 30 days |
This register covers the principal cookies and patterns observed in the site's configuration; specific names and storage periods can vary with features, browser settings, plugin updates and user choices. A cookie pattern such as ec_viewed_calc_* represents multiple calculator-specific names, not separate advertising systems. You can inspect current cookies in your browser's site-data tools.
Browser storage for engineering work
EngineersCalc also uses browser storage for functions requested by users. This is distinct from the analytics cookie register. Examples include localStorage keys ec_saved_calculations (up to 10 calculation snapshots) and ec_artifacts_v1 (up to 20 cached or locally saved finalized Engineering Artifacts). The PDF export workflow temporarily uses the sessionStorage key ec_artifact_export. Some workflows may use additional local browser state.
Data stored locally may remain on the device after logout, and server-side account deletion cannot erase an offline browser's local copies. Use your browser's controls to clear site data if necessary, but export work you need first. Clearing browser data can permanently remove locally saved engineering results.
Consent choices and withdrawal
The CookieYes banner offers Reject All, Accept All and Customise. The preference interface allows a user to enable or disable optional categories and choose Save My Preferences. Necessary cookies are shown as always active. Analytics was shown off in the tested initial preference view.
A persistent CookieYes control is available to reopen preferences and withdraw or amend optional consent. Withdrawing consent does not retroactively invalidate processing carried out while consent was valid. Deleting cookies in your browser is an additional control, not the only consent-withdrawal method. If cookies are blocked by your browser, some site features may not function as intended.
Other cookies and scanning limitations
The CookieYes scanner may display categories such as Functional, Performance, Advertisement and Uncategorised even where no corresponding cookie has been confirmed during the latest review. Their presence in the consent interface does not mean EngineersCalc currently serves personalised advertising.
Automated inventories are indicative rather than comprehensive. Because browser settings, plugin updates, login status and routes influence what is stored, the listed technologies are reviewed periodically and adjusted as the site changes. Dynamic cookie names are described in this policy as families where practical.
Updates, contact and Privacy Policy
The responsible operator is Daniel Mrowiński, an individual operating EngineersCalc in Poland. Questions about cookie use or privacy requests may be sent to [email protected].
Further information about personal data, legal bases, recipients, international transfers, rights and retention is provided in the Privacy Policy. Technologies and settings may change as the platform develops; the policy and register must be updated when material changes are deployed.
Questions about this document?
For policy questions and corrections, contact EngineersCalc. Do not send confidential engineering data unless a suitable secure channel has been agreed.
Contact EngineersCalc