Fittery Privacy Policy

1. About Fittery and this policy

Fittery is a free Android battery monitoring and information utility developed by Saksham Sharma (UnExplainableFish52). It helps you understand battery condition, charging behavior, battery usage, and related device information. Official releases are intended to be available free of charge through Google Play and the Fittery GitHub repository.

This policy covers the official application and information you voluntarily provide to its developer. Third-party forks and external services may have different practices.

Release verification: The application's release-specific permissions, network activity, local storage, and reporting features are still being verified. Descriptions of its privacy goals below are not a confirmation that every release has been audited. This policy will be updated with verified implementation details before Google Play publication.

2. Local monitoring and personal information

Fittery's ordinary battery monitoring is designed to work locally without sending personal information to the developer. Its purpose is to provide battery readings and calculations, rather than collect names, phone numbers, postal addresses, financial details, passwords, or payment information.

Reading information on your device is different from transmitting it. Device information and logs are not necessarily anonymous: they may contain identifiers or other personal details. Information you choose to send for support and information processed independently by Google Play or GitHub are described separately below.

3. Battery and device information

Depending on the device, Android version, and features available in your release, battery monitoring may use:

• Battery percentage, charging state, temperature, and voltage.
• Charging and discharging behavior, current, power, and consumption estimates.
• Battery health and capacity estimates.
• Charging history, monitoring records, and other available Android battery metrics.

Android devices do not all expose the same measurements. Some values may be unavailable or estimated. Access to a measurement does not, by itself, mean it is saved or transmitted externally.

4. Information transmitted by the app

Local processing and minimizing unnecessary external transmission are Fittery's design goals. The exact network operations and third-party dependencies of the release must be verified before a definitive statement about transmitted data can be made.

This policy does not claim that every release has zero network activity or that device data is always anonymous. It does not identify advertising, analytics, Firebase, Crashlytics, or automatic diagnostics as implemented features without confirmation from the application source.

5. Voluntary feedback and support

You may choose to email the developer or open an issue on the project's GitHub repository. The developer receives the information you provide, such as your email address or GitHub username, message, screenshots, attachments, and any device or diagnostic details you include. This information may be reviewed to respond to your inquiry, investigate an issue, and improve Fittery.

Only share details needed to explain the issue. Logs and screenshots may contain personal or sensitive information; review them before sending. Use email for private requests. GitHub issues are public, and public reports, quotations, and copies may remain accessible even after an issue is closed or edited.

An in-app diagnostic reporting feature has not yet been confirmed. This policy does not describe automatic log uploads or an in-app feedback button as existing functionality. If optional reporting is introduced, its disclosures must identify what will be sent and to whom before you choose to submit it.

6. Support information and deletion requests

You can request access to, correction of, or deletion of personal information you have sent privately to the developer by emailing [email protected]. Identify the relevant conversation without sending unnecessary sensitive information. Any identity check should be limited to what is reasonably needed to handle your request.

The intended approach is to keep private diagnostic material only while reasonably needed to investigate and address an issue, then delete material that is no longer needed. Unresolved or unreproducible reports should also be reviewed rather than kept indefinitely without a reason. The storage locations, access arrangements, retention criteria, and deletion process still require confirmation; automatic or immediate deletion is not promised.

Email and hosting services may keep separate copies or backups under their own policies. A request to the developer cannot guarantee removal of public GitHub copies, third-party archives, or information held independently by those services.

7. Google Play, GitHub, and external services

Google Play and Android may independently process account, installation, update, performance, or crash information. The developer may receive installation statistics, performance insights, crash reports, or other reporting made available through Google Play Console. Platform reporting is separate from information transmitted directly by Fittery and does not, by itself, mean an analytics SDK is integrated into the app.

Google handles information under the Google Privacy Policy. Visiting the project repository, downloading releases, or posting issues involves GitHub's services under the GitHub Privacy Statement. Your email service also processes messages under its own terms and privacy policy.

These services may process information in countries other than your own. Their policies describe their processing and international transfer arrangements. This policy does not assert that the developer has verified a particular transfer safeguard or processing arrangement.

8. Notifications and background monitoring

