ProofKit - Your Unique Diary — Privacy Policy

This policy applies to ProofKit - Your Unique Diary (Korean store listing name: 푸킷 - 세상에 하나뿐인 일기장, package name: com.smoothie.proofkit, the “Service”), an app published on Google Play and the App Store by CreapySmoothie (registered business name: 무시무시한스무디).

We take your personal information seriously and comply with the Personal Information Protection Act of the Republic of Korea and other applicable law. This policy explains what personal information the Service collects and how it is used, stored and destroyed.

• Effective: 12 August 2026
• Last updated: 26 September 2026

Note on the 26 September 2026 update — features that had shipped in the app were not reflected in this policy. We corrected the following: added Facebook and LINE as sign-in methods (1-1); stated that app usage records (analytics) are collected and sent to Meta (1-3, 4, 5); and described how purchase tokens are handled now that the paid Pro subscription exists (1-6, 2, 3).

1. What we collect and how

1-1. Signing up and signing in (required)

You can sign in to the Service in the following ways.

When you sign in, a unique identifier (UID) is generated and stored so the Service can tell users apart internally.

We do not hold your password. For email sign-in, the password is kept by our authentication processor (Google LLC, Firebase Authentication) in a form that cannot be decrypted, and the Service operator cannot look up your password. Social sign-in does not collect a password at all.

1-2. Information you enter or register while using the Service

• Display name: the name shown on records and invite screens (changeable)
• Record content: titles, details and selected values (mileage, amount, category, status and so on) you leave in a space, and the time they were recorded
• Photos: images attached to records
• Space information: space name, description, template type, participant list and roles
• Enquiries: enquiry category and body

Records and photos are visible to the participants you invited to the same space. The whole point of the Service is that several people build one set of records together, so anyone who has joined a space can see all of that space's records and photos.

1-3. Information generated or collected automatically

• Push notification token: a per-device notification token, if you agreed to receive notifications
• Information sent with an enquiry: app version and operating system (used to reproduce the problem you reported)
• Advertising identifier (Android advertising ID) and device/network information: collected by our ad provider (Google AdMob) to serve the ads shown in the app and measure their performance. You can reset or delete the advertising ID in your device settings (Android: Settings → Privacy → Ads).
• App usage records (analytics): which screens you opened and what you did in the app (for example, creating a space or starting a subscription), collected to improve the Service and measure ad performance. What you wrote in a record, your photos and your display name are not included — only screen names and action names are sent. This goes to Google (Firebase Analytics), and some of those actions (sign-up, creating a space, starting a subscription and similar) are also sent to Meta Platforms so we can tell who installed after seeing an ad (see sections 4 and 5). On iOS, if you decline the app tracking prompt, the advertising identifier is not sent along with them (the action names themselves still are).

1-4. Location (optional features)

We collect location (GPS coordinates) only if you turn on one of the two features below. Both are off by default and must be turned on by you, per space.

• Automatic trip detection in vehicle spaces (beta): GPS coordinates are checked continuously on the device to judge, from changes in speed, when a trip starts and stops. Because this has to work even when the app is closed, it needs the “Allow all the time” location permission. A detected trip is only saved as a record once you approve it in a confirmation dialog; the coordinates themselves are not sent to our server, and only the start point, end point and parking location are included in the record.
• Workout route recording: when you record a workout that has a GPS route, such as a run, coordinates are collected only from when you press start until you press stop, to work out the route and distance. It only runs while the screen is open (the “while using the app” permission is enough) and collection stops when you leave the app.

1-5. Health data (optional feature, beta)

Only if you turn on health app integration in a diet/weight space or a workout space do we exchange data with Health Connect on Android or the Health app on iPhone, as follows. It is off by default and must be turned on per space.

• What we read: body weight only. It is used solely to estimate calories burned during a workout, and the Service does not separately store your weight.
• What we write: weight recorded in a diet space; workout type, duration, distance and estimated calories burned recorded in a workout space; and routes recorded by GPS (section 1-4).
• We do not import from the health app automatically. We may find and show workouts a watch or another app already left in the health app when you open a room, but they are only recorded in the Service if you tap “Add” yourself.

Data exchanged this way is stored in Health Connect (Android) or the Health app (iOS) on your device, and any later handling follows the policies of each platform provider (Google, Apple). The Service operator does not separately collect or store this data on a server.

1-6. What we do not collect

