At Dayforce HCM North America Portfolio, we treat browser data as a component of your professional security. This policy outlines how we utilize localized files to maintain session persistence during your dayforce login and ensure identity verification across our HCM infrastructure.
We categorize every cookie file by its functional weight. Our systems prioritize "Strictly Necessary" tokens to prevent unauthorized interception of payroll data during a dayforce sso login event.
Session cookies are purged automatically upon browser termination to prevent local cache vulnerabilities in shared office environments.
Essential for identifying the user throughout a complex dayforce hcm login sequence. Without these, the server cannot maintain your "Logged In" status as you navigate between payroll reports and tax filings.
Stored locally to remember your regional language settings and multi-factor authentication (MFA) "Trust this Device" selections for up to 30 days.
Aggregated, non-identifiable telemetry that helps our administrators detect lag spikes during peak dayforce sign in windows across the North American network.
Supports the dayforce single sign on bridge between corporate identity providers (like Okta or Azure) and the Dayforce HCM core database.
Users retain the inherent right to modify their local storage policy through browser settings. These global controls override any site-specific preference. To maintain the highest level of security for your dayforce account sign in, we recommend clearing your cache when transitioning between shared computers or public networking environments.
Operational Infrastructure 2026
This policy is governing the dayforce website under our Portfolio management. Third-party identities, such as Greystar systems or regional benefits portals accessed via dayforce log in, may deploy their own distinct telemetry markers independent of this policy.
All dayforce hcm sign in session tokens are encrypted at rest on the client browser using AES-256 standards. We do not store plain-text credentials within cookie files under any circumstances.
If you have specific questions regarding our tracking protocols or wish to audit your session data, please contact our Compliance Officer:
Your acceptance of our session protocols ensures a stable connection to your payroll records.