Where supported by the installed release, notification permission is intended to display battery status and monitoring information. Background or foreground-service functionality is intended to continue battery-related monitoring, rather than observe unrelated private activity.

You can manage notifications and applicable app permissions in Android settings. Android may restrict background activity, and some monitoring features may depend on allowing that activity. Monitoring uses processing resources and can consume battery power; consumption varies by device and operating conditions.

The exact permission list and service behavior must be confirmed against the release. This policy does not imply that permissions or background features have been implemented simply because they are described as possible monitoring functions.

9. Local storage and your controls

Fittery's intended approach is to keep saved monitoring records, charging history, and settings on your device. Which records are actually saved, how long they remain, and whether Android backup includes them still require release verification.

Android generally provides a way to clear an app's private storage under Settings > Apps > Fittery > Storage; labels vary by device. Clearing storage resets local app data and preferences. Uninstalling generally removes app-private data, but exports, shared files, backups, and subsequently restored copies may remain.

No in-app history deletion, export, or backup control is promised unless it exists in your release. Clearing local storage does not delete messages or reports you have already sent to the developer or another service. The developer cannot delete information that remains only on your device.

10. Security and transparency

Fittery aims to limit unnecessary information access and external transmission. Your device security, Android settings, and the information you choose to share all affect privacy. No software or communication method can guarantee absolute security.

The project is hosted in the official GitHub repository. Published application source allows interested users to inspect its implementation. Open-source licensing alone does not guarantee security, privacy, or the absence of vulnerabilities.

11. GNU GPL licensing and software freedom

The project's LICENSE file contains the GNU General Public License, version 3 (GPLv3). Subject to that license, you may run Fittery, study its source, modify it, share copies, and redistribute modified versions. The license file and applicable project notices govern these permissions.

The developer provides official Fittery releases free of charge. GPLv3 also permits third parties to charge for redistribution. Charging does not remove requirements to preserve applicable copyright and license notices, provide corresponding source as required, identify modifications, and comply with the license's other terms.

Acknowledging the original project is appreciated; ordinary private use does not require public attribution. Third-party forks and redistributions must not be represented as official or endorsed by the original developer. This policy does not add a restriction on commercial use or redistribution.

12. Battery measurement limitations

Battery information may be measured, estimated, calculated, or derived from Android system APIs. Hardware and sensor limitations, manufacturer differences, Android restrictions, sampling behavior, estimation methods, and operating conditions can affect the results.

Fittery aims to provide useful information but cannot guarantee perfect accuracy. Capacity, health, power, and remaining-time estimates are not laboratory-grade diagnostics. Do not rely exclusively on these readings for financial, safety-critical, repair, or other consequential decisions.

13. Warranty and liability

Fittery is provided "AS IS", without warranties to the extent permitted by applicable law and as described in its license. You are responsible for evaluating whether its information is suitable for your needs.

Any limitation of the developer's liability is subject to the applicable license and law. This policy does not exclude mandatory consumer protections, privacy rights, or liability that cannot lawfully be excluded.

14. Privacy rights and children's information

Depending on your location and applicable law, including EU or UK data protection rules where they apply, you may have rights to access, correct, delete, restrict, or object to processing of your personal information, and to portability where applicable. Where processing relies on consent, you may withdraw that consent. You may also have a right to complain to your local data protection authority.

For information voluntarily supplied for support, the purposes are responding to inquiries and investigating issues. The applicable lawful basis, recipients, retention criteria, and any international transfer arrangements must be confirmed for the developer's actual support setup before final publication. This policy does not claim universal legal compliance or certification.

If you believe a child has sent personal information to the developer through a support channel, contact the developer to request review and removal as applicable. Do not send unnecessary personal information about yourself or a child in a public issue.

15. Contact

For privacy inquiries, data requests, feedback, bug reports, or questions about Fittery, contact Saksham Sharma at [email protected].

Technical discussions may also take place in the official Fittery repository. Use email when your request includes personal or confidential information.

16. Changes to this policy

This policy may change when Fittery's features, information handling, third-party services, or applicable requirements change. Material changes will be reflected in the published policy, with an updated date.

The latest version is available at saksham.info.np/fittery-privacy.html.