Last updated: September 10, 2026
1. INTRODUCTION
GenFrame ("the App," "GenFrame," "we," "our") is a creative platform built on artificial intelligence that turns still images into video and performs face replacement. The pages below set out, in detail, how information reaching the App is handled.
Your use of GenFrame — whether you browse it, upload to it, or purchase within it — signals that you understand and accept the practices set out here. Read this notice together with our Terms of Use; it can be amended, and the Updates section explains how you will hear about that.
2. FACE DATA COLLECTION AND USE
The Face Data We Work With
Photographs and videos you supply are analysed for the geometry of the faces they contain: contour lines, the placement of eyes and other feature points, and the alignment measurements a convincing replacement requires. Those measurements are what we mean by face data throughout this notice.
Why We Collect It
There is a single reason: producing the face-replacement result you asked for. Identifying who you are, verifying an identity, matching you against any database, or any application beyond rendering your requested effect — none of these happens, at any time, for any reason.
WE DO NOT KEEP FACE DATA. Once processing ends, face data does not survive on our systems. Facial analysis exists only while your request is actively being rendered, and what it produces is destroyed irreversibly and permanently the moment that render finishes.
Rendering an effect can, however, require sending your media to one of the model providers we work with. That is set out in full below, under "Who Receives It, and Who Does Not" — please read it.
How Long It Can Exist, and Why At All
While a render is under way, face data sits on encrypted servers we control, and it may do so for no longer than 24 hours. That window is a technical fallback and nothing more: it exists so a request still completes when the network drops, a connection stalls, or the processing queue backs up. Ordinarily deletion happens the instant rendering completes. Twenty-four hours is a ceiling that cannot be exceeded — never a normal storage period — and indefinite storage of face data does not occur under any circumstances. That ceiling governs the servers we control. Where an effect is rendered on a model provider's infrastructure, that provider keeps to a schedule of its own, which we point you to below rather than restate as though it were ours.
The Processing Sequence
Your media arrives at our servers; facial features are examined; a short-lived face map is assembled for blending; the effect you requested is rendered; the face data is erased as soon as that completes, and in no event later than 24 hours after your session closes.
Where the render itself happens depends on the effect. Some effects run from beginning to end on hardware we operate, and your media never leaves our servers. Others are produced by generative models we license rather than host, and for those the media you supplied — the face in it included — is transmitted to that provider and rendered on its infrastructure. The effect you pick decides which of the two paths applies. Both providers are named in the next section and again under "Integrated Services".
Who Receives It, and Who Does Not
Face data is never sold. It is never handed to anyone for advertising, for profiling, or for any purpose disconnected from the render you asked for. That rule holds without exception.
It does reach the generative-model providers that carry out the render, because a render cannot be produced without it. Two are used:
- Kling, operated by Kuaishou Technology, for video generation. Media sent there is processed on that provider's infrastructure, which sits outside both the European Economic Area and the United States.
- GPT Image 2, operated by OpenAI, for image generation.
Each receives only the media the effect you selected actually requires, and receives it over an encrypted connection. Each applies a retention schedule of its own, set by that provider rather than by us and published in that provider's own privacy terms. Our own copy is deleted as described above.
Beyond those two, nobody receives it. Our hosting and network providers carry it as encrypted traffic they cannot read, and no analytics, advertising, or attribution partner receives it in any form.
What Our Other Vendors Do Not Hold
Leaving aside the two model providers named above, not one of the outside providers we work with — neither our hosting providers nor any analytics vendor — receives face data, reaches it, or keeps it. Our infrastructure partners (DigitalOcean, on whose servers the processing runs, and Cloudflare, which fronts our domains) move encrypted packets that keep our servers running, yet raw facial analysis output and anything biometric derived from it stay beyond their reach. What our analytics partners (Firebase, AppsFlyer, Meta App Events, Apphud) do receive is limited to anonymised technical and behavioural signals; face data is not among it and never will be.
Nothing Biometric, Nothing Identifying
We keep no facial template, and no facial recognition system is operated here. At no point is face data turned toward identifying a person or authenticating one.
3. WHAT INFORMATION DO WE GATHER?
Supplied By You
- Images and video, taken with the camera or chosen from your device through the system picker. Saving a finished render back to your photo library asks your permission first.
- The facial measurements described in Section 2, derived for face replacement alone, never for biometric identification, and gone from our servers within 24 hours. Depending on the effect, the media they come from may be transmitted to a model provider for rendering; Section 2 names them.
Gathered Automatically
- How the App is used: which features you open, and for how long
- Connection information, including your IP address and its origin
- Hardware and software details: device model, operating-system version, screen dimensions
- Carrier information and device identifiers, the advertising identifier (IDFA) among them, where you have permitted tracking
- Environment settings such as region, language, time zone, battery state, and browser
- The push token issued by Apple, if you turn notifications on, which also lets our attribution partner recognise an uninstall
Performance figures are collected by our analytics tooling (Google Analytics for Firebase and Meta App Events) so the App can be improved. Face data forms no part of what they see.
Identifiers and Local Storage
Authentication and core features rely on session cookies. Operational needs are also served by other identifier technologies, among them pixels, beacons, and storage kept locally on your device.
4. OUR DATA PROCESSING PRACTICES
The Core Purpose
Uploaded visual media and the facial measurements taken from it exist to do one job: render face-replacement effects. Recognition, authentication, and biometric identification are not part of that job and do not take place.
The Sequence
Upload, then analysis on our servers, then extraction of face data, then rendering — on our own hardware, or, for effects produced by a model we license, on that provider's infrastructure — then integration of the result, then encrypted short-term storage, then automatic deletion the moment processing ends, at the outside 24 hours after your session closes.
Everything Else We Do With Data
Information that is neither facial nor visual underpins running the service, tuning its performance, diagnosing faults, keeping it secure, studying how it is used, planning new features, and tailoring advertising.
5. INFORMATION DISCLOSURE
Face Data Stands Apart
Face data goes to no external party except the generative-model providers that perform the render — Kling (Kuaishou) and GPT Image 2 (OpenAI), both described in Section 2 and listed again below. It is never disclosed to anyone else, and our copy is erased permanently once processing has finished.
Where the Service Runs
GenFrame runs on cloud infrastructure operated by DigitalOcean, with Cloudflare supplying DNS, content delivery, and protection in front of it. Their role is to keep our servers running by carrying encrypted packets. Raw facial analysis output, and any biometric information drawn from your content, remain inaccessible to them; they neither receive, nor store, nor process face data in any form whatsoever.
Integrated Services
Two of the services below generate the results you ask for, and receive your media in order to do it:
- Kling (Kuaishou Technology) — video generation. Receives the images and clips you submit for effects rendered by this model, the faces in them included. Processing takes place outside the European Economic Area and outside the United States.
- GPT Image 2 (OpenAI) — image generation. Receives the images you submit for effects rendered by this model, the faces in them included.
The remainder are incorporated for analytics, delivery, monetisation, and performance monitoring. Face data reaches none of them:
- Firebase (Google) — application infrastructure, stability and crash monitoring, remote configuration of features, and delivery of template assets. Receives no face data.
- AppsFlyer — campaign analytics, install attribution, deep-link resolution, and uninstall measurement. Receives no face data.
- Meta App Events — event and engagement measurement, and advertising optimisation. Receives no face data.
- Apphud — administration of subscriptions and in-app purchases, together with the entitlements attached to them. Receives no face data.
- Apple (App Store, StoreKit, SKAdNetwork) — processing of payments and privacy-preserving measurement of advertising. Receives no face data.
Each of these operates under a privacy policy of its own, and reading them is something we recommend. Every one of them is engaged under terms that oblige it to protect your data to a standard equal to the one this notice sets out, and to handle it only on our instructions and for the purpose named beside it above.
Transfers Across Borders
Where data moves between countries, it does so under standard contractual clauses and the other legal safeguards that applicable data-protection law requires. This matters in particular for effects rendered by Kling: choosing one of them sends your media to infrastructure outside the European Economic Area and outside the United States, and the transfer is made on that footing.
When the Law Requires It
Information may be disclosed where a legal obligation compels it, or where doing so protects rights, our users, or the wider public. Face data is excluded from this: it has already been erased before any such obligation could attach to it.
6. DATA STORAGE AND PROTECTION
How Long Things Are Kept
- Face data: not kept by us at all once processing has run. Deletion from our servers is permanent, occurs on completion, and cannot fall outside a 24-hour ceiling. Where a render was carried out by one of the model providers named in Section 2, that provider's own retention schedule applies to the copy it received, and is governed by its terms rather than by this one.
- Uploaded media: erased from our servers no more than 24 hours after your session closes.
- Material held on your handset: it stays there until you remove it yourself.
- Aggregated and anonymised records, which contain no face data: held for as long as analysis requires. Neither identifying you from them nor rebuilding face data out of them is possible.
Keeping It Safe
Organisational and technical measures are in place to guard against corruption, loss, and access by anyone unauthorised. Every outside provider we engage is bound by confidentiality and data-protection commitments.
7. USER RIGHTS
Which of the following you can exercise depends on where you live:
- Restriction of processing: have processing narrowed where the law provides for it
- Withdrawal of consent: take back consent whenever you wish
- Rectification: have inaccurate records put right
- Objection: contest processing, marketing included
- Erasure: ask that data be removed — bearing in mind that face data has already been deleted automatically within 24 hours of processing
- Access and portability: obtain the data processed about you in a machine-readable form
Use the contact route given below to raise any of these. Charges do not apply unless the law expressly allows one.
8. RESPONSE TIMEFRAME
You can expect an answer within one month. Where a request proves complex, that period may run up to two months longer, and we will tell you beforehand why the extension is needed.
9. AGE REQUIREMENTS
As a general rule, you must be 13 or older. Anyone between 13 and 17 needs the agreement of a parent or guardian.
Within the EU the threshold is 16, unless a parent or guardian has given valid consent.
Should we learn that an underage user's data has reached us, it is deleted at once. Please tell us straight away if you become aware of underage use.
10. POLICY UPDATES
This notice will be revised when the law or the way we operate changes, and you will be told through a notification inside the App. Where applicable law does not insist on explicit consent, carrying on with the App a week after that notification counts as acceptance.
11. CONTACT
For anything to do with this Privacy Policy or with how face data is handled, write to:
Email: MarandolaSchebler846@outlook.com
Our Terms of Use are published here: https://sites.google.com/view/genframe-terms