Privacy Policy

1. Scope

This Privacy Policy explains how YK.George.Apps, operated by Yuta Kobayashi (“YK.George.Apps,” “we,” “us,” or “our”), handles information in connection with our mobile applications and related website (collectively, the “Services”).

Not every application uses every feature or third-party service described below. The practices applicable to a particular application depend on its functions, platform, permissions, settings selected by the user, and the services included in that application.

2. Information Stored Locally on Your Device

Our applications may allow you to create or store information such as calculations, calculation history, notes, recipe bookmarks and URLs, QR code or barcode content, game progress, settings, calendar events, schedules, reminders, notification settings, health checkup records, or blood test records.

Unless a particular application clearly states otherwise or you enable a synchronization or sharing function, this user-created content is stored locally on your device and is not intentionally transmitted to us, advertising providers, or analytics providers.

Depending on your device settings and the application’s configuration, locally stored information may be included in operating-system backup services provided by Apple or Google. Those backups are controlled by the applicable platform provider and are governed by its privacy policy.

Health information: Information entered into an application for recording health checkups or blood test results is intended to remain on your device. We do not intentionally use the contents of those health records for advertising or analytics.

3. Schedule and Calendar Information

3.1 Local Schedule Database

The schedule application stores event and schedule information in its application database. This information may include event titles, dates and times, recurrence settings, reminders, categories, colors, notes, locations, completion status, and other information that you choose to enter.

Unless you enable a calendar or cloud synchronization function, schedule information remains in the application’s local database.

3.2 Device Calendar Integration

If you enable integration with the device’s standard calendar, the application may read, create, update, or delete calendar events through the calendar access provided by the operating system. The exact access depends on the permission you grant and the feature you use.

Information written to a device calendar may be stored or synchronized by the calendar account provider configured on your device, such as Apple, Google, Microsoft, or another provider. Those providers process the information under their own privacy policies.

You may revoke calendar permission through your device settings. Revoking permission stops the application from accessing the device calendar but does not automatically delete events already written to that calendar.

3.3 Google Calendar Integration

If you choose to connect Google Calendar, the application uses Google OAuth 2.0 and the Google Calendar API after you authorize access. The application may access and synchronize schedule information necessary for the feature, including event titles, dates and times, recurrence settings, reminders, notes, locations, calendar identifiers, event identifiers, and synchronization status.

The application may store OAuth access or refresh tokens and related authorization information on your device to maintain the connection. These tokens are used only to access the Google Calendar functions that you authorize.

Google Calendar information is used only to provide and improve the user-facing calendar synchronization feature. We do not use Google Calendar information for advertising, ad personalization, analytics profiling, creditworthiness, or unrelated purposes, and we do not permit advertising or analytics SDKs to receive the contents of your calendar events.

Our use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements.

You may disconnect Google Calendar in the application and may also revoke access through your Google Account settings. Disconnecting stops future synchronization and should remove locally stored Google OAuth authorization tokens. Events already stored in Google Calendar or in the application’s local database remain until you delete them from the applicable location.

3.4 iCloud and CloudKit Synchronization

If you enable iCloud synchronization, the application uses Apple CloudKit to store and synchronize schedule information through the private CloudKit database associated with your Apple Account. This allows schedule information to synchronize between supported devices signed in with the same Apple Account.

We do not receive your Apple Account password. Apple processes and stores CloudKit data under Apple’s terms and privacy policy. Disabling iCloud synchronization stops future synchronization but may not immediately remove information already stored in iCloud or on other synchronized devices.

Deleting schedule information while synchronization is enabled may synchronize that deletion to other devices. Information may also remain in device or iCloud backups until those backups are removed or expire.

3.5 Notifications

The schedule application may use local notifications to remind you of events or schedules at times you select. Unless the application clearly states otherwise, notification timing and notification content are processed on your device and are not sent to our server.

You may disable notifications through your device settings. Disabling notifications does not delete schedule information.

4. Application Lock, Passcode, and Biometric Authentication

A paid feature of the schedule application may allow you to lock access to the application using an application passcode or biometric authentication.

