Glow Up Girlie

Privacy

Glow Up Girlie is operated by ARKANAV ENTERPRISES PVT LTD. This notice explains the app’s photo analysis, AI makeup previews, saved-scan assistant, purchases and saved results.

Last updated: 16 November 2026

Photos and beauty preferences

The app stores onboarding preferences, selected photos and saved scan history on the device. Before an AI scan, an explicit consent action is required to send the selected photo, age and selected beauty preferences through the app’s analysis service to OpenAI. Shared preferences include beauty goals, optional self-reported skin concerns and product preferences, plus the chosen aesthetic or self-reported skin type when relevant.

Skin-concern selections can include information such as acne, redness or sensitivity. They are optional, are used as the user’s stated preferences, and are not a diagnosis. Gender and ethnicity selections stay in the local profile and are not included in the AI request.

OpenAI processes the photo to produce cosmetic styling guidance. For Glow Up Guide, the same original photo is also used to generate an AI makeup preview in the selected style. The image instructions require preservation of identity, apparent age, facial features and natural skin tone. Generated previews are illustrations of makeup styling, not a prediction or a photograph of a real treatment. AI output can be inaccurate.

How the analysis service handles data

Cloudflare hosts the app’s backend and database. Original photo and profile request payloads are processed in memory and sent to OpenAI; the application does not save those original request payloads in its database or application logs. Completed guidance and the generated preview are stored together as an encrypted result, associated with an installation identifier and scan-job identifier. The app uses these records to recover saved results and prevent duplicate scan charges.

OpenAI’s published API policy states that API data is not used to train its models by default. Its default abuse-monitoring retention can be up to 30 days, with exceptions described in its policy. Glow Up Girlie does not promise zero provider retention. See OpenAI’s API data controls.

Optional saved-scan assistant

After completing a scan, you can ask up to ten new successfully answered questions about that scan and related styling. This includes makeup guidance, outfit colour combinations, wardrobe neutrals, shoes and accessories based on your saved results and clothing descriptions you type. Each question is independent; the assistant does not inspect new photos or use your conversation history to infer a follow-up topic.

Before the first new assistant question, a separate explicit consent action is required to send your question and the verified text guidance from that scan through our service to OpenAI. The assistant request does not include the original face photo, AI preview image, age/profile fields, gender or ethnicity selections, or other scans. Please avoid including private information that is unnecessary for a styling question.

The service creates an encrypted, scan-specific context ticket from a verified completed result, which the app saves on your device. This ticket lets the service verify the original guidance without accepting edited or invented results from the device. It can support further questions after the subscription or original server-result retention expires, while that scan has questions left and its ticket remains available. If an older result has already expired and no ticket was saved, new assistant answers may be unavailable; existing local answers remain readable.

Questions and answers are saved on your device for offline reading. The service also stores encrypted question/answer records linked to your installation and scan, to recover answers, enforce the ten-answer limit and return an identical repeated question without another model call. It stores a keyed question fingerprint for matching, rather than a plaintext question index. Saved answers do not require an active subscription to read; new answers for an existing completed scan remain available within its remaining allowance after subscription expiry. Network service availability and anti-abuse rate limits still apply.

Purchases and installation identifiers

Apple handles App Store payments. RevenueCat receives the app’s installation-linked user ID and purchase information to validate subscriptions, restore purchases, provide subscription access and support purchase analytics in its dashboard. The backend checks current subscription status and authenticated purchase-event records before granting a scan allowance. Payment-card information is not sent to the app’s backend.

RevenueCat’s SDK also processes a device vendor identifier (IDFV) and technical information such as platform, locale and currency for subscription functionality and purchase analytics. IDFV is a device identifier and is separate from the advertising identifier (IDFA), which the app does not use. The app does not use PostHog or request contacts or precise/coarse location for these features. See RevenueCat’s app-privacy information.

Optional referral rewards and device verification

The optional invite program links an invitation code, the referring installation and a new installation’s completed onboarding. Three eligible new devices can earn the inviter one free scan, once per lifetime; no purchase is required from the invited people. Reward reservations and successful-scan usage are recorded separately from paid subscription allowances. Failed scans do not spend the reward.

