Privacy Policy
Refrigerant Log: EPA 608
1. What this policy covers
This policy describes the checked-in Android app source reviewed on October 2, 2026. The app works without a user account. A previously distributed app version may behave differently from the reviewed source. This app is an independent record-keeping utility; it is not affiliated with or endorsed by the U.S. Environmental Protection Agency (EPA), and it does not verify technician certifications or determine regulatory compliance.
2. Information you enter
You may save a technician's name, EPA 608 certificate number and type, company and phone; equipment site name and address, equipment identifier and type, refrigerant, charge details, owner contact and notes; and service dates, service type, technician details, quantities added or recovered, leak-rate estimate, test method, leak location, verification dates and results, and notes.
The reviewed source stores these records in app-private on-device preferences. It does not upload these work records to a developer-operated account or record-sync service. Android backup is disabled in the checked-in app manifest. This does not protect data if someone can unlock or otherwise access your device. The checked-in Android data-extraction rules also exclude app data from device-to-device transfer. Some Android 12+ manufacturers may still allow migration; behavior has not been verified across manufacturers.
3. Reports and sharing
Service-history PDFs are generated on your device. The app sends a PDF outside itself only when you choose an Android print, save, or share destination. That destination and any recipient then handle their copy under their own practices. The report labels its rate values as informational estimates and does not submit records to the EPA.
4. Optional campaign notifications
The app includes an optional campaign-announcement setting. The reviewed source does not request notification permission or join campaign topics automatically. If you opt in and allow notifications, Firebase Cloud Messaging processes a device registration token, the app/category/portfolio topic subscriptions needed for delivery, and related delivery data. Your equipment and service records are not used for campaign targeting.
You can turn campaign announcements off in the app. The app then requests topic removal, disables FCM auto-initialization, and requests token deletion. Firebase may retain technical delivery data under its own policies; the app cannot confirm provider-side deletion.
5. Optional Google Play purchase
The source contains an optional Google Play lifetime Pro purchase integration. It is available only when the app is built for Google Play with a secure purchase-verification endpoint configured and the store offers the product. If you purchase, Google Play handles payment. For verification, the app may send the package name, product ID, purchase token, and purchase source to the configured verification service. The app does not receive your payment-card details. The exact production configuration and server retention settings were not verified in this source review.
6. Advertising
No Google Mobile Ads SDK or ad-loading placement was found in the reviewed Android source or dependency lockfile. An unused local configuration file contains ad-unit identifiers, but no reviewed app code loads ads. The behavior of older distributed versions has not been verified.
7. Permissions and network use
The app's main Android manifest declares internet access for configured Firebase messaging and purchase verification, and notification permission for campaign notifications. The final merged permissions of a newly built release must be checked because Android libraries can contribute permissions during packaging.
8. Storage, retention, and deletion
Your saved profile, equipment, and service records remain in the app's local storage until you delete them, clear the app's storage in Android settings, or uninstall the app. A PDF already printed, saved, or shared must be deleted from that destination separately. Campaign-registration and purchase-verification data handled by Firebase, Google Play, or the configured backend follow those providers' retention rules; those server-side rules were not verified here.
9. Children
This service-record utility is designed for refrigeration and air-conditioning technicians and businesses, not children. It does not request a user's age. If you have a privacy question, contact us using the address below.
10. Official information and contact
For current rules, consult official EPA information such as the EPA HFC use and reuse resources and EPA Section 608 questions and answers. The app's estimates are not a substitute for those rules or qualified advice.
For questions about this app's privacy practices, contact raghebtube@gmail.com.