Privacy Policy

If you submit your email address to the ReleaseJet Pro waitlist form, we collect that email address and, where provided by the form, a source tag (e.g. "pricing") indicating which page you submitted from. Submissions are handled by Formspree Inc. (USA) on our behalf.

• Legal basis: your consent (Article 6(1)(a) GDPR).
• Retention: until ReleaseJet Pro launches, or until you ask us to delete your email — whichever comes first. We will not use your address for any marketing other than notifying you that Pro is available.
• How to withdraw consent: email hello@releasejet.dev and ask to be removed.

We use Vercel Web Analytics to count page views and basic performance metrics. The data is aggregated, does not use cookies, does not identify individual visitors, and does not follow you across sites.

• Legal basis: legitimate interest (Article 6(1)(f)) in understanding which pages people read, so we can improve the site.
• Retention:governed by Vercel's default analytics retention (currently 90 days rolling).
• No consent banner:because no information is stored on your device, the EU “cookie law” (ePrivacy Directive, Article 5(3)) does not require one.

Our hosting provider, Vercel Inc. (USA), automatically records standard HTTP access logs for requests made to the site — IP address, user-agent, request path, timestamp, and response status. These logs are kept by Vercel under their retention policy (currently around 30 days) and are used for security, abuse prevention, and debugging.

Legal basis: legitimate interest in operating a secure service.

When ReleaseJet Pro is eventually sold, we will store license records in our Vercel Postgres database (Frankfurt, EU region) containing an organisation identifier, the billing email address, subscription plan, feature flags, status, and creation / revocation timestamps.

As of this policy's “Last updated” date, no Pro customers exist and this table is empty. See §3.5 below for what will change when Pro launches.

ReleaseJet Pro is in development. No payment processor is integrated yet and no Pro licenses are currently sold. When Pro launches we expect to collect and store the following, and we'll update this policy to remove the “not yet active” marker before the first Pro purchase:

• Billing information, handled by a third-party payment processor — most likely Stripe, to be confirmed before launch. We will never see or store your card details. What we receive from the processor is a customer identifier, the subscription status, and a receipt reference.
• License records, stored in our Vercel Postgres database (Frankfurt, EU region): your organisation identifier, billing email, subscription plan, feature flags, and activation / revocation timestamps. These records are retained for six years after revocation to meet Greek tax-record obligations.
• Activation telemetry, limited to the fact that a license was activated or refreshed (timestamp + license key). No code, repository contents, or release-note payloads ever leave your machine.

If you are reading this before Pro launches and have joined the waitlist, we'll email you once payment goes live — you'll be able to review this section in its updated form and decide whether to subscribe.

The CLI stores the following locally, on the computer where you run it:

• ~/.releasejet/credentials.yml — your GitHub or GitLab API token, and (if you have one) your ReleaseJet Pro license key and its short-lived JWT.
• ~/.npmrc — a one-line entry that authenticates your npm client to the npm.releasejet.dev private registry, using your Pro license key.
• .releasejet.yml in your project — configuration (label mappings, tag format, webhook URL environment-variable references). No secrets belong in this file; literal webhook URLs are rejected at load time.

We never transmit any of these files. They remain under your control and under the file permissions of your own operating system.

The CLI acts on your behalf when you run it:

• It calls the GitHub or GitLab API with the token you provide, to read tags, issues, pull requests, and milestones, and (if you ask it to) to publish a release.
• It can post formatted release notes to the Slack, Discord, or Microsoft Teams webhook URLs you configure. Those payloads include data already present in your repository, such as issue titles, labels, and the GitHub/GitLab usernames of authors, assignees, and closers.

Neither the CLI nor we as the operator are a party to these transmissions — they happen between your machine and the services you already use, with credentials you control.

The CLI contacts our infrastructure in exactly two situations:

• Pro license activation and refresh — when you run releasejet auth activate or auth refresh, the CLI sends your Pro license key to releasejet.dev/api/license/activate or /refresh and receives a signed JWT. Nothing else — no project names, no repository data, no telemetry — is included.
• Installing the @releasejet/pro package — your npm client authenticates to npm.releasejet.dev using your license key, then downloads the tarball.

Free users of the CLI do not contact our servers at all. There is no telemetry, no automatic update check, no crash reporting, no usage metric, and no “phone home” of any kind.