Cookie policy

Effective Date: September 8, 2026 Last Updated: September 8, 2026

1. Introduction

At Phillforce, we want you to understand what happens when you visit our website or use our platform. Like most modern online services, Phillforce may use cookies and similar technologies to keep our websites and applications functioning properly, protect accounts, remember preferences, understand how our services are used, improve performance, and, where applicable, support marketing activities. This Cookie Policy explains what cookies and similar technologies are, why Phillforce uses them, the types of cookies we may use, how third-party services may interact with them, and the choices available to you. This Cookie Policy forms part of the broader privacy framework of Phillforce, Inc. and should be read together with our Privacy Policy and Terms of Service.

2. Who We Are

Phillforce is operated by: Phillforce, Inc. 8 Wading Bird Loop Blythewood, SC 29016 United States Website: phillforce.com Privacy enquiries: privacy@phillforce.com General enquiries: philip@phillforce.com

A cookie is a small piece of information that a website or online service may store on your browser or device. Cookies can help a website recognize your browser, maintain a login session, remember settings, understand how pages are used, protect against malicious activity, or perform other functions necessary for the service. Some cookies last only while your browser is open. Others remain on your device for a defined period or until they are deleted. Cookies do not all serve the same purpose, and Phillforce does not treat all cookies the same way.

4. Similar Technologies

When this Policy refers to “cookies,” we may also be referring to similar technologies where appropriate. These may include technologies such as:

local storage;
session storage;
pixels;
tags;
software development kits;
browser identifiers;
embedded scripts;
similar device-storage or access technologies.

The legal rules applying to these technologies can depend on the technology, purpose, location of the user, and applicable law. Where applicable law treats another technology similarly to cookies, Phillforce intends to apply the appropriate privacy and consent requirements.

5. Why Phillforce Uses Cookies

We use cookies and similar technologies only where they serve a legitimate function connected to the Phillforce website or platform. Depending on the service and your preferences, these technologies may help us:

keep you signed in;
authenticate accounts;
protect accounts and sessions;
prevent fraud and abuse;
remember privacy choices;
remember interface preferences;
maintain website functionality;
improve page performance;
understand how visitors use Phillforce;
identify technical problems;
improve product usability;
measure the effectiveness of website content; and
support marketing or advertising activities where those technologies are actually implemented and legally permitted.

We do not believe that every available tracking technology needs to be added merely because it exists. Our goal is to use technologies that serve a clear product, security, operational, analytical, or legitimate commercial purpose.

6. Categories of Cookies We May Use

Phillforce may use the categories described below. Not every category will necessarily be active at all times. The cookies and technologies actually deployed should reflect the current Phillforce website and product configuration.

7. Strictly Necessary Cookies

Strictly necessary cookies are used for functions required to operate the website or provide a service you specifically request. They may support functions such as:

account authentication;
login sessions;
security;
fraud prevention;
protection against unauthorized requests;
load balancing;
account access;
checkout functionality;
remembering cookie-consent choices;
maintaining essential platform functionality.

Without these cookies, certain parts of Phillforce may not work correctly. Because these technologies are necessary for the service to function or to provide a feature requested by you, they may be used without optional cookie consent where applicable law permits. You may still be able to block them through your browser, but doing so may prevent important parts of Phillforce from functioning.

8. Preference and Functional Cookies

Preference or functional cookies help Phillforce remember choices you make. These may include:

interface preferences;
display preferences;
time zone;
language;
theme preferences;
remembered settings;
selected product preferences.

These technologies help make the service feel consistent when you return. Where applicable law requires consent for these cookies, Phillforce will obtain the required consent before using them.

9. Analytics and Performance Cookies

Analytics and performance technologies help us understand how our websites and products are being used. For example, they may help us understand:

how many people visit a page;
which pages are used most frequently;
where visitors entered the website;
how users move between pages;
whether visitors complete important actions;
whether pages experience errors;
how long certain pages take to load;
whether product features are being used;
how we can improve usability and performance.

We may use analytics information to improve Phillforce, identify problems, understand customer journeys, and evaluate the performance of our website. Where required by applicable law, analytics cookies or similar technologies will not be activated until you have provided the appropriate consent. If you refuse or disable analytics cookies, the core Phillforce service should continue to work, although we may have less information about how the website or platform is being used.

10. Marketing and Advertising Cookies

Phillforce may use marketing, advertising, or campaign-measurement technologies if and when we engage in activities that require them. Such technologies could help us:

