Skip to content
FRCTL
Login

Legal

Privacy Policy

FRCTL is operated by FRCTL SYSTEMS, an assumed business name of MINDLAB AI LLC.

Last updated: October 30, 2026

This Privacy Policy explains how FRCTL SYSTEMS, an assumed business name of MINDLAB AI LLC ("FRCTL SYSTEMS," "we," "us," or "our") collects, uses, and shares information when you visit our marketing site, create an account, or use FRCTL, our browser-based image and video editor, and related services (collectively, the "Service").

By using the Service, you agree to this Privacy Policy. If you do not agree, please do not use the Service.

We collect information in the following categories:

  • Account information such as your email address, display name, authentication identifiers, subscription tier, and whether you have told us your work is commercial.
  • Billing information processed by our payment provider (for example, Stripe), such as subscription status, billing interval, and customer identifiers. We do not store full payment card numbers on our servers.
  • Technical data our hosting and infrastructure providers record in the ordinary course of serving requests, such as IP address, browser type, and timestamps.
  • Product events counting a fixed set of moments — the app opened, a file loaded, an effect added, the preview run for half a minute, live mode entered, a project saved, an export finished, the daily drop opened, the editor and live tutorials started, skipped or finished, a logo downloaded from the logo maker while signed in, and the three upgrade moments (a limit reached, an offer shown, an offer clicked). These are not stored against your account. Each one carries a random identifier your browser generated for itself, the plan in force at the time, and which limit it was, and nothing else. No account, no email, no IP address, no browser or device details, no referrer, no page views, no clicks, and nothing you make in the editor.
  • Diagnostic reports when something crashes, containing the error, a stack trace, and your account identifier so we can tell one person hitting a bug fifty times from fifty people hitting it once.
  • Content you choose to upload to the Service, such as a profile avatar, marketplace listing covers, video packs, or posts. Everything you create in the editor — images, video, audio, presets, and exports — is processed locally on your device and is never transmitted to us unless you deliberately upload or publish it. Turning on cloud backup, which Creator and Pro plans include and which is off until you switch it on, is one such deliberate upload: it copies the media in your saved projects to private storage that only your account can read, so a project opens on another device.
  • Support communications if you contact us, including the content of your message and any information you choose to provide.
  • Partnership enquiries you send from our site, including your name, email address, any link you give us, and your message. Alongside each one we store a one-way hash of the network address it came from, used only to stop the form being flooded and never to identify or profile you.

FRCTL counts a small, fixed set of product events, listed above. They exist to answer questions about the whole population and never about a person: of everyone who opened FRCTL this week, what fraction loaded a file, and of those, what fraction made something. Those are percentages, and percentages do not need names.

So there is no name on them. An event carries a random identifier your browser generated for itself and stored locally — not your account, not derived from your account, not shared between browsers, and thrown away the moment you clear site data. Somebody holding our entire event table could tell you what fraction of sessions never got past loading a file, and could not tell you one thing about any individual person.

For a short period in September 2026 these events were stored against accounts, with a setting to switch them off. That did not match what this page had always said, so it was changed rather than defended: every event collected under the old arrangement was deleted, the account column was removed from the table, and the setting went with it. There is no longer an opt-out because there is no longer anything about you to opt out of.

There are still no advertising or analytics companies involved, no third-party trackers, and no tracking pixels on our pages. We do not follow you across other sites, we do not record what you make, and we do not sell or share any of it. Crash reports are the one place an account identifier is still attached, so we can tell one person hitting a bug fifty times from fifty people hitting it once; they go to an error-monitoring provider that works on our behalf and nobody else.

The editor can use your camera as a live video source and your microphone or system audio to drive audio-reactive visuals. When you grant permission, that media is opened directly by your browser and used only on your device.

No camera frame or audio sample is ever transmitted to us. Camera video is drawn straight into the editor's graphics pipeline; audio is analysed locally for loudness and frequency information only, and is never recorded. Access is released as soon as you leave live mode or close the editor.

Mirror Cam, in Live, turns a phone into a camera paired to your computer. The phone runs a segmentation model itself and sends your computer only the outline of the person it finds, never the picture. If the phone cannot keep up, it can send its camera video instead so that your computer does the segmenting, and you can choose that yourself. Either way the outline or the video travels only over a direct connection between your two devices and never through us. When no direct connection can be made, nothing is sent and the phone says why. Neither is recorded or stored on either device, and the camera turns off when the pairing ends.

The Face Blur tool detects faces so it can obscure them. Detection runs entirely on your device using a model and runtime we ship with the application — nothing is uploaded, and the feature works with no network connection. It produces temporary on-screen regions that are discarded immediately after use.

We do not create, store, or transmit any face template, faceprint, biometric identifier, or other biometric information, and we do not use face detection to identify anyone. Only whether you switched the tool on is saved with a preset; the detected positions are not.

The subject-isolation tool works the same way: an on-device segmentation model that never uploads your image.

