Privacy Policy

CocoIndex Inc (“we,” “our,” or “us”) operates the cocoindex.io website, including its blog and documentation (“the Service”), and publishes the open source CocoIndex library. This Privacy Policy explains what information we collect through the Service and the library, why we collect it, who processes it for us, and the choices you have. CocoIndex Inc is the controller of this information.

This policy does not cover data you process with CocoIndex software. The open source library and our commercial products run on your own infrastructure, and the data in your pipelines never reaches us.

Information We Collect

The Service has no accounts or sign-up forms. We collect information in three ways:

• Automatically, when you browse the Service, through the analytics tools described in Analytics & Cookies: a pseudonymous identifier stored in a cookie or your browser’s local storage; the pages you view and the page that referred you; interactions such as clicks on links and buttons (with the link text and destination), how far you scroll, and copying code samples; device and browser details such as browser type, operating system, screen size, and language; page-load performance timings; and your IP address, which the providers use to derive your approximate location (country, region, and city).
• When you book a demo through Calendly. See Demo Bookings.
• When you email us, for example with a question or a job application: your name, email address, and whatever you choose to send.

Pseudonymous identifiers and IP-derived location are personal data under laws such as the GDPR and several U.S. state privacy laws, even though they don’t tell us your name. We don’t use them to try to identify you, and we don’t link analytics data to what you send us by email or through Calendly.

Analytics & Cookies

We use analytics to understand which pages and posts people read and which links they follow, so we can improve the Service and our content. The following tools run on the Service:

• Google Analytics, on every page. It sets the _ga and _ga_LTKWNY5XKT cookies. See Google’s privacy policy.
• PostHog, on every page. It stores an identifier in a ph_<project key>_posthog cookie and in local storage, and records page views and the interactions listed above. See PostHog’s privacy policy.
• Mixpanel, on every page, receiving the same events as PostHog. It sets an mp_<project token>_mixpanel cookie. See Mixpanel’s privacy policy.
• Scarf, on blog posts only. Each post loads a 1×1 tracking pixel, which sends Scarf your IP address, your browser’s user agent, and the address of the post you’re reading. See Scarf’s privacy policy.
• Cloudflare Web Analytics, on every page, including the documentation. Cloudflare, which delivers the Service, adds its script to each page it serves. It is cookieless: it sets no cookies and stores nothing in your browser’s local storage. It records the address of the page you view; the page that referred you; your browser’s user agent, from which Cloudflare derives your browser, operating system, and device type; your country, derived from your IP address; and page-load performance timings. Cloudflare states that it does not fingerprint visitors or track them across websites. See Cloudflare Web Analytics and Cloudflare’s privacy policy.

The documentation at cocoindex.io/docs is built separately. It currently loads none of the cookie-based tools above (Google Analytics, PostHog, and Mixpanel) and no Scarf pixel, so it sets no analytics cookies; Cloudflare Web Analytics runs there as it does on every page. The documentation’s search box is powered by Algolia DocSearch: when you search, your query and standard request data, including your IP address, are sent to Algolia to return results. See Algolia’s privacy policy.

You can block or delete cookies in your browser settings, use a content blocker, or install Google’s Google Analytics opt-out add-on. The Service works the same without analytics.

Demo Bookings

“Book a demo” links take you to Calendly (calendly.com), where you pick a time and enter your name, your email address, and any details you want to share. Calendly processes this for us so we can schedule the meeting; we use it to prepare for the conversation and to follow up afterward. On the Service itself, we record only that a booking link was clicked, not what you enter on Calendly. See Calendly’s privacy notice for how Calendly handles your data.

CocoIndex Software & Telemetry

CocoIndex is an open source framework. It runs on your infrastructure, and it does not collect, store, or retain your pipeline data, pipeline output, or any personal data from your pipelines. Since all source code is open and transparent, you can inspect the repository at any time.

Usage telemetry

Release builds of the open source library send a small number of usage events so we can see which platforms and language versions are in use and prioritize builds and support accordingly. Each event is an HTTPS request to our endpoint at Scarf (cocoindex.gateway.scarf.sh) and contains only:

