Cookie Notice
Last updated October 3, 2026
NextShift Trades uses cookies and similar technologies to keep you signed in, remember preferences, and understand how the Service is used.
Types of cookies we use
- Essential cookies required to sign in and access courses.
- Preference cookies that remember your settings.
- Analytics cookies that help us improve the Service.
Managing cookies
You can control cookies through your browser settings. Disabling essential cookies may prevent you from signing in or accessing purchased courses.
Optional advertising cookies and your choice
After you accept advertising measurement, the standard Meta Pixel may create or read first-party _fbp (browser identifier) and _fbc (ad-click identifier, when available) cookies. It can read accepted fbclid and approved UTM parameters in the public page URL. Meta-domain cookies may also be involved, subject to your browser settings. These identifiers support ad measurement and attribution; they are not required for checkout or course access.
Your accept/reject choice is stored in first-party localStorage (nextshift-ad-consent-v3) for 90 days. This is the choice duration, not a promise that Meta cookies or Meta-held data expire after 90 days. Session storage can also suppress Pixel retries after a load failure. No Pixel loads before acceptance; Global Privacy Control (GPC) disables advertising measurement. Use Advertising choices here or on eligible public pages to reject or withdraw. Withdrawal attempts removal of _fbp/_fbc and reloads without Pixel; it cannot delete Meta-domain cookies or recall information already sent. Browser settings provide additional cookie controls.
Separate purchase permission, when available, uses a Secure, HttpOnly, SameSite=Lax first-party cookie (nextshift_purchase_consent) lasting up to 90 days; the server stores only a hash of its random token. The cookie links new checkouts to your permission and is not sent to Meta. First-party localStorage (nextshift-purchase-choice-v1) remembers the purchase choice or pending withdrawal. Existing _fbp/_fbc identifiers are used only with separate purchase permission. See the Privacy Policy for purchase fields, retention and withdrawal limits. Purchase reporting is currently disabled during validation; no checkout-start event is sent.