1. Overview
Cookies, local storage, pixels, SDK storage, and similar technologies help the service remember state, protect accounts, measure reliability, and support payment and embedded provider flows.
Some technologies are required for the service to work. Others should be optional where consent is required by local law.
2. Strictly necessary technologies
These technologies are needed for sign-in, session continuity, CSRF protection, abuse prevention, rate limiting, load balancing, checkout, security logging, and workspace access control.
- Authentication and session cookies.
- Security, CSRF, and anti-abuse tokens.
- Checkout and payment-flow state from payment providers.
- Load-balancing, reliability, and error-recovery identifiers.
3. Preference technologies
Preference storage can remember display choices, theme mode, region, dismissed notices, and similar settings so the product behaves consistently across visits.
Preference storage is not used to make high-impact decisions about users.
4. Analytics technologies
Analytics help MeshDay understand aggregate funnel health, feature use, reliability, errors, activation, and retention. Production analytics should avoid placing personal data in URLs, event names, or free-text properties.
Where required, analytics should run only after the user has given consent, and users should be able to change that choice later.
5. Third-party technologies
Providers such as Stripe, hosting platforms, analytics tools, support tools, identity services, security services, and embedded content providers may set their own cookies or local storage when their services are used.
Those providers may act as processors, independent controllers, or separate service providers depending on the feature and jurisdiction. Their own terms and notices apply to their technologies.
6. Choices
Users can often block or delete cookies through browser settings. Blocking required cookies can prevent sign-in, checkout, workspace access, security checks, or other core functions from working.
A production consent tool should let users accept or reject optional categories where required and should record consent state for auditability.
7. Changes
This notice should be updated when MeshDay adds or removes cookie categories, analytics tools, payment providers, embedded services, regions, or consent-management features.