WATTAGAM Privacy Policy
Effective date: September 8, 2026
WATTAGAM (hereinafter the "Service") processes personal information so that users can safely store and share the scenes, locations, and trip participation information they record while traveling. The Service protects users' personal information in accordance with relevant laws and regulations, including the Personal Information Protection Act and the Act on the Protection and Use of Location Information.
In this document, "the Company" means the entity that provides the Service.
1. Purposes of Processing Personal Information
The Company processes personal information for the following purposes.
| Purpose | Description |
|---|---|
| Membership registration and login | Processing Google, Apple, and Kakao social login; identifying users; maintaining sessions; preventing fraudulent registration and restricting account creation per device |
| Profile management | Displaying and changing nicknames and profile photos |
| Trip record management | Creating, editing, and deleting trips; displaying trip lists; generating join codes; managing participants |
| Scene recording and playback | Storing short video scenes captured by users, thumbnails, and the capture location and time, and displaying them on the map, trip details, and movie exports |
| Sharing with trip participants | Allowing participants to view the scenes, routes, comments, likes, and profile information of the same trip |
| Location-based features | Storing scene capture locations, recording travel routes during a trip, setting the map center position, and displaying the map |
| Trip plans and place search | Selecting a destination from Apple place search results that the user has explicitly submitted, checking the preview, then encrypting and storing the selected destination, time, location, category, and memo and sharing them with participants of the same trip |
| End-to-end encryption features | Device registration, device approval, public keys, and storing and delivering encrypted Master Keys/Travel Keys |
| Customer support and error handling | Receiving bug reports, reviewing the app version and diagnostic logs selected by the user, and reproducing and improving errors |
| Service operation and security | API request records, preventing fraudulent use, verifying access permissions, and responding to outages |
| Compliance with legal obligations | Fulfilling retention obligations under relevant laws, responding to disputes, and responding to lawful requests from investigative agencies and others |
2. Personal Information Processed
The Company may process the following information in the course of the Service being used.
2.1 Member and Authentication Information
| Category | Items |
|---|---|
| Social login | Login provider (Google/Apple/Kakao), provider-specific user identifier (providerId), email, nickname or name |
| Account information | User ID, email, nickname, profile photo storage path, account status, registration date, modification date |
| Device identification information | Device UUID generated by the app (registeredDeviceId), platform, device display name, device status, public key fingerprint |
| Session information | Login token, session ID, recent login session information |
The actual mobile login methods of the Service are Google, Apple, and Kakao social login.
2.2 Trip and Participation Information
| Category | Items |
|---|---|
| Trip information | Trip ID, title, city, country, country code, start date, end date, representative trip latitude/longitude, public/private status, join code, creation date, modification date, deletion request time |
| Participant information | Trip ID, user ID, nickname, email, profile photo URL, whether the user is the owner, join date, whether the user holds the Travel Key |
A user who enters a trip join code becomes a participant of that trip and can view the scenes, participant profiles, comments, likes, and travel routes of the same trip.
2.3 Scene, Video, Photo, and Comment Information
| Category | Items |
|---|---|
| Scene metadata | Scene ID, trip ID, author ID, title, place name, capture latitude/longitude, playback length, capture time, creation time, video orientation, caption position, whether the caption has been composited |
| Videos and thumbnails | Video files captured by the user, thumbnail files, server storage object paths, temporary access URLs |
| Profile photo | Profile image selected and uploaded by the user |
| Comments/likes | Comment content, author ID, nickname, creation time, whether liked and the number of likes |
| Stickers/movie export | Stickers made from photos selected by the user on the device, sticker placement information, movie export results |
Newly uploaded scene videos and thumbnails are encrypted on the mobile device before being sent to the server. The server stores the encrypted files as they are and does not decrypt and store plaintext video files or plaintext thumbnail files. However, scene metadata such as the scene title, capture time, capture coordinates, and caption position may be stored in the server database in order to provide the Service's functions.
The Service currently handles trip scenes and exported movies without sound and does not collect audio when recording new scenes. If an audio recording feature is introduced, separate notice or consent will be obtained.
2.4 Location Information
| Category | Items |
|---|---|
| Scene capture location | Latitude/longitude, place name, and capture time at the time of scene capture |
| Trip location tracking | Trip ID, user ID, location point ID, recording time, server receipt time, encryption nonce, encrypted location payload, keyVersion |
| Trip plan location | Latitude/longitude selected by the user from Apple place search results or designated as the current map center when editing a plan. It is stored on the server only in encrypted form (see 2.5) |
| App startup map center | Current location (GPS); if that fails, the coordinates of a trip the user holds; if neither is available, the default coordinates (Seoul) |
Location tracking operates only when the user turns it on directly in the trip settings. Even if it is turned off, location history that has already been recorded is not automatically deleted, and it can be deleted through a separate deletion feature such as "Delete my location history" or through a customer support request.
Trip location tracking coordinates are stored in plaintext on the device and are encrypted at the time of upload, and the server stores only the encrypted payload rather than plaintext latitude/longitude. The latitude/longitude of a scene capture location is stored as scene metadata.
2.5 Trip Plan Information
When a user selects driving or walking as the mode of transport for a segment or requests a recalculation of the estimated time, the device passes the latitude/longitude of the departure and arrival places and the mode of transport to Apple MapKit to look up the current estimated travel time. The Company's servers do not store that request or the raw route response. The segment's mode of transport, travel time, calculation method, calculation time, and coordinate snapshot that the user has confirmed as complete are encrypted and stored together with the rest of the plan content. For flights, other modes, and manually entered times, an Apple estimated-time lookup is not required.
| Category | Items |
|---|---|
| Items stored on the server | Plan item ID, trip ID, author ID, sort order, encryption nonce, encrypted plan payload, keyVersion, creation/modification time, editing-in-progress indicator (editor ID and expiration time) |
| Items present only inside the encrypted payload | Destination title/place name, date/time, memo, location (latitude/longitude), place category selected by the user |
| Items processed only temporarily during search and preview | Search query, the map area visible on screen, address, website URL, POI category, and session result ID of Apple search results, place website metadata and images, Look Around snapshot |
The content of plan items is encrypted on the device with the trip key before being uploaded, and the server does not retain any plan content in plaintext, including the title, time, location, and category. All the server can know is the first row of the table above, that is, the sort order and "who is currently editing." The editing-in-progress indicator exists to prevent participants of the same trip from simultaneously editing the same item and overwriting each other's content, and it is automatically released after 2 minutes.
Place search is performed only when the user triggers the search button or the keyboard's search action, and it is not sent automatically while typing. The only information permanently stored from a selected search result is the place name, coordinates, and the category selected by the user. The address, website URL, Apple POI category and result ID, website HTML and images, and Look Around snapshot may be processed temporarily in device memory, but they are not permanently stored on the Company's servers, in the local DB, or in files.
Plans can be created and edited jointly by participants of the same trip. A user who has joined a trip can view and edit plan items created by other participants, and when the trip or account is deleted, the corresponding plan items are deleted together.
2.6 Customer Support and Diagnostic Information
| Category | Items |
|---|---|
| Bug report | Title, content, app version, reporter ID, creation time, processing status |
| Optionally attached diagnostic log | Sanitized app error log, if the user chooses to attach it |
| Server access log | Request method, request path, response status, processing time, remote IP address, request time |
The app's raw error log may include internal device file paths or text entered by the user. The diagnostic log attached to a bug report is transmitted after local file paths, URL queries, some caption text, and the like have been sanitized.
2.7 Information Stored Locally on the Device
For quick usability and offline recording, the Service stores the following information on the user's device.
- Login token: stored in secure storage
- Device UUID, language setting, and the most recently loaded profile/trip/participant cache: stored in the encrypted on-device DB
- Scene metadata, synchronization status, and video/thumbnail paths: stored in the encrypted on-device DB
- Original captured videos and thumbnails, and participant media decrypted after download: stored as permanent files in app-only storage
- Location tracking points: stored as plaintext coordinates in the encrypted on-device DB before upload, and kept locally even after upload for display in the app
- Trip plan items: place name, coordinates, user-selected category, date/time, and memo are stored in plaintext in the encrypted on-device DB so they can be viewed offline (they are encrypted and transmitted at the time of upload)
- Place search and preview information: the address, website, and Apple identification information of search results and the website/Look Around images are processed temporarily in device memory and are not permanently stored in the local DB or files
- Temporary/result files of stickers and movie exports: stored in app-only storage or in the photo album selected by the user
Local files and the local DB on the device may be deleted together when the user deletes the app or deletes app data through OS/device settings.
3. Methods of Collecting Personal Information
The Company collects personal information by the following methods.
- When the user logs in with a Google, Apple, or Kakao account
- When the user creates or edits a profile, trip, scene, comment, like, plan, or bug report
- When the user triggers the place search button or keyboard search and selects a search result (there is no automatic search while typing)
- When the user grants camera, photo library, or location permission and uses the corresponding feature
- When the user turns on location tracking directly
- When the app calls the server API or the server generates an access log
- When the current location is queried at app startup to determine the map center
4. Retention and Use Period of Personal Information
In principle, the Company destroys personal information without delay once the purpose of processing has been achieved. However, due to the nature of the Service, trip records the user has created are retained until the user deletes them or requests account deletion.
| Item | Retention period |
|---|---|
| Member account information | Upon withdrawal, the email, social login linkage information, and login sessions are destroyed (de-identified) immediately. Only the account's unique identifier (internal management number), in a state that can no longer identify an individual, is retained until a separate deletion request, in order to show the author indication that remains in content shared with other users, such as trips, comments, and likes |
| Profile information | Upon withdrawal, the nickname and profile photo are destroyed immediately. Otherwise, until the user edits or deletes them |
| Trip information | Until the user deletes the trip or the account deletion request is processed |
| Scene metadata and encrypted media | Until the user deletes the scene or trip or the account deletion request is processed |
| Comments and likes | Until the comment is deleted, the scene is deleted, the trip is deleted, or the account deletion request is processed |
| Location tracking information | Until the user requests deletion of location history or account deletion |
| Trip plan items | Until the user deletes the plan item or trip or the account deletion request is processed |
| Bug reports | Retained for 1 year after processing is completed and then destroyed. Retained for as long as necessary where needed for dispute response or reproduction verification |
| Server access logs | Retained for up to 1 year for security, outage response, and prevention of fraudulent use, and then destroyed |
| Information retained under laws and regulations | Retained for the period prescribed by the relevant laws and regulations |
Trip deletion is first marked as pending deletion so that the trip no longer appears in the app, and a background deletion job on the server then sequentially deletes the trip, scenes, participants, encryption keys, and GCS media. In the event of an outage or retries, actual completion of destruction may take longer.
When the in-app account withdrawal button is pressed, the following is processed.
- Immediately: The account status is changed to withdrawn, the email, nickname, profile photo, and social login linkage information are destroyed (de-identified), and login sessions on all devices are terminated immediately. The user may register again with the same email/social account.
- Afterward, a server background job (which may take longer in the event of an outage or retries) sequentially processes the following.
- A trip in which the user was the only participant is deleted in its entirety (including scenes, media, and encryption keys).
- A trip with other participants is not deleted, and ownership is automatically transferred to the other user who joined earliest, so that the trip is maintained. In this case, only the scenes created by the withdrawing user are deleted, and the records of the other participants remain as they are.
- For a trip the user only participated in (did not own), only the participation information is removed.
- The user's location tracking records, encryption keys (Travel Key/Master Key/device public key), and registered device information are deleted.
- The author indication that remains in content shared with other users (comments, likes, etc.) is not deleted and is displayed as "Withdrawn user," which can no longer identify an individual.
Inquiries about account deletion may also be received through an in-app bug report or the privacy inquiry email.
5. Provision of Personal Information to Third Parties
In principle, the Company does not provide users' personal information to third parties. However, it may be provided to the extent necessary in the following cases.
- When the user directly shares a trip join code and another user joins that trip, the trip records, scene metadata, participant profiles, comments, likes, and location routes are displayed to participants of the same trip.
- It may be provided where there is a basis in law or where there is a lawful request from an authorized agency such as an investigative agency or a court.
- Where the user has separately consented, it may be provided within the scope of that consent.
Trip videos and thumbnails are stored on the server in encrypted form. Participants of the same trip receive a temporary access URL from the server, download the ciphertext, and then decrypt and view it on their device with the encryption key granted to them.
6. Entrustment of Personal Information Processing and Use of External Services
To provide the Service, the Company may entrust personal information processing tasks or use external services and SDKs as follows.
6.1 Entrustment of Personal Information Processing
| Processor or external service | Purpose of use | Information processed |
|---|---|---|
| Google Cloud Storage | Storing encrypted scene videos/thumbnails and profile images | Encrypted media files, profile images, storage object paths |
6.2 External Services and SDKs
The following external services are used to provide Service functions such as login, map display, place search, and place preview. Each external service provider may process information in accordance with its own privacy policy.
| External service | Purpose of use | Information that may be processed |
|---|---|---|
| Google Sign-In / Google OAuth | Google login and token verification | Google ID token, Google user identifier, email, name |
| Apple Sign In | Apple login and token verification | Apple identity token, Apple user identifier, email, name (at first consent) |
| Kakao Login / Kakao API | Kakao login and token verification | Kakao access token, Kakao user identifier, email, nickname |
| Mapbox | Map display | Map SDK/API request information, device/app/network information, location-related information (in accordance with the map SDK's policy) |
| Apple Maps / MapKit | Apple map display, place search, Look Around preview | Search query, the map area visible on screen, coordinates of looked-up or selected places, device location if permitted, request time, device model, OS, input language, and app/device/network configuration and performance information (in accordance with Apple's policy) |
| Public website of the selected place | Looking up public metadata and images for the place's representative image | Request URL, request time, IP address, and ordinary access information such as the WATTAGAM/1.0 User-Agent |
| Apple App Store / Google Play | App distribution and updates | Information processed by each platform in connection with app installation and updates |
External service providers may process information in accordance with their own privacy policies. The Company will update this policy if the scope of use of external services changes.
Apple place search, Look Around requests, and place website requests are sent directly from the user's device to the corresponding external service. The Company's servers do not relay, log, or store search queries, the map area visible on screen, or place website requests. If a place website image cannot be loaded, it is replaced with a local scene, Look Around, or the category default display built into the app, and this does not affect saving the plan itself.
7. Overseas Transfer of Personal Information
Because the Service uses external services such as cloud storage, social login, and maps, personal information may be transferred overseas or processed overseas.
| Recipient | Country of transfer | Items transferred | Purpose of transfer | Date/time and method of transfer | Retention and use period |
|---|---|---|---|---|---|
| Google and Google Cloud | The United States and other countries where Google's infrastructure is located | Google login-related information, files stored in Google Cloud Storage and object metadata | Login verification, file storage and delivery | Transmitted over the network when the Service is used | Until the purpose of each service is achieved or until the retention period under contract/policy |
| Apple | The United States and other countries where Apple's infrastructure is located | Apple login-related information, map search queries, the map area visible on screen, coordinates of looked-up/selected places, device location if permitted, request time, device model/OS/language, and app/device/network configuration and performance information | Login verification, Apple map display, place search, Look Around preview | Transmitted over the network from the device when using Apple login or MapKit place features | Until the retention and use period under Apple's maps and privacy policies |
| Kakao | The Republic of Korea and other countries where Kakao's infrastructure is located | Kakao login-related information | Login verification | Transmitted over the network when using Kakao login | Until the retention period under Kakao's policy |
| Mapbox | The United States and other countries where Mapbox's infrastructure is located | Map SDK/API requests and map display-related information | Map display and provision of map services | Transmitted over the network when using map features | Until the retention period under Mapbox's policy |
| Operator of the public website of the selected place | Country where that website's infrastructure is located (varies by place) | Access information such as request URL, request time, IP address, and WATTAGAM/1.0 User-Agent | Looking up public metadata and images for the place's representative image | Sent directly from the device over HTTPS when displaying a preview of a place selected by the user | Until the retention and use period under that website operator's policy (the Company does not store it) |
Inquiries regarding overseas transfer may be made to the contact in Section 14. The specific processing country and storage location of each external service may change depending on that service's infrastructure and policies.
Because the public website of a place varies depending on the search result, it is difficult to individually specify in advance the recipient, the country, and the retention period of the relevant operator. Place search and plan saving work even if a representative image is not provided, and the Company does not permanently retain the URL, HTML, or image data received from that website on its servers, in the local DB, or in files.
8. Processing of Personal Location Information
The Company may process personal location information to provide location-based features.
8.1 Purposes of Use of Personal Location Information
- Displaying on the map the place where a scene was captured
- Recording the user's travel route during a trip and displaying it to trip participants
- Centering the map on the current or approximate location at app startup
- Displaying location records chronologically together with trip scenes
- Searching for places based on the map area the user is viewing and displaying the selected place on the map
8.2 Methods of Collecting Personal Location Information
- When location permission has been granted at the time of scene capture, the current location is queried.
- Location tracking operates only when the user turns it on directly in the trip settings and approves the operating system's "Always Allow" location permission.
- On Android, a Foreground Service and notification permission may be used for background location recording.
- On iOS, the location background mode may be used for background location recording.
- Place search is performed only when the user explicitly triggers the search. Even without app location permission, a search can be made based on the map area the user is viewing, and where location permission has been granted, that device location may be used for Apple Maps features.
8.3 Retention and Destruction of Personal Location Information
- Turning off location tracking is an action that stops future recording and does not automatically delete location history that has already been recorded.
- Users may request deletion of their own location history for each trip or use the deletion feature provided in the app.
- When an account deletion request is processed, location information is also deleted, except where retention is necessary for providing the Service or required by law.
- Trip location tracking coordinates uploaded to the server are stored encrypted, and the server does not store plaintext coordinates.
- Place search queries, the map area visible on screen, and permitted device location may be processed in accordance with Apple's policy, but are not stored on the Company's servers.
- Records confirming the collection, use, and provision of personal location information may be retained for at least 6 months in accordance with relevant laws and regulations.
8.4 Rights of Personal Location Information Subjects
Users may at any time withdraw consent to the collection and use of personal location information or request a temporary suspension. Users can turn off location tracking in the app or withdraw location permission in operating system settings, and may request access to, correction of, or deletion of location history that has already been stored.
8.5 Rights of Legal Representatives
A legal representative of a child under the age of 14, or of a personal location information subject who requires protection under law, may exercise the rights of the personal location information subject on their behalf in accordance with relevant laws and regulations.
9. User Rights and How to Exercise Them
Users may exercise the following rights at any time.
- Request to access personal information
- Request to correct personal information containing errors, etc.
- Request to delete personal information
- Request to suspend processing of personal information
- Request to withdraw consent to, or temporarily suspend, the collection and use of personal location information
- Request to access or be notified of records confirming the collection, use, and provision of personal location information
Requests to exercise rights may be made through the in-app profile/trip/location history deletion features, an in-app bug report, or the privacy inquiry email. The Company processes them in accordance with relevant laws and regulations after verifying identity.
10. Procedures and Methods for Destroying Personal Information
The Company destroys personal information whose retention period has expired or whose processing purpose has been achieved by the following methods.
- Electronic files: deleted or removed from the storage medium so that recovery is difficult
- Database records: deleted or de-identified
- GCS storage objects: deleting the object or the trip-level prefix
- Local data on the device: removed by deleting the app, deleting app data after logging out of the account, or using the in-app deletion feature
Information that must be retained under other laws and regulations is stored separately and destroyed when that period ends.
11. Measures to Ensure the Security of Personal Information
The Company applies the following measures to protect personal information.
- Server API access control based on authentication tokens
- Verification of trip owner/participant/scene author permissions
- Single active session management per device
- Password hash storage for administrator/email accounts that use passwords
- End-to-end encryption of media uploaded to the server and verification of the WE01 encryption container
- Key distribution structure based on per-trip Travel Keys, per-user Master Keys, and device public keys
- No retention of plaintext location tracking coordinates on the server
- Use of private GCS buckets and issuance of temporary signed URLs valid for about 1 hour
- SQLCipher encryption of the mobile local DB
- Storage of login tokens in the device's secure storage
- Sanitization of diagnostic logs for error reports
- Separation of server access logs and administrator permissions
12. Sensitive Information and Unique Identification Information
The Company does not request unique identification information under law, such as resident registration numbers, passport numbers, or driver's license numbers. Because trip records may contain the faces, locations, and private lives of the user or companions, users must take care not to infringe the rights of others.
13. Children Under the Age of 14
The Service is not intended for use by children under the age of 14 and does not knowingly collect personal information of children under the age of 14. If the Company confirms that a child's personal information has been collected without the consent of a legal representative, it will delete it without delay or take the necessary measures.
14. Contact for Personal Information and Location Information Inquiries
Inquiries, exercise of rights, and complaint handling relating to personal information and location information may be requested through the contacts below.
| Category | Details |
|---|---|
| Inquiry email | support@vloom.dev |
| In-app inquiry | Settings > Bug Report |
15. Remedies for Infringement of Rights
Users may seek consultation or dispute mediation regarding personal information infringement from the following agencies.
- Personal Information Infringement Report Center (KISA): privacy.kisa.or.kr / 118 (no area code)
- Personal Information Dispute Mediation Committee: www.kopico.go.kr / 1833-6972
- Supreme Prosecutors' Office Cyber Crime Investigation Division: www.spo.go.kr / 1301 (no area code)
- National Police Agency Cyber Bureau: ecrm.police.go.kr / 182 (no area code)
16. Changes to the Privacy Policy
If the Company changes this policy, it will give notice through the in-app legal documents screen or other means of announcement. For significant changes, notice will be given a reasonable period before they take effect, and separate consent will be obtained for changes that require consent under law.
17. Addendum
This Privacy Policy applies from September 7, 2026.