Privacy Policy
App name: Anbu Jigi
Controller: Nam Yonghyun
Operator label: Sometimes Studios, a personal developer brand
Effective date: May 8, 2026
Last updated: June 18, 2026
Version: 1.9
Summary
Anbu Jigi does not operate a developer server. Core app data such as contacts and contact records is stored on the user's device and is not automatically sent to the developer.
- Contact information is used only for contact-reminder features.
- Contacts permission is used for core features such as full address-book import, resync, and deletion-preview cleanup for contacts removed from the device address book.
- Contact, contact-history, and reminder-setting data is not used for advertising targeting.
- Declining advertising privacy consent does not block the app's contact-management features.
- If a user chooses to send an inquiry or bug-report email, the email address, message content, and limited app/device diagnostics are processed for support purposes.
- Deleting the app deletes the app data stored on the device.
1. Controller And Contact
| Item | Details |
|---|---|
| Controller | Nam Yonghyun |
| Operator label | Sometimes Studios, a personal developer brand |
| privacy@sometimesstudios.com | |
| Response target | Within 7 business days after receipt |
This app is operated by Nam Yonghyun as an individual developer. "Sometimes Studios" is used as a personal developer brand name and is not currently a registered company or legal entity.
2. Data Processed By The App
2-1. Data Processed Directly
| Data | How it is processed | Purpose | Legal basis |
|---|---|---|---|
| Contact names and phone numbers | Read from the device address book and stored in the app's local database | Full address-book import, resync, contact-cycle tracking, reminder display, and deletion-preview cleanup for contacts removed from the device address book | Consent during onboarding permission request |
| Manual contact records, date only | Entered by the user and stored in the app's local database | Updating the last-contact date | Performance of the app's core function |
| Reminder and settings values | Stored locally in SharedPreferences | Keeping reminder time and cycle settings | Performance of the app's core function |
| Inquiry and bug-report emails | Received by the developer only when the user sends them through an external mail app or copies and sends them manually | Responding to inquiries, investigating errors, and improving the app | User request and legitimate interest |
| Inquiry and bug-report diagnostics | Email body may include only app version/build, locale, text-size setting, notification/exact-alarm permission status, Android version/API, manufacturer, and model | Error reproduction and support response | User request and legitimate interest |
Contacts permission is used to import contacts the user wants the app to manage, reflect later address-book changes, and preview cleanup for entries that no longer exist in the device address book. The app does not send contacts to a developer server and does not use contact information for advertising targeting.
The inquiry and bug-report feature works through a mail app or mail provider chosen by the user, such as Gmail. The diagnostic information does not include contacts, phone numbers, contact history, message contents, Android ID, serial number, IMEI, MAC address, or advertising ID.
2-2. Data Not Processed
- Call logs, call contents, or voice data
- SMS contents or SMS records
- Location data
- Account information such as email or password. The app has no account system.
- Demographic information, sensitive categories, or government identifiers.
Notifications never display contact names or phone numbers; they contain only generic text prompting you to open the app. The call button only opens the device dialer (ACTION_DIAL); the app does not automatically detect whether a call took place and records a contact only when you confirm it yourself. The app does not read or store call logs, SMS contents, or SMS records.
2-3. Third-Party SDKs
| SDK | Provider | Data handled | Purpose | Policy |
|---|---|---|---|---|
| Google AdMob | Google LLC | Advertising identifier, device information, and app usage data for advertising purposes | Displaying banner and interstitial ads | Google Privacy Policy |
| Google User Messaging Platform (UMP) | Google LLC | Advertising consent status and privacy choices | Collecting advertising consent and managing ad privacy choices | Google Privacy Policy |
Contact, contact-history, and reminder-setting data is not provided to AdMob or any other third party for advertising targeting.
In regions where advertising consent is required, including the EEA, the United Kingdom, and Switzerland, Google UMP may show an advertising consent screen before ad requests are made.
In California and other regions where additional ad privacy choices may be required, users may manage those choices through Google's ad privacy options screen.
Declining or limiting advertising privacy choices does not block contact management, manual records, or reminder settings. Ads may be limited, non-personalized, or not requested depending on Google SDK policy and consent status.
3. Storage, Security, And Deletion
- Storage location: App data is stored only in the device's local SQLite database and SharedPreferences. It is not sent to a developer server, cloud storage, or external storage controlled by the developer.
- External transmission: Except for Google AdMob and UMP SDK processing, the app does not automatically transmit user data over the network. If the user chooses to send an inquiry or bug-report email, the email content and limited diagnostics are delivered to the developer.
- Encryption: Android device storage protections apply to app-internal storage, and Google SDK communications use HTTPS.
- Backup disabled: Android automatic backup is disabled with
android:allowBackup="false".
| Data | Retention | Deletion |
|---|---|---|
| Contacts and contact records | While the app is installed, unless deleted by the user | Delete in the app, clear app data, or uninstall the app |
| Reminder and settings values | While the app is installed | Clear app data or uninstall the app |
| Inquiry and bug-report emails and diagnostics | For as long as needed to handle the inquiry and follow-up support, generally deleted within 1 year after the final response unless longer retention is needed for dispute handling, security investigation, or legal obligations | Request deletion by email |
Because the developer does not operate a server for this app, deleting the app or clearing app data removes the app data stored on the device.
4. User Rights
Depending on the user's region, rights may include access, correction, deletion, restriction, withdrawal of consent, portability, objection, and ad privacy choices.
| Right | How to exercise it |
|---|---|
| Access and correction | Review or edit data in the app, or contact privacy@sometimesstudios.com |
| Deletion | Delete entries in the app, clear app data, or uninstall the app |
| Permission withdrawal | Use Android device settings → Apps → Anbu Jigi → Permissions |
| Advertising privacy choices | Use the in-app ad privacy options when Google reports that they are required |
| Data portability | Contact privacy@sometimesstudios.com. In-app export is planned for a later version. |
5. Permissions
| Permission | Required? | Effect if denied |
|---|---|---|
READ_CONTACTS | Required for core contact-import and resync features | The app cannot import or resync contacts from the address book. |
POST_NOTIFICATIONS | Optional | The app can still be used, but reminders may not be shown as notifications. |
SCHEDULE_EXACT_ALARM | Optional | The app can still be used, but reminder timing may be less precise depending on Android and device policy. |
6. Automated Decision-Making And Profiling
The app does not perform automated decision-making or profiling under GDPR Article 22. Reminder timing is calculated from user settings and contact dates, without AI-based inference.
7. Sharing And International Transfer
The app does not sell contact, contact-history, or reminder-setting data, and does not share those data categories for cross-context behavioral advertising.
Google SDKs may process advertising identifiers, device information, app usage data for ads, and consent status using Google infrastructure, including infrastructure outside the user's country. Google is responsible for its own processing under its published policies and safeguards.
8. Children
The app is not directed to children under 14 in Korea or under 13 under COPPA/GDPR-K style standards. In Google Play Console, it should be declared as not designed for children. If the developer becomes aware that a child is using the app without appropriate consent, the developer will guide the guardian on app deletion or app-data deletion.
9. Future Cloud Backup Or Device Transfer
The current version has no developer server storage, cloud backup, Google Drive sync, or account transfer feature. If such a feature is added later, the app will explain the backup scope, storage location, encryption, retention, and deletion method, and will require an explicit user choice before use.
10. Changes
If this policy changes, the updated policy will be posted on this page before it takes effect. Important or unfavorable changes will be announced in advance where reasonably possible.
User-initiated inquiry or bug-report emails sent through an external mail app are not automatic collection or a new processing delegation. They are processed only because the user chooses to send the support request, and only for support, error investigation, and app improvement.
11. Contact
Privacy inquiries: privacy@sometimesstudios.com
Supplement: This policy is effective from May 8, 2026. Previous version: v1.8, June 18, 2026.