Privacy Policy — Just Married
Effective date: November 13, 2026
Last updated: November 13, 2026
"Just Married" (AI wedding snap preview; the "Service" or the "App") is operated by Thing Apps (the "Company"). This Policy explains what personal information the Service collects, what it sends outside, and when it is deleted.
Contact: thingpieceapps@gmail.com
1. Summary
The Service creates AI wedding-concept preview images from the face photos of the groom and bride that you upload. To do so, the photos are sent to overseas AI providers (NEXUSAI SERVICES LLC, operator of kie.ai, and Google LLC), and these providers may use the data they receive to train or improve AI models (Section 3). Other collection is minimal.
- The App starts without a sign-in, on a device account (anonymous account). Google and Apple sign-in are not currently offered (accounts that signed in with Google or Apple earlier keep working).
- No analytics, behavioral tracking, advertising identifiers, or crash reporting. The App does not request App Tracking Transparency (ATT) permission. We do, however, collect a one-way hash of a device identifier so that free credits are not granted to the same device more than once (Sections 2.2 and 4). This hash is not used for advertising or tracking.
- No ads. We do not sell personal information.
- The only device permissions are photo library and camera, requested only at the moment you pick or take a photo.
- You can delete your account inside the App (Settings → Account); photos and results are deleted immediately.
2. Personal Information We Collect
2.1 Information you provide
| Item | When | Purpose | Stored at |
|---|---|---|---|
| Email address and the account identifier from the login provider (Google/Apple) | Social login (no longer offered to new users; applies only to accounts that signed in with a social provider earlier) | Identifying your account, signing in again, preventing duplicate sign-up credits after re-registration | Supabase (Seoul, Republic of Korea) |
| Front-facing face photos of the groom and bride | Registering "our photos" | Input for AI wedding preview generation | Cloudflare R2 private bucket |
| Reference photo (scene photo uploaded in Custom Create) | Using Custom Create | Input for generation | Cloudflare R2 private bucket |
| Free-text prompts (Custom Create, Continue Editing) | Using those features | Input for generation | Supabase |
| Report / inquiry text and attached photo | Reporting or contacting us | Handling the inquiry, acting on inappropriate results | Supabase, Cloudflare R2 |
If you use "Hide My Email" with Apple, we receive only Apple's relay address. We do not collect your name, phone number, postal address, or payment card number.
2.2 Information generated while you use the Service
| Item | Purpose |
|---|---|
| Account identifier (UUID), whether the account is anonymous | Separating each user's data |
| Generation request records (selected cuts, resolution, aspect ratio, status, failure reason) | Processing generations, automatic refunds, incident response |
| Generated result images | Storing, showing, saving and sharing in "My results" |
| On-device explicit-content check result for a result image | Flagging inappropriate results made from free-text prompts |
| Credit balance and history (sign-up grant, use, refund, purchase) | Operating the credit system, handling disputes |
| One-way hash (SHA-256) of a device identifier — on Android the device identifier (ANDROID_ID), on iOS a random installation identifier the App stores on the device. The raw value is not stored | Preventing duplicate free (sign-up) credits. The hash is not used to identify or contact you |
| Store purchase records (transaction identifier, product, sandbox/production) | Confirming purchases, preventing one purchase from being credited to several accounts |
| Consent records (document version and time of consent) | Proving consent |
| Access logs (IP address, request time, app version) | Operations and security, incident analysis (recorded automatically by the backend) |
2.3 Information we do not collect
Name (even if the login provider passes it, we do not store it), phone number, contacts, location, advertising identifiers (IDFA / advertising ID), health data, payment card details, browsing history. Card details are handled entirely by Apple or Google; the Company never holds them. Device identifiers are kept only as the one-way hash described in 2.2; the raw device identifier is not stored.
2.4 Analytics and crash reporting
None. The App contains no analytics SDK and no crash-reporting SDK. The Google Firebase core SDK is included, but analytics, advertising and crash features are not used and no usage data is sent. If this changes, we will update this Policy before release.
3. Overseas Transfer of Personal Information (Outsourced Processing)
This is the part people care about most, so we state it precisely.
When you tap Generate, the Company's backend sends the following to the AI API intermediary kie.ai (NEXUSAI SERVICES LLC), which forwards it to the image-model provider Google LLC (Gemini) to create the image:
- A temporary signed link, valid for one hour, to the groom/bride face photos (and the reference photo in Custom Create)
- The scene description of the selected cut, and any text you entered in Custom Create or Continue Editing
- The requested resolution and aspect ratio
Your name, email, account identifier and IP address are not sent to the provider. The internal path of the signed link does, however, include your account identifier.
| Recipient | Contact | Country | When and how | Items | Purpose | Retention |
|---|---|---|---|---|---|---|
| NEXUSAI SERVICES LLC (kie.ai, AI API intermediary) | 118 Krameria St, Denver, CO 80220, USA · https://kie.ai/privacy-policy | United States | Encrypted network transfer on each generation request | Items above, and the generated result image | Relaying AI image-generation requests, and operating and improving the provider's own services (which may include AI model training) | Generated result images 14 days; request logs (text/metadata) 2 months, then deleted automatically (per kie.ai's public documentation). kie.ai does not publish a retention period for input photos |
| Google LLC (Gemini image model) | https://support.google.com/policies, privacy@google.com | United States and others | Forwarded via kie.ai on each generation request | Items above | AI image generation, policy-violation detection, and service improvement under the provider's terms (which may include AI model training) | Under the Gemini API terms, inputs and outputs are kept 55 days for policy-violation detection. Other retention and deletion are governed by Google's terms and privacy policy |
Your data may be used for AI training. The Company itself does not use your photos or results to train AI models and does not sell them. However, under their own terms, the two providers above may use the face photos, reference photos, text prompts and result images they receive to operate and improve their services, including training AI models, and the Company has no agreement in place that prevents this. Please use generation only if you understand and agree to this.
Face data, in one place. The only face information the App collects is the ordinary photos you choose yourself. The App does not use Face ID, TrueDepth, ARKit or face recognition; it does not extract or store facial landmarks, geometry or biometric templates; and it does not identify or authenticate anyone from a photo. Face photos are used for one purpose — generating the wedding preview images you request — are shared only with the two providers above, and are kept on the Company's side in a private Cloudflare R2 bucket until you replace or delete them or delete your account (Section 4).
Consent to this overseas transfer and the uses above (including possible AI training) is obtained on the in-app consent screen before any photo is first sent. The screen states what is sent (face photos and text prompts), to whom (kie.ai and Google), and that it may be used for training, and links to this Policy for details. Without consent you cannot use generation; you can withdraw consent by deleting your account. Data already sent to the providers cannot be recalled by the Company.
Other outsourced processing:
| Processor | Work | Country | Privacy policy |
|---|---|---|---|
| Supabase, Inc. | Database, authentication, backend functions | Data stored in the Republic of Korea (Seoul region) | https://supabase.com/privacy |
| Cloudflare, Inc. | Private storage of photos and result images | United States and others | https://www.cloudflare.com/privacypolicy/ |
| Apple Inc. / Google LLC | In-app purchase processing and receipt validation | United States and others | https://www.apple.com/legal/privacy/ · https://policies.google.com/privacy |
4. Retention and Deletion
| Item | Retention |
|---|---|
| Face photos, reference photos | Until you replace or delete them, or delete your account |
| Generated result images | Until you delete them or delete your account |
| Generation records, consent records, reports/inquiries | Until you delete your account |
| Credit history (grants, use, refunds) | Until you delete your account |
| Store purchase records (hash of the transaction identifier, product, credits granted, time) | 5 years after account deletion (statutory retention of payment records under the Korean Act on Consumer Protection in Electronic Commerce). On deletion the link to your account is severed and the records are kept in a form that cannot be tied to an identifiable person |
| Hashes used to prevent repeat or duplicate sign-up grants (hash of the email or login provider identifier; hash of the device identifier) | Kept after account deletion (see below) |
| Access logs | Up to 90 days |
On account deletion. When you complete Settings → Account → Delete, we immediately and permanently delete your uploaded photo files, generated result image files, generation records, consent records, reports/inquiries and account data. Copies remaining in backups or caches are normally cleared within 30 days.
Three exceptions:
- Store purchase records subject to statutory retention are kept for the period in the table above. Which account made the payment is erased; the transaction identifier survives only as a one-way hash, used solely to prevent one payment from being credited to another account again.
- To prevent an account that received free sign-up credits from deleting itself and re-registering to receive them again, we keep a single one-way hash of the email address (or the login provider's identifier). The raw email is not kept, and the hash cannot be used to identify or contact you. This record exists only for social-login accounts.
- For the same purpose, the one-way hash of the device identifier of a device that received free credits is not deleted when you delete your account; otherwise deleting the account and reinstalling the App would grant the free credits again. This hash cannot be reversed either, and it is not used to identify or contact you.
Method: electronic files are deleted so they cannot be recovered. There are no paper records.
5. Your Rights (and Those of Legal Representatives)
You may at any time request access, correction, deletion or suspension of processing, and withdraw consent.
- In the App: replace or delete photos (Our Photos), delete results (My Results), delete your account (Settings → Account).
- By email: write to thingpieceapps@gmail.com; we act without delay (within 10 days). To verify identity, tell us the email you signed in with or your account identifier.
An anonymous account (started without signing in) is tied to the device and the app installation. If you delete the App or change devices, that account and its photos, results and credits cannot be recovered, and the Company cannot identify you to act on an email request. The App does not currently offer linking a Google or Apple account, so there is no way to move or recover an anonymous account.
Under the Korean Personal Information Protection Act you may lodge a complaint with the Personal Information Protection Commission (https://www.pipc.go.kr) or the Privacy Infringement Report Center (https://privacy.kisa.or.kr, 118 within Korea). Residents of the EEA and UK have GDPR rights (restriction, portability, complaint to a supervisory authority); our legal bases are performance of a contract (providing the generation you requested) and, for payment and credit records and the device identifier hash, our legitimate interest in preventing duplicate grants.
6. Children Under 14
The Service is not directed at children under 14 and we do not knowingly collect their personal information. If you believe a child has provided information, contact us and we will delete it without delay.
7. Security Measures
- All traffic is encrypted with TLS.
- Row-level security in the database lets only the owning account read and write its data.
- Photos and result images live in a bucket closed to public access and are reachable only through short-lived signed links. Storage paths are prefixed with the owner's identifier, so another account's file cannot be addressed.
- API keys for the AI provider and storage stay on the server and are never shipped in the App.
- Credit balances and purchase records cannot be changed by the App, only by the backend.
- The explicit-content check for free-prompt results runs on the device; nothing is sent externally for it.
No system is perfectly secure, and we do not guarantee absolute security.
8. Notice on AI-Generated Content
The result images are concept previews synthesized by AI from your face; they are not real photographs. The Company states this on the Service screens and in this notice, and currently inserts no visible mark (watermark) into the images. When you share or post a result image externally, you must disclose that it is AI-generated and must not use it in a way that misleads others into thinking it is a real photograph.
9. Platform Disclosures
Apple App Store. The App accesses the photo library and camera only when you pick or take a photo. The chosen photo is transferred for generation as described in Section 3. The App does not track you and does not request ATT permission. The device identifier hash is used only to prevent duplicate free credits, never for tracking.
Google Play Data Safety. Photos, email (with social login), a device identifier hash (to prevent duplicate free credits) and app activity (generation requests, entered text) are collected and sent off-device to provide the Service. Data in transit is encrypted. Deletion is as in Section 5.
10. Privacy Officer
- Responsible party: Thing Apps Operations Team
- Email: thingpieceapps@gmail.com
Send privacy inquiries, complaints and remedy requests to the address above.
11. Changes
When we change this Policy we update the effective date above; material changes (items collected, recipients, retention) are announced in the App 7 days before taking effect, and the App asks for renewed consent.
In the event of any discrepancy between the Korean and English versions of this Policy, the Korean version shall prevail.