Privacy,
plainly.

Summary

Frameloop does not require a Frameloop account during the beta. Local tools operate on your device. When you deliberately start an AI generation or image edit, the media, prompt, and selected generation settings needed for that request are sent to fal.ai using the API key you provide.

Information on your device

Your fal.ai API key is stored in iOS Keychain. Project settings, pending video job references, and local library records are stored on your device. Frame extraction and metadata inspection run locally. Frameloop does not receive this information through a separate Frameloop server during the beta.

You can remove the stored provider key from Settings. You can delete locally stored renders from the Library. Copies you save to Photos are controlled separately through the Photos app.

Remote generation

For remote generation, Frameloop sends the selected input image or images, your prompt, model identifier, and generation settings directly to fal.ai. fal.ai returns queue status and generated media. Your fal.ai account is billed by fal.ai according to the model you choose.

fal.ai handles this information under its own privacy policy and terms. Those documents control fal.ai retention, security, and account practices. Do not submit media you are not authorized to process.

This website

This initial website is static and does not use advertising pixels, behavioral analytics, or account cookies. If you email us to request TestFlight access or support, we receive your email address and the information you include. We use it to respond and manage the beta.

Your choices

You choose whether to grant Photos access, provide a fal.ai key, or start a remote request. You can use local tools without remote generation. You can request deletion of beta correspondence held by Frameloop by emailing the address below. Requests concerning a fal.ai account or fal.ai-hosted information must be directed to fal.ai.

Contact

For privacy questions or requests, email hello@frameloop.io.