This Cookie Policy explains how FRESCOR.org (“we”, “us”, “our”) uses cookies and similar technologies on frescor.org. It describes what each cookie does, how long it lasts, how you give or withdraw consent, and how you can control cookies in your browser. Please read it together with our Privacy Policy, which explains how we handle personal data more generally.
Last updated: October 19, 2026
Key takeaways
- We use only necessary and functional cookies. No analytics or advertising cookies are set by default.
- Your choices are recorded by the CookieYes consent banner, and you can change them at any time.
- Most cookies on this site come from WordPress itself, from the WooCommerce shop and from the Wordfence security plugin.
- Two small browser storage entries (
frescor_themeandfrescor_calc) remember your display preference and your calculator inputs. They stay on your device and are never sent to us.
What cookies are
A cookie is a small text file that a website asks your browser to store on your device. When you return to the site, or move from one page to another, your browser sends the cookie back. This lets the site remember things such as whether you are logged in, what is in your shopping cart, or which consent choices you made.
Cookies are usually described along three lines:
- First-party or third-party. First-party cookies are set by the site you are visiting (frescor.org). Third-party cookies are set by a different domain, for example an embedded video player or an advertising network.
- Session or persistent. Session cookies are deleted when you close your browser. Persistent cookies remain until they reach their expiry date or until you delete them.
- Purpose. Some cookies are strictly necessary for the site to work. Others remember preferences, measure use of the site or support advertising. Only strictly necessary cookies can be set without your consent.
Similar technologies
Websites can also store information using the browser’s local storage (part of the Web Storage standard). Local storage works like a small key-value notebook kept by your browser for one website. Unlike cookies, its contents are not automatically sent to the server with each request. The law on consent applies to local storage in the same way as to cookies, so we describe the entries we use in this policy too.
How we use cookies
We keep cookie use to a minimum. frescor.org is a knowledge resource with articles, an archive of the original FRESCOR research project, a few interactive tools and a small shop for professional services and a digital eBook. To run these features, we use cookies for the following purposes:
- Running the website securely. Keeping logged-in sessions, protecting forms and the login page, and blocking malicious traffic.
- Operating the shop. Remembering the contents of your cart while you browse and complete checkout.
- Remembering your choices. Storing your cookie consent choices, dismissed notices and, if you choose, your details for comment forms.
- Recording how an order arrived. WooCommerce can note the source of a visit (for example, a direct visit or a link from another website) so that it can be saved with an order. This is described in detail below.
We do not currently use analytics services (such as Google Analytics), advertising networks, social media tracking pixels or cross-site tracking of any kind. If this changes, we will update this policy and ask for your consent before any such cookies are set.
Your consent and the CookieYes banner
When you first visit frescor.org, a consent banner provided by CookieYes appears. It lets you accept all cookies, reject all non-essential cookies, or choose category by category. Strictly necessary cookies are always active because the site cannot work properly without them. All other categories stay off until you switch them on.
The banner groups cookies into five categories:
| Category | What it covers | Used on this site? |
|---|---|---|
| Necessary | Cookies essential for security, logging in, the shopping cart, checkout and remembering your consent choices. These cannot be switched off in the banner. | Yes |
| Functional | Cookies that remember preferences and support optional features, such as saved comment details, dismissed notices, recently viewed products and order source records. | Yes |
| Analytics | Cookies that help a site owner understand how visitors use the site, usually through statistics services. | No, none set by default |
| Performance | Cookies that measure and improve technical performance, such as load times. | No, none set by default |
| Advertisement | Cookies that build profiles of interests and show targeted ads, often across sites. | No, none set by default |
The Analytics, Performance and Advertisement categories appear in the banner because they are part of the standard CookieYes layout and keep the banner ready for any future change. At present, no cookies are assigned to them. Your choice is stored in the cookieyes-consent cookie so that the banner does not reappear on every page.
How to change or withdraw your consent
You can change your mind at any time. Withdrawing consent is as easy as giving it. Use the link below to reopen the consent banner and update your choices:
When you withdraw consent for a category, we stop setting new cookies in that category. Cookies that were already stored may remain on your device until they expire, so you may also want to delete them through your browser settings (see Browser controls below).
Withdrawing consent does not affect the lawfulness of anything that happened before you withdrew it. Rejecting functional cookies will not stop you from reading articles, using the glossary or buying from the shop.
Cookies we use
The tables below list the cookies that may be set on frescor.org. All of them are first-party cookies. Names that end with * or contain a placeholder such as [hash] include a unique value, which WordPress or the plugin generates for each site, user or session. Whether a particular cookie appears on your device depends on what you do. For example, login cookies are only set if you log in, and cart cookies are only set once you add something to your cart.
Consent management (CookieYes)
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
cookieyes-consent |
CookieYes | Stores your consent choices for each cookie category so that they are respected on later visits and the banner is not shown again. | 1 year | Necessary |
WordPress core
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
wordpress_test_cookie |
WordPress | Checks whether your browser accepts cookies. It is set on the login page. | Session | Necessary |
wordpress_logged_in_[hash] |
WordPress | Shows that you are logged in and identifies your account after login. | Session, or 14 days if you choose “Remember Me” | Necessary |
wordpress_sec_[hash] |
WordPress | Stores secure authentication details for the WordPress dashboard and account areas. | Session, or 14 days if you choose “Remember Me” | Necessary |
wp-settings-[user ID] |
WordPress | Remembers interface settings for logged-in users, such as dashboard layout and editor view. | 1 year | Functional |
wp-settings-time-[user ID] |
WordPress | Records when the wp-settings cookie was last updated. |
1 year | Functional |
comment_author_[hash], comment_author_email_[hash], comment_author_url_[hash] |
WordPress | Remembers the name, email address and website you entered in a comment form, so that you do not have to type them again. Only set if comments are enabled on a page and you tick the box to save your details. | About 1 year (347 days) | Functional |
Without “Remember Me”, WordPress login cookies end when you close your browser. The login itself also expires on the server after 48 hours.
Shop (WooCommerce)
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
woocommerce_cart_hash |
WooCommerce | Helps the shop detect when the contents of your cart change, so that cart totals stay accurate. | Session | Necessary |
woocommerce_items_in_cart |
WooCommerce | Records whether your cart contains items, so that pages show the correct cart state. | Session | Necessary |
wp_woocommerce_session_[hash] |
WooCommerce | Holds a unique code that links your browser to your cart data, stored on our server, during shopping and checkout. | 2 days | Necessary |
woocommerce_recently_viewed |
WooCommerce | Keeps a list of products you have recently viewed, where a “recently viewed products” list is shown. | Session | Functional |
store_notice[notice ID] |
WooCommerce | Remembers that you have dismissed a store-wide notice, so it is not shown again. | Session | Functional |
Order attribution (WooCommerce, sbjs_* cookies)
WooCommerce includes an order attribution feature. It uses a small open-source script called Sourcebuster.js, which sets cookies whose names begin with sbjs_. These cookies note how you arrived at the site: for example, a direct visit, a link from another website, or a search engine. They also record basic details of your current visit, such as the first page you landed on, the number of pages viewed and your browser type (user agent). If you place an order, WooCommerce saves this summary with the order, so that we can understand which channels bring in customers.
Points to note:
- The cookies are first-party. Their contents are not sent to any third party, and they do not track you across other websites.
- WooCommerce sets them as session cookies by default, so they are deleted when you close your browser. The
sbjs_sessioncookie also expires after 30 minutes of inactivity, which marks the end of a “visit”. - Information is only stored on our server if you complete an order. It is then kept as part of the order record, as described in our Privacy Policy.
- We have placed these cookies in the Functional category in our consent banner. They are not used for analytics dashboards or advertising.
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
sbjs_migrations |
WooCommerce (Sourcebuster.js) | Technical record of the script’s data format version. | Session | Functional |
sbjs_current_add |
WooCommerce (Sourcebuster.js) | Time of the current visit, landing page and referring page. | Session | Functional |
sbjs_first_add |
WooCommerce (Sourcebuster.js) | Time of the first recorded visit, landing page and referring page. | Session | Functional |
sbjs_current |
WooCommerce (Sourcebuster.js) | Traffic source of the current visit (for example, direct, referral or organic search). | Session | Functional |
sbjs_first |
WooCommerce (Sourcebuster.js) | Traffic source of the first recorded visit. | Session | Functional |
sbjs_udata |
WooCommerce (Sourcebuster.js) | Basic visit data, such as number of visits and browser user agent. | Session | Functional |
sbjs_session |
WooCommerce (Sourcebuster.js) | Number of pages viewed in the current visit and whether the visit is still active. | 30 minutes of inactivity, or end of session | Functional |
Security (Wordfence)
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
wfwaf-authcookie-[hash] |
Wordfence | Set only for logged-in users. It lets the web application firewall recognize logged-in users and their permission level, so that legitimate actions are not blocked as attacks. | 12 hours | Necessary |
wf_loginalerted_[hash] |
Wordfence | Set after a privileged user logs in. It recognizes devices that have logged in before, so that Wordfence alerts the site administrator only when a login comes from a new device. | 1 year | Necessary |
Wordfence also checks visitor IP addresses to block known malicious traffic and limit login attempts. That processing is described in our Privacy Policy.
Local storage used by the theme
The FRESCOR theme uses your browser’s local storage for two convenience features. These entries are not cookies. They are never sent to our server and stay on your device until you clear them. Both are functional: they only remember choices you made yourself.
| Key | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
frescor_theme |
frescor.org theme | Remembers whether you chose the light or dark color scheme, so the site keeps your preference on later visits. | Until you clear site data in your browser | Functional |
frescor_calc |
frescor.org theme | Saves the task set you entered in the schedulability calculator (for example, execution times, periods and deadlines), so you do not lose your work if you reload the page. | Until you clear the calculator, clear site data or remove it in your browser | Functional |
If you do not want these values stored, you can clear the site data for frescor.org in your browser settings. If you do not set a color scheme, the site follows your operating system’s light or dark setting. The calculator also works without saving anything; your inputs are simply lost when you leave the page.
Browser controls
In addition to the consent banner, every major browser lets you view, block and delete cookies and other site data. Typical options include:
- Viewing and deleting cookies and local storage for one site or for all sites.
- Blocking third-party cookies, or all cookies.
- Deleting cookies automatically when you close the browser.
- Using a private or incognito window, which discards cookies and local storage at the end of the session.
The relevant settings are usually found under “Privacy”, “Privacy and security” or “Cookies and site data”. The help pages of your browser explain the exact steps:
- Google Chrome: delete, allow and manage cookies
- Mozilla Firefox: clear cookies and site data
- Apple Safari: manage cookies and website data
- Microsoft Edge: delete cookies
If you block all cookies, some parts of the site will not work. In particular, you will not be able to log in, keep items in your cart or complete a purchase. Blocking cookies also removes the cookieyes-consent cookie, so the banner will appear again on your next visit.
Third-party cookies
We do not intentionally allow third parties to set cookies through frescor.org. We do not embed advertising, social media “like” buttons or tracking pixels. Links to external sites, such as standards bodies, RTOS projects, research publishers or CORDIS, take you to websites that have their own cookie policies, and we have no control over those cookies.
If you pay for an order, the payment step may be handled by a payment provider. If you are redirected to the provider’s own pages, or the provider’s secure payment fields are loaded on our checkout page, that provider may set its own cookies, for example for fraud prevention. Those cookies are governed by the provider’s privacy and cookie policies. If we add any third-party service that sets cookies in future, we will list it here and, where required, ask for your consent first.
Updates to this policy
We review this policy when we add, remove or reconfigure plugins, themes or services that affect cookies, and at least once a year. When we make changes, we update the “Last updated” date at the top of this page. If a change introduces a new category of non-essential cookies, such as analytics, we will ask for your consent again through the banner before setting them.
Contact
If you have questions about this Cookie Policy or how we use cookies and local storage, please contact FRESCOR.org at support@frescor.org. You can also write to us at available on request via support@frescor.org. For general enquiries, see our Contact page. More information about your rights over personal data is set out in our Privacy Policy.