understand whether a campaign resulted in a website visit;
measure advertising effectiveness;
reduce irrelevant advertising;
understand marketing attribution;
create or measure audiences;
support permitted retargeting or personalized advertising.

Phillforce will not treat marketing cookies as strictly necessary. Where consent or an opt-out mechanism is required by applicable law, Phillforce will provide the applicable control. If Phillforce does not currently use advertising technologies, this section does not mean that such technologies are automatically active. It explains how they will be treated if they are introduced.

11. Authentication Cookies

Phillforce may use cookies and related technologies to support secure authentication. These may be used to:

establish an authenticated session;
recognize that you have successfully logged in;
maintain login state;
protect account access;
prevent unauthorized session activity;
support secure logout.

Authentication cookies are generally considered necessary for the account functionality you request. If these cookies are blocked, you may be unable to sign in or use protected areas of Phillforce.

12. Security Cookies

Phillforce may use cookies, identifiers, and related technologies to help protect the website, accounts, customers, and infrastructure. These technologies may help us:

detect suspicious login activity;
prevent cross-site request attacks;
distinguish legitimate requests from automated abuse;
prevent fraud;
protect sessions;
enforce security controls;
detect unusual platform activity.

For security reasons, we do not publicly disclose the detailed operation of Phillforce's defensive technologies. Security-related cookies that are strictly necessary to protect a service requested by the user may operate without optional consent where permitted by applicable law.

Phillforce serves users globally. Cookie rules vary between jurisdictions. Where applicable law requires consent before Phillforce places or accesses non-essential cookies, we will seek that consent before activating those technologies. Our cookie interface may provide options such as: Accept All Reject Non-Essential Manage Preferences Rejecting non-essential cookies should not prevent you from accessing the basic Phillforce website or using core platform functions that do not depend on those cookies. Strictly necessary technologies may continue to operate because they are required to provide the requested service or maintain essential security.

You should be able to change your cookie choices after your initial selection. Where our website provides a cookie preference manager, you may reopen it through a link such as: Cookie Settings or another privacy-preference control made available on the Phillforce website. Changing your preference does not necessarily erase information already lawfully processed before your change. However, where you withdraw consent, Phillforce will stop future use of the relevant consent-based technologies in accordance with applicable law.

15. Rejecting Non-Essential Cookies

You may choose to reject cookies that are not necessary for the operation of Phillforce. Where legally required, Phillforce will not make access to basic website functionality conditional on accepting optional analytics or advertising cookies. If you reject optional cookies:

core account functionality should remain available;
strictly necessary cookies may still operate;
analytics may become less accurate;
some preference features may not persist;
personalized or campaign-related functionality may be unavailable.

16. Browser Controls

Most modern browsers allow you to control cookies directly. Depending on your browser, you may be able to:

view stored cookies;
delete cookies;
block cookies;
block third-party cookies;
clear cookies when the browser closes;
restrict specific websites from storing cookies;
use private or incognito browsing modes.

Please remember that blocking all cookies may affect the operation of Phillforce. For example, the platform may be unable to maintain your authenticated session if necessary authentication cookies are blocked.

17. Global Privacy Control and Universal Opt-Out Signals

Some browsers, browser extensions, and devices allow users to communicate privacy preferences automatically. One example is Global Privacy Control, or GPC. Where Phillforce is legally required to recognize an applicable universal opt-out mechanism, we will treat a supported and legally valid signal as required by applicable law. For example, where an applicable U.S. privacy law requires covered businesses to honor a signal that communicates a request to opt out of the sale or sharing of personal information, Phillforce intends to honor that requirement. Because privacy laws and technical standards continue to evolve, the way we process universal privacy signals may change over time.

18. Do Not Track Signals

Some browsers may transmit a “Do Not Track” signal. There is not currently one universally adopted legal or technical standard governing all uses of Do Not Track signals across every jurisdiction. Phillforce may therefore respond to legally recognized universal privacy mechanisms where required rather than treating every browser Do Not Track signal as equivalent. Where applicable law requires Phillforce to honor a particular signal or preference mechanism, we will do so.

19. Third-Party Cookies

Some technologies used by Phillforce may be provided by third parties. For example, third parties may support:

authentication;
analytics;
payments;
video content;
embedded media;
customer support;
scheduling;
advertising;
security;
infrastructure.

A third-party service may place or access cookies according to the functionality being used and its own privacy practices. Phillforce seeks to use third-party technologies for legitimate business purposes and to configure them appropriately. Where third-party cookies are non-essential and consent is required by law, they should not be activated before the required consent has been obtained.

20. Google Authentication

