Security & privacy

Tests run on your computer. Little leaves it, and we write down exactly what goes where.

As of November 9, 2026. Things still in progress are marked as such.

What runs on your computer

The engine that manages runs and judges results is a separate program running on your computer.
The engine opens no door for outside connections (network ports). It talks to the app only through a channel that only this computer’s owner can use.
The Chrome used for testing also opens on your computer.
Run records stay on this computer and aren’t sent to a server.

With your own AI key, or Codex or Claude Code signed in on this computer: to judge the screen, screenshots and instructions go straight to that provider. They don’t pass through Prefly’s servers.
With a Prefly plan and no key (in preparation): requests go through Prefly’s servers to the model provider. The servers don’t store screens, instructions, or responses. They keep only a usage record (time, model, token counts, credits charged, and similar).
Accounts: the source uses self-hosted Keycloak OpenID Connect, email codes and configured social connections. Actual delivery and deployment settings require separate confirmation. Prefly’s servers never handle passwords. They store your email, name, language, and phone number (if you add one), plus device name, operating system, and app version. The full list is in the Privacy Policy.
When filling in a new project’s name and icon: the engine reads only the first-screen information at that address. Apart from a label identifying itself as Prefly, it sends no cookies or account information.
Waitlist: we collect your email, language, inquiry topic, and the page you signed up from.

AI keys are kept in your operating system’s Keychain. After you add one, only the last few characters show on screen, and disconnecting also deletes it from Keychain.
Test account passwords are also kept in Keychain. There is no way to show the original again.
We’re designing a way for the AI to see only a placeholder instead of the password (not built yet).

CAPTCHAs and identity verification are handed to a person, never bypassed.
Sign-ins and payments use only test accounts you add yourself. Real customer accounts and real payments are never used.
We’re designing it to stop right before a payment is confirmed if it can’t verify that payment is in test mode (not built yet).

Local deletion removes personal data and app/CI access. Original identity-provider deletion and external billing cleanup are separate and may be delayed, blocked or unknown. A deleted-identity digest barrier has no expiry. Usage/payment retention, refund and compensation policies are not finalized.
Phone verification ties one Korean mobile number to an account, and a number can belong to only one account. Verification codes are stored without the original, and only a masked number shows on screen. Deleting your account deletes the number; only verification records from the last 24 hours are kept for one more day, detached from the account, to prevent abuse, then deleted (sending text messages is in preparation).

We haven’t chosen a payment provider.
We’re confirming model providers’ data retention and training terms through contracts.
We haven’t decided how long payment records are kept.
Windows isn’t supported yet.