Legal

Cookies and local storage

Effective November 2, 2026. This notice is part of our Privacy notice and uses the defined terms of our Terms of Service. It describes every cookie and every similar item of browser storage that the Clarté website and the Clarté app set or read, why each exists, how long it lasts, and how you control it.

1. Summary

The website and the app do not use advertising cookies, cross-site tracking cookies, third-party analytics tools, social-media pixels, session-replay tools or fingerprinting. We do not sell your personal information and we do not share it for cross-context behavioral advertising. We set a small number of first-party items, most of them strictly necessary to run the service, and a few optional ones that depend on your choices in the Consent Center. The only third party that your browser contacts when it loads a public page is the font service described in Section 9.

2. Definitions and interpretation

2.1 Defined terms. In this notice: “Clarté”, “we” and “us” mean LIKE A KING INC., a New York corporation doing business in California as Clarté; “Services” means the website at theclarte.pro, the Clarté progressive web app (the “App”) and the services offered through them; “Cookie” means a small text file that a website stores in your browser and sends back to the website that set it; “Similar Technology” means any other mechanism that stores or reads information on your device, including session storage, local storage, Cache Storage, service workers, and push subscriptions; “Strictly Necessary” means needed to provide a feature that you have asked for or to keep the Services secure; “Consent Center” means the banner and preferences dialog that appear on the website and that you can reopen at any time from “Your privacy choices” in the footer; “GPC” means the Global Privacy Control signal; “Personal Information” has the meaning given in the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act (Cal. Civ. Code § 1798.100 and following) (the “CCPA”); and “Privacy Notice” means our Privacy notice.

2.2 Interpretation. Headings are for convenience only. “Including” means “including without limitation”. A reference to a statute or regulation includes it as amended or replaced. Where this notice and the Privacy Notice address the same subject, the Privacy Notice controls on your rights and this notice controls on the technical description of the items listed in Section 4. This notice is to be read in favor of your privacy where it is ambiguous.

2.3 Scope. This notice covers the Services as they exist on the effective date. It does not cover websites that we link to or that link to us, which have their own practices.

3. Legal framework

3.1 California. The California Online Privacy Protection Act (Cal. Bus. & Prof. Code § 22575 and following) requires us to disclose how we respond to Do Not Track signals and whether third parties collect information about your online activities. The CCPA gives you the right to know, delete, correct, opt out of the sale or sharing of Personal Information, and limit the use of sensitive personal information, and its regulations (Cal. Code Regs. tit. 11, § 7025) require a business to treat an opt-out preference signal, such as GPC, as a valid request to opt out of sale or sharing. The California Invasion of Privacy Act (Cal. Penal Code § 630 and following) restricts the interception and recording of communications; we do not use session-replay or wiretapping tools.

3.2 Federal. The Federal Trade Commission Act, section 5 (15 U.S.C. § 45), prohibits deceptive practices, and we describe our practices in this notice accurately. The Children’s Online Privacy Protection Act (15 U.S.C. § 6501 and following) is addressed in Section 14.

3.3 Consent standard. Where the law requires your consent for an item that is not Strictly Necessary, we ask for it before we set the item, we give “Accept all” and “Reject non-essential” equal prominence, and we record your decision. Consent that is not freely given is not relied on.

4. Every cookie and storage item

The following table lists every item that the Services set or read. “First party” means set by theclarte.pro itself. We have no third-party cookies on our own pages. Category names match the Consent Center.

4.1 Items that are not set by default. The items in the Analytics and Preferences categories are not created unless you allow them (or, for Preferences, have not turned them off). The aim cookie and the push subscription exist only because you asked for them. The sign-in cookies exist only while you sign in.

4.2 Items we do not use. We do not use IndexedDB, WebSQL, Flash storage, ETag or cache-based tracking, canvas or audio fingerprinting, or any device identifier for tracking.

4.3 Changes in names. Names in this table are the names the Services use today. If we rename an item without changing its purpose, we shall update the table at the next release.

5. The Consent Center

5.1 First layer. The first time you visit, a banner offers three buttons of equal size and weight: “Accept all”, “Reject non-essential” and “Customize”. Nothing in the Analytics or Preferences categories is created before you choose, except that we honor a GPC signal as described in Section 7. The banner can be dismissed only by making a choice.

