Privacy Policy
Hinge Counter · updated 2026-10-21
Your counter stays on your device
Hinge Counter stores daily recorded opening totals, manual and observed count attribution, dates and your tracking preference in the app sandbox. The app does not send these records to the developer. It has no accounts, advertising, tracking or third-party analytics SDKs.
Hinge observations
On supported hardware, the app uses live hinge observations while an app scene is active. Angle and observation timing are processed locally to recognize a close-to-open movement. Raw angle samples are not saved in your history. Missed openings during lock, suspension or use of another app are not reconstructed.
Widgets, backups and exports
The app shares a copy of saved totals with its own widget extension through an App Group on this device. Your operating-system backup settings may include app data. CSV and JSON files leave the app only when you choose an export or sharing destination. Those services process your files under their own policies.
Retention and deletion
Records remain until you erase them, replace them by restoring a backup, or remove the app and its data. Settings > Erase all counts clears the in-app history and attempts to replace the widget snapshot; check the widget status afterward. Copies in device backups, exported files, a destination service or a previously rendered widget are not remotely erased. Manage those copies with the relevant system or service.
Support and external websites
Opening a support or privacy link hands the URL to your browser. GitHub hosts this website and the public issue tracker and may process connection information under its own privacy statement. If you file an issue, information you choose to submit is public and processed by GitHub. Do not include backups, personal identifiers or private information. The app never uploads a support report automatically.
Contact and changes
Contact the project maintainer through the linked GitHub issue tracker with non-sensitive questions. This policy applies to the functionality described here. We will update it when that functionality or data handling changes.
Contact the maintainer via a public GitHub issue. Do not post private information.