Cookies and storage
Tracking is switched off.
This version loads no tracking tools and shows no consent banner. This page also explains how the optional advertising measurement would work if enabled.
This version of the website
The website’s own code sets no cookies and does not read or save a consent choice in localStorage while measurement is off. There are no measurement settings to change on this page in that mode.
- Images and fonts are served by this website, not by external image or font services.
- The website’s code has no other analytics tools, embedded videos or external support chats installed.
- A campaign code from your link, its campaign parameters and your reading position may be held in the page’s memory as you navigate. The website’s code does not save them in cookies or localStorage.
- Reloading creates a new document. A code may then be read again if it is still in the address. Being able to display or copy a code does not confirm an offer.
Switching measurement off does not automatically erase information that your browser saved on a previous visit. Below, we explain how you can manage that information.
Accepting, declining and changing your choice
When the consent feature is enabled, “Accept” and “Reject” have the same styling and each takes one click. Not answering does not give consent. An initial refusal neither loads the Pixel nor tells Meta that you declined. The website’s content is available whichever option you choose.
When measurement is off, no consent banner or choice controls are shown. In an enabled version, “Your measurement choice” appears further down this page and is also linked from “Change your choice” in the footer.
The consent banner and choice buttons need JavaScript. Without JavaScript, the Pixel cannot load either. Ordinary links and the website’s content still work.
What is saved about your choice
The following applies when the consent feature is enabled, including in test mode. Acceptance and refusal are saved in the same way if your browser allows it.
- Location and key
- Your choice is stored in localStorage for this website’s origin, under the key steerly.consent.v1. The same origin means the same protocol, hostname and port. The website’s languages therefore share the choice, but different browsers or devices do not. It is not an HTTP cookie and is not automatically sent with page requests.
- Contents
- The record contains version number 1 in v, a yes or no to marketing in marketing, and the time of the choice in at. The time is an ISO date string in UTC. The record contains no name or app account.
- How long the choice applies
- The choice applies for 365 days from the last recorded choice. Making a new choice starts a new period; simply visiting a page does not extend it. This is a fixed number of days, not a calculation in calendar months.
- When the choice no longer applies
- An expired, unreadable, future-dated or wrong-version choice does not give permission. Measurement stops until there is a new acceptance. localStorage does not automatically delete the record when it expires: it may remain until replaced or until the website’s data is cleared.
If storage fails, your answer applies only in the current document’s memory as you navigate here. It is not a promise for the whole browser session, a reload or a new tab. After a failed write, the website tries to remove an older saved choice. If removal is also blocked, that older choice may be read again on the next page load. Check your choice again and use your browser’s site-data settings if needed.
Open tabs on the same origin follow changes to the saved choice when the browser notifies them. Its validity is also checked when you return to a tab. A choice held only in memory cannot reliably be shared with other documents.
What optional measurement does
In normal measurement mode, the Meta Pixel measures how Facebook and Instagram ads lead to visits to the website and its pricing page. Our code requests the events below only while valid consent applies. This does not happen in OFF mode; in test mode, the simulation stays in the developer console.
- PageView
- A page visit for the current page and when you navigate to another page with measurement accepted. If you accept partway through a visit, the current page is reported, not the earlier pages you read before answering.
- ViewContent
- An additional event for the pricing page, in Swedish, English and Arabic. Our code attaches only the page labels content_name: Priser and content_category: pricing. This is a visit to an information page, not a purchase or the start of a trial.
The Pixel’s automatic collection of button clicks and extra page metadata is switched off with autoConfig. The website’s code does not add events for installation, registration, trials, purchases, button clicks or redeemed campaign codes. It does not send names, email addresses or app-account details as custom event fields either.
That does not mean a Pixel request is anonymous or contains only the event name. Meta may receive an IP address, browser and device information, the page address, referring page, and Pixel and cookie identifiers. The page address may include query parameters, such as a campaign code or fbclid from an ad. Our event list does not mean that the Pixel removes those parameters from addresses.
Who receives the information
With accepted measurement in normal mode, the Pixel script is fetched directly from Meta. Meta receives the Pixel’s measurement events. Meta’s Business Tools Terms name Meta Platforms Ireland Limited for processing subject to the EU General Data Protection Regulation. This is not a promise that information is processed only within the EU.
Our purpose is advertising measurement. Meta’s terms also describe how event data may be linked to Meta accounts and combined with other information for ad delivery and to personalise Meta’s products. Sending an event is therefore not the same as using an anonymous visitor counter. Information can be received even if you do not have a Facebook or Instagram account.
Meta’s Business Tools Terms say that event data may be retained for up to two years, subject to those terms. Audiences a business creates may be retained until the business deletes them. The website’s code does not create any such audiences. These periods apply at Meta and should not be confused with cookie lifetimes or our stored consent choice.
Cookies when normal measurement is allowed
After acceptance in normal measurement mode, the Meta Pixel may use the cookies below. This website’s code does not set them in OFF or test mode. A first-party cookie sits on the visited website’s domain; this does not mean its information stays with the website’s owner.
- _fbp
- A browser identifier that the Pixel may create on the website’s domain for advertising and analytics. Meta’s Cookies Policy gives a lifetime of 90 days.
- _fbc
- May contain the identifier for a click on a Meta ad, taken from the fbclid address parameter, to link a visit to the ad. The Pixel may create it when a click identifier is available after acceptance; it is not present on every visit. Meta’s ClickID documentation recommends a 90-day expiry for an HTTP-set _fbc cookie. This is a published recommendation, not a measured guarantee for every version of the browser Pixel.
- Cookies on Meta’s own domains
- When contacting Meta, the browser may also use Meta’s own cookies if its settings allow this. Meta’s Cookies Policy lists examples including fr for ad delivery and measurement, 90 days, and datr for browser identification and security, 400 days. These are examples from Meta’s policy, not a claim that every visitor here receives all these cookies.
Your browser, its tracking protection, your settings and clearing site data can prevent cookies or shorten their actual lifetime. Later visits with consent may create or update cookies. The published periods are not a promise of a particular end date measured from your very first visit, or of when information already sent will be deleted at Meta.
The website does not write its own _fbc cookie through HTTP and has no server integration to create it. The sources for these descriptions and periods are at the end of this page, retrieved on 13 September 2026.
What withdrawing consent does
Choose “Reject” in the choice controls to withdraw an earlier acceptance. The website’s own future measurement events stop. If the Meta Pixel has already been started, the code also tells it that consent has been revoked. Events waiting in the website’s queue for the script to load are removed.
The code attempts to delete _fbp and _fbc for the / path on the current domain and possible parent domains. Deletion may fail if the browser blocks it or a cookie has a different path, different domain settings or cannot be accessed by JavaScript. This website cannot delete cookies on Meta’s own domains.
Withdrawing consent does not erase information already sent. It does not undo a download already in progress or remove a script already loaded into the current document. A loaded script may remain for the document’s lifetime, including when you change pages without reloading. Our consent requirement still applies to new measurement events.
Deleting a Meta cookie alone is not the same as withdrawing consent. If a valid acceptance remains, the Pixel may create cookies again. If you delete the consent choice itself, the website asks again on the next page load, or when the browser reports the change, provided the consent feature is enabled.
Web server and hosting
When you load the website, the hosting provider receives technical information, such as an IP address and the requested address, which may contain query parameters. This is separate from the Pixel’s optional advertising measurement.
The hosting provider, any hosting cookies and server-log retention have not yet been confirmed for launch. These need to be checked and described before publication. We therefore give no unconfirmed log-retention period or guarantee about the country of processing.
The website and app are different
This page describes the website, not all processing in the Steerly app. Your website consent choice does not change your settings in the app or on Meta. App installs, registrations, trials and purchases are not measured by this website’s code.
You can send questions about your account or information to info@steerly.se. Also see our privacy notice, with the document status shown there.
Before measurement changes
Technical support and this description are not approval to start tracking visitors. Measurement must not be activated until approved privacy information covers the processing. New events, recipients or storage technologies require the description to be reviewed before they are used. Test mode does not bypass the check and must not be published as a consent-enabled website: a saved test answer must not become permission for later live measurement.
A different host for the Pixel script changes only where the browser downloads the script. It does not implement Conversions API, server events or deduplication. That kind of integration needs separate hosting, protected secrets, assigned responsibilities and the relevant agreements. It is not part of this static website.
Your browser settings
You can inspect and remove cookies and site data in your browser settings. Blocking third-party cookies does not guarantee that all Pixel requests are blocked: first-party cookies and network requests are different things. Use the website’s choice controls to decline our advertising measurement when the feature is enabled.
You can read pages and open menus, questions and course lists without JavaScript. If your browser prevents copying with a button, you can select and copy the text yourself.
Sources and published periods
Meta’s Cookies Policy describes cookies including _fbp, fr and datr, their purposes and lifetimes. The same information is available in the policy’s printable version.
Meta’s ClickID documentation describes _fbp, _fbc and the link to fbclid, and recommends 90 days for an HTTP-set _fbc cookie. That recommendation should not be confused with a server feature we have implemented.
Meta’s Pixel and GDPR documentation describes the information the Pixel may receive and its consent commands. The advanced guide describes autoConfig, and the event reference describes standard events.
Meta’s Business Tools Terms describe recipients, use of event data and retention at Meta. All these sources were retrieved on 13 September 2026. They are published vendor information, not results from testing live tracking on this website.
Measurement is switched off
There is no consent choice to make in this version. No measurement tools load. Information from a previous visit may remain in your browser; you can manage it in your browser’s site-data settings.
Questions about cookies and storage
Email info@steerly.se if you have questions, want to ask about information already sent, or notice anything that does not match this description.
- Company
- Steerly AB
- Company registration number
- 559531-3312
- Postal address
- Kungsängsgatan 35
753 22 Uppsala - info@steerly.se
