Skin Journal Privacy Policy

Effective 3 September 2026

This policy explains how the Skin Journal iOS and Android app handles information when you use its photo journal, optional AI skin-analysis and subscription features.

Information handled by the app

• Photos, scanned products, food context and notes: journal entries are saved on your device. When you actively request skin analysis, product scanning or food scanning, the photo you choose is sent securely through the Skin Journal backend to OpenAI to provide that feature. When a product brand and name are visible but its ingredient label is not readable, OpenAI web search may look for the exact product's public ingredient page; the app saves the returned source link so you can review it because formulations can change. A requested skin analysis can also include detected product brands, names and ingredients, current and recent food names and major ingredients, your note and short summaries from recent entries. The AI may discuss cautious, non-medical diet-and-skin associations and tracking patterns, but does not use a single meal or photo to claim causation or prescribe dietary restriction.
• Optional Android analytics and advertising measurement: Google Analytics for Firebase and Meta App Events are disabled by default. If you explicitly allow them, the Android app sends app lifecycle or screen activity, fixed funnel events, app and device information, an app-instance or device identifier, the resettable Android Advertising ID when available, and limited Google Play subscription metadata such as product, offer type, price and currency. Google can derive coarse geography from a masked IP address; Meta receives network and install-attribution information when events are delivered. Skin Journal uses this information to understand feature use and attribute, measure and optimise campaigns that lead to installs and in-app actions. Google ad-personalisation signals, Meta advanced matching, and automatic Meta lifecycle and purchase logging remain disabled. No ads are served inside Skin Journal. The current iOS app and web build do not initialise or send Firebase Analytics or Meta App Events data.
• Your analytics choice: the Android app stores this choice on your device. You can decline without losing app features and can review or withdraw the choice from the Today screen. Withdrawing consent stops future collection by the app, subject to information already processed under Google Analytics and Meta retention settings.
• Analytics content exclusions: Skin Journal's Firebase and Meta events do not include photos, image paths, notes, skincare product or routine names, skin scores, confidence values, summaries or other AI results, AI-report text, raw error messages, purchase-verification tokens, transaction identifiers, or a Skin Journal user ID.
• Usage information: AI analysis and product or food scanning require an active Premium subscription or trial. To enforce the separate Premium daily limits, the backend stores the date, account tier, request count and a one-way hash derived from the verified store transaction.
• Subscription information: the app stores purchase-verification data in secure storage on your device and sends it to the backend. The backend uses Apple App Store or Google Play services to verify subscription status and does not store the raw verification credential in the usage database.
• AI safety reports: if you report an AI result as inaccurate or unsafe, the backend stores the report category, the text of that AI result and a one-way report-token hash. The photo and original product/note fields are not attached to the report, although generated result text can repeat details from the context you submitted.

How information is used

Information is used to provide features you request, save your journal locally, enforce the Premium daily limit, verify subscription or trial access, prevent misuse and maintain the service. If an Android user opts in to Analytics, the limited measurement information described above is also used to improve the app, understand its conversion funnel, and attribute installs and in-app actions to advertising campaigns through Google and Meta. Skin Journal does not sell personal information or serve advertising inside the app. Google ad-personalisation signals remain disabled; Meta events are used for the campaign measurement and optimisation described above. The current iOS app and web build do not use Firebase Analytics or Meta App Events.

Service providers

• OpenAI processes a photo and its accompanying routine context when you actively request product scanning, food scanning or Premium AI analysis. For an exact-product ingredient lookup, OpenAI can search public web pages using the detected brand and product name and return a source URL. Requests disable optional response storage. Under OpenAI's standard API data controls, abuse-monitoring logs are normally retained for up to 30 days, with longer retention possible where required by law or reasonably necessary for safety.
• Render hosts the Skin Journal backend and PostgreSQL usage database.
• Apple App Store or Google Play processes purchases and provides subscription verification for the store you use.
• Google Analytics for Firebase processes the optional Android measurement information described above on the developer's behalf. When the user has opted in, Google Play install-referrer and Google Ads integrations can use that information for campaign attribution and conversion measurement. Skin Journal does not enable ad personalisation or send journal content in custom Analytics events.
• Meta receives the optional Android App Events described above to attribute Meta ads and measure or optimise campaign results. After opt-in, the app explicitly publishes an install event and fixed events such as journal activation, Premium offer view, checkout, trial or subscription. Meta can associate event and device information, including the available Advertising ID and install-referrer information, under Meta's Business Tools Terms and privacy policy. Skin Journal does not send contact details, journal content, purchase tokens or transaction identifiers to Meta and does not use Meta advanced matching.

Retention and deletion

The Skin Journal backend does not intentionally retain submitted photos, scanned product or food context, notes or AI results after completing a request, unless you choose to report an AI result. AI safety reports and usage-limit records become eligible for deletion during scheduled cleanup after 90 days. You can delete individual journal entries from the Photos tab. Uninstalling the app removes its remaining locally stored journal data and its saved Analytics choice, subject to your device and backup settings. Google Analytics and Meta retain measurement information under their configured settings and applicable terms. Withdrawing Analytics consent stops future collection by the app but does not automatically delete information already processed by Google or Meta; contact the support address below for a privacy request.

Security and your choices

Data sent to the backend is encrypted in transit using HTTPS. You decide whether to select a photo, request a scan or analysis, or allow Android Analytics and advertising measurement. You can keep using the local photo journal without requesting AI analysis or allowing Analytics. Analytics storage and advertising measurement remain disabled until you opt in, and you can withdraw that choice from the Today screen. No method of storage or transmission can be guaranteed completely secure.

Health information

AI results are estimates for cosmetic routine tracking. They are not medical advice, a diagnosis or a substitute for advice from a qualified healthcare professional.

Children

Skin Journal is not directed to children under 13.

Contact

For privacy questions or deletion requests, email SkinJournalHelp@outlook.com. Because the app has no Skin Journal user accounts, include only the minimum information needed to handle your request.

Changes to this policy

This page may be updated when the app or its service providers change. The effective date above will be updated when material changes are made.