Cookies and local storage
Last updated: 3 November 2026
allqus uses only what is needed to work. There are no tracking cookies, advertising cookies or third-party analytics, so we don’t ask you to accept cookies.
Cookies
| Name | Purpose | Kept for |
|---|---|---|
| sb-…-auth-token | Keeps you signed in (only when you have an account) | Until you sign out, refreshed while you use the site |
| allqus_admin | Administrator session (only for the operator) | 8 hours |
Local storage in your browser
Some settings are saved in your browser only (not sent to us), for example: light or dark theme, whether the side menu is open, editor preferences in Docs (zoom, ruler), ad preferences and the list of ads you’ve seen, the time used as a guest, a draft of the project open in Coder (so your work isn’t lost if the page closes), the Swiss alerts you hid, whether you hid the weather background, the app lock setting (only an identifier of the lock key, never biometric data), the app’s own files when you install allqus as an app (program files and an offline page only, never your chats or answers), and the WhatsApp number you last typed in Write a message (so you don’t have to type it again; delete it by clearing the field). You can delete them at any time in your browser’s settings (“Clear site data”).
Third parties
If you click a link to another website, or sign in with Google, or pay with Stripe, or open WhatsApp from Write a message, or click an affiliate link (Awin and the shop), those services set their own cookies under their own policies. Advertisers’ websites are reached through a short redirect that only counts the click. Previews in Coder run on a separate, sandboxed page that can’t read our cookies or storage; code you run there may load libraries from public CDNs (jsDelivr, esm.sh).