Cookie Policy
Effective date: 16 August 2026
Last updated: 16 August 2026
Version: 1.0
Operator: Abdurrahman Ersin Alagöz, trading as ClarifyLeads, Istanbul, Türkiye
Contact: [email protected]
This Cookie Policy explains how ClarifyLeads uses cookies, local storage, session storage and similar browser technologies on its public website and authenticated application.
1. What these technologies are
A cookie is a small text value stored by a website in a browser. Local storage and session storage are browser mechanisms that can retain application state without using a traditional cookie. These technologies may be first-party, meaning set for ClarifyLeads, or third-party, meaning controlled by another provider.
Some technologies are strictly necessary for sign-in, security, checkout or a function expressly requested by the user. Others, such as optional analytics or advertising tools, may require consent before activation.
2. Current ClarifyLeads inventory
The following inventory reflects the ClarifyLeads-controlled application configuration at the effective date. Exact WordPress cookie suffixes and durations may vary with account and security settings.
| Technology / example key | Provider | Purpose | Category | Typical duration |
|---|---|---|---|---|
wordpress_logged_in_*, wordpress_sec_* and related WordPress authentication cookies | ClarifyLeads / WordPress | Maintain authenticated WordPress access and protect account sessions | Strictly necessary | Session or up to approximately 14 days depending on “remember me” and configuration |
wordpress_test_cookie | ClarifyLeads / WordPress | Check whether the browser accepts cookies | Strictly necessary | Session |
session | ClarifyLeads backend | Authenticate the WordPress-to-backend session | Strictly necessary | Up to 7 days by current default |
clarify_jobs_v1 in local storage | ClarifyLeads | Remember recent job identifiers and display processing status across pages | Functional / requested service | Until removed by the application or the user clears site data |
clarify_credits in local storage | ClarifyLeads | Cache the displayed Action Credit balance and update the interface | Functional / requested service | Until updated, removed or site data is cleared |
crm_column_prefs in local storage | ClarifyLeads | Remember the user's selected CRM columns | Functional preference | Until reset or site data is cleared |
crmCurrentPage in session storage | ClarifyLeads | Preserve the current CRM page during the browser-tab session | Functional preference | Until the browser tab/session ends |
clarify_idempotency_v1:* in session storage | ClarifyLeads | Prevent accidental duplicate job submissions | Security / strictly necessary | Normally up to 30 minutes or until cleared / tab session ends |
| Checkout cookies and storage | Lemon Squeezy | Secure checkout, fraud prevention, payment, tax and subscription processing | Strictly necessary for a purchase | Determined by Lemon Squeezy on its domain |
| OAuth/provider cookies | Google or another selected sign-in provider | Complete social authentication requested by the user | Strictly necessary for that login method | Determined by the provider |
3. Analytics and advertising
ClarifyLeads-controlled application components are not intended to deploy Google Analytics, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, Microsoft Clarity, Hotjar or another advertising tracker at the effective date.
ClarifyLeads therefore does not intentionally set advertising or cross-site behavioural-tracking cookies on its controlled application pages. A separate theme, plugin, injected script, Tag Manager container, CDN or hosting layer may be added or changed over time; the live inventory will be updated when such technology is enabled.
If we introduce optional analytics or advertising technology, we will update this inventory and obtain consent before activation where required. Rejecting optional technology must be as easy as accepting it.
4. External images and resources
The CRM interface may request company logos or favicons from services operated by Clearbit or Google using the company domain being displayed. These requests are not necessarily cookies, but the external provider can receive the requested domain and ordinary connection data such as the user's IP address, browser type and request time.
We may proxy, remove or replace these resources. Blocking the provider in a browser or network may cause a logo to be replaced by a fallback without preventing core CRM use.
5. Payment-provider and platform technology
When you open a Lemon Squeezy checkout, sign in through Google, or connect a supported communication channel, you interact with that provider's domain or service. The provider may use its own cookies or similar technologies under its privacy and cookie information. ClarifyLeads does not control provider-side storage.
6. Legal basis and consent
We use strictly necessary technology to provide a service you request, authenticate sessions, maintain security, prevent duplicate submissions and complete checkout. Where law permits, this technology does not require an optional cookie-consent choice, although it must still be disclosed.
We will rely on consent for non-essential analytics, advertising or similar device access where consent is required. Consent can be withdrawn without affecting the lawfulness of earlier processing.
7. Your controls
You can:
- sign out to end the active account session;
- use the ClarifyLeads preference or reset controls where available;
- clear cookies, local storage and session storage in browser settings;
- block third-party content or cookies through browser controls; and
- change or withdraw optional-cookie consent through the consent interface, if optional tools are introduced.
Blocking necessary cookies may prevent login, checkout or job execution. Clearing clarify_jobs_v1 may remove local status references, but it does not itself cancel an already-running backend job. Clearing browser data also does not delete server-side account or CRM data; use the account deletion controls for that purpose.
8. Do Not Track and global privacy signals
Because industry treatment of browser signals varies, the current Service does not promise a uniform response to every “Do Not Track” signal. Where legally required and technically supported, we will honour recognised consent or opt-out signals for optional processing.
9. Updates
We may update this Policy when browser storage, providers or site configuration changes. A current live scan should be performed after material WordPress, theme, CDN, Tag Manager, checkout or authentication changes.
10. Contact
Questions about cookies or browser storage may be sent to [email protected].