Cookie Policy
Version 1.0 · Effective 30 October 2026Previous versions
1. What this policy covers
1.1. This policy explains the cookies and similar technologies (such as your browser's local storage) used on livuria.com and app.livuria.com by FilFar Development s. r. o. ("Livuria", "we"), and the cookies that Paddle, which sells our plans, sets when you use our checkout (section 3.3). How we handle personal data in general is explained in our Privacy Policy.
1.2. A cookie is a small file a website stores in your browser. Local storage, session storage and IndexedDB are similar places in your browser where a website can keep information.
2. In short
- We use only technologies that are strictly necessary for the service you ask for (signing in, security, Private Content, checkout), that only remember what you're doing on a page (functional), or that you switch on yourself where you make the choice (your language, your billing country, "Trust this device", "Remember this device"); each says so where you choose it.
- No analytics, no advertising, no tracking cookies, and no social media plugins.
- When you open our checkout, Paddle sets its own cookies, under its own responsibility (section 3.3).
- That's why you don't see a cookie banner: nothing is stored that you didn't ask for or choose. If we ever add an optional technology, we will ask for your consent first, and you'll be able to change your choice at any time.
3. What we use
In the tables:
- strictly necessary means needed for the service you asked for, such as signing in;
- your choice means kept only because you chose it, where we tell you that it's saved in your browser;
- functional means it only remembers how you're using the page, until you close it or undo what set it.
3.1. On app.livuria.com (the Livuria app)
| Name | Type | Purpose | Duration | Category |
|---|---|---|---|---|
livuria-session |
Cookie (secure, not readable by scripts) | Keeps your visit secure while you sign in, and keeps you signed in | 120 minutes after your last activity, or until you sign out | Strictly necessary |
XSRF-TOKEN |
Cookie (secure) | Protects your account against cross-site request forgery | Like the session | Strictly necessary |
livuria_device |
Cookie (secure, not readable by scripts, sent only to our API) | Recognises your browser for security: so that you can see and sign out your devices, and so that we can alert you when your account is used on a new device. We store only a one-way hash of it, never the value itself, and we never use it to link different accounts. Set when you sign in or create an account. | 400 days, renewed each time you sign in, so that a browser you use only about once a year is still recognised, instead of setting off a new-device alert | Strictly necessary (security) |
livuria_device_trust |
Cookie (secure, not readable by scripts, sent only when you sign in) | Remembers that you chose "Trust this device", so that we don't ask for your two-factor code on it | 30 days | Your choice |
NEXT_LOCALE |
Cookie | Remembers the language you chose | 1 year | Your choice |
| Private Content device key | IndexedDB | If you choose "Remember this device" for Private Content, lets this device unlock your encrypted content | Until you choose Forget this device, turn Private Content off, or clear this browser's site data; signing out doesn't remove it | Your choice |
| Private Content lock; payment-method return | Session storage | Keeps Private Content locked when you lock it, and brings you back after updating your payment method | Until you close the tab | Strictly necessary |
| Example-setup notice | Local storage | Shows the notice about example content for 5 minutes after you load it | Until you choose Keep examples or Remove example setup, or clear this browser's site data | Functional |
| Billing country | Local storage | Remembers the billing country you chose in Plan & billing | Until you clear your browser's storage, or delete your account in this browser | Your choice |
| Pending invitation | Session storage | Keeps a plan invitation's link while you sign in or create an account | Until you accept it, or close the tab | Strictly necessary |
3.2. On livuria.com (our website)
| Name | Type | Purpose | Duration | Category |
|---|---|---|---|---|
NEXT_LOCALE |
Cookie | Remembers the language you're viewing the site in, when it differs from your browser's | Until you close your browser | Functional |
livuria:pricing-country |
Session storage | Remembers the country you chose for the prices shown on the pricing section (or that you chose the US-dollar prices) | Until you close the tab | Functional |
livuria:checkout-transaction |
Session storage | Keeps your checkout going if the page reloads | Until the checkout completes, or you close the tab | Strictly necessary |
Our public pages for cancelling a contract and withdrawing from one, "Cancel contracts here" (livuria.com/cancel) and "Withdraw from contract here" (livuria.com/withdraw), which you can use without signing in, use nothing beyond this table.
3.3. Paddle, our payment partner
Our checkout page loads Paddle.js, the script of Paddle, our reseller and Merchant of Record, when you start a purchase or update your payment method. Our other pages don't load it: the prices on our homepage come from our own server, for the country you choose, and your browser doesn't contact Paddle for them.
When Paddle.js loads, your browser connects directly to Paddle's servers (cdn.paddle.com, buy.paddle.com, api.paddle.com), which receive your IP address and browser details, as any website your browser connects to does (Privacy Policy, section 3.8). Paddle's checkout runs in a window that belongs to Paddle: what it stores in your browser, and what it loads, is Paddle's responsibility, as described in Paddle's privacy notice. We have seen Paddle set this cookie:
| Name | Set by | Purpose | Duration | Category |
|---|---|---|---|---|
__cf_bm |
Paddle, on Paddle's own domain (paddle.com), when its checkout loads; not readable by scripts | Paddle's bot protection, provided by Cloudflare: it tells people from automated traffic | About 30 minutes | Strictly necessary (Paddle's security) |
In our checks, Paddle.js set no cookies and used no storage on livuria.com itself.
4. How to manage cookies
4.1. You can delete cookies and site data, or block them, in your browser's settings. If you block the strictly necessary ones, you won't be able to sign in or use Livuria.
4.2. Deleting livuria_device means your browser will appear as a new device the next time you sign in, and we will send you a new-device alert. Deleting livuria_device_trust means we'll ask for your two-factor code again.
5. Changes to this policy
We'll update this policy when we change what we use. If we add anything optional, such as analytics, we will ask for your consent before using it, and add it to this policy before we use it.
6. Contact
FilFar Development s. r. o., Sibírska 7087/8, 080 01 Prešov, Slovakia. Email: support@livuria.com. Telephone: +421 914 284 915.
Not covered: our staff's administration site, which has its own sign-in cookies.