Legal
Cookie Policy
Last updated: 2026-11-15Operator: Taparam Eliptik Yazilim ve Teknoloji Anonim Sirketi · Republic of Türkiye · CapCeeper brand
Table of contents
1. Introduction2. What cookies and similar technologies are3. Categories of cookies4. Examples of CapCeeper cookies and storage keys5. Widgets and third-party sites6. How to manage cookies7. Duration8. Changes to this Cookie Policy9. Contact1. Introduction
This Cookie Policy explains how Taparam Eliptik Yazilim ve Teknoloji Anonim Sirketi (Turkish: Taparam Eliptik Yazılım ve Teknoloji Anonim Şirketi) (“Company”, “we”, “us”) uses cookies and similar technologies on CapCeeper websites, dashboards, and official Widget frames served from CapCeeper domains.
It should be read together with the Privacy Policy. Capitalized terms not defined here have the meanings given in the Terms of Service or Privacy Policy.
By using CapCeeper, you acknowledge the use of Essential cookies required to provide the Service. Optional cookies (if any) are used only according to your consent choices.
2. What cookies and similar technologies are
Cookies are small text files placed on your device by a website. CapCeeper may also use local storage, session storage, or similar browser storage (together referred to as “cookies” in this Policy for convenience) to remember preferences, keep sessions secure, and store consent records.
Cookies may be “first-party” (set by CapCeeper domains) or, in limited cases, related to third-party services you choose to invoke (for example an OAuth provider during login). CapCeeper stage-1 product pages do not load third-party advertising pixels.
Cookies may be session cookies (deleted when you close the browser) or persistent cookies (remaining until they expire or you delete them).
3. Categories of cookies
Essential cookies (required): These cookies are necessary to provide core features you request, such as authentication, security protections, load balancing where used, theme preference persistence, and storing your cookie consent choice. Because they are required to operate the Service, they cannot be disabled through CapCeeper’s in-product preference center while you continue using CapCeeper. You may block them in your browser, but parts of the Service may stop working.
Analytics cookies (optional): These cookies, if enabled in a future or current release, help CapCeeper understand aggregated product usage (for example which documentation pages are visited) so we can improve the Service. They are off by default. In stage 1, CapCeeper may not load analytics scripts even if you select “Accept all” or enable Analytics in Customize; your consent is stored so CapCeeper may activate analytics later without changing the default-off posture for new visitors who choose Essential only.
Marketing cookies: CapCeeper does not use marketing or advertising cookies on product pages in stage 1. CapCeeper does not sell advertising inventory on the Market Data product UI.
4. Examples of CapCeeper cookies and storage keys
cc_consent (HTTP cookie and localStorage JSON): stores whether you chose Essential only, Accept all, or a custom preference, with a timestamp and whether analytics was enabled. Purpose: Essential — remember and honor consent. Typical lifetime: up to one year for the cookie channel.
cc_token (localStorage): CapCeeper session token used to keep you signed in to the dashboard after login or OAuth. Purpose: Essential — authentication. Cleared on sign-out.
cc_email, cc_name, cc_plan (localStorage): cached account display fields for the signed-in UI. Purpose: Essential — account session UX. Cleared on sign-out.
cc_theme (localStorage): light or dark mode preference. Purpose: Essential / functional UI preference. Persistent until changed.
cc_watch (localStorage): coin identifiers on your watchlist stored on your device. Purpose: Essential / functional product preference; typically not uploaded as a separate personal-data feed beyond authenticated sync if offered later.
cc_compare (localStorage): coin identifiers selected for the compare tool (limited set). Purpose: Essential / functional product preference on-device.
cc_api_key_once (localStorage, short-lived): temporarily holds a newly issued API Key so the dashboard can show it once after registration or OAuth callback; then removed. Purpose: Essential — secure one-time key reveal.
Server-set session or security cookies (names may vary by reverse-proxy or app deployment): may keep TLS sessions, load-balancer affinity, or CSRF protections. Purpose: Essential — security and reliability.
OAuth provider cookies: when you click “Continue with Google” or “Continue with GitHub”, Google or GitHub may set cookies under their own domains per their policies. CapCeeper does not control those cookies.
5. Widgets and third-party sites
When you embed an official CapCeeper Widget on your website, end users load content from CapCeeper domains inside a sandboxed frame or via CapCeeper’s embed loader. CapCeeper may set CapCeeper-domain cookies inside that context according to this Policy (for example to serve the Widget reliably).
If you operate a site that embeds CapCeeper Widgets, you are responsible for providing your own cookie and privacy notices to your visitors as required by laws applicable to you. CapCeeper’s credit/attribution must remain visible per the API License and Terms.
CapCeeper Widgets must not be used as a covert bulk data extraction channel; see the Acceptable Use Policy and API License.
6. How to manage cookies
First visit: CapCeeper displays a cookie banner offering Essential only, Customize, and Accept all.
Customize: you may enable or disable optional Analytics (when offered). Essential remains always on. Marketing remains unused.
Revisit preferences: use the “Manage cookies” control in the site footer (Legal column), which reopens CapCeeper’s cookie preference dialog. You may also clear site data in your browser and reload CapCeeper to see the first-visit banner again if consent storage was removed.
Browser controls: most browsers let you block or delete cookies. Blocking Essential cookies may break login, checkout, or consent remembering.
Do Not Track: CapCeeper’s stage-1 stack may not respond to DNT signals beyond honoring the explicit consent banner choices described here.
7. Duration
Session cookies expire when you close your browser. Persistent cookies expire according to their configured max-age or when you delete them. Consent cookies are commonly set for up to twelve (12) months, after which CapCeeper may ask again.
Server-side logs associated with requests are retained according to the Privacy Policy retention rules and are distinct from browser cookies.
8. Changes to this Cookie Policy
We may update this Cookie Policy as CapCeeper evolves (for example if analytics are introduced). The “Last updated” date will change when we revise the Policy. Material changes may be accompanied by a renewed consent prompt where appropriate.
9. Contact
Questions about cookies: [email protected] or [email protected].
Controller: Taparam Eliptik Yazilim ve Teknoloji Anonim Sirketi, Republic of Türkiye.
Related: Terms of Service · Privacy Policy · Disclaimer · Refund & Cancellation · API License · Acceptable Use Policy
Questions? [email protected] · Privacy: [email protected]