5.2 Preferences dialog. “Customize” opens a dialog with four categories: Strictly necessary (always on), Preferences, First-party analytics, and Marketing. Marketing is shown switched off and cannot be turned on because we do not use marketing technologies. The dialog also contains the “Do Not Sell or Share My Personal Information” and “Limit the Use of My Sensitive Personal Information” statements and a privacy request form (Section 12).

5.3 Effect of your choice. If you choose “Reject non-essential” or switch a category off, the Services stop using that category and delete its items from your tab immediately (session storage keys cs_sid and cs_attr for Analytics; cs_book, cs_estimate, clarte-concierge and tab:… for Preferences). If you allow a category later, it starts again from that point.

5.4 Reopening. You can reopen the Consent Center at any time from “Your privacy choices” at the bottom of every page. Changing your choice is as easy as making it.

5.5 Re-asking. We ask again after twelve months, or if we change the technologies in this notice in a way that needs new consent (the version in the cc cookie then no longer matches).

6. First-party analytics

6.1 What it is. If you allow Analytics, our own server counts page views and named events (such as starting an estimate or reaching a step of the booking form). No third-party script is loaded. The analytics beacon is sent to our own address and contains the page path, the referring page, any campaign tags in the link (utm_source, utm_medium, utm_campaign), your screen width, and the random code in cs_sid.

6.2 What it does not do. It does not set a cookie. It does not store your IP address. It derives a visitor code by hashing your IP address and browser details with a secret salt that changes every day, is kept only in the server’s memory and is never stored with the data, so a visitor cannot be recognized from one day to the next or across sites. We exclude known bots, we do not run analytics on the admin, team and notice pages, and we do not count our own team’s visits.

6.3 Retention. Analytics rows are kept for 14 months and then deleted (Privacy Notice, Section 6A).

6.4 Default. Analytics is off until you turn it on. If we ever change the default, we shall say so here before we do and the Consent Center will show the new default accurately.

7. Global Privacy Control and Do Not Track

7.1 GPC. We treat a GPC signal sent by your browser (the Sec-GPC header or the navigator.globalPrivacyControl setting) as a valid request to opt out of the sale and sharing of your Personal Information, for that browser and, if we know who you are because you are signed in, for your account. Because we neither sell nor share Personal Information, the signal does not change what the Services collect for that purpose; but when GPC is present we also store only an anonymous page view, with no visitor code and no session code, and the Consent Center shows that the signal was honored. The signal is logged with your consent decision so that we can show that we honored it.

7.2 Do Not Track. Do Not Track is an older browser setting for which no common standard exists. As California law requires us to say, we treat a Do Not Track signal the same way as GPC for analytics purposes: we store only an anonymous page view. We do not track you across other websites, and no third party collects information about your activity on our pages for its own purposes.

7.3 No penalty. We do not treat you differently, or deny, degrade or charge more for the Services, because you send a signal or use your privacy choices.

8. Sale and sharing analysis under the CCPA

8.1 Sale. A “sale” under the CCPA is disclosing Personal Information to a third party for monetary or other valuable consideration. We do not disclose Personal Information to third parties in exchange for money or anything of value. We disclose it to service providers and contractors (for example hosting, payment processing, email and text delivery, and background checks for team members) under written contracts that restrict their use to our instructions; those are disclosures for a business purpose, not sales.

8.2 Sharing. “Sharing” is disclosing Personal Information to a third party for cross-context behavioral advertising, that is, advertising based on your activity across businesses or services other than the one you are using. We do not use advertising networks, retargeting, social-media pixels, or advertising identifiers, and we do not disclose Personal Information for that purpose.

8.3 Why no banner opt-out is needed. Because we do not sell or share, there is no “Do Not Sell or Share” setting that changes how the Services work. We nevertheless display the “Do Not Sell or Share My Personal Information” and “Limit the Use of My Sensitive Personal Information” links in the Consent Center, honor GPC, and accept requests, so that you can exercise the right whenever you wish and so that you have a record.

8.4 Sensitive Personal Information. We use sensitive personal information (for example gate and alarm codes that you choose to give us, and the precise location of team members who are clocked in) only to provide the service you asked for or to run employment and safety functions, and not to infer characteristics about you. Cookies and storage items in Section 4 do not collect sensitive personal information.

