Remote Stopwatch
Privacy Policy
This page explains how information is handled in Remote Stopwatch. The Japanese version is the authoritative version.
1. Scope
This policy applies to information handled in connection with Remote Stopwatch. Remote Stopwatch is a non-official measurement app that uses two or more smartphones to measure time between separated points such as a start point and a goal point. Devices assigned as START and STOP participants join the same measurement room, and the app corrects press timestamps and displays the result. It is intended for training, practice, events, and casual use rather than official competition timing.
2. Information not intentionally collected
The initial version is not intended to collect the following information:
- Name
- Email address
- Location information
- Contacts
- Photos
- Audio
- Files stored on the device
- Camera footage or video
If future features add goal-confirmation video correction or similar processing, this policy will be updated before release.
3. Information that may be handled
- Room ID, Client ID, joinSecret, and temporary connection data similar to a session token
- Device role information such as host, starter, stopper, and viewer
- Optional labels such as device name, lane label, and runner name
- START events, STOP events, and START/STOP press timestamps
- Measurement results such as elapsedMillis, ranking, and history
- RTT, offset, estimated error, and WebSocket connection status
- Communication status, diagnostic logs, and test-log fields such as appPhase
- Advertising identifiers or related data handled by ad SDKs when AdMob ads are shown
- Purchase state, subscription state, purchase restoration result, and Billing error state handled through Google Play Billing
Device name, lane label, and runner name are optional labels. They can be general labels such as "Lane 1", "Device A", or "Finish judge". If a personal name is entered, it may be shown to other devices in the same room or in copied/shared result text.
4. Purpose of use
- Create, join, and maintain measurement rooms
- Synchronize START and STOP events
- Calculate corrected times
- Display results and history, and create copy/share text
- Display connection status and estimated error
- Investigate issues and respond to inquiries
- Determine Free/Team extension restrictions, ad display, measurement stock, and STOP/Viewer device limits
5. Retention period
Room information and connection information are generally handled temporarily only to the extent needed to maintain the measurement room and display results. In-app history may be stored on the device. If the user sends logs such as Copy test log, they may be used for support and troubleshooting.
If long-term cloud history storage is introduced in the future, this policy will be updated.
6. Third-party services, ads, and billing
Personal information is not sold. Infrastructure services such as Cloudflare may be used for server communication.
The Free version and Team extension show banner ads and rewarded ads through Google AdMob. Google may handle advertising identifiers or related data. Team extension still shows ads.
Google Play Billing is used for Team extension subscription purchase, purchase-state checks, purchase restoration, and subscription management. Google may handle purchase state, subscription state, purchase restoration results, and Billing error state. Payment card information is not directly obtained by the developer.
Team extension status is used only to expand the connection capacity of Rooms created or updated by the START device. Team extension allows up to 10 STOP devices, up to 10 Viewer devices, and up to 21 total Room clients. Measurement stock is the same as Free: 5 initial measurements, +3 per rewarded ad, and a stock cap of 30. STOP devices and participants do not need Team extension. The START device's Team extension status is applied to the Room.
Secret values such as purchaseToken, signing keys, and service-account keys are not intentionally included in Copy test logs, copied result text, CODEX_RESULT files, public repositories, or ZIP artifacts.
7. Use by children
This app is not primarily intended for children under 13. If a minor uses the app, use should be decided by a parent or responsible guardian.
8. Security
Public releases are intended to use secure communication methods such as HTTPS and WSS. Development-only local connections such as debugLocal are not intended for public release. Signing keys, secrets, and tokens are not included in the public repository.
9. Revisions
This policy may be revised as needed. The latest version will be published on this page.
10. Contact
Contact for this policy: nishigon.app.support@gmail.com