If you choose to sign in using Google, you may be redirected to or interact with Google services. Google may use cookies or other technologies as part of its authentication process according to Google's own policies. Phillforce uses Google authentication information only as described in the Phillforce Privacy Policy and according to the permissions you authorize. Using Google authentication does not mean Phillforce receives your Google password.

21. LinkedIn Authentication

If Phillforce supports LinkedIn authentication and you choose to use it, you may interact with LinkedIn systems during the authentication process. LinkedIn may use cookies or related technologies according to its own policies and authentication requirements. Phillforce will use information received from LinkedIn according to the permissions you approve and the Phillforce Privacy Policy. Phillforce does not receive your LinkedIn password.

22. Embedded Content

Phillforce may display content provided by external platforms. Examples may include:

videos;
social media content;
scheduling tools;
demonstrations;
maps;
embedded documents;
other external media.

Some embedded services may set cookies or collect information when the content loads or when you interact with it. Where legally required, non-essential embedded content may be blocked until you consent to the relevant category of cookies or technologies. If you choose to activate embedded third-party content, the provider's own privacy and cookie practices may apply.

23. Payment Services

Where Phillforce uses an external payment processor, that provider may use strictly necessary or fraud-prevention cookies as part of the checkout process. These technologies can support functions such as:

payment security;
fraud detection;
transaction processing;
session management;
checkout functionality.

Payment providers may process information according to their own terms and privacy policies. Phillforce does not control every cookie independently used by a payment provider on the provider's own website or checkout environment.

24. WordPress and Website Infrastructure

Phillforce websites may use WordPress, website infrastructure, content-management technologies, hosting services, performance technologies, or related tools. These systems may set technical cookies needed for functions such as:

login sessions;
administrator authentication;
website security;
content delivery;
preference management;
performance;
form functionality.

The exact cookies used may change as Phillforce's technology stack evolves. We aim to keep our published cookie information aligned with the technologies actually in use.

25. Phillforce Intelligence Platform

The authenticated Phillforce Intelligence application may use cookies or similar technologies that differ from those used on the public marketing website. For example, the platform may require technologies that maintain:

authenticated sessions;
account security;
platform preferences;
workspace state;
privacy preferences;
protected application functionality.

Necessary platform cookies may remain active while you are using the authenticated service. Optional analytics or marketing technologies remain subject to the applicable choices and legal requirements.

26. Local Storage and Session Storage

Phillforce may use browser local storage or session storage where appropriate. These technologies can allow a website or application to store information within the browser. They may be used for purposes such as:

maintaining interface state;
remembering temporary preferences;
supporting application functionality;
improving performance.

Where applicable law treats the storage or access of such information in the same way as cookies, Phillforce intends to apply the appropriate consent and disclosure requirements.

27. Session Cookies

Some cookies exist only during a browser session. They may help Phillforce:

maintain login state;
preserve temporary selections;
maintain application security;
provide navigation functionality.

Session cookies are generally removed when the browser session ends, although browser behavior can differ.

28. Persistent Cookies

Some cookies remain on a device after the browser is closed. Persistent cookies may be used to:

remember preferences;
remember privacy choices;
support certain security functions;
understand repeat visits;
perform analytics where permitted.

Persistent cookies have defined expiration periods or remain until deleted. Phillforce intends to avoid retaining cookies longer than reasonably necessary for their purpose.

29. First-Party Cookies

First-party cookies are set by or for Phillforce domains. They may support functions including:

authentication;
security;
account sessions;
preferences;
analytics;
consent management.

These cookies are generally associated directly with the Phillforce website or service you are using.

30. Third-Party Cookies

Third-party cookies may be placed by external service providers whose technologies are used through Phillforce. Where applicable, these providers may include authentication, analytics, payment, media, marketing, or other technology providers. Phillforce evaluates third-party technologies based on their business purpose and the privacy obligations applicable to their use.

31. How Long Cookies Remain

Cookie duration depends on the purpose and technology. Some cookies may expire:

when you close your browser;
after several minutes;
after several hours;
after several days;
after several months;
at another defined expiration time.

Phillforce intends to configure cookie durations proportionately to their purpose. The exact duration of active cookies should be identified in the cookie preference manager or cookie register where reasonably practicable.

Because website technologies can change, Phillforce maintains or intends to maintain a current record of the cookies and similar technologies deployed through its websites and applications. The register may identify information such as: Cookie or technology name Provider Purpose Category Duration Whether it is first-party or third-party The live cookie register should reflect the technologies actually deployed on Phillforce systems. Phillforce should not publish invented cookie names or outdated cookie information merely to make the policy appear complete.

