Photo processing

Loading and arranging photos, creating comparison images, and adding watermarks all happen on your device. Photos and comparison images are never uploaded to our servers or to third-party servers, and no AI image analysis or generation is used. Camera and photo access is used only to take, select, and save photos.

Purchases

GlowUp Camera uses Apple’s in-app purchases and the services of RevenueCat, Inc. for purchases, restores, and checks of access to Pro features. Information such as purchase history, entitlement status, and RevenueCat’s anonymous app user identifier is used to provide purchased features, verify purchases, and analyse purchase activity. Plans shown on the Pro screen are loaded from RevenueCat’s configuration. We do not receive payment details such as card numbers.

Ads

Free users can watch a Google AdMob rewarded ad to remove the watermark from one save per day. There are no interstitial ads. Google and its advertising partners may handle device or advertising identifiers, ad views and interactions, approximate region inferred from an IP address, and crash, performance, and diagnostic information. This information supports ad delivery, measurement, and service improvements. Some information may be associated with identifiers; it is not all anonymous statistics.

Tracking permission (iOS)

The advertising identifier (IDFA) is used only if you allow tracking. All features work if you decline. You can change this in Settings > Privacy & Security > Tracking.

Location

The app itself has no feature that obtains precise GPS location or requests location permission for that purpose. This does not mean that advertising services and their partners perform no location-related processing.

Scope of this supplement

This supplement applies only to GlowUp Camera. The general Aplista privacy policy continues to apply to retention, contact procedures for access, correction or deletion requests, and notices of changes.

Notes are stored on your device and in iCloud (an Apple service) and are not sent to our servers, except when you use “AI formatting”, as described below.

What is sent

Only the body of the note you asked to format (the title is not sent).

When

Only when you request formatting. If Settings > “AI formatting” > “Confirm before sending” is on, the text is sent only after you tap “Send and format” on the confirmation screen; nothing is sent if you tap “Cancel”.

Also sent

Along with the text, the app sends a Firebase ID token (containing your user ID) to verify the user, and a Firebase App Check token to verify that the request comes from the genuine app. Our server uses the user ID only to count free uses and to check purchases (RevenueCat). Only the note body and formatting instructions are sent to Gemini — not your user ID.

Where

Through our server (Google Cloud Run, Tokyo region asia-northeast1) to Google LLC’s generative AI “Gemini API” (model: gemini-2.5-flash-lite).

Purpose

Only to fix typos and tidy the text. It is not used for advertising or for training AI by us.

Storage by us

Our server does not store the text or the AI response. To manage free uses, only the usage count and timestamps are stored in Firebase (Cloud Firestore), linked to your Firebase Authentication user ID (an anonymous ID if you are not signed in). Server operation logs (Google Cloud Logging; the text is not logged) are kept for 30 days (default logs) and 400 days (logs required by Google).

Handling by Google

Google handles the content sent under the Gemini API terms. We use the Gemini API on the paid tier (a billing-enabled Google Cloud project), under which Google does not use submitted content to improve its products. See https://ai.google.dev/gemini-api/terms and https://policies.google.com/privacy for details.

Subscriptions

Purchases are processed by Apple, and we do not receive payment details. We use the services of RevenueCat, Inc. to manage purchases, and handle purchase history and entitlement status linked to the user ID above. https://www.revenuecat.com/privacy

Sighting posts (public)

You can post bear sightings anonymously without logging in. When you post, the following information is stored in Google Firebase (Cloud Firestore) and is visible to all users of the app.

• Location of the post (latitude and longitude of the place confirmed when posting; stored without rounding)
• Free-text description (if entered)
• Date and time of the post
• Anonymous ID (iOS: Apple’s identifierForVendor, kept in the device Keychain so the same ID is used after reinstalling; Android: the device’s ANDROID_ID and a Firebase anonymous authentication user ID)

The anonymous ID is not displayed on screen.

Photos cannot be posted. Do not include personal information such as names, addresses, or phone numbers in the description.

Retention

• User posts: deleted automatically 7 days after posting (deletion may take place slightly after that time). When the display limit is exceeded, older posts are also deleted first.
• Public information from official sources: kept without expiry and overwritten by newer information.
• Video news: kept for 30 days.
• Reports: kept without expiry (for review and record keeping).
• Notification data (see “Nearby notifications” below): currently kept without expiry. To request deletion, please contact support@aplista.net.

Reports

In the iOS app, you can report a post with “Report a problem” from a map pin. The report is stored in Firebase together with the reported post and the reporter’s anonymous ID.

Review and removal of posts

Reported posts are reviewed by the operator, and posts that violate the terms of use are removed.

Nearby notifications

