개인정보처리방침

Privacy Policy

Effective date · 11 September 2026

Article 1 (Purpose)

Mo.Moment ("Operator") establishes this Privacy Policy under Article 30 of the Personal Information Protection Act of the Republic of Korea, so that data subjects can understand how personal information is processed and can raise complaints. Gizmory (the "Service") is a local-first archive for the history of electronic devices you have owned or used. This Policy applies to the app, gizmory.app, and account-linked features. Effective date: 11 September 2026.

Article 2 (Items processed and how they are collected)

The Operator processes only what is needed to run the Service. You can use Chronicle, Discover, Studio, and Insights without an account.

1. Records that stay on this device (with or without sign-in)
Device names, brands, years, purchase dates and prices, status, memos, life events, chronicle photos, tags and collections, story drafts, wishlist items, studio projects, and settings. By default these live only in on-device SQLite and app storage.

2. Information sent to a server only when you turn a feature on or run it
Pro cloud backup — by running a backup yourself from the My screen, or only if you turn on auto backup — sends a snapshot of your records (JSON). Chronicle photo bytes are not in the cloud snapshot. Auto backup is off by default. You create, keep, and restore a local backup yourself from the My screen. If you include photos, original device and story photos go into a ZIP bundle; data-only keeps JSON. The local backup file is not sent to a server.

3. Social login and community (only while signed in)
On Apple or Google sign-in: an email if provided, account identifier, display name, and profile image URL if provided. Ratings, one-line reviews, published device story bodies, story photos uploaded to our servers (story-photos) when you publish a wiki story, Device Dex correction or new-device requests, device registration stats (registration events used for aggregates), and content reports. Posting requires sign-in; reading public content can still generate connection logs.

4. Launch waitlist (web, only if you enter an email)
Email address.

5. Diagnostics (release builds with reporting enabled)
Error messages, stacks, performance traces, and app/OS/device technical information may be sent to Sentry. Screenshot and request-body collection are disabled, but this does not guarantee that errors never contain personal information.

6. Payments (if you buy a paid feature)
The Operator does not collect card numbers. Apple App Store, or Google Play handles checkout. RevenueCat processes purchase status, product identifiers, subscription entitlements, minimum receipt data needed for restoration, and an anonymous app user identifier generated by its SDK. If you sign in, it may be linked to your account identifier.

7. Reading photo metadata (EXIF) — opt-in
"Find past gadgets from photos" only runs after you enter the feature yourself and grant photo access. It then reads capture device info (make, model, capture date) left in your photos' EXIF data — only on this device — to suggest candidates. The photos themselves and the metadata read from them are never sent anywhere. Scan results are added to your device list only after you review a candidate and confirm it yourself.

8. In-app YouTube playback — optional
When you tap play, a privacy-enhanced YouTube player loads. Playback and interaction data, IP address, app, browser and device information, cookies or similar identifiers may be sent to Google/YouTube, and an approximate region may be inferred from the IP address. Ads may appear under YouTube policies.

How collected: your input; OS APIs after you grant permission; transfers you start (sign-in, backup, publish, pay, or play video); and logs created when the app crashes.

Article 3 (Purposes of processing)

The Operator does not use personal information for other purposes. If a purpose changes, a new consent or a statutory procedure under Article 18 of the Act will be followed.
1. Store, view, edit, export, and restore your chronicle
2. Cloud backup and continuing on another device, only when you turn it on
3. Community features for signed-in users (reviews, stories, Device Dex requests, reports)
4. Aggregate registration stats to improve the Device Dex (not to identify you)
5. Provide Pro and restore purchases
6. Launch or update notices if you joined the waitlist
7. Diagnostics and security
8. In-app YouTube playback that you choose to start
9. Legal duties and support replies

Article 4 (Retention periods)

Where retention is legally required, only the relevant records are retained separately and deleted when the period ends. Applicable Korean periods include 5 years for contracts, withdrawal, payments and supply; 3 years for consumer complaints and disputes; and 6 months for advertising records.

Local records remain until you delete them. Cloud snapshots remain until backup or account deletion; disabling auto backup does not delete existing copies.

Deleting an individual Lounge post or reply marks it deleted and hides it publicly; it is not immediate physical erasure of its server text. Turning push off or signing out disables the device token. There is currently no uniform automatic deletion period for tokens, delivery history, read records, reports or audit records. You may request deletion or suspension; necessary legal or rights-protection retention must be explained with its basis and scope.

