Legal

Privacy Policy

Kliourr (www.kliourr.com) is a library of UI components and App Kits. To run it we need a small amount of personal data, and this page sets out exactly what that is, why we have it, who helps us process it, and how you can see, fix or delete it.

Effective
19 November 2026
Last updated
21 November 2026

01The short version

  • We collect what an account needs (your name, email address and a scrambled form of your password) and what you do with it (which components you unlock, your plan).
  • We use cookies only to keep you signed in and to keep sign-in safe. There are no advertising cookies, no third-party analytics and no third-party pixels. We count visits ourselves, without cookies, and keep no IP address with them.
  • We don't sell or rent your personal data, we don't share it for advertising, and we don't use it to train AI models.
  • A few providers help us run the site (hosting, the database, Google and GitHub sign-in, and account email). They process data for us under contract.
  • You can download, correct or delete your data yourself in your account settings at any time, or write to support@kliourr.com.

02Who we are

Kliourr (“Kliourr”, “we”, “us”) is operated by [legal entity name], a [type of entity, e.g. sole proprietor / private limited company] registered in [country] ([company or registration number, if any]), with its address at [registered address].

For the personal data described here, we are the controller under the EU and UK General Data Protection Regulation (GDPR), the business under the California Consumer Privacy Act (CCPA), and the data fiduciary under India's Digital Personal Data Protection Act, 2023 (DPDP Act).

Privacy questions and requests go to support@kliourr.com. Our grievance officer for India and point of contact for privacy matters is [name and title of the person responsible].

Representatives. If we have no establishment in the EU or the UK and the GDPR requires one, our EU representative is [EU representative name and address, or “not appointed”] and our UK representative is [UK representative name and address, or “not appointed”].

03What we collect

What you give us

  • Account details. Your name and email address when you sign up. If you sign up with a password, we store only a one-way bcrypt hash of it, never the password itself.
  • Google sign-in. If you choose “Continue with Google”, Google tells us your name, your email address and that the address is verified. We ask for nothing else: no contacts, no files, no access to your Google account. If an account with that email already exists, signing in with Google opens it.
  • GitHub sign-in. If you choose “Continue with GitHub”, GitHub tells us your name, your username and your account's email addresses, and we keep only your primary address, and only if GitHub has verified it. We don't see your repositories, code or anything else on GitHub. If an account with that email already exists, signing in with GitHub opens it.
  • Messages. Anything you send when you email us, such as a support or privacy request.

What we record as you use Kliourr

  • Plan and unlocks. Your plan (Starter, Pro or Exclusive), which components you have unlocked and which App Kits you have taken, and when, so we can show your code and count this month's unlocks and kits.
  • App Kit downloads. Whether your plan allows a download. We don't keep a separate history of which kits you download.
  • Technical data. Like every website, our servers receive your IP address, browser and device type, the page you asked for, and the time. Our host keeps these request logs for a short period. We also hold IP addresses briefly in server memory to limit repeated sign-in and sign-up attempts.
  • Visit statistics. For each page you view we keep the page, the site or campaign that sent you (for example google.com), your country (worked out by our host from your IP address, which we don't keep), and your device type, operating system and browser name. To count visitors without a cookie, we also keep a code made from the day's date, a secret, your IP address and your browser. It changes every day, can't be turned back into your IP address and isn't linked to your account. If your browser sends Global Privacy Control or Do Not Track, we don't count your visit at all.

What we don't collect

We don't collect payment card details (payments aren't switched on yet; see Payments), precise location, government IDs, or any special category of data such as health, religion or biometrics. We don't run third-party analytics, session recording, advertising or social-media tracking scripts. Please don't send us sensitive data you don't need to.

04How we use it, and our legal bases

The GDPR asks us to name a legal basis for each use. Where a law outside the EU and UK applies, we rely on the equivalent ground in that law (for India, your consent or a legitimate use the DPDP Act allows).

