OshiCue, operated by Rem-do Apps, respects user privacy and clarifies how fan activity data and permissions stored on the device are handled.
The Japanese privacy policy is the authoritative version. This English translation is provided for convenience.
1. Information Collected or Stored
- Favorites, events, deadlines, timetables, spending, goods, notes, external links for each favorite, share cards, and import/export data entered by the user.
- For visited places registered separately from event venues: the place name, address, coordinates, visit date, notes, tags, photos, and an optional related favorite. Only the selected place information is recorded.
- Images selected through PhotosUI. Photos (PhotoKit) may assist with loading iCloud Photos when needed. UIKit and Core Image are used for JPEG normalization, previews, free-form cropping, 90-degree rotation, angle correction, brightness, and contrast adjustments. Image files are stored in the app's Application Support area, while metadata such as attachment IDs, paths, MIME types, captions, and creation dates are stored in SwiftData.
- Notification settings, calendar-added state, widget snapshots, Live Activity progress display, tip display state, Free/Plus state, StoreKit purchase verification, iCloud backup/restore state, device sync state, and Apple Music linkage information.
- Text entered through camera OCR or paste. It is used to create on-device draft candidates and is not saved automatically.
- Recognized text when the user operates voice input. Audio recordings are not stored as persistent app data.
- For AI-assisted schedule creation: Sign in with Apple authentication information, usage counts, input URLs, a portion of page text, detail page URLs, partial image URLs, generated schedule candidates, processing results, and error categories. Candidates can be edited before saving, and only schedules saved by the user become device-local data.
- HealthKit-derived data explicitly loaded by Plus users for event or statistics views, such as steps, active energy, average/maximum heart rate, and weekly/monthly summaries. HealthKit is used read-only, and CareKit is not used. This data is not used for advertising, tracking, marketing, iCloud backup, device sync, or transmission to the operator's own server.
- Summaries of crash, hang, launch, memory, and other diagnostic information aggregated on the device by MetricKit. These summaries are not transmitted externally and remain limited to on-device OSLog and UserDefaults summaries.
- Google Mobile Ads SDK and Google User Messaging Platform may process device or ad-related information for ad display, consent handling, fraud prevention, and ad delivery quality. IDFA may be used if App Tracking Transparency permission is granted.
2. Purpose of Use
- To provide schedule, deadline, spending, image attachment, image preview, cropping, rotation, adjustment, album saving, share card, import/export, and widget functions.
- To provide local notifications, iOS calendar additions, and widget snapshots through App Group.
- To provide App Shortcuts, venue maps, visited place maps, automatic updates to the day's progress display, tips, OCR and on-device draft candidates, voice input, related link previews, and export file checks.
- For regular visited-place search, to show candidates from a place name or address; and only after the user taps “Find Nearby,” to use the current location temporarily to show nearby candidates in distance order.
- As a Plus feature, to read HealthKit data when requested by the user and display it as an OshiCue participation record in event details and weekly or monthly statistics. It is read-only and is not used for advertising, tracking, marketing, or iCloud backup.
- As a Plus feature, to save recovery backups to the user's CloudKit private database when automatic iCloud backup is enabled and restore them after user confirmation.
- As a Plus feature, to sync schedules, records, attached images, and other supported data across devices using the same Apple Account after the user reviews and selects the initial source.
- To search Apple Music for favorites or groups and open the relevant artist page. If MusicKit developer token retrieval fails, candidates may continue to be displayed through an iTunes Search API fallback.
- To create event or stream schedule candidates from URLs explicitly entered by the user and allow review and editing before saving. Usage counts are managed by Apple sign-in account.
- To manage OshiCue Plus purchases, restoration, entitlement reflection, Free limits, and ad display.
- To investigate defects, improve quality, respond to App Review, and support user inquiries.
3. Local Storage, iCloud Backup, and Device Sync
OshiCue is designed local-first. Main user data is stored in SwiftData and app file storage on the device.
iCloud Backup and Restore
When automatic iCloud backup is enabled for Plus, recovery backup data and attached images are saved to the user's CloudKit private database after device-local storage succeeds. Restore occurs after the user reviews and confirms it.
Device Sync
Device sync is a separate Plus feature from recovery-oriented backup and restore. After the user reviews and selects the data to use as the initial source, changes to schedules, records, attached images, and other supported data are synced across devices using the same Apple Account.
JSON Import and Export
JSON import is available on the Free plan. CSV export, JSON export, iCloud backup and restore, and device sync are Plus features.
JSON exports do not include image files. Use iCloud backup when images must also be restored.
Data Excluded from Backup and Sync
OCR, on-device draft candidates, recognized voice input text, HealthKit-derived data, TipKit display state, and MetricKit diagnostic summaries are excluded from iCloud backup. HealthKit-derived data is also excluded from device sync.
AI-generated candidates are not saved automatically; only schedules saved by the user become device-local data. The operator does not provide its own social network or community features.
4. Permissions
Photo, notification, calendar, Apple Music, camera, microphone, speech recognition, HealthKit, and location permissions are not requested at first launch.
The required iOS permission prompt or PhotosUI flow is shown when the user performs the corresponding operation, such as adding an image, loading an iCloud Photo with PhotoKit assistance, saving to the device photo library, setting a reminder, adding to a calendar, searching Apple Music, using camera OCR or voice input, or loading HealthKit data.
Opening venue or visited place maps and regular place/address search do not request location permission. “When In Use” location permission is requested only after the user taps “Find Nearby,” and the current location is used only while displaying nearby candidates. The current location itself and movement history are not saved; only the place name, address, and coordinates selected by the user are recorded as a visited place.
5. External Transmission and Third-Party Provision
The operator does not provide locally stored fan activity data or HealthKit-derived data to third parties except when required by law or with user consent.
External Services Used
- Apple CloudKit for iCloud backup, restore, and device sync.
- Apple MapKit and Core Location for place search, maps, and “Find Nearby.”
- Apple MusicKit for Apple Music linkage.
- Google Mobile Ads SDK for advertising.
- Apple App Store and StoreKit for purchases.
- iOS ShareLink for sharing.
- Apple Speech framework for speech recognition.
AI-Assisted Schedule Creation
AI-assisted schedule creation may send input URLs, portions of page text, detail URLs, and partial image URLs to an external AI service through Cloudflare Workers.
D1 stores only minimal logs needed for authentication sessions, usage counts, model, item counts, and error categories; it does not store schedule data, original images, or full page text. HealthKit-derived data is not used for CloudKit, AI analysis, or advertising.
6. Advertising and Tracking
The Free plan may display ads. The production app checks App Tracking Transparency status before starting ad requests. It then uses Google User Messaging Platform for ad consent and enables ad display only when ad requests are permitted.
Users can continue using the app with ads that do not use IDFA if tracking is not allowed. HealthKit-derived data is not used for advertising, tracking, or marketing.
Advertising data is handled under Google and Apple policies.
7. Data Deletion
Users can delete favorites, events, deadlines, spending, goods, random goods, visited places, attached images, and related data in the app. Deleting a visited place also deletes photos attached to that place.
If the app is deleted, local app data is deleted according to iOS behavior.
Minimum logs needed for AI-assisted schedule creation usage counts and abuse prevention may be retained to the extent needed for stable service operation and inquiry support. App Store purchase history is associated with the Apple Account.
8. Security Measures
OshiCue is designed to minimize information handling through local storage, limited permission requests, service abstraction, and limited App Group usage.
9. Disclosure, Correction, and Deletion Requests
For inquiry information held by the operator, requests for disclosure, correction, deletion, or suspension of use will be handled within a reasonable scope after identity confirmation. Device-local data should be managed by the user on the user's device.
10. Changes
This policy may be revised due to feature additions, legal changes, external SDK changes, or App Store requirements. Important changes will be announced in the app or on distribution pages.
11. Contact
For questions about personal information or app data handling, contact contact@remudo.com.