Legal
ClosetMe Privacy Policy
Effective 2026-11-07
Jiwoong Lee (the "Operator") operates the ClosetMe app and the website closetme.app (the "Service") and publishes this policy under the Korean Personal Information Protection Act (PIPA) to protect users' personal information and handle related concerns promptly.
0. At a glance
- If you do not sign in, your wardrobe, outfit and calendar records and photos stay on this device and are never sent to the Operator's server.
- If you sign in, the original of your records is in your account on the Operator's server, with a copy on the device. Original clothing photos stay on the device even when you sign in.
- Only posts you publish to the community are visible to others. Item photos and body information are published only if you turn on each option when posting.
- We never receive or keep passwords or email addresses. We do not collect advertising identifiers or run personalized ads.
- Our servers and data are in the Republic of Korea (AWS Seoul region). Some processing, such as push delivery, is handled by overseas providers (Section 7).
- App-usage analytics is off by default and collected only with your opt-in consent.
1. Purposes
We process personal information only to: (1) create and manage accounts (identification, duplicate-account notice, keeping you signed in, account deletion); (2) provide the Service (storing account records and showing them on multiple devices, weather, product link information, notifications, data export); (3) run the community (profiles, posts, comments, follows, likes, saves, moderation, reports and blocks, and notifying members of actions taken on their posts and account restrictions); (4) operate safely (abuse prevention, incident response, disputes, legal obligations); (5) improve the Service through opt-in analytics; (6) run ads (per-ad impression and click totals and ad reports, without distinguishing users); (7) answer inquiries. If a purpose changes we take the steps required by PIPA Article 18, such as obtaining separate consent.
2. Information we process and how we collect it
2.1 Users who are not signed in
We keep no service records on our server. Using the following features sends the values needed to handle the request; wardrobe, outfit and calendar records and photos are never included.
| Feature | Sent | Server handling |
|---|---|---|
| Weather | Location coordinates | Used only to look up weather, not stored (Section 9) |
| Update check | App version | Latest-version notice |
| Browsing the community | Room, post and public profile query | Returns public content |
| Optional analytics | Items in 2.4 | Only with opt-in consent |
| Every request | IP address, time, request path, device/app information (User-Agent) | Access logs (Section 3) |
2.2 When you sign up (sign in)
| Item | How collected | Required |
|---|---|---|
| Google or Apple account identifier | From the token Google or Apple issues at sign-in | Required |
| Hash of your email address (the address itself is not stored) | Same | Required |
| Nickname | Generated automatically | Required |
We do not receive passwords. Our server only verifies the token signed by Google or Apple with that provider's public key and cannot access your Google or Apple password. Because we do not keep your email address, we cannot email you.
2.3 While a member uses the Service
| Item | Type | Note |
|---|---|---|
| Clothing details (category, color, brand, notes, product links), outfit, calendar, trip and recurring-plan records | When entered | |
| Clothing display photos (background removed, or a downscaled photo if removal failed), wear photos | When added | Wear photos may show your face and body |
| Body information: gender, height, shoulder/chest/waist/hip/thigh/arm indices, inseam, body shape, personal color | Optional | Not kept on the server if "Keep body data on this device" is on (Section 15) |
| Public profile: handle, bio | Optional | Visible to other users |
| Posts: outfit snapshot or wear photo, caption, community room, item photos and body information you choose to publish | When you post | Visible to other users |
| Comments, follows, likes, saves, reports (reason and description), blocks | When used | Comments are public |
| Post action records (type of action, reason category, time), account restriction reason category | When the Operator takes action or a post is hidden automatically after multiple reports | Told only to the member concerned; not shown to other users. The reason is also kept in audit records |
| Notification settings (types, times), app language | When set | |
| Notification token, installation identifier | Generated automatically | To send push notifications and not to signed-out devices |
| Sign-in session tokens | Generated automatically | |
| Record-transfer job records (list of moved records, a copy of account records before merging) | When guest records are moved | For undo and error recovery |
| Address of a product link preview request | When added | Not logged with your identifier or the full address |
| Audit records such as account creation and deletion | Generated automatically | |
| Access logs: account identifier, IP address (web server), hash of the IP address (app server), time, request path, app version, platform, device/app information | Generated automatically |
2.4 Optional app-usage analytics (opt-in)
Analytics is off by default and sent to our server only if you opt in under Settings > Privacy. Declining or withdrawing has no disadvantage. We collect fixed screen and button identifiers, action names and their success or failure, random session and action UUIDs, a random event UUID to detect duplicates, a pseudonymous identifier, platform, app version and time. Members' analytics records are linked to the account and are therefore not anonymous. We do not collect what you type, photos, location or advertising identifiers, and we use no third-party analytics SDK. Consent state, policy version and consent-verification values are kept separately, and consent secrets are never stored in plain form.
2.5 Inquiries
If you email us, we process your email address, name (if shown), the message and attachments.
2.6 What we do not collect
Passwords, email addresses, phone numbers, resident registration numbers or other unique identifiers, payment information, advertising identifiers (IDFA/AAID), contacts, or stored location coordinates.
3. Retention
| Information | Retention |
|---|---|
| Account information, account records, photos, body information, public profile | 30 days after account deletion |
| Posts and comments | Hidden immediately on deletion or account deletion; deleted from the server 30 days later |
| Follows, likes, saves, reports, blocks | Same as account information |
| Post action records, account restriction reason category | Same as the post and account information. Reasons kept in audit records follow the audit record period (1 year) |
| Server copies of deleted or replaced wear photos | Deleted by a cleanup job after 1 hour |
| Record-transfer job records | 90 days from creation; deleted with your data |
| Sign-in session tokens | Up to 60 days; revoked immediately on sign-out or account deletion |
| Notification token, installation identifier | Deactivated on sign-out or account deletion; deleted 30 days after account deletion |
| Optional analytics records and statistics based on them | 90 days; deleted immediately on withdrawal, account deletion or data deletion. Withdrawn consent controls are deleted within 90 days of withdrawal |
| Product link preview cache | 30 days after expiry |
| Audit records | 1 year; anonymized on account deletion |
| Access logs | 3 months (Protection of Communications Secrets Act, Article 15-2; Enforcement Decree, Article 41) |
| Server error logs | 3 months (kept in the same server logs as access logs) |
| Job processing logs (background job server) | 30 days |
| Inquiry emails | 1 year after the inquiry is resolved |
| Photos uploaded as "backup" by earlier app versions | Original clothing photo copies are deleted first when the new data-structure version ships; the rest after support for earlier versions ends, or earlier on data deletion, or 30 days after account deletion |
The 30-day grace period after account deletion is the minimum needed to respond to disputes and lawful requests from investigative authorities. During it, the same sign-in method cannot be used to sign up again; signing in after 30 days creates a new account.
4. Destruction
- Personal information is destroyed without delay when its retention period ends or its purpose is achieved.
- Electronic files are deleted so they cannot be recovered. Thirty days after account deletion, database records are deleted first and then stored photos; photo deletion is retried until it succeeds. We keep no personal information on paper.
- Information the law requires us to keep (such as access logs) is stored separately and destroyed when the period ends.
5. Provision to third parties
We do not provide or sell your personal information to third parties, except with your consent, where a law specifically requires it, or where unavoidable to meet a legal obligation (such as a lawful request from investigative authorities), and then only as the law allows. Posts and public profiles you publish yourself are visible to other users.
6. Processors
| Processor | Task | Location |
|---|---|---|
| Amazon Web Services, Inc. | Servers, database and photo storage; access log storage | Republic of Korea (Seoul region) |
| Amazon Web Services, Inc. | Delivery of public post images (Amazon CloudFront) | Global edge locations (Section 7) |
| Google LLC | Push delivery (Firebase Cloud Messaging); receiving inquiry email (Gmail) | United States and other countries (Section 7) |
| Apple Inc. | iPhone push delivery (Apple Push Notification service) | United States (Section 7) |
We use these processors under their published data processing terms, which prohibit processing beyond the entrusted task and require technical and organizational safeguards and limits on sub-processing. We will update this policy if processors or tasks change.
7. Overseas transfers
To perform our service agreement with you, we entrust or store personal information overseas as follows (PIPA Article 28-8(1)(iii)).
| Recipient (contact) | Country | Items | When and how | Purpose | Retention |
|---|---|---|---|---|---|
| Google LLC — Firebase Cloud Messaging (https://support.google.com/policies/contact/general_privacy_form) | U.S. and other countries with Google data centers | Notification token, app installation identifier, notification title and body | Over the network when the app prepares to receive notifications and each time a notification is sent to a member | Push delivery | Per Google's retention policy after delivery; registration removed on sign-out or account deletion |
| Apple Inc. — Apple Push Notification service (https://www.apple.com/legal/privacy/contact/) | U.S. | Device notification token, notification title and body | Over the network each time a notification is sent to an iPhone member | Push delivery | Per Apple's retention policy after delivery |
| Amazon Web Services, Inc. — Amazon CloudFront (https://aws.amazon.com/privacy/) | U.S., Japan and other edge locations | Public post images and item images you chose to publish | Cached temporarily at a nearby edge location when another user opens a public post | Fast delivery of public content | For the cache lifetime; no longer delivered once the original is deleted |
| Google LLC — Gmail (https://support.google.com/policies/contact/general_privacy_form) | U.S. and other countries with Google data centers | Sender email address, name, message and attachments | Over the network when you email us | Answering inquiries | 1 year after the inquiry is resolved |
| Norwegian Meteorological Institute (https://www.met.no/en/About-us/contact-us) | Norway | Coordinates converted to an approximately 1.2 km grid | Our server queries over HTTPS when weather is looked up | Weather lookup | Not kept by us; per the Institute's request-log policy |
Coordinates sent to the Norwegian Meteorological Institute are grid values sent without any account or device information and cannot identify you, but we list them because they come from your location.
On Android devices, the notification component (Firebase) may contact Google when the app is first launched to prepare for notifications, creating an installation identifier and a notification token. This token is not registered with our server before you sign in.
How to refuse and what happens
- Push notifications (Google, Apple): turning off notifications in device or app settings, or signing out, stops transfers for member notifications; you will not receive member notifications.
- Public post delivery (CloudFront): not posting, or deleting posts, stops it; you cannot use community publishing.
- Inquiry email (Gmail): not emailing us stops it; you can still exercise your rights directly in the app (export, deletion, account deletion).
- Weather (Norwegian Meteorological Institute): not granting location permission stops it; weather guidance will not be shown.
Google and Apple sign-in is authentication you perform directly with those companies; we only receive the result and do not transfer personal information overseas for it.
8. Where records and photos are kept
| Data | Not signed in | Signed in |
|---|---|---|
| Clothing details | Device only | Server (original) + device copy |
| Original clothing photos | Device only | Device only; never uploaded |
| Clothing display photos | Device only | Server (private) + device copy |
| Wear photos | Device only | Server (private) + device copy |
| Outfit, calendar, trip and recurring-plan records | Device only | Server (original) + device copy |
| Inspiration photos | Device only | Device only; never uploaded |
| Notification inbox | Device only | Device only; never uploaded |
| Body information | Device only | Server (original) + device copy; device only if "Keep body data on this device" is on |
| Ad view counts and hidden ads | Not applicable | Device only |
| Public profile, posts, comments | None | On the server and visible to other users |
| Follows, likes, saves, reports, blocks | None | On the server, linked to the account |
"Server (original) + device copy" means the server version is authoritative; the device copy lets you view records offline. The device keeps guest records and each account's records separately so they never mix.
Moving guest records to an account: when you sign in on a device with guest records, the app asks and moves them only if you choose "Move". If the account already has records for the same date, outfits, photos and photo tags are all kept, notes are joined, the account's rating, place and weather take priority, and clothing types and outfit categories with the same name are merged. Original clothing photos, inspiration photos and the inbox are not uploaded; they move within the device to the account's storage. Guest records on the device are deleted only after everything is confirmed on the server, and you can cancel and undo before the move finishes. A record-transfer job record is kept on the server for undo and recovery (Section 3).
9. Location
- Location is used only to look up the weather. Denying location permission affects only weather guidance.
- When you view the weather, the app sends the device's coordinates to our server. The server handles weather requests without account authentication, so the coordinates are not linked to your account, and looks up the weather from the Norwegian Meteorological Institute using coordinates converted to an approximately 1.2 km grid.
- The server does not log coordinates and uses only the grid values as cache keys. Location is not stored in your account.
- If we introduce a feature that needs to store coordinates, we will update this policy and ask for your consent first.
10. Photos
- Background removal runs on your device with a model bundled in the app; photos are not sent to our server or any external service for it.
- No photo is uploaded while you are not signed in.
- When you sign in, clothing display photos and wear photos are stored in private storage under a path for your account. Other users cannot access them, and the app downloads only your own photos through signed addresses valid for 1 hour.
- Original clothing photos are never uploaded. The display photo uploaded is the background-removed version made on the device or, if removal failed, a downscaled copy with metadata such as photo location (EXIF) removed.
- Wear photos are kept on the server while you are signed in. To remove one from the server, delete it; the server copy is deleted by a cleanup job after 1 hour.
- Outfit share links contain no photos, only categories, colors, layout, names and shop links.
- When you post to the community, the outfit snapshot or one wear photo you choose, your caption and the community room are sent to the server and published. Private account photos never become posts on their own.
- Private account photos are never shown to other users, are processed only for providing the Service, customer support and safe operation, and are not used to train machine-learning models.
11. Ads
- The Service shows ads that the Operator reviews and places directly, on the home screen and community feed, to signed-in members only.
- Ads are not chosen using your photos, wardrobe, outfits, calendar, body or location information, or app usage records. We do not run personalized ads, collect advertising identifiers (IDFA/AAID) or use third-party ad SDKs.
- When an ad is shown or tapped, the server only adds one to that ad's impression or click total. We do not store who saw or tapped which ad. To prevent abuse, requests are counted temporarily against the account identifier for at most one day.
- When you report an ad, only the reason is stored with the ad; the reporter's account is not stored.
- View counts that keep the same ad from appearing too often, and the list of hidden ads, are stored only on this device.
- Tapping an ad opens the advertiser's website in your browser, where the advertiser's privacy policy applies.
- We do not send promotional push notifications without your separate consent.
12. Cookies and similar technologies
- The app does not use cookies. The website uses no cookies to analyze behavior or for advertising; it uses cookies only to keep operators signed in to the admin console.
- We do not collect behavioral information for personalized advertising.
- Shops opened in the in-app browser may use their own cookies; the app does not read them, and they are governed by each shop's policy.
- The app records unexpected errors only on the device and never sends them off the device. File paths, addresses, identifiers and email fragments are removed before recording.
13. Your rights and how to exercise them
- You may ask us to let you access, correct or delete your personal information, to stop processing it, or to withdraw consent.
- In the app you can directly: export your data (Settings > Privacy; built on the device, with only missing photos downloaded from the server); delete your data (guest: all guest records and photos on the device and scheduled notifications, plus analytics withdrawal; member, online: analytics records and consent, wardrobe, outfit, calendar, body and transfer records deleted from the database immediately and then photos, while the account, public profile, posts and guest records remain); sign out (tokens revoked, device notifications removed, account records kept on the device); sign out and remove from this device; delete your account (immediately marked deleted, analytics deleted immediately, the rest 30 days later; guest records kept); keep body data on this device; withdraw analytics consent; turn off notifications; edit your public profile; delete posts and comments.
- For other requests, email the address in Section 19. We will act within 10 days of receipt and tell you the result, or the reason if the law allows us to limit access or suspension.
- You may make requests through a legal representative or an authorized agent, who must submit a power of attorney in the form set by the PIPC notice on processing methods.
- Because we do not keep email addresses, we may ask for the minimum information needed to confirm you own the account (for example, the handle shown on the app's account screen).
- Deleting your account does not make us ask Google or Apple to disconnect the app; you can remove ClosetMe from your Google or Apple account settings yourself.
- Device-only records (original clothing photos, inspiration photos, inbox) have no server copy and cannot be recovered once deleted.
14. Security measures
- Administrative: only the Operator handles personal information; the admin console is limited to authorized operators, and its activity (audit records) is kept for 1 year.
- Technical: encryption in transit (HTTPS); database encryption at rest; private photo storage with server-side encryption and 1-hour signed addresses; least-privilege access; a log redaction list (auth tokens, cookies, email hashes, latitude and longitude, body measurements, raw IP addresses in app-server logs) with tests that check it; blocking internal-network access when the server fetches external addresses; response checks that keep sensitive fields out of API responses.
- Physical: servers and data are protected by the physical security of AWS data centers.
15. Sensitive information and body information
- We do not collect sensitive information under PIPA Article 23 (ideology or beliefs, union or party membership, political views, health, sex life, genetic information, criminal records, biometric information, race or ethnicity) or unique identifiers.
- Body information (gender, height, body proportion indices, body shape, personal color) is optional input used for the silhouette preview that helps judge garment length and for comparing similar body types; we do not treat it as information about illness or health. Because it concerns the body, we protect it as if it were sensitive: it is never logged, detailed indices are never sent to other users, and it is stored with a post only if you turn on body information when posting, in which case other users see only the values needed for comparison, such as height and body shape.
- Turning on "Keep body data on this device" (Settings > Privacy) deletes the server copy and stores body data only on the device from then on; similar-body comparison in the feed turns off, and you will need to re-enter it on a new device.
- Wear photos and post photos may show your face, but we perform no technical processing, such as face recognition, to identify individuals. Information in photos or captions you publish may become visible to other users, so please check before posting. You can delete a post at any time.
16. Review of public posts
The Operator does not currently check public post images with any external image analysis service. Public posts are reviewed by the Operator directly when they are reported or when the Operator notices them, and may be hidden or deleted based on that review (Terms of Service, Article 12). If three different members report the same post, it is hidden automatically before the Operator reviews it, and the Operator then reviews it and restores it or keeps it hidden. If the Operator introduces an external image analysis service, it will first add that processor and any overseas transfer to this policy before using it. If you disagree with a review result, you can ask for another review at the address in Section 19.
17. Children under 14
- Children under 14 cannot create accounts. By agreeing on the sign-in screen to the Terms of Service, which include the 14-or-older condition, users confirm they are 14 or older.
- We do not knowingly collect personal information from children under 14 and will delete without delay any account or optional analytics record we learn belongs to a child under 14.
- Records of features used without signing in stay on the device.
18. Further use, pseudonymized information, and other items
We do not make further use or provision under PIPA Articles 15(3) and 17(4) and do not process pseudonymized information. We operate no video surveillance devices and are not required to designate a domestic representative.
19. Privacy officer and contact
| Privacy officer | Jiwoong Lee (Operator) |
|---|---|
| eziongbus@gmail.com | |
| Response time | Rights requests within 10 days of receipt |
The Operator has no separate department; the privacy officer handles privacy matters and complaints directly.
20. Remedies
For reports or consultation about privacy infringement, you may contact: Personal Information Dispute Mediation Committee (1833-6972, www.kopico.go.kr); Personal Information Infringement Report Center, KISA (118, privacy.kisa.or.kr); Supreme Prosecutors' Office (1301, www.spo.go.kr); Korean National Police Agency (182, ecrm.police.go.kr).
21. Changes to this policy
- This policy takes effect on November 7, 2026.
- We announce changes on the website and in the app from 7 days before they take effect, and important changes, such as new items collected or new overseas recipients, from 30 days before. Changes are recorded in the history below.
| Effective | Change |
|---|---|
| 2026-10-07 | First version |
| 2026-11-07 | Added notifying post actions and account restrictions to the purposes (Section 1), items (Section 2.3) and retention periods (Section 3), and automatic hiding after multiple reports to the review of public posts (Section 16) |