8.5 Review. If we ever add a technology that could constitute a sale or sharing (for example an advertising pixel), we shall update this notice and the Consent Center before we deploy it, obtain consent where the law requires, add a visible opt-out link, and honor GPC for it.

9. Fonts from Google and other third-party requests

9.1 Fonts. The public pages load typefaces from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). When your browser fetches them, Google receives your IP address and browser details, and may set or read data under its own privacy policy. We do not control that and we do not receive that data. We use Google Fonts only for the typography of the Services. If you prefer not to contact Google, you can block those requests in your browser; the Services will use fallback fonts.

9.2 Sign-in providers. If you choose “Continue with Google” or “Continue with Microsoft”, your browser goes to that provider’s page, which sets its own cookies under its own policy. We receive your name, email address and an account identifier, and nothing else.

9.3 Payments. When you pay, the payment page is provided by our payment processor, which may set its own cookies and other items, for fraud prevention and to complete the payment, under its own policy. Our own pages do not store your card number.

9.4 Links. If you follow a link to another website, that website’s practices apply.

10. Service worker, offline use and the installed App

10.1 What the service worker does. When you visit, your browser installs a service worker (sw.js) that keeps a versioned cache of the public shell of the Services. Public pages are fetched from the network first and the cached copy is the fallback; static files such as styles, scripts and images are served from the cache and refreshed in the background. Pages for signed-in users and team members, and all API requests, are fetched from the network only and are never written to the cache. When you are offline, the service worker shows the branded offline page.

10.2 No personal information in the cache. The cache contains public pages and static files. It contains no account data, no booking details and no conversation content.

10.3 Updates. A new version of the service worker waits until you tap “Refresh” in the notice that appears; the old cache is deleted when the new version takes over.

10.4 Removing it. You can delete the cache and unregister the service worker in your browser’s site settings, or by uninstalling the App from your device. The Services still work online without it.

10.5 Installing the App. Installing the App from your browser (“Install app” or “Add to Home Screen”) adds a shortcut and runs the same code in an app window. It does not give us access to your contacts, photos or files, and it does not add tracking technologies. Camera, microphone, location and notification permissions are separate and are asked only when a feature needs them (see the Privacy notice and the App terms).

10.6 Push notifications. If you opt in, your browser vendor’s push service delivers the notification. The vendor learns that a notification was sent to your device, under its own policy. You can turn notifications off in the App, in your browser settings or by unsubscribing the device.

11. Our records of your choice and our server logs

11.1 Consent record. When you make a choice, our server stores the time, the policy version, the categories you chose, whether a GPC signal was present, and a one-way hash of your IP address and browser details (not the address itself). We keep this record so that we can show that your choice was honored.

11.2 Security logs. Our servers keep basic request logs for security, fraud and spam prevention. We store a one-way hash of the IP address rather than the address. Retention periods are in the Privacy Notice.

12. How to control, change or withdraw

12.1 In the Consent Center. Open “Your privacy choices” in the footer, change the switches, and press “Save my choices”, “Accept all” or “Reject non-essential”. Withdrawal takes effect immediately and deletes the affected items from your tab.

12.2 In your browser. You can view, block or delete cookies, local storage, session storage and cached files in your browser’s settings. If you block the Strictly Necessary items, parts of the Services (signing in, the time clock for team members, offline pages) will not work. If you delete the cc cookie, the banner appears again.

12.3 Notifications and location. You can withdraw permission at any time in your browser or device settings.

12.4 Privacy requests. To exercise your rights to know, delete, correct, opt out of sale or sharing, or limit the use of sensitive personal information, use the form in the Consent Center or the contact form and choose “Privacy and personal data.” We respond within 45 days, and may extend once by up to 45 days where reasonably necessary, with notice. You may use an authorized agent, as the CCPA regulations allow.

12.5 Appeals and complaints. If we decline a request you may ask us to reconsider through the contact form. You may also contact the California Privacy Protection Agency or the California Attorney General.

13. Data security and retention of these items

Cookies that identify a session are HttpOnly and Secure so that scripts on a page cannot read them and so that they are not sent over an unencrypted connection. Session-storage items disappear when you close the tab. The cc cookie lasts 12 months. The aim cookie and its memory profile last 30 days for visitors who are not signed in. The sign-in cookie lasts up to 30 days. Server-side records connected with these items are kept for the periods stated in the Privacy Notice.

