MiniMeLook is an iOS app that works on your device, with no accounts and no servers of its own. It keeps a record of your child's outfit photo for each day, together with that day's weather. This policy explains what personal information MiniMeLook processes — the items, purposes, retention, outsourcing, and cross-border transfers — and your rights.
The anonymous identifier is not an account identifier meant to learn who you are, but it can link multiple activities from the same installation. So we don't call it fully anonymous; instead, we describe exactly how it is processed below.
| Item | Details |
|---|---|
| Operator / Representative | Jin Taewoo (진태우), independent developer |
| Privacy Officer | Jin Taewoo (same as the operator) |
| Contact for inquiries and rights requests | agenticsmith.biz@gmail.com |
Inquiries and rights requests are accepted at the email above. A physical address will be added only where a separate legal obligation requires it.
The following information is processed and stored on your device for app features, and is never sent to PostHog, Google, Apple, or anyone else.
| Information | Purpose | Where it's kept |
|---|---|---|
| Photos you select from Photos or shoot with the camera | Cutting out your child into a sticker | Processed on the device; the original is not copied into the app. Only the resulting sticker is kept. |
| On-device image analysis results (person-region detection) | Creating stickers; picking your child in a photo with several people | Used only during processing. |
| Sticker images | Showing the weather calendar, day details, widgets, notifications, and posters | App storage. Removed when you delete the record or the app. |
| Record date and capture time | Showing the weather calendar | Stored on the device. For photos added from your library, the capture time is not read. |
| District code and that day's weather | Showing weather per record; collections of outfits from similar weather | Stored on the device. Precise coordinates are not stored. |
| Neighborhood you chose manually | Basis for weather lookups when location permission is not allowed | Stored on the device. |
| How it felt, chosen on the day details screen (cold / just right / hot) | Showing the record | Stored on the device. The chosen value may also be used in the analytics described in §3.2. |
| Widget data (recent sticker, weather summary, neighborhood) | Home Screen and Lock Screen widgets | On-device storage shared by the app and its widgets (App Group). |
| Image attached to the evening notification | Showing outfits from similar weather in the notification | A local notification scheduled on the device; its content and attached image never pass through an external server. |
| Finished poster images | Saving to your library | Saved to the Photos app only when you ask to save and grant permission. |
Photos show the faces of your child and family, so we treat them as especially sensitive. Photos and their analysis results are processed only on the device as described above, and records keep only a district code so that your child's photos are never stored alongside a precise location. MiniMeLook is an app used by parents and guardians; the operator does not receive or store children's personal information such as photos, names, or dates of birth.
If device backup (such as iCloud Backup) is turned on, iOS may include the on-device information above in your backup. Backups are managed in your Apple Account, and the operator has no access to them.
In release versions that include product analytics, the following categories of information are sent to PostHog.
| Category | Examples | Purpose |
|---|---|---|
| Install and session identifiers | Anonymous identifier PostHog stores on the device; session identifier | Counting repeat use and use per session |
| Flow identifiers | Random identifiers created fresh for each capture and save | Linking a single capture or save flow and preventing duplicates |
| Usage events | Opening the app, taking or adding a photo, saving a record, viewing tomorrow's outfit prep, saving a poster | Understanding whether core features are used and where people drop off |
| Behavioral attributes | Entry point (app / widget / notification), photo source (camera / library), how it felt chosen on day details | Usability analysis per feature |
| Counts | Number of outfits shown in a collection; save attempt number | Usage-frequency analysis (no image content) |
| Technical outcomes | Success / failure / cancellation; predefined failure stage; processing and save duration | Diagnosing technical failures |
| App and device info | Event time; app version and build; production/development flag; OS name and version; general device type | Spotting issues by version; separating production and development data |
| Network and approximate location | IP address delivered to the server during transmission; country derived from that IP | The IP address is a technical part of any network connection. PostHog derives country-level location only from it; city, region, and coordinate-level location is turned off. We use it only to see usage by country and store no other location information |
"Duration" means elapsed processing and saving time, not the time a photo was taken or saved. Actual timestamps of those moments are not sent. Events are limited to predefined core-feature points within the categories above.
We use this data only to understand app usage, capture and save success rates, feature use, and save failures. It is not used for ad targeting and is not linked to your activity in other apps or websites.
The following information, which people tend to consider especially sensitive, is designed never to be included in analytics events or ad requests.
Product analytics are sent over an encrypted (HTTPS) connection through the PostHog SDK at specific feature points while you use the app. If you're offline, events are held briefly on the device and sent once the connection returns.
We do not use broad automatic capture of screens, buttons, or gestures, automatic app-lifecycle capture, session replay, surveys, or error/log collection — only predefined events are sent. If you don't want analytics, deleting the app stops any further transmission (the current version has no in-app setting to turn it off).
The flow for saving a poster to your library shows Google AdMob interstitial ads. To request and show ads, the Google Mobile Ads SDK processes the following information, which is sent to Google's ad infrastructure.
| Category | Examples | Purpose |
|---|---|---|
| Device and advertising identifiers | Advertising identifier (IDFA, if ATT is allowed) and other device signals | Ad requests, frequency capping, personalization (if allowed), and conversion measurement |
| Network and approximate location | IP address and approximate location derived from it | Processing ad requests and showing regionally relevant ads |
| Ad interactions and device info | Ad impressions and clicks; app, OS, and device type; SKAdNetwork attribution signals | Serving ads, measuring performance, and attribution |
If you allow ATT, personalized ads using the IDFA are shown; if not, non-personalized ads are shown. Either way, recording, poster saving, and every other feature work the same. This processing is governed by the Google Privacy Policy and How Google uses information from sites or apps that use its services. The app does not pass device location to the ad SDK, and the photos, stickers, records, location, and weather that §3.1 says stay on your device are never sent for advertising.
To attach weather to records and forecasts, we send the following to Apple Weather (WeatherKit).
| Category | Examples | Purpose |
|---|---|---|
| District representative coordinates | Your device's location (or the neighborhood you chose) converted on the device to a district, then that district's representative coordinates | Looking up today's and past days' weather and tomorrow's forecast |
| Lookup date | The date of a past day when you add a photo to it | Looking up that day's weather |
| Connection information | IP address and other information that is a technical part of the connection | Processing the request |
Your device's precise coordinates are never sent; everyone in the same district looks up weather with the same coordinates. Photos, stickers, and records are not sent with the request. If you don't allow location permission, only the representative coordinates of the neighborhood you chose are used. Apple states that location information sent to WeatherKit is used only to provide weather forecasts, is not associated with any personally identifiable information, and is never tracked between requests (developer.apple.com/weatherkit). If weather can't be retrieved, the photo is recorded without weather.
| Permission | When we ask | Purpose |
|---|---|---|
| Camera | When you choose to take a photo | Taking an outfit photo and creating a sticker |
| Photo selection (Photos picker) | When you choose to add or replace a photo | Passing only the photos you pick for processing |
| Add-only photo access | When you save a poster to your library | Adding the finished image to the Photos app |
| Location (while using the app) | When weather is first shown | Determining your district to look up weather (§3.6). Works with Precise Location turned off |
| Notifications | Right after you save your first record | Evening notification (outfits from days with weather like tomorrow's) |
Photo selection lets you choose exactly which photos to hand over, and add-only access is just for adding your results — it never reads your whole library. If you don't allow location, you can choose a neighborhood yourself and use the same features. If you don't allow notifications, everything else works the same. You can change any permission at any time in iOS Settings.
The ATT (App Tracking Transparency) prompt is shown once — not at launch, but after your first successful poster save, once you close the save-complete screen. Depending on network conditions, it may be deferred to a later save. If you allow it, personalized ads using the IDFA are shown; if you decline or don't respond, non-personalized ads are shown. Either way, every feature of the app works the same. You can change whether you allow tracking at any time in iOS Settings.
Users in the EEA/UK see a Google UMP (User Messaging Platform) consent form before the ATT prompt, asking for consent to process information for advertising. Your consent choice is stored on the device and reused on later launches; if you don't consent, you can use the app without personalized ads. You can review or withdraw your consent at any time from Ad Privacy Settings in the Settings screen. Product analytics (PostHog) are sent within the scope of §3.2 regardless of your ATT or UMP choices.
We use PostHog Cloud for product analytics. PostHog is a processor that stores and processes analytics data on the operator's instructions. This policy discloses that as outsourced processing and a cross-border transfer.
| Item | Details |
|---|---|
| Processor / Recipient | PostHog, Inc. |
| Purpose | Product usage analytics |
| Data transferred | The anonymous identifier, session and flow identifiers, usage events, technical outcomes, app/OS/network info, and approximate country described in §3.2 |
| When and how | Sent continuously over HTTPS after each event occurs |
| Storage country | United States (PostHog US region) |
| Transfer basis / subprocessors | As listed in PostHog's published subprocessor list; PostHog may process information in the United States and elsewhere to operate and support its service |
| Retention | 12 months from collection |
| Agreement | The data processing agreement (DPA) included in PostHog's standard terms |
We use Google AdMob for ads, and Google processes the ad-related information in §3.5 on its own infrastructure. This involves a cross-border transfer, as follows.
| Item | Details |
|---|---|
| Recipient | Google LLC (and its regional affiliates) |
| Purpose | Serving interstitial ads, measuring performance, and attribution |
| Data transferred | The device/advertising identifiers, IP and approximate location, and ad-interaction and device info described in §3.5 |
| Storage country | The United States and other countries where Google operates |
| Governing terms / retention | The Google Privacy Policy and Google's ad data retention policies |
| Consent | UMP consent in the EEA/UK; ATT for tracking on iOS (§4.2) |
We use Apple Weather (WeatherKit) to look up weather. This involves a cross-border transfer, as follows.
| Item | Details |
|---|---|
| Recipient | Apple Inc. |
| Purpose | Looking up weather and forecasts |
| Data transferred | The district representative coordinates, lookup date, and connection information described in §3.6 |
| When and how | Sent over HTTPS when weather is shown or attached to a record |
| Storage country | The United States and other countries where Apple operates |
| Governing terms / retention | The Apple Privacy Policy and the WeatherKit terms of use |
MiniMeLook does not sell product analytics (PostHog) data, use it for advertising, or share it with advertisers. Information sent to Google for ads is limited to what §3.5 and §5 describe.
| Information | Kept until | How it's deleted |
|---|---|---|
| Stickers, records, weather, neighborhood, and other on-device information | You delete the record or the app | The app's delete feature; deleting the app |
| Widget data | The app replaces it with newer information | Removed when the app is deleted |
| Image attached to the evening notification | Replaced when the next notification is scheduled | Removed when you turn notifications off or delete the app |
| Posters saved to your library | You delete them in the Photos app | You delete them in the Photos app |
| Analytics data waiting to be sent | Sent, or expired under the SDK's queue policy | Removed once sent or expired |
| PostHog analytics events | 12 months from collection | Retention period ends, or a deletion request is processed |
Where the law requires retention, information may be kept separately for the required period. Deleting the app does not delete images you saved to your library or moved to other apps, or your device backups.
Under applicable law, you can request access to, correction, deletion, or suspension of processing of your information, or object to processing.
MiniMeLook has no accounts, so it never links names or email addresses to the analytics identifier. That can make it hard to confirm that a given analytics record belongs to the person making a request; to identify it, you would need to provide your analytics identifier. If a record can't be identified safely, deletion at the end of the 12-month retention period stands in for it. We'll explain the handling time and how we'll notify you of the outcome in our reply.
Access to the PostHog project is managed by the operator.
If you need counseling, dispute mediation, or relief regarding a privacy violation, you can contact the organizations below (for users in the Republic of Korea).
If you disagree with a decision on a request for access, correction, deletion, or suspension of processing, or have suffered harm, you may file an administrative appeal under the Administrative Appeals Act.
MiniMeLook includes Google AdMob interstitial ads. They appear only in the flow for saving a poster to your library — once every certain number of saves, with a minimum interval between them — and never in the morning capture flow or the evening notification flow. If no ad is ready or it fails, your poster is saved without one. The information processed for ads and the related cross-border transfers are described in §3.5 and §5, and consent (ATT and UMP) in §4.2. If the ad format, the information processed, or the recipients change, we'll revise this policy under §11 before applying the change.
If we change this policy, we'll publish what changed and when it takes effect on this page.
| Item | Details |
|---|---|
| Where changes are published | This policy page (§12 revision history and updated effective date) |
| Where previous versions are kept | The repository's change history |