Cookie Policy

This policy explains the cookies and similar browser storage that Yekar.AI ("Yekar.AI", "we", "us") uses on our website at yekar.ai, our documentation at docs.yekar.ai, and the platform at app.yekar.ai together with the services behind it. It supplements our Privacy Policy, which describes how we handle personal information more generally.

A cookie is a small text file a website stores in your browser. We use two kinds: essential cookies, without which sign-in and secure sessions cannot work, and analytics cookies, which help us understand how our pages are used. We do not use advertising or cross-site tracking cookies.

The website (yekar.ai) and the documentation (docs.yekar.ai) are static pages. They set no cookies of their own; the only cookies come from Google Analytics, which we use to understand website traffic and improve our pages - and only if you allow it. Each site asks the first time you visit, and again once your answer is a year old. Until you choose Accept analytics, the Google Analytics script is not loaded at all: no Google Analytics cookie is set and no request goes to Google. Choosing Decline changes nothing else about either site.

• _ga - Google Analytics. Distinguishes one visitor from another with a random identifier so that page views can be counted per visit. Lasts up to two years (browsers may shorten this to 400 days).
• _ga_T1VLQGDC92 and _ga_V9CE28387K - Google Analytics. Keep the state of the current visit for the website and the documentation respectively. Each lasts up to two years.

If you accept, Google Analytics receives pages visited, device and browser information, IP-derived approximate location, and referral information; we ask it to anonymize IP addresses and grant it analytics storage only - advertising storage stays denied. These cookies are set for yekar.ai and are therefore also readable on our subdomains. You can change your mind at any time with Cookie settings at the foot of every page; declining after accepting stops Google Analytics from using cookies and deletes the ones above from your browser. Google's handling of this data is described in Google's cookie policy.

Separately, both sites use Cloudflare Web Analytics, a page-view counter from our hosting provider. It sets no cookies and stores nothing on your device, it does not identify you or follow you across sites, and it runs whether or not you accept Google Analytics. It records which page was viewed, the referring page, and browser, device and country information, and reports them to us only as totals.

Signing in to the platform sets cookies that identify your session. They are HTTP-only (scripts in the page cannot read them) and sent only over HTTPS in production; the session cookies are sealed so they cannot be forged or altered, and hold no personal information beyond an internal identifier. Without them you cannot stay signed in.

• yekar_session - your platform sign-in at app.yekar.ai. Lasts 24 hours, or 30 days when you choose Keep me signed in on this device. Each sign-in is also a record on our servers, and the cookie works only while that record exists: it stops working after three days without use (or sooner if your organization has set a shorter time), when you sign that browser out from Where you're signed in in Account settings, when you sign out of all devices, and when your password is changed or reset. Signing out ends it.
• yekar_second_factor - set after your password or Google step when your account has two-factor sign-in turned on, while you enter the authenticator code. Lasts 5 minutes and is removed as soon as sign-in completes.
• yekar_oauth_state - protects "Sign in with Google" against forged requests while you are on Google's consent screen. Lasts 5 minutes and is removed as soon as sign-in completes.
• yekar_conn_oauth - carries the state of an integration you are connecting (Slack, Google Workspace, Microsoft 365 and similar) between our platform and the provider's consent screen. Lasts 10 minutes.
• yekar_impersonation - set only when you have asked Yekar.AI support to look at your workspace and a member of our staff signs in as you to do so. Your organization can turn support sessions off altogether, or require one of its own admins to approve each one before it can be used. Lasts at most 3 hours and ends after 30 minutes without activity. Each such session is recorded in your organization's audit trail.
• yekar_console_session and yekar_console_oauth_state - the same pair for the builder console at console.yekar.ai. The session lasts 12 hours; the sign-in cookie 5 minutes.
• yekar_admin_session and yekar_admin_oauth_state - the same pair for Yekar.AI's internal operations console, used only by our own staff. The session lasts 12 hours; the sign-in cookie 5 minutes.

The platform does not use Google Analytics. When product analytics is enabled for a deployment, the platform can use PostHog to record which pages of the platform you visit, identified by your account and workspace - but only if you allow it. After you sign in, the platform asks you, and asks again once your answer is a year old; until you choose Share analytics, PostHog is not loaded and sets nothing. You can change your answer at any time under Settings → Account → Product analytics; turning it off stops collection in that browser straight away, clears the identifier below, and stops it on your other devices when they next load your account. Your answer is saved to your account, with the date you gave it, so you are not asked again on another device. Analytics never runs during a support session. Query strings and fragments are removed from every recorded address, no IP address is included in the events we send, and the analytics cookie is confined to app.yekar.ai - it is not shared with our other subdomains.

• ph_<project>_posthog - PostHog. Remembers an anonymous device identifier and, after sign-in, links it to your account so feature usage can be understood per workspace. Lasts up to one year. PostHog also keeps the same state in your browser's local storage.

Session recordings are off by default. They start only if you have allowed product analytics AND your workspace's administrator has turned recordings on under Settings → Privacy, and never during a support session; every change to that setting is recorded in the organization's audit trail. Where they are on, every input field and all text is masked and images and media are blocked before anything leaves your browser, and no console output or request or response bodies are captured.

Error reporting through Sentry, when enabled, sets no cookies. Before an error report leaves your browser, email addresses, access tokens and the query strings of web addresses are removed from it, and it carries no IP address, cookies or account details.

Plans on the platform are paid through Razorpay. The platform loads Razorpay's checkout script, and when you open a checkout Razorpay may set cookies under its own domains to run the payment, prevent fraud, and remember your preferences. Those cookies belong to Razorpay and are governed by Razorpay's privacy policy. Yekar.AI never receives your card details.

If you book a demo, you leave our website for Cal.com, which sets its own cookies under its own policy.

Besides cookies, we keep a few preferences and safeguards in your browser's local storage, which never leaves your device: your analytics choice on the website and the documentation (yekar.analytics-consent and yekar.docs.analytics-consent), your light-or-dark theme choice, the documentation's theme choice, and a mirror of an agent draft you are editing so that unsaved work survives a crash or a closed tab. You can clear these at any time through your browser's site-data settings; clearing the analytics choice means you are asked again.

• Browser settings - every major browser lets you view, block and delete cookies for a site, and block third-party cookies altogether. Blocking essential cookies means you cannot stay signed in to the platform.
• Cookie settings - use Cookie settings at the foot of any page on yekar.ai or docs.yekar.ai to accept or decline Google Analytics, or to withdraw a choice you made earlier. On the platform, use Settings → Account → Product analytics.
• Google Analytics - you can also install the Google Analytics opt-out browser add-on to stop Google Analytics on every site, or block the two cookies above for yekar.ai.
• Session length - leave Keep me signed in on this device unchecked to limit your platform session to 24 hours, and sign out to end it immediately.

We update this policy when the cookies we set change; the date at the top is the date of the last change. Questions about cookies or privacy can be sent through our contact page.