Loading...
Loading...
At KindredCare US, we believe in being entirely crystalline about how we collect and use data related to you. This policy provides detailed information about how we deploy server-side sessions and tracking cookies on our premium platform.
These are strictly necessary cryptographic cookies for the marketplace to function and cannot be switched off under any circumstances. They are solely activated in response to service requests such as logging into your Clerk Auth account, storing your Firebase UID, or holding Stripe session tokens for checkout securely.
These lightweight modules allow us to count programmatic visits and traffic sources via completely anonymized analytical endpoints so we can massively optimize our Next.js architecture and Vercel edge functions.
Enable the dynamic interface to provide immensely enhanced functionality and personalization, strictly like storing your preferred Nanny filters (e.g., matching "Bilingual" or "CPR Certified") to avoid repetitive selecting.
These extremely specific cookies may be injected throughout our client-side by validated marketing intelligence partners. They may be exclusively utilized by Google or Meta Pixel to orchestrate a profile of your demographic interests to safely show you KinderCare caregiver ad blocks on generic external applications safely.
Cookies are incredibly small JSON text files that are temporarily or persistently stored securely inside your browser caching system that allow KindredCare US or a PCI-compliant third party to identify your active JWT authenticated sessions. Cookies can be invoked to extract, transmit and cache essential bits of non-identifiable telemetry across diverse applications.
Whenever you execute requests into our API boundaries, we silently place a matrix of encoded `HttpOnly` security cookies locally inside your architecture to stop cross-site scripting vulnerabilities. We utilize both short-living session-tokens natively alongside persistent authorization artifacts.
"Your cryptographic security is our foundational priority. We inherently process cookie-borne data with the exact same intensive vigilance we demand from our elite childcare providers—with categorical professional integrity and a zero-trust architecture focus."
If you systematically prefer to forcibly delete historical cache metrics entirely or enforce your modern browser to strictly reject non-essential payloads moving forward, navigate simply to your core browser's security console. Please be aware that violently rejecting essential JSON-Web-Tokens forcefully will totally disable login capabilities and caregiver matching entirely.