Consumer Fraud Alerts & Awareness Platform

You remain in control

Cookies required for security and basic Platform operation may be used automatically. Optional preference, analytics and marketing technologies should operate only according to your saved choices where consent is required.

Section 01

Scope of This Cookie Policy

This Cookie Policy explains how Consumer Fraud Awareness (“CFA”, “we”, “us” or “our”) uses cookies and similar technologies on cfa.consumerfraudawareness.com, related CFA websites and web applications (together, the “Platform”).
It should be read together with our Privacy Policy, which explains how CFA collects, uses, shares, protects and retains personal data, and our Terms of Use.

Section 02

What Cookies Are

Cookies are small text files placed on or read from your browser or device when you visit a website. They allow a website to recognise a browser, remember selections, maintain secure sessions and understand how features are used.

A cookie may be set directly by CFA (“first-party cookie”) or by an authorised external provider whose technology is used on the Platform (“third-party cookie”).

Cookies do not usually reveal your identity by themselves. However, cookie identifiers, IP addresses, account activity and device information may constitute personal data when they identify or can reasonably be linked to an individual.

Section 03

Similar Technologies

References to “cookies” in this Policy also include comparable technologies where relevant:

Local storage: saves settings or limited application data in the browser.
Session storage: temporarily stores information during a browser session.
Pixels or tags: help measure page views, email interactions or campaign performance.
SDKs: provide similar functionality within an application or integrated service.
Device and server identifiers: support security, diagnostics and fraud prevention.
Log files: record requests, errors, timestamps, IP addresses and technical activity.

Section 04

Why CFA Uses Cookies

Cookies and similar technologies may be used to:

Operate the Platform and provide requested features
Keep users signed in and maintain secure sessions
Protect accounts, forms and services against fraud, spam and automated abuse
Remember language, display, consent and accessibility preferences
Measure traffic, reliability, errors and feature performance
Understand how visitors find and navigate the Platform
Improve content, user journeys and Platform design
Measure communications or campaigns where permitted
Support third-party features selected by the user, such as payment or embedded media tools

CFA will not use optional cookie categories for a materially different purpose without updating the relevant notice and obtaining fresh consent where required.

Section 05

Cookie Categories

Strictly Necessary

Always Active

Required for security, authentication, consent records, load balancing, session management and core Platform functions.

Preferences

Optional

Remember choices such as language, layout, region, accessibility settings and other customisations.

Analytics and Performance

Optional

Help us measure visits, interactions, errors and feature performance so CFA can improve the Platform.

Marketing and Measurement

Optional

May measure campaign effectiveness, referrals or communications and, where enabled, support relevant promotional activity.

CFA’s cookie preference tool allows optional categories to be accepted or rejected separately. Strictly necessary cookies cannot be disabled through the tool because the Platform may not operate securely without them.

Section 06

Current Cookie Register

The table below provides the cookie structure intended for CFA. Exact identifiers may change as the Platform is developed or providers update their technology. The production register should be checked against the cookies actually deployed before launch and after material technical changes.

Cookie or storage key	Provider	Purpose	Category	Typical Duration
cfa_cookie_consent	CFA	Stores the visitor’s cookie-category choices and consent timestamp.	Strictly Necessary	Up to 12 months
cfa_session	CFA / authentication provider	Maintains a secure signed-in session and account state.	Strictly Necessary	Session or up to 30 days
cfa_csrf	CFA	Helps protect forms and requests against cross-site request forgery.	Strictly Necessary	Session
cfa_preferences	CFA	Remembers selected language, display or accessibility preferences.	Preferences	Up to 12 months
cfa_analytics_id	CFA or configured analytics provider	Distinguishes visits for aggregated usage and performance reporting.	Analytics	Up to 13 months
cfa_referral	CFA	Records the source of a visit or campaign for attribution reporting.	Marketing / measurement	Up to 90 days
Payment-provider cookies	Configured payment provider	Support checkout security, fraud detection and payment completion.	Strictly necessary for checkout	Provider dependent
Security or CDN cookies	Configured hosting/security provider	Protect the Platform from malicious traffic, bots and abuse.	Strictly Necessary	Provider dependent

