Face and likeness data
What face-related data we process
- Full images you import or paste are processed on your device first.
- After detecting a face locally, the app crops the face region (including surrounding area) and encodes it as a JPEG image.
- The app does not compute or upload a separate biometric template, faceprint, or similar identifier.
- Your text prompt for editing may describe facial appearance or style and is sent to the third-party AI service you select (Google Gemini or Kling) together with the crop.
How we use this data
- Solely to call a third-party generative AI model to produce an edited image and display it in the app.
- We do not use face-related data to identify you, build profiles, serve ads, or for any purpose beyond this generation feature.
Sharing, third parties, and storage
- Yes. To provide AI generation, the app transmits your JPEG face-region crop and prompt over an encrypted connection to the provider you enable in the app: Google LLC’s Google Gemini API (Generative Language API), and/or the Kling (可灵) open-platform APIs operated by the Kling party (see klingai.com for the current legal entity and product names). Path: your Mac → that provider’s servers.
- This app does not operate its own backend that receives or stores those images; processing occurs on the third party’s infrastructure. Google’s and Kling’s handling is governed by their applicable terms and privacy notices for their API products.
Do third parties store face-related data, and their practices (summary)
Plain-language summary; binding terms are each provider’s official documents. “Face-related data” here means the JPEG face-region crop and related prompt text this app sends.
- Yes. To run generative editing, Google and Kling each receive and process that content on their servers. Processing typically involves short-lived server-side storage or caching, and providers may retain logs or copies for security, operations, and legal compliance as described in their policies.
- Google (Gemini API): Requests are handled on Google infrastructure. The Google AI / Gemini API Terms and Google Privacy Policy describe how Google collects, uses, retains, and secures data—including content you submit through the API—and applicable retention and safeguards. We do not operate Google’s systems and cannot control their internal retention details.
- Kling (Kling AI / 可灵, open-platform API): Per Kling’s published privacy policy (our non-binding summary; the original text controls): personal information is generally stored inside China; retention is generally limited to what is necessary for the stated purposes and periods required by law; after you delete your account, delete data voluntarily, or when retention is no longer necessary, they delete or anonymize personal information except where law requires continued retention; if the service ends, they notify users and delete or anonymize within a reasonable period. The policy also describes encryption, security programs, and access controls.
Retention
- On device: Source and output are processed and shown in the app. When allowed, the app writes PNG results next to your source file in a user-visible
faceswap folder. If the OS denies that, the app uses the standard macOS Save dialog so you pick an accessible user location. We do not place exported result images in hidden app-only container locations (such as Application Support) as the default place for user files. Settings such as API key, model id, and prompts may persist until you delete the app or its data.
- At third parties: See “Do third parties store…” above; refer to Google’s and Kling’s official documentation for full detail.
Withdrawing consent
- You can turn off consent for sending data to third-party AI in the app Settings, or decline the first-time prompt. When disabled, the app will not send face crops or prompts to Google or Kling for generation.