Cookie Policy
This Cookie Policy explains how JooDesk uses cookies and related browser technologies when visitors access its public website and any account-related features currently made available.
JooDesk is a business management software platform in development. The technologies used may differ between the public website, account features, and future product releases.
This policy describes the technologies actually used by the relevant website at the time of publication. It will be updated if material changes are made to those technologies or their purposes.
1. What Cookies Are and Why They Are Used
Cookies are small pieces of information stored by a website in a visitor's browser. Related technologies can include browser session storage, local storage, security tokens, and similar mechanisms.
Depending on the features in use, JooDesk may use these technologies to:
- Maintain necessary website or authenticated session state.
- Protect forms and requests against unauthorized activity.
- Remember temporary selections or preferences where supported.
- Maintain the security and reliable operation of the website.
- Support other functions that are clearly disclosed and appropriately implemented.
The technologies actually used depend on the page and feature being accessed. JooDesk will not describe a technology as active unless it is supported by the current implementation.
2. Essential Cookies and Security Technologies
Some cookies or related technologies may be necessary for the website to function securely. These may support session management, form security, authentication, or other essential functions.
The specific names, purposes, and retention periods depend on the current configuration of the website.
Verified Technical Cookies Inventory
| Cookie / Technology Name | Category | Purpose | Type | Established Retention |
|---|---|---|---|---|
| joodesk_session | Essential | Encrypted session identifier used to maintain user authentication state, flash messages, CSRF tokens, and temporary application workflows. | HTTP Cookie (HttpOnly, Secure, SameSite=Lax) | 120 Minutes (Idle Lifetime) |
| XSRF-TOKEN | Security | Cryptographic token providing Cross-Site Request Forgery (CSRF) defense on form submissions and state-changing actions. | HTTP Cookie (SameSite=Lax) | 120 Minutes (Matches Session) |
Note: Shopping cart selections and user preferences are managed entirely within the encrypted server-side session (joodesk_session) and do not deploy separate tracking cookies.
3. Analytics, Advertising, and Tracking
JooDesk describes analytics, advertising, and tracking technologies according to what the website actually loads and uses.
The JooDesk public website does not use third-party advertising cookies, cross-site behavioral advertising trackers, or ad-targeting pixels (such as Google Remarketing, Meta Pixel, or commercial data broker trackers).
If analytics or other optional tracking technologies are introduced in the future, JooDesk will update this policy to explain their specific purposes and any relevant third-party involvement.
Where consent is legally required, relevant non-essential technologies will be handled in accordance with applicable requirements. No non-essential tracking technologies are currently active.
4. Third-Party Services
JooDesk may use third-party providers to support website hosting, authentication, security, payments, communication, or other functions.
A provider's involvement does not automatically mean it sets cookies on every page. Any description of a third-party cookie or storage mechanism is based on the actual integration and behavior of the relevant page:
- Supabase Cloud: Utilized for server-side database services and authenticated user management. On public marketing pages, client-side authentication tokens are not stored.
- Content Delivery Networks (CDNs): Public font and style libraries (Google Fonts, Remix Icon, Chart.js) are fetched securely to render website typography and icons without deploying persistent client tracking identifiers.
- Payment Processing: Commercial subscription checkout is currently deactivated for pre-launch. When activated, payment gateways handle payment transactions subject to their respective security and cookie policies.
If a third-party service is used, visitors may also be subject to that provider's applicable terms and privacy information.
JooDesk will update this section when a material change to its third-party technologies affects the information provided in this policy.
5. Managing Cookies and Browser Storage
Visitors can generally view, restrict, or delete cookies through their browser's privacy settings.
Blocking or deleting essential cookies may affect some website functions, including login sessions, form security, or other features that rely on those technologies.
Browser controls do not necessarily manage all forms of local storage or other browser-based technologies in the same way.
Where JooDesk provides an applicable preference or consent control, visitors may use that control for the purposes it supports. Because only strictly necessary operational cookies are currently in use, a separate non-essential cookie opt-out banner is not deployed.
6. Retention and Policy Updates
Cookies and related technologies may remain stored for different periods depending on their purpose, configuration, and whether they are session-based or persistent.
JooDesk will describe retention periods when they can be established reliably. Browser settings and provider behavior may also affect how long information remains available.
This policy may be updated when the website's technologies, features, or applicable legal requirements change. The “Last Updated” date will be revised when material changes are made.
Visitors should review this page periodically to understand the current use of cookies and related technologies.
7. Contact Information
For questions about this Cookie Policy or JooDesk's use of browser technologies, contact:
General Support: support@joodesk.com
Contact Page: https://joodesk.com/contact
Please do not send passwords, payment PINs, full card details, or unnecessary sensitive information in your enquiry.
The responsible legal operator's formal name, business or registered address, and any legally required grievance or complaint details must be confirmed and published where required before commercial launch. Do not invent these details.
Thank you for your interest in JooDesk.