Apple App Attest and DeviceCheck help verify a genuine app installation and prior device participation. The device sends an attestation or signed assertion and an opaque DeviceCheck token to our service. Our service checks the proof and sends the DeviceCheck token to Apple. These tokens and proofs are not sent to OpenAI. Raw DeviceCheck tokens are not saved in the application database or application logs; the device temporarily keeps a pending proof in its protected Keychain so an interrupted request can be retried.

The service retains the attestation public key, Apple attestation receipt, assertion counter, single-use challenge records, token/proof hashes and verification outcomes linked to the installation. Apple maintains the program’s device participation marker. Device participation can survive reinstalling the app or erasing the device. Device verification is used for referral eligibility and security, not advertising or cross-app tracking. If verification is unavailable, paid scans remain available. Contact support if a transferred device appears incorrectly ineligible; eligibility resets require review and are not automatic.

Security and operational records

The backend assigns an installation ID and stores a hash of its authentication token. The device keeps its token in Keychain. Scan-job records, consent version, subscription-period references, attempt counts and transaction-derived identifiers support authentication, billing reconciliation, fraud prevention and reliable recovery.

The app also enrolls a separate random installation-recovery credential while its connection is valid. The device keeps this credential in Keychain and the service stores only its hash. It is used only to rotate an expired or interrupted access credential, retaining the same installation and saved-scan ownership after a long period of inactivity. It cannot directly access scan APIs, does not reset allowances, and is rejected if the installation is revoked. Hashed recovery-request identifiers and candidate-token hashes prevent replaying an old recovery request to reinstate an old access token. If both installation credentials are lost, the app does not claim it can recover the old installation automatically.

IP addresses reach Cloudflare when the service is contacted. The application uses a keyed hash of the connecting IP and a short time window for registration and token-renewal rate limits; raw IP addresses are not stored in those application rate-limit records. Application error logs contain stable error codes and status values, not photo/profile payloads, bearer tokens or provider response text. Cloudflare may separately process network, security and operational information under its service policies. See Cloudflare’s privacy policy.

Retention

Cloudflare backup and platform-log retention have not been independently confirmed for every deployed service configuration. Deletion removes result material from the active application database; it does not promise immediate removal from provider logs, safety records, backups or copies already delivered outside that database. Apple, RevenueCat and OpenAI apply their own relevant retention policies.

Choices, deletion and support

AI sharing can be declined before submitting a scan or asking a new assistant question. Future sharing stops when no further scans or questions are submitted; declining a later request does not recall a prior provider request. Reading a saved local answer does not send it to OpenAI. Camera access, scan-sharing consent and assistant-sharing consent are separate choices.

Delete a scan using its menu in saved history. For a production scan, the app first requests durable server deletion, then removes the corresponding local history, photos, saved result material, context ticket and assistant history. The service deletes associated encrypted question/answer records and a deletion marker prevents a retained context ticket from starting new answers. If the device is offline or deletion cannot be confirmed, the deletion request remains pending for recovery. Deleting an already completed saved scan does not refund its allowance or cancel the Apple subscription.

For access, correction, deletion or other privacy requests, email ARKANAVENTERPRISES@GMAIL.COM. Include an installation or scan-job ID if available so the correct records can be located. Verification of control may be needed before information is released or changed. Support email includes the sender’s address, message and any attachments supplied; email correspondence is separate from automatic scan-retention timers.

Age and service scope

Glow Up Girlie is intended for people aged 13 and older. It is not intended for children under 13. Contact support if information from a child under 13 has been provided. For stated ages under 18, AI instructions require gentle, age-appropriate cosmetic guidance.

The service provides cosmetic styling suggestions, not medical care, diagnosis or a guarantee of appearance changes. Service providers may process information in countries other than the user’s country. Material changes to this notice will be reflected in its updated date; a changed AI-sharing scope requires updated in-app consent.

Apple Standard End User License Agreement · Support