• the event name: init when the library loads, and app_create, app_update, or app_drop when an app is created, updated, or dropped;
• the platform, meaning CPU architecture and operating system (for example, aarch64-macos);
• the language version (for example, python3.11) and the package name and version (for example, python-1.0.0);
• an application tag, only if you set one with the COCOINDEX_APPLICATION_FOR_TRACKING environment variable.

Telemetry never includes your data, code, configuration, file paths, or a persistent machine or user identifier. Scarf receives your IP address as part of the request. Events are sent in the background and never block or affect your application.

To opt out, set the COCOINDEX_DISABLE_USAGE_TRACKING environment variable to any non-empty value other than 0 (for example, COCOINDEX_DISABLE_USAGE_TRACKING=1) before starting your program. Development builds never send events. See the telemetry documentation for details.

Our commercial products, CocoIndex Code Plus and CocoIndex Enterprise Edition, contain no telemetry.

How We Use Information

We use the information described above only for the following purposes, on the following legal bases:

• Analytics, documentation search, and hosting: to operate, secure, and improve the Service and to understand which content is useful. Legal basis: our legitimate interests (GDPR Art. 6(1)(f)).
• Demo bookings and email: to schedule and hold meetings, answer your questions, and consider job applications. Legal basis: steps you ask us to take before entering into a contract (GDPR Art. 6(1)(b)), and our legitimate interests in responding to you.
• Library telemetry: to understand how the open source library is used across platforms so we can prioritize support. Legal basis: our legitimate interests; you can opt out at any time as described above.

We do not use this information for advertising, and we do not make decisions about you based solely on automated processing.

Data Sharing and Sale

CocoIndex Inc does not sell personal information and does not share it for cross-context behavioral advertising. We disclose it only to the service providers listed below, which process it for us, and when required by law.

Service Providers

• Google Analytics, PostHog, and Mixpanel: website analytics.
• Scarf: the blog tracking pixel and the open source library’s telemetry endpoint.
• Algolia: documentation search.
• Calendly: demo scheduling.
• GitHub Pages and Cloudflare: hosting and delivery of the Service; Cloudflare also provides our cookieless web analytics (Cloudflare Web Analytics). Like any web server, they receive your IP address and request details, such as the page requested and your browser’s user agent, in order to serve pages and protect the Service from abuse.
• Google Workspace: email.

International Transfers

We are based in the United States, and our service providers process information in the United States and other countries. If you visit from outside the United States, your information will be transferred to and processed in those countries.

Retention

Analytics and telemetry data are kept according to each provider’s retention settings. Calendly booking details and emails are kept for as long as needed for the conversation and any business relationship that follows, and longer only where the law requires.

Your Choices and Rights

You can limit analytics with the cookie and browser controls described in Analytics & Cookies, and turn off library telemetry with COCOINDEX_DISABLE_USAGE_TRACKING.

Depending on where you live (for example, the European Economic Area, the United Kingdom, or California and other U.S. states with privacy laws), you may have the right to access, correct, delete, or receive a copy of your personal data; to object to or restrict our use of it; and to opt out of certain processing. To exercise these rights, email [email protected]. Because analytics data is pseudonymous, we may need the identifier stored in your browser’s cookies to find it. We will not discriminate against you for exercising your rights. If you are in the EEA or the UK, you may also lodge a complaint with your local data protection authority.

Security

We limit access to the information described here to the people at CocoIndex who need it, and we rely on service providers that maintain their own security programs. No method of transmission or storage is completely secure.

Links to Other Sites

Our Service may contain links to external websites. CocoIndex Inc is not responsible for the content or privacy policies of third-party sites.

Children

Our Service is not directed to individuals under the age of 18, and we do not knowingly collect the Personal Data of individuals under the age of 18. If you believe we may have collected Personal Data from someone under the applicable age of consent in your jurisdiction without proper consent, please let us know using the contact methods described below.

Changes to This Privacy Policy

We may update this policy occasionally, including when we add or change the tools described here. The latest version will always be posted on cocoindex.io with its “Last updated” date, and is effective upon posting.

Contact Us

If you have any questions about this Privacy Policy or want to exercise your privacy rights, please contact us at [email protected].