PurposeCreating and running your account, signing you inDataName, email, password hash, session cookie, Google or GitHub profileLegal basis (GDPR)Contract: needed to provide the service you signed up for
PurposeUnlocking components and App Kits, counting your monthly allowanceDataPlan, unlocks, App Kits taken and their datesLegal basis (GDPR)Contract
PurposeKeeping the site and accounts secure: rate limits, preventing abuse and fraud, fixing errorsDataIP address, request logs, sign-in attemptsLegal basis (GDPR)Legitimate interests: protecting you, other members and the service
PurposeUnderstanding how the site is used, to improve itDataVisit statistics: page, referring site, country, device type, operating system, browser, daily visitor codeLegal basis (GDPR)Legitimate interests: knowing what people use, with no cookie and no profile of you
PurposeAnswering your messages and requestsDataEmail address, what you writeLegal basis (GDPR)Contract, or legitimate interests where you aren't a member
PurposeAccount emails: password-reset links and confirming a new email addressDataName, email addressLegal basis (GDPR)Contract
PurposeBilling, tax and accounting, once payments openDataPlan, invoices, billing countryLegal basis (GDPR)Legal obligation, and contract
PurposeComplying with the law and defending legal claimsDataWhatever is relevant to the matterLegal basis (GDPR)Legal obligation, legitimate interests

Where we rely on legitimate interests, we have weighed them against your rights, and you can object (see Your rights). We don't make decisions about you based solely on automated processing that have legal or similarly significant effects. Monthly unlock limits are applied automatically, but they only follow the plan you chose.

The only emails we send are the ones you ask for: a password-reset link, or a link to confirm a new address. We don't send marketing emails today. If we start, we'll ask first where the law requires it, and every message will carry a way to unsubscribe.

05Cookies and browser storage

We use a handful of first-party cookies and two browser-storage entries. All of them are strictly necessary for something you asked for, so we don't show a consent banner. We use no advertising, analytics or cross-site tracking cookies, and no third party sets cookies through our pages.

Namekl_sessionWhat it doesKeeps you signed in. A signed token holding only your account ID and a random session ID, which we also keep on your account so that you're signed in on one device at a time. HttpOnly, Secure, SameSite=Lax.Lasts30 days, or until you log out
Namekl_googleWhat it doesProtects Google sign-in from forgery while you're on Google's page (state and PKCE check). Set only if you use Google sign-in.Lasts10 minutes, deleted on return
Namekl_githubWhat it doesProtects GitHub sign-in from forgery while you're on GitHub's page (state and PKCE check). Set only if you use GitHub sign-in.Lasts10 minutes, deleted on return
Namekl_adminWhat it doesSigns in the site's owner to the admin area. Never set for members.Lasts2 hours
Namekl_admin_pinWhat it doesThe owner's second sign-in step for the admin area. Never set for members.Lasts5 minutes
Namekl:viewerWhat it doesBrowser local storage, not a cookie. A copy of your name, email, plan and unlocks so pages show you as signed in without a flash. It never leaves your device and is cleared when you log out.LastsUntil you log out or clear site data
Namekl:announcements-closedWhat it doesBrowser local storage, not a cookie. Remembers which announcements (a band across the top or a popup) you closed, so they don't come back. It never leaves your device.LastsUntil you clear site data

You can block or delete cookies in your browser settings. If you block kl_session, you won't be able to stay signed in. Because we don't track you across sites, there's nothing for a “Do Not Track” or Global Privacy Control signal to switch off, but we honour both.

06Who helps us run Kliourr

These providers process personal data on our behalf, only on our instructions and under data-processing terms. We don't allow them to use it for their own purposes.

ProviderVercel Inc.What forHosting, content delivery, running the site's server code, request logsWhereUnited States, with edge servers worldwide
ProviderSupabase Inc.What forThe database that holds accounts and unlocksWhere[database region, e.g. US East / EU (Frankfurt)]
ProviderGoogle LLCWhat forSign in with Google, only if you use itWhereUnited States and worldwide
ProviderGitHub, Inc.What forSign in with GitHub, only if you use itWhereUnited States and worldwide
ProviderResend, Inc.What forSending account emails (password resets, confirming a new email address)WhereUnited States
Provider[email provider]What forReceiving and answering email sent to support@kliourr.comWhere[location]

Our pages load nothing from other companies: the site's typeface is served from our own servers, so your browser doesn't contact Google Fonts or any other third party just to show you a page. Google sign-in is covered by Google's Privacy Policy, and GitHub sign-in by GitHub's Privacy Statement.

We may also disclose personal data (a) to professional advisers such as lawyers and accountants, under confidentiality; (b) when required by law, court order or a lawful request from a public authority, and only to the extent required; (c) to protect the rights, safety or property of our members, the public or Kliourr; and (d) to a buyer or successor if Kliourr is sold, merged or reorganised, in which case this policy continues to apply to your data and we'll tell you before it becomes subject to a different one.

We'll update this list before adding a provider that processes your personal data.

07International transfers

Our providers are based in the United States and run servers in several countries, so your data may be processed outside the country where you live, including outside the European Economic Area, the UK and India.