To notify you of nearby sightings, a notification token (Firebase Cloud Messaging) and the location used for notifications (latitude/longitude and geohash; stored without rounding) are stored in Firebase. There is no in-app setting to turn notifications off; to stop them, turn off KumaMap notifications in your device settings. This information is currently not deleted automatically, so please contact support@aplista.net to request deletion.

Crash reports

To fix problems, Firebase Crashlytics collects crash records (device type, OS version, circumstances of the crash, etc.).

Ads

The iOS app shows Google AdMob ads (app-open ads, banner ads on the map, and native ads in the detail, timeline, and video list screens; there are no full-screen interstitial ads). Google and its advertising partners may handle the advertising identifier (IDFA, only if you allow tracking), device information, ad views and interactions, approximate region inferred from an IP address, and diagnostic information. You can change the tracking permission in Settings > Privacy & Security > Tracking.

The Android app shows Google AdMob banner ads (the ad SDK is initialized at launch). Google and its advertising partners may handle the advertising ID, device information, ad views and interactions, approximate region inferred from an IP address, and similar information. You can reset or delete the advertising ID in your device settings. There is no purchase or in-app setting to remove ads.

Contact and deletion requests

support@aplista.net (weekdays 10:00–18:00 JST). When requesting deletion of a post, please include the date, time, and location of the post.

External services

Google Firebase (Firestore, Authentication, Cloud Functions, Cloud Messaging, Crashlytics) https://firebase.google.com/support/privacy , Google AdMob https://policies.google.com/technologies/ads

Identification

The app identifies users by a per-device identifier (UUID) and a Firebase anonymous authentication user ID. We do not collect names or email addresses.

Study records (stored on our server)

Study records are stored in Google Firebase (Cloud Firestore), linked to the user ID above: unit, mode, number of questions, number of correct answers, time taken, date and time, and the option chosen and result for each question. They are used to show weak points and review your study. Records are kept without a set retention period (no automatic deletion). To request deletion, contact support@aplista.net.

National leaderboard (nickname is public)

Challenge mode results (subject, correct-answer streak, time, date and time) and your nickname are stored in Firebase, linked to the user ID. Your nickname and score are shown to other users on the leaderboard screen. The leaderboard shows the last 7 days, but records are kept without expiry (no automatic deletion). Please contact us to request deletion. Do not use words that identify you, such as your real name or school name.

Maintenance notice

At launch, the app loads a server setting (whether maintenance is in progress). No user IDs or similar information are sent for this.

Ads

The app shows Google AdMob ads (banner ads, full-screen interstitial ads, and app-open ads). The ad SDK is initialized at launch. Google may handle device information, approximate region inferred from an IP address, ad views and interactions, and similar information. The iOS app does not request tracking permission, so the advertising identifier (IDFA) is not used.

Deletion requests

Please email support@aplista.net (weekdays 10:00–18:00 JST) with your nickname and the approximate period you used the app.

Age of users

The app is mainly intended for junior high school students. Parents and guardians, please review this information as well.

This privacy policy applies to the mobile applications and related websites or support channels operated by our company.

When a dedicated privacy policy is provided for another service, that policy will take precedence.

We collect only the minimum personal information required to deliver our services.

Depending on the app, we obtain usage information, crash information, and device or advertising identifiers. The information obtained is described in the supplement for each app.

Contact details

Email addresses obtained when users reach out for support.

Device information

Device model and OS version to maintain app stability.

Usage metrics

Depending on the app, usage information is obtained to improve the app. The information obtained is described in the supplement for each app.

Collected data is used strictly for delivering functionality, improving quality, and providing user support.

If we need to announce material changes or new features, contact details may be used after obtaining consent.

Personal information is retained only for as long as necessary to fulfil the stated purposes.

Unless required by law, data is deleted or anonymised within 90 days after it becomes unnecessary.

When outsourcing to third parties, we sign data protection agreements and share only the minimum data after verifying safeguards.

Except where legally required, we do not provide personal data to third parties without user consent.

External services used by each app (such as Google Firebase, Google AdMob, Google Gemini API, and RevenueCat) are described in the supplement for each app.

Cloud infrastructure

Cloud vendors may host stored data in Japan or overseas.

Analytics platforms

Anonymised usage statistics may be processed by contracted providers.

In some apps, content entered by users (such as sighting reports and nicknames) is visible to other users. The apps concerned and the scope of disclosure are described in each supplement.

Users can request disclosure, correction, or deletion of their personal information.

A response outlining the handling plan will be sent within two business days after we receive an email at support@aplista.net.

For privacy inquiries please contact support@aplista.net.

Support hours: Weekdays 10:00–18:00 (JST).

Any changes to this policy will be announced on the website and within the app with a clear summary of updates.

For material changes, a banner will appear on the home page at least 30 days before the effective date.