Developer deployment check: Replace any illustrative identifiers above with the exact cookie names, providers, purposes and lifetimes detected on the live CFA domain. Do not list Google Analytics, Meta Pixel, advertising cookies or other providers unless they are actually installed.

Section 07

Third-Party Cookies and Services

CFA may use external providers for hosting, security, authentication, analytics, payments, communications, embedded media, customer support or other Platform functions. A provider may place or read cookies when its service is used.

The provider’s privacy and cookie documentation governs its independent processing. CFA will aim to configure third-party tools according to the cookie choices available on the Platform and to minimise optional tracking before consent where required.

Potential integration categories include:

Visual landing tools, delivery, security authentication providerscloud hosting, content-delivery and anti-bot protection, payments, performance, partnerships and analytics
Account authentication and identity verification
Privacy-conscious analytics and error monitoring
Payment processing and checkout security
Embedded video, maps, chat or social content
Email delivery and campaign measurement

Embedded third-party content may remain blocked until the relevant optional category is accepted. Where practical, CFA may display a placeholder allowing the user to activate that content knowingly.

Section 08

Consent and Managing Your Choices

When you first visit the Platform, CFA may display a cookie banner or preference centre. You can accept all optional categories, reject them or choose categories individually.

Your preference may be stored in a necessary cookie so that CFA can respect it on future visits. We may ask you to choose again when:

The preference record expires or is deleted
You use a different browser, device or private-browsing session
The categories or purposes materially change
A legal or technical requirement requires renewed consent

Section 09

Browser and Device Controls

Most browsers allow you to inspect, block or delete cookies through privacy or security settings. You may also configure a browser to notify you before accepting a cookie.

Browser controls apply separately to each browser and device. Deleting cookies may sign you out, clear saved preferences and cause the cookie banner to appear again.

Blocking all cookies may prevent account login, secure forms, fraud protection, checkout or other essential Platform functions from working correctly.

Mobile operating systems may provide additional controls for advertising identifiers, tracking permissions and application storage.

Section 10

Session Cookies, Persistent Cookies and Duration

Session cookies generally expire when you close the browser. Persistent cookies remain until their stated expiry date, until the relevant purpose ends or until you delete them.

CFA aims to use proportionate retention periods. Consent preferences may be stored for up to 12 months before renewal. Analytics identifiers, where enabled, should be configured for a limited period appropriate to measurement needs. Security and payment cookies may follow shorter or provider-defined durations.

A cookie’s actual lifetime may differ where the browser deletes it early, a user clears storage, a provider changes its configuration or CFA retires the relevant technology.

Section 11

Do Not Track and Global Privacy Signals

Some browsers transmit “Do Not Track” or other privacy-preference signals. Because there is not a single universally applied technical standard for all such signals, the Platform may not respond to every signal in the same way.

CFA will use its consent and preference centre as the primary method for recording cookie choices and may support recognised browser-based privacy signals where technically and legally appropriate.

Section 12

Changes to This Cookie Policy

CFA may update this Policy to reflect changes in law, providers, Platform features, cookie categories or technical configuration. The “Last updated” date identifies the current version.

Where an update materially changes an optional cookie purpose, CFA may display a new notice or request renewed consent before activating the affected category

Section 13

Questions and Privacy Requests

Questions about this Cookie Policy or CFA’s use of tracking technologies may be sent to:

Privacy email: privacy@consumerfraudawareness.com
Grievance email: grievance@consumerfraudawareness.com
Online request: Privacy Request Form
General support: Contact CFA

Include the browser or device used, the relevant CFA page and a clear description of the issue. Do not send passwords, payment-card details or unrelated identity documents.

Review your cookie choices

Essential cookies remain active. Preference, analytics and marketing categories can be changed independently.