Cookie Policy
Dwelvia uses strictly necessary cookies only — the ones without which the service would not work (sign-in and session security) — plus a cookie with the language you chose yourself. We do not use cookies for analytics, advertising or tracking.
Effective from 24 October 2026.
What cookies are
A cookie is a small piece of data a site stores in your browser to "remember" you between requests (for example, that you are signed in). Under Ukrainian and EU law (GDPR/ePrivacy) and UK law (PECR), strictly necessary cookies and settings you chose yourself do not require separate consent — but we inform you about them anyway.
Which cookies we set
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
ha_session | Keeps your sign-in session — so you don't log in on every page.
Marked HttpOnly (not accessible to JavaScript), SameSite=Lax, and on the site
Secure (HTTPS only). |
Necessary | Without «Remember me» — until the browser is closed; with it — 30 days |
ha_csrf | A cross-site request forgery (CSRF) protection token — the security of
your actions. SameSite=Lax. |
Necessary | Same as ha_session |
ha_lang | The language you picked with the 🌐 switcher — so the server shows pages in it straight away. Set only after your choice. | Preference | 1 year |
| Cloudflare cookies | All site traffic passes through Cloudflare (protection against attacks and bots); when a check is needed, Cloudflare may set its own technical security cookie. | Necessary (security) | Set by Cloudflare |
The «Sign in with Google» button and the home page font are loaded from Google's servers; Google's own rules apply to Google's domains.
Data in your browser (localStorage)
Besides cookies, we store in your browser (locally):
- interface settings — the theme, panel state, which plan is open, the fact that you dismissed the cookie notice;
- the chosen language and country (for the calculators) and the language of the last page you opened;
- the first-visit source (
ha_attr: UTM tags, referrer, first page, browser language, device type) — once per browser session it is sent to our server in an anonymous visit event, and it is saved on the account at registration (see the Privacy Policy).
The rest of this data is not sent anywhere.
Why there is no consent banner
Consent is needed only for cookies the service could work without (analytics, advertising). We have none: all of the above is strictly necessary or your own setting. So we show a short cookie notice once instead of an «accept / reject» banner.
How to disable cookies
You can delete or block cookies in your browser settings. Note: without ha_session and
ha_csrf, sign-in and saving projects will not work, as these cookies are necessary for the
service to operate.
Changes and contact
If optional cookies (e.g. analytics) appear in the future, we will update this page and ask for your consent before setting them. Privacy questions — [email protected] or the in-app feedback form. Updated: October 2026.