Cookie Policy
Every cookie Cloudesk uses, what it does and how long it lasts. It's a short list.
The short version
- Only strictly necessary cookies: signing in, protecting sign-in, store carts and portals.
- No analytics, advertising or social-media trackers — so there's no consent banner to click through.
- Preferences like dark mode and drafts stay in your own browser.
This summary is for convenience. The full text below is what applies.
Contents
1.Our approach
Cookies are small files a website asks your browser to keep; similar technologies such as local storage work in much the same way. Cloudesk uses them only where they are strictly necessary to provide the service you ask for — keeping you signed in, protecting sign-in, remembering your cart on a store — and to remember choices you make, such as light or dark mode.
We do not use analytics, advertising, profiling or social-media cookies, and the marketing website loads no third-party trackers. Images on these pages are served from our own servers, and we use your device's own fonts. Because every cookie we set is strictly necessary, the law (including the EU ePrivacy rules and the GDPR, the UK PECR, and India's DPDP Act) doesn't require a consent banner, so we don't show one. If we ever add a cookie that isn't strictly necessary, we will ask for your consent first and update this page.
2.Cookies on this website and in the app
| Name | Purpose | Lasts |
|---|---|---|
cc_session | Keeps you signed in. Holds a random token; the server stores only its hash. HttpOnly, SameSite=Lax, Secure on HTTPS. | 30 days, or until you sign out |
cc_org | Remembers which workspace you had open, so you return to it. | 1 year |
cc_mfa | Carries a sign-in that is waiting for your two-step code. | 5 minutes |
cc_oauth | Protects “Sign in with GitHub” against forged requests. | 10 minutes |
cc_sso | Protects single sign-on through your company's identity provider. | Minutes, during sign-in |
cc_mail_oauth | Protects connecting a Gmail or Microsoft mailbox. | 10 minutes |
3.Cookies on sites and stores built with Cloudesk
Websites, stores, catalogues and portals that our customers publish with Cloudesk can set these strictly necessary cookies for their visitors:
| Name | Purpose | Lasts |
|---|---|---|
cc_cart_… | Remembers the shopping cart on a store. | 30 days |
cc_cat_… | Remembers that you entered the access code for a private catalogue. | 30 days |
cd_portal_… | Keeps a customer or supplier signed in to a business's portal. | 30 days, or until signing out |
Published sites run no third-party scripts of ours. The business that owns a site is responsible for its own cookie and privacy notices, and for anything it adds to its site; a site may also remember, in your browser's local storage, that you have already seen or dismissed one of its pop-ups.
4.Local and session storage
The app keeps some things in your browser's own storage, on your device only, so it works the way you left it. Nothing here is used to track you:
- Your light/dark theme choice (
cc-theme). - Unsent mail and chat drafts, recent searches, which sidebar groups and calendars you collapsed or hid.
- Point-of-sale carts and held orders, and changes waiting to be sent when you are offline.
- Sound and label-printing preferences, the builder's clipboard, and which reminders you dismissed today.
- While you sign up, your answers so far are kept in session storage (never your password) and cleared when you finish or close the tab.
You can clear these at any time from your browser settings; the app will simply forget those preferences.
5.Payment and sign-in partners
When you choose to pay an invoice, Razorpay's checkout opens over the page (or you are taken to Stripe's checkout). When you connect a mailbox or sign in with GitHub, Google or Microsoft, you go to their pages. These partners may set their own cookies, which are needed to complete the payment or sign-in securely and are covered by their own cookie and privacy policies. Nothing from them loads on our marketing pages.
6.Controlling cookies
Most browsers let you see, block and delete cookies. Because ours are strictly necessary, blocking them will stop sign-in, carts and checkout from working. Deleting cc_session signs you out. For more about how we handle personal data, see the Privacy Policy. Questions? use the details on our contact page.