Back to OneClient

Cookie Policy

Effective date: June 18, 2026  ·  Last updated: September 19, 2026

In plain English

We use cookies and similar technologies (like browser local storage) to keep you signed in, remember your settings, secure the Service against bots, understand how the Service is used, and measure whether the ads we run actually bring people to OneClient. We don't sell your data. Where the law requires us to ask first — the EEA, the UK, and Switzerland — no non-essential cookie or identifier is stored until you agree; elsewhere these technologies are on by default and you can switch them off at any time from Section 5. Two things are counted either way, storing nothing about you: which link brought you here, and anonymous page-view counts that last only as long as the visit (Section 7). Blocking essential cookies will break parts of the Service (sign-in, the booking flow). The live list of cookies we set is in Section 3.

1. About This Policy

This Cookie Policy ("Policy") explains how OneClient Tech L.L.C-FZ ("OneClient", "we", "us", or "our") and our Sub-processors use cookies and similar technologies on the OneClient website (1client.app) and the OneClient platform (collectively, the "Service"). It forms part of, and should be read alongside, our Terms of Service and Privacy Policy.

Capitalised terms used but not defined in this Policy have the meaning given in the Terms of Service or the Privacy Policy.

2. What Are Cookies and Similar Technologies

"Cookies" are small text files placed on your device by a website you visit. They are widely used to make websites work, work more efficiently, and provide information to the operators of the site. This Policy also covers similar technologies that perform comparable functions:

Cookies are either "session cookies" (deleted when you close your browser) or "persistent cookies" (remain until they expire or you delete them). They are either "first-party" (set by the domain you are visiting) or "third-party" (set by another domain).

3. Cookies and Similar Technologies We Use

We group cookies and similar technologies into four categories. On this website the consent banner lets you accept or refuse Statistics and Marketing individually; Necessary cannot be switched off, and nothing on this website uses Preferences:

These are the cookies set on this website by the tags we load. Each is written only where its category is permitted, and the Statistics and Marketing ones are removed or stop being written when you withdraw that category.

Name / Identifier Provider Purpose Category Duration
oc-consent OneClient Records the choice you made in the consent banner, and when, so you are not asked again on every page. Nothing is stored where the banner is not shown and you have not made a choice. Necessary (localStorage) 12 months, then you are asked again
_ga, _ga_* Google LLC (Google Analytics 4) — privacy policy Distinguishes visitors and sessions for aggregate traffic measurement on this website. Where Statistics is refused, Google Analytics sends only cookieless measurement signals. Statistics (cookie) Up to 2 years
_fbp Meta Platforms, Inc. — privacy policy Identifies the browser to Meta so that a visit and a later sign-up can be connected to the advertisement that started them. Marketing (cookie) 90 days
_fbc Meta Platforms, Inc. Holds the Meta click identifier of the advertisement you arrived through, when you arrived through one. Marketing (cookie) 90 days

3.1 Storage used inside the OneClient platform

The table above covers the tags on this marketing website. The Specialist portal (my.1client.app) and the Specialist booking pages are served from other origins, so the storage they use is listed here, together with the other browser storage our own code writes on this website.

Name / Identifier Provider Purpose Category Duration
__clerk_*, __session Clerk Inc. Authentication and session management for Specialist Accounts; sign-in state, federated-identity tokens. Necessary (cookie) Session / up to 1 year
__Host-ratelimit-* OneClient (Vercel edge) Server-side rate-limiting and abuse prevention on sensitive endpoints (e.g. email-verification code requests). Necessary (cookie) Session / up to 1 hour
_grecaptcha and related Google LLC (reCAPTCHA) — privacy policy Bot-protection during the booking flow and other sensitive interactions. Google may set additional cookies on the reCAPTCHA domain in connection with this service. Necessary (third-party cookie) Session / up to 6 months
booking-storage OneClient Preserves selected services, date, and time during the Client booking flow so that navigating between steps does not lose the in-progress Booking. Necessary (localStorage) Persistent (until you clear it or complete the Booking)
i18nextLng OneClient Stores your preferred display language so the Service is rendered in that language on return visits. Preferences (localStorage) Persistent
oc-ref OneClient Remembers the partner referral code you arrived with (?ref=) so it still reaches sign-up if you browse other pages first. It does not change prices or plans. localStorage Persistent
oneclient-settings-* OneClient Stores user-interface preferences (e.g. dismissed banners, layout settings, theme overrides). Preferences (localStorage) Persistent
oc-first-touch, oc-last-touch OneClient Remembers which link or campaign brought you to this website (the utm_ tags on the address, the referring site, and the page you landed on) so it still reaches sign-up if you browse other pages first. A channel name, not an advertising identifier: it identifies the link, not you, and is not shared with any advertising network. localStorage — outside the consent categories, see Section 7 90 days
ph_*_posthog PostHog Inc. — privacy policy Product analytics: counts page views and the steps of the sign-up funnel, and is what lets a visit to this website and the matching sign-up on my.1client.app be counted as one person instead of two. On this marketing website the cookie is written only where the Statistics category is permitted; refusing Statistics does not stop the counting, but it is then done in memory for the length of the visit, with no identifier stored and no way to connect one visit to another. On my.1client.app, the application itself, it is written as part of operating the Service. Statistics (cookie, .1client.app) Up to 1 year
meta_fbc OneClient Holds the Meta click identifier from the advertisement you arrived through, so it is still available when you reach the sign-up link on another page of this website. Written only where the Marketing category is permitted, and erased if you later refuse it. Marketing (localStorage, this website) 7 days
meta_attr OneClient Carries the Meta advertising identifiers, and your Marketing choice, from this website to the sign-up flow on my.1client.app, since cookies cannot cross between the two domains. Written only where the Marketing category is permitted, except for the record of a refusal, which is what stops the sign-up from being reported. Cleared once sign-up completes. Marketing (localStorage) 7 days, or until sign-up completes

