Privacy Policy

ClaveFlux runs your workflows with your own model provider keys, so it handles some sensitive things. This page says plainly what is stored and what is not.

Last updated October 1, 2026

Who is responsible

ClaveFlux is operated by Snehith Kumar, an individual. Questions about this policy go through the contact page.

What I store

Account details. Your email address, and a hashed password if you chose password sign in. If you sign in with Google, I receive the basic profile details Google shares for sign in.

Your work. The workflows you draw, their settings and prompts, the datasets you upload or connect, the results of runs and evals, and the history of your jobs.

Provider API keys. If you add a key for a model provider, it is stored encrypted (AES-256-GCM). It is decrypted only at the moment a run needs to call that provider, and only the last few characters are shown back to you in the app.

Where your data goes

When a run uses an AI step, the prompt and the data in that step are sent to the provider you chose, using your key, so that provider can answer. That provider then handles the data under its own terms and privacy policy. ClaveFlux does not train models and does not sell or rent your data.

If you connect Google Sheets, ClaveFlux reads the sheets you point it at to build your dataset.

A few services help run the site: a hosting provider for the servers and database, Cloudflare in front of the site for delivery and basic security, and an email service that sends sign in and password reset messages. I may also use an error reporting service, which can receive technical details about a failure such as the page and error message.

Cookies and tracking

The app keeps you signed in with a session token in your browser and remembers display choices such as light or dark mode. There are no advertising trackers on ClaveFlux.

How long data is kept

Your workflows and datasets stay until you delete them or your account. Run history can be set to expire after a number of days in your settings, and older finished jobs are archived on a schedule. Backups of the database can outlive a deletion for a short while before they rotate out.

Your choices

You can delete workflows, datasets, runs, and provider keys inside the app at any time. To get a copy of your data, fix something, or delete your whole account, write to me from the email you signed up with through the contact page. I will confirm when it is done.

Security

Traffic to the site uses HTTPS and provider keys are encrypted at rest. No system is perfectly safe. If something happens that affects your data, I will tell the people affected.

Children

ClaveFlux is not meant for anyone under 16, and I do not knowingly collect their data.

Changes to this policy

If I change how data is handled, I will update this page and the date at the top.