14. Children

The Services are for adults aged 18 and over and are not directed to children under 13 (or under 16). We do not knowingly collect Personal Information from children, and we set no cookie or storage item for the purpose of identifying a child. If you believe that a child has used the Services, please tell us through the contact form so that we can delete the information. The Services show no advertising to anyone.

15. Worked examples

The following examples illustrate how this notice applies. They are explanatory; they do not add or remove any right.

Example 1: First visit, you click “Reject non-essential”. The banner closes. The cc cookie is set to v2026-11-02.a0.p0 and your decision is logged on our server. The Services create no cs_sid, cs_attr, cs_book, cs_estimate, clarte-concierge or tab: items. You can still browse and request an estimate; the estimate form works, but your answers are not kept if you move to another page, and the AI chat does not keep its conversation across pages. Nothing else about the Services is degraded, and the price, the availability of appointments and the quality of service are the same (CCPA, Cal. Civ. Code § 1798.125).

Example 2: You click “Accept all”, then change your mind. You open “Your privacy choices” in the footer and press “Reject non-essential”. Your cc cookie is rewritten with analytics 0 and preferences 0, the keys cs_sid, cs_attr, cs_book, cs_estimate, clarte-concierge and every tab: key are removed from the current tab at once, and the server logs a new decision. Analytics collected earlier, which is anonymous and is not linked to you, is retained for its 14-month period; if you want it deleted we cannot identify which rows were yours because we do not store identifiers that would allow it, which is a consequence of the privacy design in Section 6.

Example 3: A browser that sends Global Privacy Control. Your browser sends the GPC signal. The banner appears but states “Global Privacy Control detected: honored”. Analytics is off by default for everyone; if you turn it on while GPC is present, the server still stores only an anonymous page view with no visitor code and no session code. The sale and sharing opt-out is applied to that browser and, if you are signed in, to your account.

Example 4: A shared family computer. Two people use the same browser profile. One of them ticks “Remember this conversation on this device”, which sets the aim cookie. The other person, using the same profile, will see the remembered preferences in the chat. If that is not what you want, do not tick the box on a shared device, or untick it, say “forget me” to the AI chat, or clear cookies for theclarte.pro. Sign-in cookies do not create this issue if you sign out.

Example 5: A team member working in a basement with no signal. A team member clocks out of a job while offline. The punch is saved in local storage under cs_punch_queue. When the device reconnects, the App sends the punch with the original timestamp, and the item is deleted. The team member is paid for the time worked whether the punch reaches the server immediately or later (Labor Code §§ 204 and 226). The team member should not clear site data until the App shows that the punch was sent.

Example 6: You uninstall the App. Uninstalling the App from your device removes the service worker and its cache on most platforms. Cookies and session storage are controlled by your browser. If notifications were turned on, the push subscription on our server is deactivated the next time a notification fails to deliver, and it is deleted when you delete your account.

Example 7: You use a private or incognito window. The Consent Center treats each private window as a new visit, so the banner appears again. Everything the window stores is removed when the window closes. Signing in inside a private window sets the cs cookie for that window only.

Example 8: You visit with JavaScript disabled. The static pages load. The Consent Center, analytics, the AI chat and the App features need JavaScript. Because the cc cookie cannot be set, nothing optional is created. The service worker does not run.

16. Legal bases and the consent standard in detail

16.1 Strictly Necessary items. We set Strictly Necessary items without asking because California and federal law do not require consent for storage that is needed to provide a service you requested or to keep it secure, and because we are transparent about them here. The sign-in cookies, the consent cookie, the time-clock queue and the offline cache fall in this category. The Strictly Necessary category excludes anything used for analytics, advertising or profiling.

16.2 Optional items. The Analytics and Preferences categories are optional. We apply them only after a choice, on an opt-in basis for analytics, and we apply Preferences until you turn them off. If you reject them, the Services remain available.

16.3 Consent properly given. Consent is expressed by a clear affirmative act through the Consent Center. We do not use pre-checked boxes for optional categories that are off by default, we do not use confusing wording or dark patterns (Cal. Code Regs. tit. 11, § 7004), we do not ask more than once a year unless the technologies change, and we do not make the Services conditional on accepting optional items.

