Trust & Privacy

What this website does with code and data

Each statement describes the website as it works today and names the automated test that checks it.

Source scope: samples for everyone, a private workspace for invited people

The public demonstration inspects only product-owned synthetic sample projects. It has no upload, link, Git URL or GitHub connection, and an inspection request must name a known sample and one of its known versions.

Checked by tests: lists only the approved synthetic samples, refuse a sample that is not marked synthetic, refuses %s.

People invited by the site owner also get a private workspace. They sign in with a password and a code from an authenticator app and upload a ZIP of their code. Each saved ZIP is encrypted, only its own account can open it, and it is kept until its owner deletes it. Uploaded code is unpacked and inspected only in a separate process with no network access and resource limits, never in the web server.

Checked by tests: denies every read, run, download and deletion of another owner's project, stores source and reports encrypted, bound to their place, cannot reach the network, not even servers on this machine, and gets no secrets from the environment, needs the password and a new authenticator code; a wrong confirmation deletes nothing.

Early preview. The private workspace is new and has not yet had an independent security review. Upload only code you are comfortable sharing in an early preview, and remove passwords and keys from it first.

What runs

Ctrlflip reads committed files and analyses them statically. It never runs the inspected project's code, package scripts or tests. Each inspection runs in a separate worker with a memory cap and a time limit, and receives only the environment variables Git needs.

Checked by tests: gives worker threads only the environment Git needs (no secrets from the server), stops a job at the time limit and reports it as failed, concluding nothing.

A static reading cannot show how an application behaves when it runs. Each report says which files and checks it covered, and lists what it couldn't check.

Storage

Precomputed example reports are kept in the server's memory and shared by all visitors; they contain synthetic sample data only. When you run a sample inspection, your browser gets a random anonymous ID in a cookie (HttpOnly, SameSite=Strict), and your results are stored on the server under that ID. No other browser can read, compare or delete them.

Checked by tests: gives an anonymous workspace in an HttpOnly, SameSite=Strict cookie and strict security headers, cannot read another workspace's inspection, report, fix prompt or history, serves precomputed example reports without a workspace, labelled synthetic and precomputed.

Usage is counted with pseudonyms: events hold no cookie value, IP address or free text.

Checked by test: records the usefulness measurements without cookie values.

Retention and deletion

Your sample runs are deleted automatically after 7 days. “Delete my demo data” on the Example Report page deletes them, and your usage events, immediately. A run that was still in progress when you deleted your data is discarded when it finishes; it cannot bring the data back.

Checked by tests: removes inspections after the retention period, deletes everything stored for the workspace on request, never stores a result that finishes after the workspace was deleted.

AI data flows

The website sends nothing to any AI provider, and the server makes no outbound network requests to produce a report. “Copy Fix Instructions” shows you the exact text before you copy it; you decide whether to paste it into an AI builder. The instructions contain file paths, line numbers and descriptions, not source code excerpts.

Checked by tests: the web server makes no outbound network requests, fix instructions name the product and contain no source code excerpts.

Limits

  • Each browser may start 30 sample runs per hour and keep 50 results.
  • The server runs a bounded number of inspections at a time with a short waiting queue; when the queue is full it says so instead of accepting more work.
  • Results cover JavaScript and TypeScript code, the checks named on each report, and the files it says it read.

Checked by tests: limits inspections per hour per browser, limits stored inspections per browser, refuses work when the queue is full instead of growing without bound.

Support

A support address has not been published yet. During the early preview, invited people contact the site owner directly.