VibeForge Privacy Policy
Unified notice and ONE TAKE section published: October 18, 2026. Language versions added: October 18, 2026. The substance, effective dates, and existing public URLs of the AlertCoin Native and AI photo cleaner policies remain unchanged.
This page brings together privacy information for VibeForge apps. Each app-specific section applies only to that app. One app’s advertising or analytics settings, retention periods, service providers, target age, or legal basis do not automatically apply to another app.
- Operator and contact
- AlertCoin Native (musun129)
- AI photo cleaner · Existing English policy URL
- ONE TAKE — pre-launch notice
Operator and contact
- Operator: VibeForge
- Data Protection Officer: Seyun Ahn
- Privacy and support enquiries: vibeforgesoft@gmail.com
You may contact this email address to request access, correction, deletion, or suspension of the processing of your personal data. Please identify the app and describe your request. Do not send personal videos, photos, identification documents, or authentication information that is not needed for your request. What we can do may depend on our ability to verify the requester and identify the relevant records, as well as legal retention obligations. We will explain the outcome or any limitations. Email addresses, message content, and attachments you send directly are used to handle your enquiry. See each app’s section for its specific rights, retention, and deletion provisions.
Combining these notices does not change consent settings or actual data processing in any app. The original Korean AlertCoin policy is preserved in the Korean version of this page. The original English AI photo cleaner policy is preserved below and remains available at its existing URL. Translations do not change those policies. ONE TAKE’s section is a pre-launch notice, with unresolved operational matters identified separately.
AlertCoin Native (musun129) — existing policy, English translation
The following is an English translation of the existing Korean policy. Its substance and effective date remain unchanged. Analytics enabled by default, AdMob, price-alert servers, and their retention rules apply only to AlertCoin Native, not to AI photo cleaner or ONE TAKE.
AlertCoin Native Privacy Policy
Last updated: September 13, 2026
Effective date: September 13, 2026
1. Service and operator
VibeForge (Data Protection Officer: Seyun Ahn, referred to below as the “Operator”) processes information needed to provide cryptocurrency price information and target-price alerts.
AlertCoin Native has no sign-up or login feature and does not ask you to enter your name, phone number, email address, financial account, transaction history, or payment information. However, identifiers generated by the app and server may be linked to a particular device even though they do not directly identify you by name.
2. Information processed and purposes
| Information processed | Purpose |
|---|---|
| Device/user identifiers generated by the app and server, device-linking information, push notification identifiers | Device registration and authentication, distinguishing alerts for each device, and delivering push notifications |
| App version, operating system, language, time zone, notification permission status | Checking compatibility, reflecting device settings, and troubleshooting |
| Exchange, cryptocurrency, target price, alert conditions, enabled status, sound/vibration settings | Creating price alerts, evaluating conditions, and displaying alerts |
| Current/target prices, alert status, delivery/retry/acknowledgement times, error types | Delivering alerts, checking missed alerts, and troubleshooting |
| Cryptocurrency search terms | Providing search results. Used only while processing the search request and not stored in the cryptocurrency database. |
| IP address, request time/path/status, and error logs | Service security, abuse prevention, and incident analysis |
| Approximate location inferred from IP address, app/ad interactions, diagnostics, advertising and device identifiers | Ad delivery, measurement and analysis, and fraud prevention |
| When analytics sharing is enabled: per-installation analytics identifiers, app/device information, automatic events such as app launches, screen views and engagement time, and approximate location inferred from IP address | Analysing user numbers and app usage and improving the service |
3. External services and international processing
The Operator entrusts necessary processing to Google Firebase, Supabase, and Oracle Cloud Infrastructure to provide the service. International outsourced processing and storage needed for essential services such as price alerts and security are disclosed in this policy under Article 28-8(1)(3) of the Korean Personal Information Protection Act, as necessary for the performance of the service contract. Information is transmitted over encrypted connections when the app or server is used.
International service providers, countries, and retention details
| Recipient | Information processed and purpose | Processing countries | Retention |
|---|---|---|---|
| Google LLC | Installation/device identifiers and security signals, push identifiers and notification content, for app security, configuration delivery, and push notifications | May be processed on Google servers worldwide; not restricted to a specific country. | For the period needed to provide the service and under Google’s retention policy. |
| Supabase Pte. Ltd. | Storage of device/user identifiers, device-linking information, alert settings, and alert history | The operational database is in Tokyo, Japan. During support, Supabase in Singapore and its subprocessors may process some information in other countries. | The retention/deletion rules below apply. After contract termination, the 30-day cleanup period specified in the Supabase contract applies. |
| Oracle Corporation | Server operation to process app/server requests, device/alert information, and service request/error logs | Tokyo, Japan. Oracle personnel in other countries may carry out limited processing during service support. | Operational logs: up to 30 days. Backups that may include those logs: up to 28 days. |
If you do not want international outsourced processing, you may stop using the app or stop allowing notification permission. This may prevent you from using all or part of the price lookup or alert features. Processing locations and retention rules may change with providers’ infrastructure and policies.
For providers’ privacy enquiries, use Google’s privacy contact, privacy@supabase.com, or Oracle’s Korean contact privacy_kr_grp@oracle.com.
App usage analytics
Versions offering analytics sharing collect basic usage analytics through Google Analytics for Firebase, without a separate analytics consent pop-up at startup. Analytics sharing is enabled by default and can be disabled in Settings. A previous choice to disable analytics sharing is retained. Google LLC may process per-installation analytics identifiers, app version/device/operating system information, app launches, basic screen views, engagement time, automatic events associated with notifications and ads, and approximate location inferred from IP address. This is optional processing to understand user numbers and usage and improve the app.
When you use the app with analytics sharing enabled, information is transmitted over encrypted connections to Google servers and may be processed worldwide, including in the United States. Processing is not limited to a particular country. Detailed-data retention follows section 5 below. Google’s processing is governed by the Google Privacy Policy and Analytics data protection information.
Analytics advertising ID collection, ad personalization, and optional account data sharing are disabled. The Operator does not send alert target prices, search terms, push tokens, or authentication tokens as Analytics user identifiers or custom information. These settings do not stop all processing by the separate AdMob advertising service.
Advertising
The app uses Google AdMob to provide ads. AdMob processing follows the Google Privacy Policy.
External APIs for current prices
When you look up a current price, the selected market information and the IP address needed for the network connection are sent directly over an encrypted connection to the Upbit or Bithumb API. App device identifiers and push notification identifiers are not sent. Exact retention periods follow each exchange’s policy.
4. Required processing and optional features
Device registration, device-linking information, price-alert settings, and push notification identifiers are needed to provide price alerts. Without notification permission, you cannot receive system notifications, but some screens remain usable.
The app currently includes ads, so information related to ad delivery may be processed automatically.
You can disable app usage analytics sharing in Settings. Price lookup and alerts remain available. Turning off App usage analytics sharing stops new Analytics collection. Records already transmitted are not immediately deleted.
5. Retention and deletion
| Data | Retention/deletion rules |
|---|---|
| Detailed Analytics user/event data | Retained in Google Analytics for 14 months. New activity restarts the user identifier’s retention period. This limit does not apply to standard aggregated reports. |
| Alert history and delivery records | Deleted progressively after 90 days from creation. |
| Device/alert information deleted by the user | Deleted progressively after 30 days from the deletion action, if no need remains to protect other records. |
| Long-unused devices and linked alerts | Deletion begins after 180 days from the last registration/update. |
| Invalid or outdated push notification identifiers | Removed progressively when confirmed invalid. |
| Cryptocurrency search terms | Used only during search requests and not stored in the cryptocurrency database. Search terms that may appear in operational logs are masked. |
| Service request/error logs | Retained for up to 30 days. |
| Backups that may contain server settings and operational logs | Retained for up to 28 days. The operational database is not included in these backups. |
Expired electronic records are securely deleted so that they cannot be recovered, or automatically deleted upon expiry. Deletion may be delayed to the extent necessary to protect related records or meet legal retention requirements.
Copies maintained by external providers for service operation are subject to their contracts and policies. Deleting information in the app does not guarantee immediate deletion of all external copies.
6. Resetting notification connections and uninstalling
Reset notifications and connections in Settings disables the current device’s server alerts, resets push notification identifiers and device links, and registers the same device again. It is not an account deletion feature and does not immediately and completely delete past alert history, operational records, or information processed by external services.
Uninstalling removes locally stored app data according to Android’s uninstall procedure. Information already sent to servers or external services follows the retention/deletion rules above.
Resetting notifications and connections does not disable Analytics sharing or delete Google Analytics records. Analytics sharing can be disabled separately in the setting described above.
7. Your rights and requests
You or your legal representative may request access, correction/deletion, or suspension of processing. After receiving your email, the Operator will verify your identity or authority to act and whether the requested device and records can be linked to you, then reply with the outcome or reasons for any limitations. We may ask for the minimum additional information necessary for verification.
AlertCoin Native has no user account or email-based identity verification. Some requests may be difficult to fulfil if we cannot reliably establish the relationship between the requester and a particular device or server record. Requests may also be limited by legal retention requirements or the rights of others. We will explain such limitations.
- Email: vibeforgesoft@gmail.com
8. Security measures
The Operator applies necessary safeguards, including encryption in transit, protection of device-linking information, restricted access, minimisation of sensitive information in operational logs, and regular deletion. No transmission or storage method can guarantee absolute security.
9. Children
AlertCoin Native is offered on Google Play to people aged 18 or older and does not ask for names or dates of birth. If the target audience changes, safeguards required by applicable law and Google Play policy will be implemented first.
10. Data Protection Officer
- Operator: VibeForge
- Data Protection Officer: Seyun Ahn
- Email: vibeforgesoft@gmail.com
11. Policy changes
If processing changes, this policy and Google Play Data safety information will be updated together, with the effective date and last-updated date shown.
AI photo cleaner — existing English policy
The existing public URL and original English text below are preserved. Photo analysis, advertising, optional SDKs, and permissions described in this section apply only to AI photo cleaner.
Privacy Policy
Last updated: September 16, 2025
This policy explains what data our AI-based photo organization/optimization application (the “App”) processes, for what purposes, which third-party services it may use, required permissions, security measures, and your choices.
1. Personal Data Collection & Use
The App has no sign-up or login feature and does not collect or transmit directly identifying personal data such as your name, email address, or phone number to external servers.
Original photos (image data), EXIF location information, and facial feature data are not uploaded to any server.
2. Data Processed (On-Device Only)
The following data is generated/stored/used only on your device to provide photo classification and cleanup features.
| Category | Items | Description | External Transfer |
|---|---|---|---|
| Photo metadata | Internal ID, file size, captured (estimated) time, URI | From MediaStore queries | None |
| Hashes | Perceptual hash (pHash) | Duplicate detection (irreversible; cannot reconstruct originals) | None |
| Classification labels | DUPLICATE / BLUR / LARGE / DOCUMENT / UNKNOWN | On-device ML/rule results | None |
| App settings | Theme, scan options, ads/notifications toggles | User convenience | None |
| Scan progress | Processed count, progress | UI display / resume processing | None |
| (Optional) Usage events* | Feature usage patterns, screen views | Stability/quality improvement (when Firebase is enabled) | Pseudonymous to Firebase |
| (Optional) Advertising ID | Google Advertising ID | Personalized/non-personalized ads (AdMob) | Sent by AdMob SDK |
*If analytics collection is disabled in the App or OS settings, such data is not sent.
3. Purposes of Use
| Purpose | Details |
|---|---|
| Photo cleanup/optimization | Automatic grouping of duplicates, blurry shots, large files, and document candidates |
| Storage management | Help you identify items for deletion/cleanup |
| UX continuity | Store settings and latest scan state locally |
| (Optional) Quality improvement | Error/flow insights based on pseudonymous events |
| (Optional) Advertising | Show personalized or non-personalized ads based on your choice |
4. Third-Party Services & Disclosures
The App may use the services below. We do not provide directly identifying data.
| Service | Purpose | Possible Data Sent (examples) | Notes |
|---|---|---|---|
| Google AdMob | Advertising | Advertising ID, device/OS info, basic app usage stats | Personalized ads can be limited at device/App level |
| Google Play services / FCM (optional) | Notifications, stability | Push token (pseudonymous), basic device info | For important notices/feature updates |
| Firebase Analytics (optional) | Usage analytics | Event names and simple parameters (pseudonymous) | No name/email collection |
| Google ML Kit (on-device) | Blur/document etc. classification | None (on-device processing) | No external image upload |
Ad personalization: You can reset the Ad ID or limit ad personalization in device settings (e.g., Android), and an in-app “Disable personalized ads” toggle (if provided) takes precedence.
5. Retention & Deletion
| Item | Where stored | Deletion timing |
|---|---|---|
| Hashes/labels/metadata | App local DB (e.g., Room) | Upon app uninstall or when you run “Delete scan data” |
| App settings | Local SharedPreferences/DB | On app uninstall or settings reset |
| Progress cache | Temporary memory/DB | Cleaned after scan completion or app restart |
| (Optional) Analytics events | Firebase | Subject to Firebase retention policies (pseudonymous) |
You may remove local data via in-app options such as “Reset data” or “Delete scan results” (if provided).
6. App Permissions
| Permission | Purpose | Notes |
|---|---|---|
| READ_MEDIA_IMAGES (or READ_EXTERNAL_STORAGE, per SDK) | Read photo list/metadata | Required to scan targets |
| POST_NOTIFICATIONS (optional) | Progress/completion notifications | Shows scan status |
| FOREGROUND_SERVICE / DATA_SYNC | Reliable background scanning | Complies with platform policies |
| INTERNET | Ads/SDK connectivity | No upload of original photos |
| VIBRATE (optional) | Notification vibration | User experience |
Permissions are not used for any purpose other than stated above.
7. Security
- No server transmission of originals/EXIF/content
- pHash is irreversible and cannot be back-calculated
- All network communications use HTTPS
- Principle of least privilege and regular library updates
- No storage/transmission of sensitive originals minimizes exposure risk
8. Changes to This Policy
- Material changes will be disclosed in App release notes or settings
- Important updates may also be notified via in-app notices
- The latest version is always available at this URL
9. Contact
| Item | Details |
|---|---|
| Data Protection Officer | Seyun Ahn |
| vibeforgesoft@gmail.com | |
| Support channel | In-app “Send feedback” |
10. On-Device Machine Learning
- All classifications (duplicates/blur/document/large) are computed on the device
- No external upload of image originals, thumbnails, or EXIF location
- Hashes/labels are pseudonymous/irreversible and must not be used for re-identification
- No separate detection of child/sensitive imagery is performed
11. Ad Personalization & Opt-Out
| Control | Description |
|---|---|
| OS settings | Reset Advertising ID / limit ad personalization |
| In-app setting (if provided) | “Disable personalized ads” toggle |
| Network-level (advanced) | Use DNS/firewall according to your device policy |
| Opt-out effect | Personalized → contextual/general ads |
12. Your Choices
| Item | How to change |
|---|---|
| Delete scan data | Use “Delete scan results” in the App, or uninstall the App |
| Disable notifications | OS permission settings or in-app toggle |
| Limit ad personalization | Device settings and in-app toggle |
| Disable analytics | In-app setting (if provided) or OS-level limit |
13. Legal Basis (as applicable by region)
- Legitimate interests: storage optimization and provision of core functionality
- Consent: personalized advertising and optional usage analytics
- You may withdraw consent at any time (some features may be limited after withdrawal).
14. International Transfers
The App has no server upload feature for original photos or EXIF/face data, so no such data is transferred abroad. Firebase/AdMob SDKs may process pseudonymous logs on Google infrastructure subject to Google policies (including standard contractual clauses where applicable).
This policy may be updated due to feature or legal changes. Previous versions are available on request via email.
ONE TAKE — pre-launch privacy notice
Published: October 18, 2026. ONE TAKE section updated: October 24, 2026. App: ONE TAKE (com.vibeforge.onetake).
ONE TAKE is preparing for launch. This advance notice describes the features currently prepared and their data-processing boundaries.
The release candidate includes optional service-notice push messaging (FCM), off by default and enabled only after your consent and Android notification permission.
The analytics settings and limited QA observations confirmed so far, the enquiry handling procedure, and remaining processing details are set out below. Account-specific operational details and final release testing remain separate. This notice does not announce the app’s launch or the availability of all optional features.
ONE TAKE service and on-device data
ONE TAKE is an Android app for recording video, editing production information and effects, and saving/sharing finished videos. It has no sign-up/login, advertising, subscriptions, or in-app purchases. Payments for paid downloads are handled by Google Play.
| Data | Purpose and processing location | Retention/deletion |
|---|---|---|
| Camera video, microphone audio, recordings, and finished videos | Recording, editing, playback, and saving on the device | Subject to the app’s recording review and media deletion procedures. Videos in shared media storage may remain after uninstalling. |
| Brand/production titles, participant information, and editing state | Creation and recovery in app-private storage on the device | Editing state and settings are excluded from automatic backup. They may be lost on uninstall; recovery after reinstalling is not guaranteed. |
| Listing information, thumbnails, temporary processing data, and settings | On-device listing, editing, and playback | Subject to feature-specific cleanup and Android storage lifecycles. Copies made by the user must be managed separately. |
Production information may include names entered by the user. Videos, audio, thumbnails, and the original text of production information are not uploaded as ONE TAKE usage analytics or service-notice data. If you select another app through sharing, that app receives read access to the selected finished video. Subsequent processing follows the receiving service’s policy.
Camera and microphone permissions are needed to record video and audio. Denying them limits recording; you can change permissions in Android Settings. Uninstalling the app, deleting videos from shared storage, and deleting data sent to external services are separate actions.
Optional ONE TAKE usage analytics
Sharing app usage statistics is optional and off by default. If you choose to enable it, ONE TAKE uses Google Analytics for Firebase to understand app use and improve the app. You can still capture, edit, save and share videos without enabling statistics, and you can turn statistics off in Settings.
App-generated statistics cover screen types, completed creation steps, export results and predefined error categories. We do not send your videos, entered project text, media locations, project identifiers, push tokens or an app-assigned user ID as analytics events. The SDK may process an app-instance identifier, app and operating-system information, language and basic device information, app launches, sessions, engagement time and approximate location derived from IP addresses. Granular location and device data collection is set to off; this does not mean that all location, device or network information is excluded. Advertising ID collection, ad personalization, automatic screen reporting and notification-linked Analytics reporting are configured off.
Turning statistics off blocks new app-generated analytics events and requests that the SDK disable collection and storage. The app does not queue screen or creation events while statistics are off for later replay. However, when you turn statistics back on, the SDK engagement-time metric may include time spent with statistics off. Data already in transit or received by the server is not immediately cancelled or deleted. Turning statistics off and requesting deletion of earlier data are separate actions.
User-level and event-level data retention is set to two months, with reset on new activity off. Expired data follows Google’s monthly deletion process; this is not a promise that every copy is deleted exactly after 60 days. Standard aggregated reports are not subject to this retention setting. Google Signals is inactive, and ad personalization and optional account data sharing are off. Our operating policy is not to add Google Ads or BigQuery links.
Verification scope (October 23, 2026): the test and production property settings were saved and checked again after 24 hours. Event receipt and withdrawal were observed only in a separate QA environment; this is not evidence of production collection, deletion of every server copy, or validation of the final release build. The engagement-time limitation described above remains unresolved. Final account-specific processing details and release Data safety disclosure remain to be checked before launch.
Optional ONE TAKE updates and service notices
The release candidate connects to Firebase Cloud Messaging for optional updates and service notices. Notice consent is separate from analytics consent and is OFF by default. Both explicit in-app consent and Android notification/channel permission are required. Declining does not prevent video creation. Advertising, promotional, or personalised messages will not be sent.
When you enable notices, Google Firebase Cloud Messaging and Firebase Installations may use installation identifiers, registration information, app version, SDK/device information, and information needed for communication to deliver notices. The Operator will not maintain a separate token database. Notices will not contain personal video or production information.
Turning notices off first blocks local display, opening, and pending actions. Unsubscription and registration deletion may complete later, depending on connectivity and SDK processing. Communication or temporary registration may occur to clean up earlier operations. Completion deadlines are not guaranteed after uninstalling, prolonged inactivity, or while offline. Registration deletion does not mean deletion of the installation ID, Analytics data, or all server records.
The app retains only environment/notice IDs and expiry times for deduplication, up to 128 entries on the device. Notices have a maximum validity of 24 hours, and expired entries are cleaned up during the next processing operation. This delivery validity period is not the retention period for all Google records. Notice bodies and tokens are not kept in a permanent app archive.
ONE TAKE external processing, enquiries, and changes
When optional features operate, data sent to Google uses the relevant service’s encrypted communications and may be processed on Google infrastructure outside Korea. Processing and storage exclusively in Korea are not promised. See the Google Privacy Policy, Analytics data protection information, and Firebase privacy information.
AlertCoin’s Supabase/Oracle servers, price-alert retention/backup periods, and legal basis for international processing do not apply to ONE TAKE. Before operating ONE TAKE’s optional features, we will finalise and disclose recipients, processing roles, countries, purposes, timing/methods, retention periods, legal grounds, and how to refuse processing and the effects of refusal. Data and copies already processed by external services follow those services’ retention/deletion procedures; uninstalling does not immediately remove everything.
For enquiries and requests for access, correction, deletion, or suspension of processing, contact vibeforgesoft@gmail.com. As there are no accounts, it may be difficult to establish the relationship between a requester and particular SDK records. We will explain the outcome or limitations. Turning analytics OFF or deleting an FCM registration will not be presented as confirmation that all historical records have been deleted. For launch, ordinary enquiry emails and handling records will be retained for 90 days after the enquiry is resolved, then deleted, to support follow-up enquiries. Unnecessary video/photo attachments will be deleted promptly after review. Records subject to statutory retention obligations or needed for an ongoing dispute will be handled separately, limited to the necessary information and period. Any applicable statutory retention categories and periods will be identified and disclosed before launch. When we receive a request, we determine its scope and the minimum verification needed. We act on records we can identify, or explain the scope and reasons for any limitation. We cannot remotely access or delete videos or editing data stored on your device. When an ordinary enquiry is resolved, we record its deletion date and delete the related emails and handling records under our control according to the retention period stated above.
When you open ONE TAKE’s in-app help and contact option, the app prepares an editable email with the app version (including build number), Android version, manufacturer, and device model to help us understand your enquiry. You can change or remove these details before sending. They reach us only if you send the email using your email app. Device identifiers, serial numbers, advertising IDs, videos, photos, and logs are not automatically included or attached.
ONE TAKE audience age
ONE TAKE is intended for people aged 16 and over. It is not intended for children under 16. This is ONE TAKE’s own audience policy; AlertCoin’s age-18-and-over criterion does not apply. Google Play’s content rating is determined separately through its rating questionnaire and is not the same as this minimum audience age.
Setting a minimum audience age does not replace applicable protections for users under 18.
If actual features or processing change, this section, in-app notices, and Google Play Data safety information will be updated together.