Skip to main content

Legal · BETIHUT-LEGAL-COOK

Cookie Policy

Entity
XCITERR LTD. · AUTOMAIZE SOLUTIONS LTD
Reg. No.
206478710 · HE 480609
Effective
16 July 2026
Status
Version 1.3 · Effective

This Cookie Policy explains how AUTOMAIZE SOLUTIONS LTD, as the Betihuti technology operator, uses cookies and similar browser-storage technologies on Betihuti websites (the "Website") and forms part of our Privacy Notice. XCITERR LTD. does not place a separate tracker through the Website; it receives recruitment information only as described in the Privacy Notice. The native iOS and Android apps do not use browser cookies for app operation; their optional analytics and diagnostics preference is recorded through the same consent service.

We use cookies in accordance with the GDPR and applicable electronic-communications laws. The allocation of recruitment and technology responsibilities is described in the Privacy Notice and Company Information page.

1.What cookies are

  1. 1.1Cookies are small text files placed on your device when you visit a website. We also use local storage for the session fallback, a consent-state backup and consented interface preferences. We refer to these browser-storage technologies collectively as "cookies" in this Policy.
  2. 1.2Cookies may be set by us ("first-party cookies") or by a third party providing a service to us ("third-party cookies"), and may persist only for the duration of your visit ("session cookies") or for a defined period thereafter ("persistent cookies").
  3. 1.3The shipped Website does not load Google Analytics, Vercel Analytics, advertising pixels or cross-site tracking tags.

2.Categories of cookies we use

  1. 2.1Strictly necessary cookies keep you signed in, secure your session, remember an explicitly selected language, assign a random consent subject and cache your current choice. The Service cannot provide those requested functions without them.
  2. 2.2Functional storage remembers optional interface preferences such as saved views or layout choices. It is used only after the functional category has a current server-recorded grant.
  3. 2.3We do not currently set a dedicated analytics cookie. If you grant analytics, first-party product events may be sent to our own API and stored in the Betihuti database. Rejecting, withdrawing, allowing the record to expire or having only a local/unconfirmed value means no optional analytics request is sent.
  4. 2.4Native Firebase Crashlytics is also off by default. The mobile app enables it only after the same server-recorded optional analytics/diagnostics preference is granted and disables it on withdrawal. Firebase Cloud Messaging is separate and is used only after notification permission for push delivery.
  5. 2.5We do not use advertising or cross-site tracking cookies.

3.Cookies and storage currently in use

  1. 3.1sb-<project-ref>-auth-token (including chunked variants) — Strictly necessary. Keeps an authenticated session available across Betihuti subdomains; localStorage is the fallback on localhost/preview hosts or when the value is too large for one cookie. Duration: Cookie: up to 7 days; fallback storage: until sign-out, session expiry or browser clearing.
  2. 3.2betihut_cookie_consent — Strictly necessary. Caches the current server-recorded cookie categories so optional code can remain fail-closed without another network round trip. Duration: Up to 395 days.
  3. 3.3betihut_consent_id — Strictly necessary. HttpOnly random subject identifier that links an anonymous browser choice to the append-only consent ledger without storing a name or email. Duration: Up to 395 days.
  4. 3.4betihut_locale — Strictly necessary preference. Remembers the language explicitly selected by the visitor and localizes authentication and service messages. Duration: Up to 1 year.

4.Consent and legal basis

  1. 4.1Strictly necessary cookies are used on the basis of our legitimate interest in providing a secure and functional Service.
  2. 4.2Functional and analytics cookies are used only with your consent, which we obtain through our cookie banner before any non-essential cookie is placed.
  3. 4.3When you make or change a choice, we keep an append-only consent record containing the categories, action, policy version, time, surface, host/path context and minimized technical evidence such as an IP prefix and hashed IP/user-agent evidence. The record normally expires after 395 days and is used to demonstrate and enforce your choice.
  4. 4.4A local cache cannot open an optional gate by itself. The choice must be current, on the active policy version and confirmed by the server ledger. Missing, rejected, withdrawn, stale, expired or local-only evidence fails closed.
  5. 4.5Essential hosting and security processing is not product analytics. Vercel and Cloudflare necessarily receive HTTP request metadata to deliver and protect the Website; we minimize and retain those logs under the Privacy Notice rather than conditioning basic page delivery on an analytics choice.

5.Managing your preferences

  1. 5.1You may accept or decline non-essential cookies at any time through the cookie controls available in your privacy settings.
  2. 5.2You may also delete or block cookies through your browser settings; however, blocking strictly necessary cookies may prevent parts of the Service from functioning.

6.Changes to this Policy

  1. 6.1We may update this Policy to reflect changes in our use of cookies or in applicable law, and will update the effective date stated above.