We use information to:

  • Provide, maintain, and secure the Service, including authentication, entitlements, and exports.
  • Process subscriptions, partner codes, and billing through our payment partners.
  • Respond to support requests and communicate about your account.
  • Debug issues, prevent abuse, and enforce our Terms.
  • Understand, in aggregate and without knowing who anyone is, how far people get in the product and which plan limits they reach, so we can decide what to build next and what each plan should include.
  • Comply with legal obligations and protect the rights, safety, and property of FRCTL SYSTEMS, FRCTL, and our users.

We do not sell your personal information, and we share it with no advertising or analytics companies. We share information only with the service providers that run the Service on our behalf — hosting, database and authentication, file storage for cloud backup if you turn it on, payment processing, and crash reporting — and only as far as each needs to do its job.

If you pair a phone to Live with Phone Remote, the control messages it sends (which fader or pad moved, and to what value) and, for its clip loader, the names of the clips in your session pass through our database and realtime provider between your phone and your computer and are not stored. Pictures of your clips are sent only over a direct connection between the two devices and never through us; when no direct connection can be made, the phone shows names alone. We keep only a record that the pairing exists and when it ends, and the pairing code itself only as a one-way hash. A Mirror Cam phone pairs the same way, and its status messages (whether its camera is running, how many outlines a second it manages, and its battery level) may pass through our realtime provider in the same way, unstored. What it sees does not: see Camera, microphone, and face detection.

We may also disclose information if required by law, to protect against fraud or security threats, or in connection with a merger, acquisition, or sale of assets, subject to appropriate confidentiality protections.

FRCTL sets no cookies of its own, and no advertising or analytics cookies are set on our pages by anyone else.

What we do use is your browser's local storage, for six things only: the sign-in token that keeps you logged in, your own editor preferences such as favourite effects, output aspect ratio, and panel sizes, how you have placed and shaped the Mirror Cam outline on this computer, the logo you are working on in the logo maker, so a reload or signing up does not lose it, the control layouts you build on a phone paired with Phone Remote and the part of the picture you frame on a Mirror Cam phone, both of which stay on that phone, and one random identifier that lets us count how many browsers reached a step rather than how many times a step was reached. That identifier is made on your device, is tied to no account, and is readable by nobody else. None of it identifies you to third parties.

Separately, the editor keeps your work in your browser's on-device database: the media you put in saved projects, an automatic copy of the session you have open, so a crash or a closed tab does not cost you what you were making, a pointer to any file too large to copy (its name, and the browser's record that you chose it), so a project can reopen it where it sits once you allow it, and, if you choose a profile picture when you sign up, that picture until your first sign-in on this browser uploads it to your profile and removes it from the device. None of it is sent to us unless you turn on cloud backup on a Creator or Pro plan, which copies the media in your saved projects (never the session copy) to private storage only your account can read. You can discard the session copy from the editor's start screen, and clearing this site's data removes all of it from this device. Clearing site data does not remove cloud backup copies: delete those from your account settings.

Because all of it is strictly necessary to provide a service you asked for, no consent banner is required — the counting identifier is not used to profile you, follow you, or tell anyone else anything. You can clear it at any time through your browser's site-data settings — note this is site data rather than cookies, so clearing cookies alone will not remove it. Clearing it signs you out and resets your preferences.

When you make a payment we send you to our payment provider's own checkout page, which is a separate site with its own cookies and privacy policy. No payment form is embedded in ours.

We retain account and billing records for as long as your account is active and as needed to comply with legal, tax, and accounting obligations. You can delete your account yourself from your account settings. Our payment provider keeps its own record of past payments, which tax and accounting law requires, and that record is not removed by deleting your account. An account that has sold marketplace items, or holds a Lifetime preorder, is closed by contacting us instead, so that buyers keep what they paid for and the licence is settled.

Product events are deleted after 90 days. Before they are deleted they are counted into daily totals — how many browsers reached a given step or limit on a given day, per plan — and those totals are kept. Neither the events nor the totals identify anybody or can be traced back to you.

Cloud backup copies are kept while you have a plan that includes backup. If that plan ends, they stay available read-only for 30 days and are then deleted. You can delete them yourself at any time from your account settings, and deleting your account deletes them immediately.

Deleting your account deletes everything held against it. Product events are not held against it — there is nothing in them to find you by, and so nothing to delete on your behalf.

We use administrative, technical, and organizational safeguards designed to protect your information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Depending on where you live, you may have rights to access, correct, delete, or port certain personal information, or to object to or restrict certain processing. You can update profile details, change your email and password, and delete your account in your account settings, and manage billing through the customer portal when available.

To exercise privacy rights or ask questions about this policy, contact FRCTL SYSTEMS at aven.frctl@gmail.com. We may need to verify your identity before responding.

The Service is not directed to children under 13 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will take appropriate steps to delete it.

If you access the Service from outside the United States, your information may be processed in the United States or other countries where we or our service providers operate. Those locations may have different data protection laws than your home country.

We may update this Privacy Policy from time to time. We will post the revised version on this page and update the "Last updated" date. Material changes may also be communicated through the Service or by email where appropriate.