When we transfer personal data from the EEA, the UK or Switzerland to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (with the UK Addendum where relevant), or on the recipient's certification under the EU–US Data Privacy Framework and its UK and Swiss extensions, together with additional safeguards where needed. You can ask us for a copy of the relevant safeguards. Transfers out of India follow the DPDP Act and any restrictions the Indian government sets under it.

08How long we keep it

We keep personal data only as long as we need it for the purposes above:

DataAccount details, plan and unlocksKept forAs long as your account exists. Deleted at once when you delete your account, or within 30 days of a deletion request sent by email, apart from anything we must keep under the rows below.
DataSession and sign-in cookiesKept forAs shown in the cookie table above.
DataVisit statisticsKept forUp to 400 days, then deleted. The visitor code in them changes every day.
DataRate-limit records (IP address, attempt count)Kept forHeld in server memory for 15 minutes to 1 hour, never written to the database.
DataPassword-reset and email-change linksKept forThey stop working after 30 minutes and 1 hour. We don't store them; a reset link also stops working once used.
DataServer request logs at our hostKept forA short period set by our hosting plan, currently [log retention, e.g. up to 30 days].
DataDatabase backupsKept forOverwritten on a rolling basis within [backup retention, e.g. 7 days]. Deleted data disappears from backups as they roll over.
DataEmails with usKept forUp to 2 years after the conversation ends, unless still needed for an open matter.
DataBilling and tax records, once payments openKept forAs long as tax and accounting laws require, typically 6 to 10 years depending on the country.

We may keep data longer where the law requires it, or where it's needed to establish, exercise or defend a legal claim. Data we no longer need is deleted or irreversibly anonymised.

09Security

We protect your data with measures suited to what we hold, including:

  • HTTPS on every page, and a strict Content Security Policy and security headers.
  • Passwords stored only as bcrypt hashes, so even we can't read them.
  • Sign-in cookies that are signed, HttpOnly and Secure, so page scripts can't read them.
  • A database closed to the public internet API (row-level security with no public policies); only our server can read it.
  • Limits on repeated sign-in, sign-up and email attempts.
  • Changing or resetting your password signs out every other session at once.
  • A two-step sign-in (password, then PIN) for the owner's admin area, with short sessions.
  • Access to personal data limited to the people who need it to run Kliourr.

No system is perfectly secure, and we can't guarantee that data will never be accessed without permission. Use a strong, unique password and keep your devices safe. If you think your account has been compromised, write to us right away at support@kliourr.com.

10Your rights

Depending on where you live, you have some or all of these rights over your personal data. Under the GDPR and UK GDPR you have all of them:

  • Access: get a copy of the personal data we hold about you and how we use it.
  • Correction: have inaccurate or incomplete data fixed.
  • Deletion: have your data erased (see Deleting your account).
  • Portability: receive the data you gave us in a common, machine-readable format, or have it sent to another provider.
  • Restriction: ask us to pause using your data while a concern is looked into.
  • Objection: object to uses based on our legitimate interests, and to any direct marketing at any time.
  • Withdrawing consent: where we rely on consent, withdraw it at any time. This doesn't affect what we did before.
  • Complaint: complain to your data-protection authority, such as your EU country's supervisory authority or the UK Information Commissioner's Office (ico.org.uk). We'd appreciate the chance to sort it out first.

How to use them

Most of this you can do yourself, at any time, in the Settings section of your account: download a copy of your data, change your name, email or password, and delete your account. For anything else, email support@kliourr.com from the address on your account, saying what you'd like. We may ask for a little more to confirm it's you before acting. We'll reply within one month (or the shorter time your law sets), and if a request is complex we may extend that as the law allows, telling you why. Using your rights is free, unless a request is clearly unfounded or excessive.

Other privacy laws, such as Brazil's LGPD, Canada's PIPEDA, Australia's Privacy Act and Switzerland's FADP, give similar rights, and we honour them the same way.

11California and other US states

