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.

• _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.

Google Analytics receives pages visited, device and browser information, IP-derived approximate location, and referral information. These cookies are set for yekar.ai and are therefore also readable on our subdomains. Google's handling of this data is described in Google's cookie policy.

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. Signing out ends it.
• 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. 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 uses PostHog to record which features are used and, only after you have signed in, to identify events with your account. Query strings are removed from every recorded address, 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. Where they are turned on for a workspace, every input field and all text is masked before anything leaves your browser, and no request or response bodies are captured. Error reporting through Sentry, when enabled, sets no cookies.

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, the platform keeps a few preferences and safeguards in your browser's local storage, which never leaves your device: 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.

• 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.
• Google Analytics - 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.