Privacy policy

This policy covers NextConstraint and the data it holds. To price the leaks in your funnel it needs numbers about your company, so this page says exactly what we hold, why, who else processes it, how long it stays, and how to delete it. We do not sell your data, share it with other customers, or use it to train anyone’s AI models.

The leak calculator runs in your browser. What you type into it is not sent to us. If you get a result, the estimated amount and which leak it is (not your numbers) are kept in your browser for 30 days, so the pricing section and checkout can show “Your estimated leak”. The sample workspace runs on made-up data, kept in your browser.

Like any website, our hosting provider processes each request, including your IP address and browser details, to serve the page. We count page views with Vercel Analytics, which uses no cookies and does not track you across sites.

Your account. Your email address and a password (stored only as a hash by our database provider), or, if you sign in with Google, the email address and basic profile Google returns. We use it to sign you in and to email you.

What you tell us about your company. Its name, domain and description, the numbers you enter, your goals, and anything else you type into your workspace, including your questions in Ask. We use it to price your leaks, pick fixes and answer you.

Public pages we read for you. When you ask, we read the public pages of your domain that robots.txt allows: titles, headings, visible text, links, images and structured data, and we take screenshots of the main pages. We use them to understand your site.

Data from tools you connect. Only the numbers each connection needs: counts and totals such as visitors, sign-ups, revenue, paying customers and cancellations. We never store your customers’ personal details. Some data your payment provider sends us, such as a failed invoice or a payment, includes a customer’s name and email. NextConstraint uses only what it needs to count and total them: amounts, currencies, dates, statuses, billing intervals, and the provider’s customer ID so each customer is counted once. It discards the rest without storing or logging it. We never read your source code.

Files you upload. Screenshots or PDFs you add to answer a data request, so the numbers in them can be read.

Billing records. Your plan, its status and renewal date, and the customer and subscription IDs our payment provider gives us, plus the billing notifications it sends us, which include your name and email as you gave them at checkout. We also record whether you have had the intro month. We use these to give you access, to keep the intro month once per person, and to send billing emails. We never receive your full card number.

AI usage. For each AI request: which feature, the model, and how much it used. We use this to apply the fair-use limit.

Account emails (confirming your address, resetting your password), billing emails (a welcome after your first payment, a reminder three days before your first full-price monthly charge, and on the annual plan a reminder 30 days before each yearly renewal), and product emails about your company: your plan, verdicts on your fixes, and connections that stopped working. We also email you before a deletion becomes final, and about any change to these terms or this policy that affects you. Product emails say how to turn them off in Settings.

Answering in Ask, writing AI plans and reading screenshots means sending the relevant parts of your workspace to Anthropic, which runs the Claude models we use: your company details, the website text we read, your connected numbers, your question, and the files or screenshots being read. Anthropic processes it to return the answer and, under its commercial terms, does not use it to train its models. Pricing your leaks, picking the fix and the verdict use no AI. If you would rather a detail never left our systems, do not put it in your workspace.

We use a small number of providers, each for one job:

• Supabase stores your account, your workspace, uploaded files, screenshots and your encrypted connection keys, signs you in, and sends the sign-in emails (confirming your address, resetting your password).
• Vercel hosts the site and the app, processes every request, and counts page views without cookies.
• Dodo Payments is the merchant of record: it runs checkout, takes payments, charges and remits tax, issues invoices, and runs the billing portal where you cancel or change your card.
• Resend sends our other emails.
• Anthropic runs the AI features described above.

Purchases are processed by Dodo Payments as merchant of record, which also handles order-related questions such as invoices, payment methods and charges.

Google processes your sign-in if you choose Google. The tools you connect (such as Stripe, Dodo Payments, Vercel, Plausible, PostHog or Supabase) process the requests we make to them on your behalf. Each provider handles data under its own terms and privacy policy.

When you connect a tool we store the key, token or password that connection needs, and use it only to read the numbers described above. After setup, NextConstraint only ever reads from your tools, and asks for the least access each one allows:

• Stripe (beta). NextConstraint accepts only restricted keys, and setup asks for read access only.
• Dodo Payments and Plausible. Setup asks for a read-only key.
• PostHog. Keys are checked and refused if they can write.
• Vercel. NextConstraint accepts only a token limited to one project. Vercel tokens can’t be made read-only, so that token has full access to that one project, even though NextConstraint only reads with it.
• Supabase. Setup makes a one-time change: it creates a small schema with one view, and one role whose only grant is that view. Like any database role, it can also call functions your project lets everyone call; setup lists any of those that run with elevated rights. It touches no data. The view holds only sign-up and last-sign-in times, and no user data leaves your database except counts: never emails or user rows. NextConstraint keeps only that role’s password, never a Supabase key. Disconnecting shows the SQL that removes the view and role.
• Your keys. Encrypted at rest (AES-256-GCM) and used only server-side.

Google Analytics, YouTube and X are no longer offered as new connections. If you connected one earlier, its access is read-only, and disconnecting it also revokes our access with the provider.

NextConstraint does not set cookies of its own, and runs no advertising or cross-site trackers. Your browser’s local storage keeps what the site needs between visits: your login session, the sample workspace if you open it, an unfinished company setup, the plan you picked on the pricing section, and the leak calculator’s estimate described above. Your browser’s session storage, which is cleared when you close the tab, keeps the screen you had open and an unfinished connection form, without its key. Clearing your browser’s site data removes all of it.

Google’s sign-in page and Dodo’s checkout and billing portal are on their own sites and set their own cookies under their own policies.

Your workspace stays until you delete it or close your account.

• When you leave. Disconnect a tool and its stored key is deleted at once. Delete your account and your stored keys are deleted at once; everything else is deleted after 7 days, and you can log in before then to restore it. If you used the intro month, we keep only a one-way hash of your email, so the intro month stays once per person. Backups expire within 7 more days.

When you ask to delete your account from Settings, we also stop your plan from renewing so you are not charged again, revoke our access to Google and X, and sign you out everywhere. After the 7 days we delete your login, company records, history and verdicts, uploaded files, screenshots, chat history, and the billing records we hold. The email hash cannot be turned back into your email and is not linked to anything else. Dodo Payments keeps its own invoice and payment records for as long as tax and accounting law requires, and our providers keep their own logs under their own retention.

Every row in our database belongs to one account, and that is enforced by the database itself, not only by our code. Connection keys are encrypted at rest and used only on our servers. Payment notifications are signature-checked and processed once. The website reader refuses private network addresses, checks redirects, caps response sizes, and treats everything it fetches as untrusted. No system is perfect, and we will tell you promptly if something happens that affects your data.

You can see and correct your workspace data in the app, copy out what you need, and delete everything from Settings. Depending on where you live, you may also have the right to a copy of your data, to object to or restrict some processing, and to complain to a data protection authority. Write to us and we will help.

NextConstraint is a business tool for people 18 and older, and is not directed at anyone younger.

If we change this policy in a way that meaningfully affects you, we will update the date at the top and email you before the change takes effect.

Privacy questions, data requests or complaints: support@nextconstraint.app. NextConstraint is responsible for the data described here.