• We do not extract metadata such as capture location from photos. Photos are re-saved at a maximum of 2,048px on the long edge before upload, and the original capture information is not preserved in that process.
• We do not access your contacts, call logs or text messages.
• We do not collect payment method details such as card numbers. Payment for the paid Pro subscription happens in Google Play or the App Store; the Service never sees or stores your payment method. What the Service receives is only the purchase token issued by the store, the product ID and the subscription expiry time, used solely to confirm who is a paid user (see the retention period in section 3).

2. Why we use it

• Identifying members and keeping them signed in
• Providing core features such as creating, joining and sharing spaces
• Sending notifications about new records to participants of the same space
• (Only where turned on) automatic vehicle trip detection, workout route recording, and syncing weight and workout records with a health app
• Responding to enquiries and improving the Service
• Preventing misuse and keeping the Service stable
• Confirming entitlement to the paid Pro subscription and handling renewal and expiry
• Serving in-app ads and measuring ad performance
• Analysing usage in order to improve the Service

We do not use collected personal information for any purpose beyond those above, and we do not sell it to third parties.

The records, photos and display names you leave in a space are not used for advertising and are not passed to ad providers. What ad providers receive is the advertising identifier and device/network information from section 1-3, plus the name of the action (for example, “space created”) — not what you wrote in that record.

3. How long we keep it

As a rule, we destroy information without delay once the purpose of use is achieved.

How information is destroyed

• Deleting a space also deletes that space's records, participant information and attached photos. This cannot be undone.
• Leaving a space means you can no longer see it, but records you already left stay in the space and are not deleted. The records were built up by several people, so deleting them because one person left would damage the other participants' records. If you want your own records gone as well, ask the space owner to delete the space — or delete it yourself if you are the owner.

4. Providing personal information to third parties

The Service does not provide your personal information to third parties except as set out below.

• Otherwise, where you have consented in advance
• Where an investigative authority or similar makes a lawful request under applicable law

How AdMob handles personal information is set out at https://policies.google.com/technologies/partner-sites, and how Meta handles it at https://www.facebook.com/privacy/policy.

Other participants in the same space seeing your records, photos and display name is not provision to a third party — it is the Service working as intended (see 1-2).

5. Processing entrusted to others, and transfer abroad

To run the Service reliably we entrust the processing of personal information as follows, and personal information is accordingly transferred outside the Republic of Korea.

• Items transferred: the items collected under section 1 of this policy
• When and how: transmitted over the network at the time the Service is used
• Retention/use period: the same as the periods in section 3

The Service's data is stored in the Google Cloud United States region (us-central1).

You may refuse transfer abroad, but if you do you cannot use the core features of the Service (account sign-in, storing and sharing records, notifications).

6. Your rights and how to exercise them

You can exercise the following rights at any time.

What is deleted when you delete your account

The following are deleted immediately and irreversibly.

• Account information (including linked sign-in information)
• Spaces you created and all records and photos in them — other users who were participating in those spaces will no longer be able to see them either.
• Enquiries you sent
• Push notification token

However, records you left in spaces created by others are not deleted. They were built up by several people together, so deleting them because one person left would damage the other participants' records (the same reasoning as “leaving a space” in section 3). If you want those records gone too, ask that space's owner to delete them before you delete your account.

7. Security measures

• Access control: server security rules restrict users to the data of spaces they have joined.
• Encryption in transit: all communication between the app and the server is encrypted (HTTPS).
• Minimal collection: we collect only the minimum needed to provide the Service.
• No direct password storage: passwords for email sign-in are kept by our authentication processor (Firebase Authentication) in a form that cannot be decrypted; the Service does not separately store or look up passwords.

8. Children under 14

The Service is not directed at children under 14 and does not knowingly collect their personal information. If we learn that we have collected the personal information of a child under 14, we destroy it without delay.

9. Privacy officer and contact

Please contact us below with any questions, complaints or requests for remedy regarding the handling of personal information.

• Privacy officer: 황세건 (Segeon Hwang)
• Email: segun408@gmail.com
• In-app: App → My Page → Contact us

If you need to report or get advice about a privacy infringement, you can contact the following Korean authorities.

• Korea Internet & Security Agency, Privacy Infringement Report Centre (privacy.kisa.or.kr / 118)
• Personal Information Dispute Mediation Committee (kopico.go.kr / 1833-6972)
• Supreme Prosecutors' Office, Cyber Investigation Division (spo.go.kr / 1301)
• Korean National Police Agency, Cyber Bureau (ecrm.police.go.kr / 182)

10. Changes to this policy

If this policy changes, we will give notice of the change in advance through an in-app announcement or this page. Changes that materially affect your rights will be announced at least 30 days beforehand.