← Liora

Privacy Policy

Effective: September 8, 2026

This page explains what Liora collects and why. We keep this short on purpose: we collect the minimum we need to run the service.

What we collect

If you create an account, we collect the data needed to run the service for you:

  • your email address and login credentials
  • the tasks and calendar events you add or connect
  • basic usage data (like device and browser type) so we can keep the app working correctly

Why we collect it

To run your account and your subscription, and to provide the calendar and task features you use.

What we don't do

We don't sell, rent, or share your personal data with anyone — not with advertisers, not with marketers, not with "partners". Ever. On the technical side, your data is handled only by our hosting provider (storage) and Paddle (when you pay).

Payment data

Payments are handled entirely by Paddle.com Market Ltd, acting as merchant of record. Paddle is the seller on your receipt, processes your card and handles VAT. Liora never sees or stores your card number.

Who else processes your data

Liora works with three processors and no one else:

  • Hetzner Online GmbH — servers in Germany, where your account and your day are stored. Data does not leave the EU.
  • Paddle.com Market Ltd — payments and invoices. Paddle is based in the United Kingdom, which the European Commission has recognised as providing adequate data protection.
  • Google Ireland Ltd — Google OAuth, if you sign in with Google or connect your calendar. From your Google profile we receive four things and nothing else: first name, last name, email address and profile picture. The Google Calendar API is used only while the calendar connection is on.
  • Resend — sends the emails the service needs: sign-in codes, password resets and billing notices. Resend sees your email address and the text of those letters, nothing else.

Google Calendar data

If you connect a Google account, Liora reads the list of your calendars and the events from the calendars you choose. We use this only to show your schedule inside Liora.

Access is read-only. Liora cannot create, change or delete anything in your Google Calendar.

Event data is stored on our servers only to render your day, and is deleted when you disconnect the integration or delete your account. We don't sell it, don't use it for advertising, and don't share it with third parties. No person reads it, except where required for security or by law.

Liora's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect your data

Everything you keep in Liora is protected by the measures below — your account and password, your tasks and your day, your subscription record, and the sensitive data that comes from the Google connection: the tokens that authorise it and the calendar events read on your behalf.

  • Encrypted in transit. Every connection is served over HTTPS with TLS 1.2 or newer, including traffic between our own servers. Plain HTTP is redirected and never carries data.
  • Encrypted at rest. Account passwords are stored as bcrypt hashes and never in readable form. Google refresh tokens are stored only as AES-256-GCM ciphertext, with the key held in the server environment and never in the database, so a copy of the database on its own cannot be used to reach your Google account. Card numbers we never receive at all — Paddle handles them.
  • Least privilege. We ask for the minimum we need. From Google that means two read-only calendar scopes and nothing more, so the application is technically unable to create, change or delete anything in your Google account.
  • Access control. Sessions use HttpOnly, Secure, SameSite cookies and are held server-side, so they can be revoked. Every request for your data — tasks, day, calendar, subscription — is authorised against the signed-in user, so one account can never read another account's data. Each internal service connects to the database under its own login, limited to the data that service needs.
  • Hardened infrastructure. Servers are hosted by Hetzner in Germany, in ISO/IEC 27001 certified data centres. Databases and internal services are not exposed to the internet — the firewall publishes HTTPS only. Administrative access is by SSH key, password logins are disabled, and access is limited to the data controller named below.
  • Abuse protection. Sign-in, registration and password reset are rate limited per client, and verification codes expire and are invalidated after a fixed number of failed attempts.
  • Deletion. Deleting your account erases your data within 30 days. Disconnecting the Google integration deletes the stored refresh token and every event imported from Google, without waiting for anything else.
  • No human access, no model training. Nobody reads the content of your day, your tasks or your calendar, and none of it is ever used to train, fine-tune or improve any AI or machine-learning model — ours or anyone else's. Access would only occur with your explicit permission, for a security investigation, or where the law requires it.

Found a security problem? Write to hello@liorasystem.com — we answer security reports before anything else.

Cookies

Liora sets only technical cookies — the ones needed to keep your account working and to remember the language and the look you chose. None of them tracks you. We use no analytics, tracking, advertising, or third-party cookies. That's also why there is no cookie banner: there's nothing to consent to. If this ever changes, we'll update this policy first and ask for your consent.

Your rights

Under the GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, and to hand it over in a portable format. Write to hello@liorasystem.com — we answer within 30 days and delete, no questions asked.

We process your data to perform our contract with you (your account and subscription), and — for the calendar connection — on the consent you give when you connect Google. You can withdraw that consent at any time by disconnecting the integration.

If you think we handle your data wrongly, you can complain to your local data protection authority. In Poland that is the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw.

How long we keep it

We keep account data for as long as your account is active. After you delete your account we erase it within 30 days, except billing records, which Paddle and we keep for as long as tax law requires.

Changes to this policy

If we change how we handle your data in a meaningful way, we'll let you know by email.

Who is responsible for your data

The data controller is Aleksandr Svistun, a private individual based in Poland, reachable at hello@liorasystem.com. Write to that address with any question about your data or to exercise any of the rights above.