Privacy Policy

1. Scope

This Privacy Policy applies to the handling of user information in the application “PanelPower” (the “Service”) provided by the operator of PanelPower (the “Operator”).

2. Information collected and stored

The Operator collects or stores the following information to the extent necessary to provide the Service.

2.1 Account and profile information

• User identifier (UID) issued by Firebase Authentication
• Display name
• Email address
• Profile image reference information
• Date of birth
• Gender category
• Weight class
• Competition category
• Social media links registered by the user

2.2 Competition and usage information

• Personal record (PR) entries for squats, bench presses, deadlifts and other lifts; record dates, equipment categories and related notes
• Body weight and measurement dates
• Total, IPF Points, GL Points and other competition metrics calculated from PRs, body weight and other data
• Ranking positions, display categories and aggregation results
• Reaction content, senders and targets
• PR updates and other activity information shown in Activity
• Room membership, roles within Rooms, participation status, member identifiers and other Room usage information
• Information needed to issue, use and revoke Claim Codes and link them to the relevant Legacy records
• Member information, PRs, body weight and other records entered or updated through Kiosk

2.3 Information received during authentication

When Google Sign-In or Sign in with Apple is used, the Service may receive identifying information necessary for authentication, a display name, email address, profile image and other information from the selected authentication service. If a user selects “Hide My Email” with Sign in with Apple, the Service may receive a forwarding email address issued by Apple.

2.4 In-app purchase information

In-app purchases to support development are processed through the App Store (StoreKit) on iOS and Google Play’s billing system on Android. For purchases through either store, the Operator does not transmit or store payment information, full purchase receipts or transaction identifiers in Firebase or other servers operated by the Operator.

To prevent duplicate purchase completion screens and safely resume unfinished purchase processing, a hash value generated from transaction information that is difficult to reverse may be stored on the device. This information is used only on the device and is not used for advertising, user tracking, Rankings or similar purposes.

2.5 Training records

Training records, including exercises, weights, repetitions, sets, RPE, rest durations, routines and notes, are stored only in the app’s database on the device and are not sent to the Operator’s servers. However, training details and routines that a user shares in chat are stored and displayed as chat content in the Room where they are shared.

2.6 Room chat

For Room chat, the Service stores messages, shared training details and routines, message reactions, display names and images used in chat, automatic PR update posts, report contents and information about blocked users.

Photos users select as their chat icons are cropped to a square and resized in the app before being stored. Chat icon images are displayed to signed-in users.

2.7 Notification information

To send push notifications, the Service stores device notification tokens, Firebase Installations identifiers, device type (iOS / Android), app version, notification permission status, the app’s display language and notification settings for each Room. Rest timer notifications are scheduled on the device and are not sent to the server.

2.8 Announcements and monthly summaries

The Service stores delivery and read status for announcements from the Operator, and monthly summaries for Rooms the user belongs to.

2.9 Connected apps

Only when a user enables the connection, the Service receives training records, achievements and similar data from Squatdegrees, a connected app provided by the Operator, and displays them in Rankings and similar features.

2.10 Display language

The display language selected in Settings is stored on the device. It is also sent to the server as part of the notification information described above to select the language of notifications.

3. Purposes of use

The information collected is used for the following purposes.

• Creating accounts, verifying identity, maintaining sign-in status and preventing unauthorized access
• Storing, displaying and updating profiles, PRs, body weight and competition metrics
• Calculating and displaying IPF Points, GL Points, Total and Rankings
• Creating, joining, managing and displaying Public Rooms, Private Rooms and Legacy Rooms
• Providing shared features such as Room Rankings, reactions and Activity
• Providing chat and sharing features
• Delivering push notifications and announcements
• Responding to reports and maintaining safety
• Linking existing Legacy records to user accounts using Claim Codes
• Entering and synchronizing records and maintaining consistency between Kiosk and the Service
• Responding to inquiries, assisting with account deletion and addressing defects
• Maintaining and improving the safety, accuracy and functionality of the Service
• Investigating and addressing violations of the Terms of Service, misuse or security issues

4. Account authentication

The Service uses Google Sign-In or Sign in with Apple and authenticates accounts through Firebase Authentication. The Operator does not collect or store Google or Apple passwords.

Information handling by authentication services is also subject to the terms and privacy policies established by Google or Apple.

5. Information displayed in Rooms, Rankings and profiles

Depending on the Rooms and features selected by the user, display names, profile images, weight classes, competition categories, PRs, Total, IPF Points, GL Points, Rankings, reactions, Activity, social media links and other information may be displayed to other users.

• Public Room: A Room included in search results or public listings. Room information and participants’ profile and competition information may be displayed to other users according to the visibility settings of the Service.
• Private Room: A Room with entry conditions such as an invitation or approval. Information within the Room is generally displayed to participants or authorized users.
• Legacy Room: A Room containing member and competition records inherited from earlier versions of PanelPower or Kiosk. Records not yet linked to an account may exist and may be linked to the record owner’s account using a Claim Code.