16.4 Records of consent. We keep a record of each decision as described in Section 11 for as long as is needed to demonstrate compliance and no longer than 36 months.

16.5 Withdrawal. You may withdraw consent at any time without giving a reason. Withdrawal does not affect the lawfulness of processing that took place before it.

17. Cross-reference table

The table below identifies where each topic in this notice is addressed in our other documents, so that the documents are read together.

18. Accessibility of the Consent Center

The banner and the preferences dialog are built to be used with a keyboard and a screen reader. The banner is announced as a dialog with a label and a description. Its three buttons are real buttons with visible focus. The preferences dialog traps focus while open, closes with the Escape key, returns focus to the control that opened it, and uses switch controls with accessible names and states. Motion is reduced if your system asks for reduced motion. If you cannot use the Consent Center for any reason, you can exercise the same choices through the contact form, and we shall record your choice for you. See the Accessibility statement.

19. Procedure for requests about cookies and storage

19.1 How to submit. Use the Consent Center form or the contact form. Give the name and email address that you used with the Services, if any, and describe your request. We do not need to identify a browser to act on a cookie choice; the choice lives in your browser.

19.2 Verification. A request that concerns only your browser settings does not need verification. A request that concerns information linked to your account is verified by asking you to sign in or to confirm control of the email address on file, in a way that is proportionate to the information involved and that does not require more personal information than necessary.

19.3 Timeline. We confirm receipt within 10 business days and respond within 45 calendar days. We may extend once by up to 45 further calendar days if reasonably necessary, and we shall tell you why within the first 45 days.

19.4 Authorized agents. You may use an authorized agent. We may ask for written permission signed by you, or proof that the agent holds a power of attorney under Probate Code sections 4000 to 4465, and we may verify your identity directly.

19.5 Records. We keep a record of each request, our response and the date, for 24 months, as the CCPA regulations require (Cal. Code Regs. tit. 11, § 7101).

20. Security of these technologies

Sign-in cookies are random values that point to a session record on our server; they carry no personal information. They are HttpOnly, so scripts on a page cannot read them; Secure, so they are not sent over an unencrypted connection; and SameSite=Lax, so they are not sent in most cross-site requests. We rotate the session identifier on sign-in. The sign-in forgery cookie is signed. The consent cookie contains no personal information. Session storage and local storage hold only the items in Section 4. We run the Services over HTTPS only. If you believe an item has been misused, tell us through the contact form.

21. Interaction with other documents; disputes; survival

21.1 Order of precedence. This notice is incorporated into the Privacy Notice and into the Terms of Service. If it conflicts with the Privacy Notice about your rights, the Privacy Notice controls. If it conflicts with the Terms of Service, the Terms of Service control, except that nothing in the Terms of Service reduces a right that this notice gives you under law.

21.2 Disputes. Disputes are resolved as the Terms of Service provide in their section on dispute resolution and arbitration, including your right to opt out and to use small-claims court. Nothing in this notice waives any right under the CCPA, the Consumers Legal Remedies Act or any other law that cannot be waived.

21.3 Escalation ladder. A complaint about our use of cookies or storage can be raised in this order: (a) the Consent Center or the contact form, where a person reviews it within 10 business days; (b) a written request for reconsideration through the same form, reviewed by a different person; (c) the California Privacy Protection Agency or the California Attorney General; and (d) the dispute resolution process in the Terms of Service. You may skip any step.

21.4 Severability. If any provision is held invalid or unenforceable, it is limited to the minimum extent necessary and the rest of this notice remains in effect.

21.5 Survival. Sections 8, 11, 19 and 21 continue to apply to information we hold after you stop using the Services.

22. Changes and version history

22.1 Changes. If we begin to use any other cookie or Similar Technology, or change the purpose of an item in Section 4, we shall update this notice before we do and obtain consent where the law requires it. The effective date at the top will change, and the Consent Center version will change so that we ask you again if consent is needed. We shall not make a change that reduces your rights retroactively.

22.2 Version history.

23. Contact

Questions or requests: please use the contact form and choose “Privacy and personal data.” We do not publish an address, telephone number or email address on this website.