Cookie Policy
What Artwello stores in your browser, why, and how to change it. The honest summary: one entry to keep you logged in, the support chat's memory if you use it, and nothing for analytics or advertising.
What cookies are
A cookie is a small file a website asks your browser to keep, so it can recognise your browser next time. Related technologies, local storage and session storage, do much the same thing with more room. This page covers all of them, and the law treats them alike.
Strictly necessary (always on)
These make the site work at all. They carry no advertising or profiling data, and the law does not require consent for them, because without them you could not stay logged in.
- wasp:sessionId: a local storage entry, not a cookie, holding the token that keeps you signed in. It is created when you log in and removed when you log out. Because it is local storage rather than a cookie, it is never transmitted automatically to any other site.
- Short-lived state kept by the app in your browser while you use it, for example your place in a form, or a generation still in progress.
- crisp-client/*: set by our support chat only if you open the chat window and start a conversation, so that your messages are still there as you move between pages or come back later. Nothing is stored while the chat bubble merely sits in the corner unopened. Stored for up to 6 months.
Analytics without cookies
We count visits with Umami, which works without cookies and stores nothing in your browser. It tells us, in aggregate, which pages people use; it does not recognise you on your next visit or follow you to other websites. Error reports we receive when something breaks (through Sentry) likewise store nothing in your browser.
That is why there is no cookie banner: there is nothing to ask your permission for. If we ever add analytics that does use cookies, such as Google Analytics, it will load only after you accept it in a banner, this page will list its cookies first, and a small cookie will record your choice for 12 months.
Cookies set by others
When you pay, checkout happens on Stripe's own pages. Stripe sets its own cookies there for fraud prevention and to make payment work; those are governed by Stripe's cookie policy, not ours. We never see them.
If you sign in with Google, Google's own sign-in flow is subject to Google's policies in the same way.
Our support chat is operated by Crisp IM SAS (France), whose servers are in the European Union. The chat window loads on our pages but stores nothing in your browser until you open it and write to us. Crisp is listed in our Subprocessors page.
What we do not use
We do not use advertising cookies, retargeting or remarketing pixels, social media trackers, or any cookie that follows you to other websites. We do not sell or share data collected through cookies. If that ever changes, this page will change first and a banner will ask you before anything loads.
Changing your mind
Nothing we use today needs your consent, so there is nothing to withdraw. If we introduce anything that does, a "Cookie settings" link will appear at the bottom of every page in the app, so you can change your choice as easily as you made it.
The support chat stores nothing unless you open it, so there is nothing to decline in advance. Simply not opening it is the choice. If you have already chatted with us and want that removed, ask us and we will delete the conversation and the contact profile behind it.
Every browser also lets you block or delete cookies wholesale, usually under Privacy or Site settings. Blocking the strictly necessary items will log you out and make parts of the site stop working, and blocking storage entirely will prevent you from signing in at all.
Questions
Ask us at [email protected]. How cookie data fits into everything else we process is described in our Privacy Policy.