Waitlist database records and operator mailbox copies, story-photo storage, diagnostics and backup copies require separate handling. Account deletion does not guarantee simultaneous erasure from every store. Retention questions and deletion requests: hello@gizmory.app.

Article 5 (Provision to third parties)

The Operator does not provide personal information to third parties, except:
1. Where you have consented in advance
2. Where a statute specially requires it or compliance is unavoidable
Gizmory does not operate its own advertising SDK. If you choose to play an in-app YouTube video, ads may appear in the YouTube player and playback data is processed under Google/YouTube policies.

Article 6 (Entrustment and overseas transfer)

The Operator entrusts the following work. Some processors are outside Korea. Contracts and oversight follow Articles 26 and 28-8 of the Act.

1. Supabase — authentication, community data, cloud backup snapshots, story-photos storage. Location: Sydney, Australia (ap-southeast-2)
2. Apple — Sign in with Apple, App Store in-app purchases
3. Google — Google sign-in, Google Play in-app purchases
4. RevenueCat — purchase and subscription status, paid entitlements, and purchase restoration
5. Sentry — error and performance diagnostics and technical information in enabled builds
6. Google/YouTube — in-app video playback you start, player interactions, and IP, app, browser and device information
7. Hosting and CDN such as Cloudflare — website and static assets

Transfers happen over encrypted connections when you use the feature (sign-in, backup, publish, pay, play video, or a crash). You may refuse under Article 8, but then sign-in, cloud backup, community, and paid checkout will not work. The default local chronicle stays on this device without entrustment.

Article 7 (Destruction)

Data should be destroyed without delay when its purpose or required retention ends, using methods that prevent recovery for electronic files and shredding or incineration for paper.

Reset records deletes local records; cloud-copy deletion is a separate option. Using Delete account executes removal of server account-linked data, but does not simultaneously erase the local chronicle, external search copies, separate photo-storage cleanup, retained reports/audits or mailbox copies. See Articles 4 and 13 and request outstanding-copy deletion at hello@gizmory.app.
Account deletion: https://gizmory.app/account-deletion

Article 8 (Your rights and how to exercise them)

You may at any time:
1. Request access, correction, deletion, or suspension of processing
2. Withdraw consent and delete your account
3. Turn off auto backup, reset local records, or delete individual devices and stories
Use in-app Settings or email hello@gizmory.app. A legal representative of a child under 14 may need to show documents required by law. The Operator will act without delay or explain why it cannot.

Article 9 (Safeguards)

Under Article 29 of the Act the Operator takes:
1. Administrative measures: least privilege, purpose limitation
2. Technical measures: HTTPS in transit, account-scoped access control, local-first design so default records are not uploaded
3. Physical measures: as provided by the cloud processor
You remain responsible for where you keep backup files and who holds the device. Regular backups are recommended.

Article 10 (Automatic collection)

The Gizmory app does not use advertising identifiers or tracking cookies for behavioural ads itself. If you tap an in-app YouTube video, its privacy-enhanced player loads and Google/YouTube may use cookies or similar technology and show ads. gizmory.app may use strictly necessary cookies or similar technology for delivery and security. It does not use its own advertising tracking cookies.

Article 11 (Children)

The Service is not directed at children under 14, and the Operator does not knowingly collect their personal information. If such information is found, it is destroyed without delay.

Article 12 (Public editorial — Gizmory Magazine)

Published issues of Gizmory Magazine in the Discover tab are public editorial content written and edited by Gizmory. They are not personal records and are not part of your account.

Article 13 (Personal information processed in the community)