• Application passcode: The passcode is stored locally using Apple Keychain and is not intentionally transmitted to us, advertising providers, or analytics providers.
• Biometric authentication: Face ID, Touch ID, or another supported biometric method is evaluated by the operating system. The application receives only the result of the authentication attempt and does not receive or store fingerprint images, facial templates, or other underlying biometric data.
• Subscription expiration: If the applicable subscription expires, the application lock is disabled. Expiration of the subscription does not delete or modify schedule information.

The application lock is an in-application access-control feature. It does not necessarily encrypt the schedule database, calendar-provider data, CloudKit data, device backups, notifications, or information accessible through another calendar application or service.

5. Permissions and On-Device Processing

Depending on the application, the Services may request access to device features only when needed to provide a function:

• Camera: Used to scan QR codes or barcodes. Camera frames are generally processed on the device and are not intentionally uploaded or retained by us.
• Calendars: Used to display, create, update, delete, import, export, or synchronize calendar events when you enable the applicable feature.
• Notifications: Used to display reminders and application notifications.
• Biometric authentication: Used to request operating-system authentication for the application lock.
• Share sheet, clipboard, or selected content: Used when you choose to import, copy, create, or share text, URLs, QR code content, calendar content, or similar information.
• Local storage: Used to save application data and settings on your device.
• Internet access: Used for calendar synchronization, iCloud, advertising, analytics, crash reporting, performance monitoring, remote configuration, purchases, support links, and other online functions.

6. Information Processed Automatically

When you use an application that includes advertising, analytics, diagnostics, performance monitoring, remote configuration, or similar services, we and our third-party service providers may process the following categories of information:

• Device and application identifiers: Such as the Android Advertising ID, Apple’s Identifier for Advertisers (IDFA) when authorized, Identifier for Vendors (IDFV), publisher first-party identifiers, Firebase installation identifiers, and crash-reporting installation identifiers.
• Device and application information: Such as device model, operating-system version, language, country or region, application name, package or bundle identifier, application version, screen orientation, available memory or storage, and network type.
• Usage information: Such as application launches, session duration, feature interactions, screen views, button interactions, application lifecycle events, and other usage events.
• Advertising information: Such as ad requests, ad impressions, clicks, ad format, advertising revenue information, consent status, and whether personalized or non-personalized advertising is permitted.
• Diagnostics and performance information: Such as crash logs, stack traces, error messages, response times, network request performance, and other technical diagnostic information.
• Network and approximate location information: Such as IP address, mobile carrier, and approximate country, region, or city inferred from an IP address. We do not intentionally collect precise GPS location unless an application clearly requests it for a specific feature.

We do not intentionally include schedule titles, schedule notes, event locations, calendar participants, Google Calendar contents, calculation expressions, calculation history, application passcodes, QR code contents, barcode contents, or health records in advertising events, analytics events, crash reports, or performance-monitoring data.

7. Information You Provide to Us

If you contact us, we may receive your email address, the content of your message, attachments you choose to send, the application name, device or operating-system information, and other information you voluntarily provide.

We use this information to respond to your request, investigate problems, prevent abuse, and improve the Services.

8. Purchases and Subscriptions

The schedule application and calculator application may offer a one-month auto-renewable subscription without a free trial.

Payments and subscription management are processed by Apple, Google, or another applicable application-store provider. We do not receive or store your full payment-card details.

The application or application-store provider may process limited purchase and entitlement information, such as the product identifier, transaction identifier, purchase token, purchase date, expiration date, renewal status, cancellation status, and entitlement status, to activate paid features and restore purchases.

We do not operate our own server for receipt or purchase-token verification. Purchase and entitlement verification is performed through the application-store frameworks and services available on the user’s device. Application-store providers and analytics services, if enabled, may independently process limited transaction information under their own policies.

9. Purposes of Processing

We may process information for the following purposes:

• to provide, maintain, and improve application functions;
• to store settings and user-created content on your device;
• to synchronize schedules with a device calendar, Google Calendar, or CloudKit when you enable the feature;
• to authenticate Google Calendar access and maintain the connection you authorize;
• to provide local reminders and application-lock functions;
• to display and measure advertising;
• to provide personalized advertising when permitted and non-personalized or contextual advertising when required or selected;
• to understand application usage and improve usability without intentionally analyzing the contents of schedules, calculations, health records, or other private user content;
• to diagnose crashes, errors, and performance problems;
• to configure application behavior and features remotely;
• to prevent fraud, invalid traffic, misuse, and security incidents;
• to process purchases, verify entitlements, and restore purchases;
• to respond to support requests; and
• to comply with applicable laws and enforce our rights.

10. Legal Bases for Processing

Where applicable law requires a legal basis, we rely on one or more of the following:

• Performance of a contract: To provide the functions you request, including synchronization and paid features.
• Consent: For calendar access, Google OAuth authorization, iCloud synchronization, notifications, biometric authentication, personalized advertising, tracking, access to advertising identifiers, analytics storage, or other processing when consent is legally required.
• Legitimate interests: To operate, secure, troubleshoot, and improve the Services; prevent fraud and invalid traffic; and provide limited or contextual advertising where permitted.
• Legal obligations: To comply with applicable law, lawful requests, accounting obligations, and dispute-resolution requirements.

You may withdraw consent by disabling the applicable function, revoking device permission, disconnecting Google Calendar, disabling iCloud synchronization, changing advertising or privacy settings, or contacting us as applicable. Withdrawal does not affect processing that was lawful before withdrawal.

11. Advertising, Tracking, and Privacy Choices

Some applications are supported by advertising. Advertising may be personalized, non-personalized, limited, or contextual depending on your region, consent choices, device settings, age-related treatment, and applicable law.

Where required, we use a consent-management platform such as Google’s User Messaging Platform to display privacy notices and obtain or record privacy choices. A privacy-options entry point may also be available within the application.

On Apple platforms, an application may request permission through Apple’s App Tracking Transparency framework before accessing the IDFA or engaging in tracking as defined by Apple. If permission is denied, the IDFA is not available to the application for tracking.

Choosing non-personalized advertising does not necessarily remove advertising. Advertising providers may still process limited information for ad delivery, frequency capping, measurement, security, fraud prevention, and compliance.

Schedule contents, Google Calendar contents, CloudKit schedule contents, calculation history, application passcodes, and biometric data are not intentionally used for advertising or ad personalization.

We do not sell personal information for money. However, disclosures to advertising partners may be considered a “sale,” “sharing,” or targeted advertising under certain privacy laws. Where applicable, you may opt out through the application’s privacy options, your device’s advertising or tracking settings, or by contacting us.

12. Third-Party Service Providers

Depending on the application, platform, and features you enable, the Services may use the following third-party services. These providers process information under their own terms and privacy policies:

• Google Privacy Policy, Google Play services, Google Calendar, and Google OAuth
• Google API Services User Data Policy
• Google advertising and partner-site technologies
• Firebase, Google Analytics for Firebase, Firebase Crashlytics, Firebase Performance Monitoring, and Firebase Remote Config
• Apple services, including App Store, iCloud, CloudKit, Keychain, device calendars, biometric authentication, and device backup services
• Meta, including Meta Audience Network
• Unity, including Unity Ads
• AppLovin

Not every application uses every provider listed above. The third-party SDKs and services included in an application may change as the application is updated.

13. Disclosure of Information

We may disclose information:

• to service providers that operate calendar synchronization, cloud storage, advertising, analytics, diagnostics, performance monitoring, remote configuration, purchases, hosting, security, or support functions;
• when you direct us to synchronize, export, share, or otherwise transfer information;
• when required by law, legal process, or a valid governmental request;
• when reasonably necessary to protect users, investigate fraud or security issues, or enforce our rights; or
• as part of a merger, acquisition, reorganization, or transfer of all or part of the Services, subject to appropriate safeguards.

Google Calendar information is not transferred except as necessary to provide the synchronization feature, with your affirmative direction or consent, for security purposes, or as required by applicable law and the Google API Services User Data Policy.

14. International Data Transfers

We are based in Japan. Google, Apple, Firebase, advertising providers, and other service providers may process or store information in Japan, the United States, the European Economic Area, or other countries where they or their service providers operate.