33. Analytics Providers

Phillforce may use analytics providers to understand website and product performance. Where an analytics provider is used, information collected may include items such as:

pages visited;
approximate geographic information;
browser type;
device information;
referral source;
interactions;
session activity;
conversion events.

The exact information depends on the provider and configuration. Phillforce aims to configure analytics in a privacy-conscious manner and, where required, activate non-essential analytics only after the applicable user choice.

34. Advertising Providers

If Phillforce uses third-party advertising or retargeting platforms, those providers may use cookies, pixels, or related technologies. Where such activities qualify as targeted advertising, sharing, sale, behavioral advertising, or another regulated use under applicable law, Phillforce will provide the rights, disclosures, consent mechanisms, or opt-out tools required by that law. Phillforce does not classify advertising cookies as necessary simply because advertising benefits the company.

35. European Economic Area and European Union

For visitors in the European Economic Area and other locations subject to applicable European electronic privacy rules, Phillforce will seek consent before using non-essential cookies or similar technologies where consent is required. Strictly necessary technologies may operate without consent where the applicable legal exception permits them. Users should be able to refuse non-essential technologies without being prevented from accessing ordinary website functionality that does not require those technologies. Where consent is relied upon, you may withdraw it through the applicable cookie preference mechanism.

36. United Kingdom

For users in the United Kingdom, Phillforce intends to apply applicable UK rules governing cookies and similar storage or access technologies. Where consent is required, Phillforce will seek the necessary choice. Where applicable UK law provides an exception for a particular technology, Phillforce may rely on that exception only where the relevant requirements are satisfied. Where an exception requires a simple way to object, Phillforce should provide that mechanism.

37. United States

The United States does not have one single cookie law that applies identically in every state and every circumstance. State privacy laws may nevertheless regulate certain tracking, advertising, profiling, sale, or sharing activities. Where an applicable U.S. privacy law provides a right to opt out of a relevant processing activity, Phillforce intends to provide and honor the required mechanism. More information about U.S. privacy rights is available in the Phillforce Privacy Policy.

38. California

Where California privacy law applies, certain online technologies may be relevant to rights concerning the sale or sharing of personal information or cross-context behavioral advertising. Phillforce does not sell personal information for monetary consideration. If Phillforce uses technology that constitutes regulated “sharing” or another opt-out activity under applicable California law, we will provide the legally required choice and honor applicable opt-out preference signals.

39. Other Countries

Phillforce serves a global audience. Cookie and tracking rules may differ in Canada, Brazil, Nigeria, Australia, countries throughout Africa, Asia, Latin America, the Middle East, and other jurisdictions. Where a local law imposes requirements that apply to Phillforce's use of cookies or similar technologies, Phillforce intends to comply with the applicable requirements.

40. Children's Privacy

Phillforce is designed for businesses, professionals, founders, and organizations and is not intended for children under 18. We do not knowingly use cookies to build advertising profiles of children through the ordinary operation of Phillforce. Additional information about children's privacy is available in our Privacy Policy.

41. Security

Cookies connected to authentication or security may contain identifiers that need to be protected. Phillforce uses security measures designed to protect account sessions and related information. For security reasons, we do not disclose detailed cookie-token structures, session-security configurations, authentication secrets, encryption keys, or defensive implementation details.

Phillforce will continue to evolve. We may update this Cookie Policy when:

our website changes;
our platform changes;
new analytics tools are introduced;
new integrations are introduced;
authentication providers change;
marketing technologies change;
applicable laws change;
our cookie-consent system changes;
our technology providers change.

The “Last Updated” date at the top of this Policy will indicate the current version. Where a material change requires a new consent choice under applicable law, Phillforce will seek that choice before beginning the relevant processing.

Phillforce may periodically review its websites and applications to identify cookies and similar technologies in active use. We may update our cookie register or preference center when technologies are added, removed, or changed. A cookie policy is only useful if it reflects the actual website. For that reason, Phillforce intends to align this Policy and its cookie settings with the systems currently deployed rather than relying on an outdated static list.

44. How to Contact Phillforce

If you have questions about this Cookie Policy, cookie preferences, or the way Phillforce uses tracking technologies, you may contact: Phillforce, Inc. 8 Wading Bird Loop Blythewood, SC 29016 United States Privacy: privacy@phillforce.com General enquiries: philip@phillforce.com Website: phillforce.com

Phillforce, Inc. Clarity before activity.

End of Cookie Policy