1. Pseudonymous profile — Once you join the community, your public identifier (handle), display nickname, bio, and a system-generated avatar value are shown to other users and on the public web. Your email address and Apple/Google sign-in identifier are never made public.
2. Private-review story submissions — Story text and photos you submit through the private-review route are first held in an Operator-only private review store. A submission with any photo is moved to the public store, and shown, only after every photo in it is approved. A rejected or still-under-review submission is not published.
3. Photo metadata (EXIF) — When you pick a story photo, the app keeps only the copy the device re-encodes for you, and uploads that copy when you submit. Most capture metadata is stripped by that re-encoding, but byte-level removal is not guaranteed. Before upload, you are warned to check the photo yourself for serial numbers, receipts, addresses, or faces.
4. Consent records — The Operator stores whether and when you accepted the Community Guide, and your consent to public web exposure before you publish.
5. Report and block records — Report reasons, targets, handling history, and your block list are kept as operational evidence and are not shown to other users.
6. Scope of disclosure — An approved, published pseudonymous profile or story can be read at the app and at gizmory.app/community whether or not a viewer is signed in, and may be indexed by search engines once the Operator turns on web indexing.
7. On account deletion — Deleting your account removes your pseudonymous profile and the community content you posted (stories, reviews, comments, and more) without recovery. Report and moderation records are kept for operational purposes with some account references set to null. This does not mean the record is fully anonymized. Audit records are kept only for actions the Operator itself took; they may include the identifier of the Operator account that took the action and of the account the action targeted (for example, a membership change), and those identifiers may remain even after the account is deleted.

Article 14 (Privacy contact)

Privacy and complaints: Mo.Moment (Mo, Yoon Won)
Trade name Mo.Moment
Representative Mo, Yoon Won
Business registration no. 422-59-00756
Mail-order business report no. 2026-고양덕양구-1596호
Reporting authority Goyang City
Address #829, 63, Baekkkot-gil, Uijeongbu-si, Gyeonggi-do
Phone +82 10 5717 4082
Email hello@gizmory.app
Hosting service provider Supabase, Inc. and Cloudflare, Inc.
Account deletion: https://gizmory.app/account-deletion

Article 15 (Remedies)

You may also contact:
1. Personal Information Infringement Report Center (privacy.kisa.or.kr / 118)
2. Personal Information Dispute Mediation Committee (www.kopico.go.kr / 1833-6972)
3. Supreme Prosecutors' Office Cyber Investigation (www.spo.go.kr / 1301)
4. National Police Agency Cyber Bureau (ecrm.police.go.kr / 182)

Article 16 (Changes)

This Policy applies from 11 September 2026. If the law or the Service changes the text, the reason and effective date will be posted in the app or on the web. Material changes will be announced before they take effect.

Article 17 (Lounge and processing clarification)

Lounge processes account-linked profiles and avatars, posts/replies, categories, linked devices and usage years, private saves and blocks, reports and moderation, and notification creation/read times. Reaction records relate to other community content that offers reactions, not a Lounge reaction feature. Unlike pre-reviewed stories, Lounge content may publish immediately and may be readable without sign-in at the public stage.

Being signed in with Lounge reply push enabled and iOS notification permission granted enables processing of Apple APNs device tokens, environment, enabled status, delivery targets, attempts and results. Current pushes contain a generic new-reply notice and internal identifiers, not nicknames or reply text. In-app activity notices may remain when Lounge push is off. OS notification permission is not marketing consent.

Signed-in device-registration raw data (account, device and local-item IDs and acquisition year) can sync independently of cloud backup. Unlike public aggregates, raw records are account-linked. Daily visits for active community profiles support personal activity statistics. An estimated birth year calculated from a selected generation can be included in settings and backup; it is not age verification.

Enabled RevenueCat builds can process an anonymous SDK identifier before purchase. Where web Pro Stripe checkout is offered, account/product/transaction information is processed; consult that checkout for cancellation. Cloudflare supports website delivery and applicable operator notification emails. External code delivery networks and YouTube may process connection information. Supabase project storage is in Sydney, Australia (ap-southeast-2); this does not limit every vendor to that country.

Processor tasks differ from independent providers. Each processing activity needs an applicable basis, such as contract necessity, consent or a legal duty; not all analytics is contract-essential. Detailed overseas contracts, countries and periods, and bases for optional analytics and statistics require further confirmation. Contact hello@gizmory.app for information and rights requests.

Depending on residence and applicable legal thresholds, US residents may have access, correction, deletion, portability, sale/sharing/targeted-advertising opt-out, sensitive-data and appeal rights. We do not unfairly discriminate for exercising rights. We do not claim automatic GPC/DNT handling is implemented or categorically deny sale/sharing under US definitions including third-party player processing. Email requests are handled under applicable statutory deadlines and exceptions. Local export is not a copy of all server-held personal information.