Privacy Policy

Overview

This policy covers three things: the Nextly marketing website, the Nextly CLI you run on your machine, and apps you build with Nextly.

Website (nextlyhq.com). We use cookies for optional analytics, with consent.
Nextly CLI. Sends anonymous usage events when you run it, with consent and easy opt-out.
Apps you build with Nextly. Your app does not report anything to us. Nothing in the framework runtime calls home.

Website

When you visit nextlyhq.com:

We may use analytics to understand traffic patterns (page views, referrers).
We do not sell your data to third parties.
We do not use advertising trackers.
We do not collect personally identifiable information unless you provide it (for example, through a contact form).

Cookies

When you visit our website, we ask for your consent before setting any non-essential cookies. You can choose from two categories:

Essential: Required for the site to function correctly. These are always active and cannot be disabled.
Analytics: Optional. When enabled, we collect usage analytics, session recordings, and may display surveys to help us improve the product. This data is processed by PostHog on EU servers (Frankfurt, Germany). No data is sold to third parties. IP addresses are not stored.

If you decline analytics cookies, we still count visits using a privacy-preserving hash that cannot identify you personally. No cookies or local storage are used in this mode.

You can change your preference at any time:

CLI Telemetry

When you run the Nextly CLI (for example, create-nextly-app or commands like nextly migrate), it sends anonymous usage events to PostHog on EU servers (Frankfurt, Germany). This helps us see which templates and databases people use, and catch failures early during alpha.

Anonymous. A random ID is generated on first run and stored locally. It is not linked to any account or email.
Project paths are hashed. We never see your project name, directory, or file paths.
Source code, schemas, and credentials never leave your machine. No file contents, no .env values, no database URLs, no error messages or stack traces.
Off by default in CI, Docker, production, and non-interactive shells.
Easy opt-out. Run nextly telemetry disable, or set NEXTLY_TELEMETRY_DISABLED=1, or set DO_NOT_TRACK=1.

For the full event list, base context, and source code links, see /docs/telemetry.

Apps you build with Nextly

The Nextly framework runtime sends nothing to us. When the app you build runs in production, it does not call home, does not report telemetry, and does not contact any Nextly service.

All data stays on your servers.
You handle your users' data privacy and compliance.
Nextly does not have access to your instance or its data.

Contact Information

If you submit information through our contact form, we use it solely to respond to your inquiry. We do not add you to marketing lists without consent.

Open Source

Nextly is open-source under the MIT license. You can audit exactly what the software does at any time. The telemetry code is in the public repo too.

Changes

We may update this policy from time to time. Changes will be posted on this page with an updated date.

Contact

Questions about this policy? Contact us.