This section applies to residents of California and other US states with consumer privacy laws, such as Colorado, Connecticut, Virginia, Utah, Texas, Oregon and others.

  • Categories we collect (in the past 12 months): identifiers (name, email, account ID, IP address); internet or network activity (request logs, unlocks, visit statistics); and commercial information (your plan). Sources: you, your use of the site, and Google if you use Google sign-in. Purposes and retention are set out above.
  • No sale or sharing. We don't sell personal information and don't “share” it for cross-context behavioural advertising, and haven't in the past 12 months. We have no actual knowledge of selling or sharing data of anyone under 16.
  • Sensitive information. We don't collect sensitive personal information for inferring characteristics about you. Your password is used only to sign you in.
  • Disclosures for a business purpose. We disclose the categories above to the service providers listed in Who helps us run Kliourr, for hosting, storage, sign-in and security.
  • Your rights. To know and access, delete, correct, and opt out of sale, sharing, targeted advertising and profiling (none of which we do), and not to be discriminated against for using these rights. You can use an authorised agent; we'll ask for proof of their authority and may ask you to confirm your identity.
  • Appeals. If we decline your request, you can appeal by replying to our decision. If you're still unhappy, you can contact your state attorney general.

12India (DPDP Act)

If you are in India, the DPDP Act and its rules give you, as a data principal, the right to:

  • a summary of the personal data we process about you and how, and the identities of others we've shared it with;
  • have it corrected, completed, updated or erased;
  • withdraw consent you've given, as easily as you gave it;
  • a readily available way to have grievances heard; and
  • nominate someone to exercise your rights if you die or become incapable.

Send requests and grievances to our grievance officer, [name], at support@kliourr.com. We'll respond within the time the DPDP rules set. If you aren't satisfied, you can complain to the Data Protection Board of India. Under the Act, you must not file false or frivolous complaints or impersonate someone else.

13Deleting your account

You can delete your account yourself: open Settings in your account, choose “Delete account” and type your email to confirm. Your account details, plan and unlocks are deleted at once and you're signed out. Deletion is permanent: your unlocked components and any plan go with it.

If you can't sign in, email support@kliourr.com from the address on the account. We'll confirm it's you, delete the account within 30 days and tell you when it's done.

Some records may remain for a limited time where the law requires it (for example billing records, once payments open) or in rolling backups until they're overwritten, as described under How long we keep it. Code you copied and App Kits you downloaded live on your own devices; we can't remove those, and deleting your account doesn't change the licence terms you received them under.

Logging out clears the kl_session cookie and the kl:viewer copy in your browser. If you used Google sign-in, you can also remove Kliourr's access from your Google account settings, and if you used GitHub, from your GitHub authorised apps.

14Payments

Paid plans aren't open yet, so we don't currently collect or process any payment information. When payments open, they'll be handled by a dedicated payment processor that is certified to the PCI DSS standard. You'll enter card details on the processor's own page, and we'll never see or store your full card number.

We'll receive only what we need to run your subscription and meet tax rules: for example the plan, payment status, the last four digits and expiry of the card, your billing country and invoices. Before payments open, we'll update this policy to name the processor and its role.

15Children

Kliourr is a tool for designers and developers and isn't directed at children. You must be at least 18 years old, or the age of majority where you live if that's higher, to create an account, and we ask you to confirm this when you sign up. We don't knowingly collect personal data from anyone younger.

If you believe a child has given us personal data, email support@kliourr.com and we'll delete it promptly.

16If something goes wrong

If a personal-data breach happens, we'll contain it, investigate it and take steps to limit the harm. Where the law requires it, we'll notify the relevant authority (under the GDPR, within 72 hours of becoming aware of it; in India, the Data Protection Board as the DPDP rules require) and tell affected members without undue delay. We'll say what happened, what data was involved, what we're doing about it, and what you can do to protect yourself.

17Other things worth knowing

Code and App Kits you take away

Components and App Kits contain demo content only, never other members' data. Once you use them in your own projects, how those projects handle their users' data is your responsibility. Some component code loads typefaces from Google Fonts; if you use it on your own site, mention that in your own privacy notice or host the fonts yourself.

AI tools and future access methods

We may later offer other ways to reach Kliourr, such as an API or integrations with AI assistants and developer tools. If we do, we'll update this policy before launch to cover any new data involved. We don't sell your data to AI companies or use it to train AI models.

Our Terms

Your use of Kliourr is also governed by our Terms of Service.

Links to other sites

Our pages link to other websites, such as Google. Their privacy practices are their own, and we encourage you to read their policies.

18Changes to this policy

We'll update this policy when what we do with data changes, or when the law does. The date at the top shows when it last changed. If a change materially affects how we use your personal data, we'll tell you in advance, by email or with a notice on the site, and ask for your consent where the law requires it. Earlier versions are available on request.

19Contact us

[legal entity name]

[registered address]

Email: support@kliourr.com

Website: www.kliourr.com

Privacy contact and grievance officer: [name and title]

If anything in this policy is unclear, or you want to know more about how we handle your data, write to us. A person will reply.