Privacy Policy

Takumi Kuroyanagi ("we," "us," or "our") sets out this Privacy Policy for the handling of user information in the smartphone application "WFO Counter" (the "App").

The App offers core features without login, while sync and friend features are available only when signed in, so the scope of handled information differs by feature. Based on the current implementation, no advertising SDKs, Firebase Analytics, Crashlytics, or similar tracking or ad-delivery tools have been confirmed.

1. Information We Handle

The App handles the following categories of information to provide its features.

• Work and settings data: attendance records, office locations, leave records, achievement unlocks, weekly goals, notification settings, and other app preferences
• Location data: used for geofence-based arrival and departure detection when automatic logging is enabled by the user
• Calendar data: read through EventKit for Japanese holiday detection when the user grants permission
• Authentication and profile data: authentication information for Sign in with Apple or Google, Firebase user identifiers, display names, user codes, selected title IDs, and status messages
• Shared data: invitation text, my code, and monthly JSON export data explicitly shared by the user
• Place search data: Apple Maps search queries and results when the user uses office location search

2. Purpose of Use

We use the information we handle for the following purposes.

• To record, aggregate, display, and calculate attendance progress
• To register office locations, monitor geofences, and determine office attendance automatically
• To detect Japanese holidays, support widgets, and control notifications
• To provide sync, profile storage, and friend features for signed-in users
• To support sharing, copying, and exporting that the user explicitly initiates
• To provide support, prevent abuse, and comply with legal obligations

3. Storage

Core app data is mainly stored on the user's device. Based on the current implementation, Apple iCloud or CloudKit sync is not used.

• On-device storage: attendance records, office locations, leave records, and achievement unlock data are stored with SwiftData or SQLite.
• On-device settings storage: app preferences, temporary notification state, and widget shared data are stored with UserDefaults or App Group UserDefaults.
• Cloud storage: only when the user signs in, some attendance records, office locations, leave records, profile information, same-day presence status, and friend relationships may be stored with Firebase Auth and Firestore.

4. External Transfers and Third-Party Services

The App sends information to external services in the following cases.

• Firebase Auth: used for authentication when signing in with Apple or Google
• Firestore: used for sync, profile storage, friend features, and same-day presence sharing while signed in
• Apple Maps: used only when the user searches for an office location to show candidates and resolve places
• OS sharing features and clipboard: used when the user explicitly shares or copies invitation text, codes, or monthly data

Based on the current implementation, location history itself is not stored on our own servers. When a location-based attendance result updates while the user is signed in, part of that result may be stored in the sync destination.

5. Information Shared Through Friend Features

When friend features are used, the following information may be shared with the other user.

• Display name
• User code
• Selected title ID
• Status message
• Same-day office status
• Same-day sharing preference

However, complete work history, office coordinates, complete leave records, and local achievement history are not included in information shared with friends.

6. Permissions

• Location: required to use automatic attendance logging. Some features, such as manual logging, remain available without it.
• Calendar: required to use Japanese holiday detection. Core features remain available without it.
• Notifications: used for reminders and status notifications.

7. User Choices

Users can make the following choices.

• Use only core features without signing in
• Grant or revoke location, calendar, and notification permissions
• Choose whether to use sharing and export features
• Change whether same-day presence is shared in friend features

8. Provision to Third Parties

Except where required by law, we do not provide personal information to third parties without user consent. However, when the user uses login, place search, or sharing features, the external services or OS features described above may be used to the extent necessary to provide those features.

9. Changes to This Policy

We may change this policy in response to legal requirements, implementation changes, feature additions, or other circumstances. If an important change is made, we will provide notice by an appropriate method.

10. Contact

For inquiries about this policy, please use the form below.

Contact form