Email addresses and dates of birth themselves are not used for publication in ordinary Rankings or Room profiles. However, derived information, such as competition categories determined from dates of birth, may be displayed. Users should check visibility when including personal information in social media links or similar content.

6. Claim Codes and Kiosk

Claim Codes are used to link member records already existing in Legacy Rooms or similar Rooms to the record owner’s account. Claim Code issuance, revocation and usage history and the relationship to the relevant records are processed to prevent unauthorized linking and maintain data consistency.

In Kiosk, Room operators or authorized users may enter or update member information, PRs, body weight and other information. Claimed records may be synchronized with or reflected in the owner’s account records.

7. External services

The Service uses the following services.

• Firebase Authentication: Account authentication
• Cloud Storage for Firebase: Storage of chat icon images
• Cloud Firestore: Storage of profiles, competition records, Rooms and related data
• Cloud Functions: Ranking aggregation, Claim processing, data synchronization, account deletion and other server processing
• Google Sign-In: Sign-in using a Google account
• Sign in with Apple: Sign-in using an Apple Account
• Firebase Cloud Messaging: Push notifications (via Apple Push Notification service on iOS)
• Firebase Installations: Device identification for notifications
• App Store / StoreKit: In-app purchase product display, payment and purchase completion processing on iOS
• Google Play’s billing system: In-app purchase product display, payment and purchase completion processing on Android

These services may process information under their providers’ terms and privacy policies. The Operator does not sell user information to third parties, except as required by law.

8. Information protection

The Operator takes reasonable security measures, including authentication, access control and server-side authorization checks, to prevent unauthorized access, loss, alteration or disclosure of user information. However, the security of communications over the internet or electronic storage is not fully guaranteed.

9. Retention period

User information is retained for the period necessary to provide the Service, maintain user accounts, address misuse and maintain data consistency. Once account deletion is complete, the user’s data subject to deletion is deleted progressively. However, information may be retained as necessary where retention is required by law, where needed to address disputes or misuse, or where administrative information is needed to track deletion progress, resume failed processing or confirm completion.

10. Account deletion

Users can initiate account deletion from Settings in the app. Reauthentication through Google Sign-In or Sign in with Apple is required before deletion. If a Room hosted by the user has other members or pending join requests, the user may first need to transfer host privileges or resolve the join requests.

10.1 Data deleted

Account deletion deletes the following data linked to the user.

• User information (users)
• Public profile (publicProfiles)
• Personal competition aggregates (userPersonalStats)
• Personal PR records (userLiftLogs)
• Personal body-weight records (userBodyWeights)
• Room roles and membership information (userRoomRoles, the user’s roomMembers and roomMemberStats)
• Reactions sent by the user or targeting the user’s member records
• Activity created by the user or linked to the user’s member records
• Notifications addressed to the user (notifications)
• Join requests, invitations and other related data linked to the user
• PRs, body weight, history and related data linked to the user in claimed Legacy records
• Claim Codes issued or used by the user and related information
• Chat messages sent by the user and reactions to those messages, reactions to the user, and automatic posts about the user’s PR updates
• Chat icon images
• Notification device registrations
• The user’s announcements
• Block information (users blocked by the user and blocks of the user by others)
• Connected app data
• The user’s training records stored on the device
• The user’s Firebase Authentication account

Training records stored on the device are also deleted from the device when the account is deleted.

10.2 Data not deleted

Deleting a user’s account does not delete Legacy Rooms themselves, other members, other users’ accounts or competition records belonging to other users. Room member counts, latest Activity displays and similar information may be adjusted to keep Rooms operating. A Room with only the user as a member may itself be deleted according to the app’s specifications.

Reports are retained for safety purposes. The deleted user’s author name included in a report is replaced with “削除済みユーザー” (“Deleted user”), and their profile image is removed.

10.3 Continued server-side processing

If there is a large amount of data to delete or depending on network conditions and other factors, deletion may continue on the server after the app screen is closed. Processing occurs in stages and may be retried after temporary failures. Some data may remain visible between the start and completion of deletion.

10.4 Revoking Sign in with Apple authorization

If Sign in with Apple is used, the user reauthenticates with Apple during account deletion, and the credentials obtained are used to revoke the Apple authentication link on the server. These credentials are used for revocation and are not stored as ongoing sign-in credentials. If revocation with Apple fails, deletion of the user’s data may not begin, and the user may be asked to retry.

11. User review and correction

Users can review and correct registered information through profile and record editing features in the app. For assistance with review, correction or deletion, please contact us through the Support page. Additional information may be requested to verify identity.

12. Use by minors

Minors should obtain consent from a parent, guardian or other legal representative as necessary before using the Service.

13. Changes to this Policy

The Operator may change this Policy in response to changes in the Service, external services used, laws or other circumstances. Important changes will be communicated clearly on this page or within the Service. Changes apply when published on this page or from a separately specified effective date.

14. Contact

Please contact the following support address with inquiries about this Policy or the handling of user information.