This privacy policy applies to the Challenge Log / チャレンジログ app (hereby referred to as "Application") for mobile devices that was created by yokokubo (hereby referred to as "Service Provider") as a Free service. This service is intended for use "AS IS".

The Application collects information when you download and use it. This information may include information such as

• Your device's Internet Protocol address (e.g. IP address)
• The pages of the Application that you visit, the time and date of your visit, the time spent on those pages
• The time spent on the Application
• The operating system you use on your mobile device

The Application does not gather precise information about the location of your mobile device.

The Service Provider may use the information you provided to contact you from time to time to provide you with important information, required notices and marketing promotions.

When you sign in, the Application processes your account identifier, email address, display name, and optional profile photo to provide your account and calendar sharing. Your records, labels, notes, sharing relationships, and notification settings are stored in Firebase when you use the corresponding cloud features. Guest records remain on your device until you choose to sign in and sync them.

The Application includes optional features that let other people see what you recorded. These features are off unless you turn them on, and each one is controlled by you.

• Shared calendars: if you accept an invitation from another user, that user can see the records on the shared calendar. You can stop sharing at any time.
• Community records: after accepting the community notice, you may turn on "Show my records to everyone" in Settings. Records saved while this setting is on are shown to other users. Notes are included only when the separate note-sharing setting is enabled. Other users see only the stamp you chose, its label, the note you attached if you added one, and the time at which it was posted. They do not see your name, your email address, your account identifier, the calendar date of the record, or your private records. The server uses a random internal author identifier to implement reporting and blocking; it is not a public account profile. The contents of a note or custom label may nevertheless identify you, so do not include personal information.
• Cheers: other users can send a single cheer on a record. For community records the sender is not identified to you.

In version 2.2.0, a community record is stored as a separate copy and remains visible until you make it private, delete the original, or it is removed through moderation. Turning "Show my records to everyone" off withdraws all your currently public records. Editing the original updates the public copy. Users who accepted the earlier 48-hour notice must accept the updated notice before creating records without a time limit. Copies created under that earlier notice keep their original expiration.

If you report a community record, the Service Provider stores your account identifier, the reported record, and the reason you selected, so that reports can be reviewed and repeated abuse can be identified. If you choose not to see a particular user, the Service Provider stores the pair of account identifiers involved so that neither of you is shown the other. Reports and blocks are retained for as long as is needed to operate and moderate the service. The other user is not told that you reported or blocked them.

When you sign in, the Application may register and store a push notification token for your device together with the language and time zone you use. This supports reminders and other app notifications in the appropriate language. Displaying notifications requires your device's notification permission. You can disable reminders in the Application and turn notification delivery off in your device settings.

Firebase (Google) processes account information, cloud records, profile images, device notification tokens, and technical service information to operate sign-in, storage, sharing, and notifications. Sentry processes error reports and technical diagnostic information to identify failures. Google AdMob may process IP-derived approximate location, device or app-scoped identifiers, ad interactions, crash information, and performance information for advertising, measurement, and fraud prevention. Version 2.2.0 requests non-personalized ads, disables the publisher first-party advertising identifier, and does not request access to IDFA. Where consent is required, ads are requested only after the consent flow permits them. A privacy-options control is provided when required so you can revise your choice. The Application does not access GPS location.

The Service Provider may disclose User Provided and Automatically Collected Information:

• as required by law, such as to comply with a subpoena, or similar legal process;
• when they believe in good faith that disclosure is necessary to protect their rights, protect your safety or the safety of others, investigate fraud, or respond to a government request;
• with their trusted services providers who work on their behalf, do not have an independent use of the information we disclose to them, and have agreed to adhere to the rules set forth in this privacy statement.

You can stop all collection of information by the Application easily by uninstalling it. You may use the standard uninstall processes as may be available as part of your mobile device or via the mobile application marketplace or network.

The Service Provider will retain User Provided data for as long as you use the Application and for a reasonable time thereafter. If you'd like them to delete User Provided Data that you have provided via the Application, please contact them at johnworks.em0@gmail.com and they will respond in a reasonable time. Community copies created after accepting the updated 2.2.0 notice have no automatic time-based expiration. You control their visibility through Settings and by editing or deleting the original record. Reports and moderation history are separate from the public copies and may be retained to handle abuse and support requests.

The Service Provider does not use the Application to knowingly solicit data from or market to children under the age of 13.

The Service Provider is concerned about safeguarding the confidentiality of your information. The Service Provider provides physical, electronic, and procedural safeguards to protect information the Service Provider processes and maintains.

This Privacy Policy may be updated from time to time for any reason. The Service Provider will notify you of any changes to the Privacy Policy by updating this page with the new Privacy Policy. You are advised to consult this Privacy Policy regularly for any changes, as continued use is deemed approval of all changes.

This privacy policy is effective as of 2026-09-20

By using the Application, you are consenting to the processing of your information as set forth in this Privacy Policy now and as amended by us.

If you have any questions regarding privacy while using the Application, or have questions about the practices, please contact the Service Provider via email at johnworks.em0@gmail.com.