4. Third-Party Services That May Set Cookies

Some pages of the Service load resources from third-party domains. When you load such a resource, your browser establishes a connection to the third-party server, which may set its own cookies governed by that third party's privacy policy. We do not control these cookies. The third-party services we use are:

5. Managing Cookies and Similar Technologies

5.1 Your Privacy Choices

Use the control below to reopen the consent banner and change any choice you have already made, including in regions where the banner is not shown on arrival. A decision applies from the moment you make it; it does not undo processing that already happened while the earlier choice was in force.

California residents: this is also the control referred to as "Your Privacy Choices". Refusing the Marketing category stops the sharing of your information for cross-context behavioural advertising described in Section 18 of the Privacy Policy. You do not need an account, and we do not ask you to identify yourself, to use it. If you already have an account, the reporting we send from our own servers is governed by the decision recorded when you created it — email support@1client.app to stop it, as described in Section 18.3.

If the control does not open — for example because a browser extension blocks this website's scripts — clear this site's cookies and storage using the browser controls below, or write to support@1client.app and we will action the request for you.

5.2 Browser controls

Most web browsers allow you to view, manage, delete, and block cookies and other site data through their settings. You can typically:

Common browser help pages:

Please note that blocking strictly necessary cookies will prevent core parts of the Service from working, including (without limitation) signing in and completing a Booking.

5.3 Clearing local storage

Local storage data (such as the booking-flow state and language preference) is managed separately from cookies in your browser. You can clear it through the browser's site-data settings (often labelled "Site Data" or "Storage") or, in some browsers, through the developer tools.

5.4 Mobile devices

On mobile devices, you can manage cookies through your browser's settings. In the OneClient mobile app, advertising and tracking permissions are governed by the operating system (Apple's App Tracking Transparency on iOS; equivalent controls on Android). The mobile app embeds no advertising SDK and reads no advertising identifier, so it does not request tracking permission. The advertising measurement described in this Policy happens on the marketing website and on our own servers, never inside the app.

6. Do Not Track

Some browsers send a "Do Not Track" ("DNT") signal to websites you visit. There is no industry-standard interpretation of DNT signals and the Service does not respond to them.

We do respond to the Global Privacy Control ("GPC") signal, which does have an agreed meaning: where your browser sends it, our consent banner withholds the Statistics and Marketing categories on this marketing website, no cookie or stored identifier is written for either there, and the advertising measurement in Section 18 of the Privacy Policy does not run. The cookieless counting described in Section 7 continues. You can still override this in either direction with the control in Section 5.1.

Where the law of your jurisdiction requires consent for the use of non-essential cookies (for example, the ePrivacy Directive in the European Economic Area and its national implementations; the Privacy and Electronic Communications Regulations in the United Kingdom; the Swiss Federal Act on Data Protection), we ask for that consent before anything non-essential is set: no cookie, and no identifier in local storage, is written for the Preferences, Statistics, or Marketing categories until you agree, and no data is shared with an advertising network. Strictly necessary cookies do not require consent under those regimes.

Two things are counted before you decide, and are described here rather than in a category because neither stores anything about you. First, the link that brought you here (oc-first-touch / oc-last-touch in Section 3.1): it records which campaign or referring site the visit came from, never who you are, and refusing a category would only make our own traffic reports wrong about their own links. Second, page views and sign-up steps are counted in the browser's memory for the length of the visit, with no cookie and no stored identifier, so the visit cannot be recognised again or connected to any other. Agreeing to Statistics upgrades that second one to the cookie in Section 3.1; withdrawing deletes it and returns to memory only. This describes the marketing website; on my.1client.app that cookie is part of operating the Service.

In jurisdictions that regulate this on an opt-out basis instead — including the United States and Australia — the non-essential categories are active when you arrive and you can switch them off at any time. In both cases the control is the same one, in Section 5.1, and withdrawal takes effect immediately. Withdrawal does not affect the lawfulness of processing carried out beforehand.

8. Changes to This Policy

We may update this Policy from time to time to reflect changes in the cookies and similar technologies we use, or for other operational, legal, or regulatory reasons. We will post the updated Policy on this page and update the "Last updated" date above. Where the changes are material, we will notify you by email or in-Service notification.

9. Contact

If you have any questions about this Policy or our use of cookies, please contact us at:

Related documents