YOUR INFORMATION

Privacy notice

Notice version: 5 September 2026

Who is responsible

This website and the Cadensight for Jira release waitlist are operated by Pavel Ozolin, doing business as Cadensight Lab. Contact us at info@cadensightlab.com or 2010 El Camino Real #1498, Santa Clara, CA 95050, United States.

What we collect and why

If you join the waitlist, Brevo receives your email address and your consent choice. We retain the form’s consent wording and version alongside the provider’s sign-up record, source and subscription status. We use this information to manage requests for Cadensight for Jira early-access and launch updates. Our basis for release emails is your consent.

Providing an email is optional. You can read the site and follow the demo link without joining. Joining does not subscribe you to a general newsletter.

Our hosting services may process network and request information, such as an IP address, requested page and time, to serve and secure the website. The form uses Cloudflare Turnstile to reduce automated submissions. It processes browser and network signals, such as IP address, browser information and the page origin, to detect abuse. This supports our legitimate interest in operating a reliable, secure service.

Your choices

No automatic email is sent when you submit this form. Submission records a request; it does not verify ownership of the email address. Release emails will remain disabled until sending, withdrawal and tracking controls are verified. Every release update includes an unsubscribe link. You can also contact us to withdraw consent. Withdrawal does not affect processing that was lawful before it, and we stop future release emails when you unsubscribe.

Service providers and international processing

Our form submits directly to Brevo to manage waitlist requests and consent. The landing application does not store a copy of the submitted email address. We do not sell personal information or share it for cross-context behavioral advertising.

We use Brevo to receive waitlist signups and manage subscription preferences. Brevo reports database storage in France, Germany and Belgium, with additional processing possible in countries where it and its providers operate. Its data-processing terms describe safeguards for international transfers, including contractual clauses and other applicable mechanisms. The form also uses Cloudflare Turnstile to detect automated submissions. Turnstile processes network and browser signals for site security and improvement of its bot-detection service. Joining does not trigger a confirmation email; release campaigns are not currently active.

The website is hosted on a Hetzner server in Germany and delivered through Cloudflare's network. These services process request and network information, such as IP address, requested address, time and browser information, to deliver and secure the site. The landing application does not store submitted email addresses or keep application request logs. Its production routers disable access logging. Container operational logs rotate by size, with up to three 10 MB files, rather than a fixed number of days. Provider security and operational records follow the providers' retention practices.

See Brevo’s data-processing terms.

How long information is kept

We remove ordinary active waitlist records no later than 12 months after signup or 30 days after the release-notification program ends, whichever comes first. We stop future release emails when you unsubscribe. Limited suppression and consent records may be kept separately for the purposes and periods below. These deadlines govern the records we control; provider backup, security and operational records are subject to separate provider retention practices.

Suppression records

We keep only the address and minimum opt-out information needed to prevent unwanted release emails while the program or its import sources could contact you again. We remove that record within 90 days after the program is permanently closed and its sending and import sources are disabled, unless a specific legal obligation requires limited retention. Suppression information is not used for marketing.

Consent evidence

We keep the minimum signup source, time, consent wording/version and subscription history needed to explain how release emails were requested. If no release email was sent, we delete that evidence with the ordinary waitlist record. Otherwise we retain it for up to 12 months after our last release email to that address. A specific unresolved complaint or legal obligation may require a limited, restricted record for longer; we review that need separately.

Cookies, tracking and browser signals

The landing-page application does not set analytics or advertising cookies, use advertising pixels, or load third-party fonts. We do not use this site’s information for advertising or engagement measurement. A Do Not Track signal does not disable security processing. The security check makes requests to Cloudflare and may use browser storage needed for abuse prevention. Cloudflare acts as a processor for site protection and also processes challenge signals to improve its bot-detection services, as described in its Turnstile Privacy Addendum. Following a link to the product hub or another website takes you to a separate service with its own processing practices.

Your privacy rights

Depending on where you live and the law that applies, you may request access, correction, deletion, restriction, or portability of your information, or object to certain processing. To make a request, email info@cadensightlab.com. We may need to verify that the request concerns your information. You may withdraw email consent at any time and, in the EU/EEA, lodge a complaint with your local data-protection supervisory authority. We do not make automated decisions producing legal or similarly significant effects from waitlist information.

Children

This website is intended for professional teams. We do not knowingly collect waitlist information from children under 16. Contact us if you believe a child has provided information so we can review and remove it.

Changes to this notice

We will update the notice date when our practices change. If a change materially affects how waitlist information is used, we will provide an appropriate notice and obtain fresh consent where required.