Privacy

What we store, and where

The Fluxtion browser playground runs entirely in your browser. Your code, your fiddle history, and your favourites live in your browser's IndexedDB and localStorage — not on our servers. Closing the tab does not delete them; clearing browser site data does.

What gets sent over the network

• Running the pre-built examples. Their generated processors are part of the site and are fetched like any other page asset; running them sends nothing to the compiler. When the page loads it asks the compiler whether you are signed in, which carries your session cookie if you have one and nothing else.
• Generating or interpreting your own processors. This needs you to sign in (see Compiler accounts below). The playground sends your graph model to the managed compiler through this site's own address and receives the generated Java. The graph model includes each node's class, wiring and configured field values, private fields included, so do not put credentials or other secrets in node fields.
• The in-browser Java runtime. The playground runs Java in your browser with CheerpJ, which your browser loads from Leaning Technologies' servers (cjrtnc.leaningtech.com). Icons are loaded from Iconify (api.iconify.design). Those services receive standard request information, such as your IP address.
• Libraries and imports. The Fluxtion libraries are served from this site. If you add a library dependency, or load a project from GitHub, those files are fetched from GitHub (raw.githubusercontent.com).
• No analytics. The playground has no analytics, tracking pixels or usage events. Cloudflare, which hosts the site, keeps standard request logs.

Compiler accounts (sign-in)

Signing in is optional. Pre-built examples run without an account. If you sign in, to compile your own graphs with the managed compiler, sign-in is handled by WorkOS (AuthKit), with your Google or GitHub account, or with a one-time code sent to your email address.

What we store when you sign in

• Your account and user identifiers.
• The verified email address WorkOS gives us. It is used only to find your account when you ask for support. It is never shown to other users and is not used for marketing.
• The name of each device or tool you connect, and when its credential was created. The credentials themselves are stored only as one-way verifiers (hashes), never as the secret.
• Session records for your sign-ins, with the session token stored only as a hash.
• A ledger of your account's usage: credits granted or removed, each compile and interpretation reserved, settled or released, refusals, and changes to your plan and its limits.

What we do not store

We do not keep the graph or source you send for generation. The ledger records a hash of each request, not its content. A generated result is kept for 24 hours, so that a request retried after a lost response can still collect it. After 24 hours it can no longer be downloaded; it is then deleted by a regular cleanup, which runs ten minutes after the previous cleanup finishes.

Who processes it

• WorkOS: sign-in.
• Cloudflare: the network edge, and access control for our admin tools.
• Railway: hosting, and the database.

Signed outputs (Pro)

When a plan includes signed output, the provenance manifest names your account by an alias derived from it, not by your account id, together with hashes of the request and of each generated file.

Keeping and deleting account data

Usage records are kept as your account's billing history. Deleting an account is not self-service yet: ask us through the contact address below and we will handle it on request.

What we do not do

• We do not require an account to run the pre-built examples.
• We do not sell or share your code.
• We do not embed third-party advertising or analytics scripts.

How to delete your data

Clear site data for this domain in your browser's developer tools. That removes IndexedDB favourites, localStorage layout preferences, and any cached Java JARs.

Contact

Questions or concerns: hello@telamin.com.