< Return

Privacy Policy

Last updated: November 14, 2026

This policy covers YK.George.Apps applications generally, including optional calendar synchronization, CloudKit synchronization, application locking, advertising, analytics, and subscriptions. The published policy and store disclosures must remain consistent with the actual implementation of each application.

Google user data: For how the Schedule And Notes app handles Google user data, see Section 3.3.

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”).

The Services include the following applications: Schedule And Notes, Simple Calculator, Notepad, Easy Input Calculator, Health Checkup Record, Organize recipes App, QRCode Maker, Barcode Reader, Solitaire Klondike, and Reversi. Section 3.3 describes how Schedule And Notes handles Google user data.

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 (Schedule And Notes: Google User Data)

This section explains how the iOS app Schedule And Notes accesses, uses, transfers, protects, retains, and deletes Google user data when you choose to use its optional Google Calendar integration. If you do not connect a Google Account, the app does not access any Google user data. The statements in this section apply to both raw Google user data and any aggregated, anonymized, or derived data. The app does not create aggregated or anonymized data sets from Google user data.

Data Access

Schedule And Notes uses Google Sign-In and the Google Calendar API, and requests only the following permissions:

The app does not access Gmail, Google Drive, Google Contacts, or any other Google service.

Data Use

Google user data is used only to provide the Google Calendar synchronization feature shown in the app: displaying events from your selected Google calendar in the app, and creating, updating, and deleting events in that calendar when you create, edit, or delete schedules in the app. Google user data is not used for advertising, ad personalization, analytics, user profiling, determining creditworthiness or lending, or any other purpose unrelated to this feature.

Data Transfer

We do not sell Google user data, and we do not share or transfer it to any third party, including advertisers, data brokers, analytics providers, crash-reporting providers, or AI service providers. Google user data is transferred only in the following cases:

Data Protection

Data Retention and Deletion

AI/ML

Schedule And Notes does not use AI or machine learning (ML) models with Google user data. Google user data, including data received from Google Workspace APIs such as the Google Calendar API, is not used to develop, improve, or train AI/ML models, and it is not transferred to any third-party AI/ML service.

Limited Use

Schedule And Notes' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

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.

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:

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:

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.

6.1 Application and Device Integrity Checks (Android)

On Android, the schedule application uses the Google Play Integrity API to check whether the application is the genuine version distributed through Google Play, whether it was obtained through Google Play, and whether the device passes Google's integrity checks. When a check is performed, Google Play and Google Play services process information such as the application package name, version number, and signing certificate; the Google Play license status of the accounts signed in on the device; device attestation information generated by Google Play services; and a value derived from the request made by the application. This processing is governed by the Google Play Terms of Service and the Google Privacy Policy.

Google returns an encrypted result, which the application sends to the verification function described in Section 8. The result does not include your name, email address, or the contents of your schedules, notes, or memos. We use integrity results only to protect paid features and to help you obtain the application from Google Play. We do not use them to identify, profile, or track individual users or devices, or for advertising.

If a problem is detected, Google Play may display a message asking you, for example, to obtain the application from Google Play.

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.

Where analytics is enabled and permitted, the application may also send subscription events to our analytics provider (Google Analytics for Firebase) in order to measure how paid features are purchased, renewed, canceled, refunded, or restored, and to measure the revenue generated by the application. These events may include the subscription product identifier, the transaction identifier assigned by the application-store provider, the purchase or renewal date, the price and currency displayed by the application store, whether the transaction is an initial purchase or an automatic renewal, introductory-offer or free-trial status, cancellation, refund, or revocation status, and the resulting entitlement status.

We do not include your name, payment-card details, application-store account identifier, billing address, or schedule contents in these events. Where applicable law requires consent for analytics storage, these events are collected only after that consent is obtained through the applicable consent notice. Test and sandbox transactions are excluded from revenue measurement.

Application-store providers and analytics services may also independently process limited transaction information under their own policies.

8.1 Purchase Verification (Android)

On Android, when you purchase or restore a subscription, and from time to time while you use the application, the schedule application may verify the subscription to prevent fraudulent purchases and the use of unauthorized copies of the application. For this purpose, the application sends the following information to a verification function that we operate on Google Cloud (Cloud Functions for Firebase): the application package name, the subscription product identifier, the purchase token issued by Google Play, and the integrity result described in Section 6. The verification function sends this information to Google to check the integrity result and the subscription status, and returns to the application only whether the subscription is valid, its expiration time, and whether an integrity problem was detected.

To avoid unnecessary verification requests, the application stores on your device a one-way hash of the purchase token, the time of the last successful verification, and the expiration time.

9. Purposes of Processing

We may process information for the following purposes:

10. Legal Bases for Processing

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

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:

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:

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

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 access tokens and refresh tokens are stored in the iOS Keychain, and all communication with Google APIs uses HTTPS (TLS) encryption. 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]