These countries may have data-protection laws that differ from those in your country. Where required, transfers are made using legally recognized safeguards or other permitted transfer mechanisms.

15. Retention and Deletion

• Local schedules and other local content: Remain on your device until you delete them through the application, clear the application’s data, or uninstall the application. Copies may remain in device backups.
• Device calendar information: Events already written to a device calendar remain under the control of the applicable calendar provider until deleted there.
• Google Calendar information: Events synchronized to Google Calendar remain in the user’s Google Calendar until deleted. OAuth authorization remains until it expires, is revoked, or the connection is removed. Disconnecting Google Calendar should remove locally stored authorization tokens but does not automatically delete existing calendar events.
• CloudKit information: Schedule information synchronized through CloudKit may remain in the user’s private iCloud storage and on synchronized devices until deleted through the application, device, or Apple’s iCloud data-management functions.
• Application-lock passcode: Is retained in Keychain while needed to provide or preserve the application-lock setting and is not intentionally transmitted to us.
• Calculation history: Remains locally on the device until deleted by the user, cleared by the application, or removed with application data. Subscription expiration does not necessarily delete it, although access to the history feature may become unavailable.
• Support communications: Are retained only as long as reasonably necessary to respond, maintain support records, prevent abuse, and resolve disputes. We generally delete or anonymize routine support communications within 12 months after the matter is closed, unless a longer period is required for legal, security, or accounting purposes.
• Analytics, advertising, diagnostics, and performance data: Are retained according to our configuration and the applicable provider’s retention policy.
• Purchase records: May be retained by the application-store provider and, where available on the device or received by us, for as long as necessary to provide entitlements, prevent fraud, comply with accounting obligations, and resolve disputes.

We generally do not maintain a user-account database for the Services. To request deletion of information held directly by us, contact us at the address below. We cannot delete information controlled independently by Google, Apple, another calendar provider, or another third-party provider, but we will explain available controls where reasonably possible.

16. Security

We use reasonable administrative, technical, and organizational measures designed to protect information. Calendar synchronization and third-party service communications generally use encrypted network connections provided by the platform or service provider.

Application passcodes are stored using Keychain. Google OAuth authorization tokens should be stored using platform-appropriate secure storage. Biometric information remains under operating-system control and is not accessible to the application.

However, no method of transmission, storage, synchronization, authentication, or security is completely secure. Synchronization conflicts, provider outages, device loss, account compromise, backup exposure, or software defects may result in unauthorized access, data loss, duplication, or inconsistency.

You are responsible for protecting your device, Apple Account, Google Account, device passcode, backups, and access to locally or remotely stored application data.

17. Your Privacy Rights

Depending on your location and applicable law, you may have rights to request access to, correction of, deletion of, or a copy of personal information; to restrict or object to processing; to withdraw consent; to opt out of the sale or sharing of personal information or targeted advertising; and to lodge a complaint with a data-protection authority.

To submit a request, contact us at the email address below and identify the application and platform involved. We may need limited additional information to verify and process the request.

Information stored only on your device, in your Google Calendar, or in your private iCloud storage is generally controlled through the application, device, Google Account, or Apple Account rather than through a database operated by us.

18. Children’s Privacy

Unless an application’s store listing expressly states that it is designed for children, the Services are not directed to children under 13 or the higher minimum age required in the user’s jurisdiction.

We do not knowingly use children’s personal information, calendar contents, or schedule contents for behavioral advertising.

If you are a parent or guardian and believe that a child has provided personal information to us, contact us so that we can investigate and take appropriate action.

19. Third-Party Links and Actions

The Services may contain links to websites, applications, phone numbers, email addresses, maps, calendars, or other third-party content.

For example, a barcode, QR code, or calendar event may contain a link selected by its creator. We do not control third-party content or privacy practices. Review the destination carefully before opening a link, sending information, making a call, joining an event, or taking another action.

20. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in the Services, synchronization functions, third-party providers, legal requirements, or our practices.

We will post the revised policy on this page and update the “Last updated” date. Where required, we will provide additional notice or request consent.

21. Contact

Operator: Yuta Kobayashi / YK.George.Apps
Country: Japan
Email: [email protected]