App: AppHelpMe - Farm Manager
Package: com.apphelpme.app
Website: apphelpme.com
# AppHelpMe: Farm Manager Privacy Policy
**Effective date:** September 22, 2026
**Last updated:** September 22, 2026
## Privacy update for new features — September 22, 2026
This update supplements the detailed Privacy Policy below and describes the privacy practices of the following AppHelpMe features:
- Grain Counter
- Bluetooth Low Energy (BLE) Rice Scale and BLE Auto
These features are designed primarily for local and offline use. Except when the user deliberately exports or shares data, AppHelpMe does not upload the images, grain-counting results, or BLE scale readings described in this update to a developer-controlled server.
### Grain Counter
When the user chooses Grain Counter, AppHelpMe may process:
- One image deliberately selected through the operating system's file picker
- A normalized, app-owned copy of the selected image
- Image orientation, rotation, crop, scale, and display transformations
- Automatically detected or manually added grain markers and their positions
- Grain counts and manually corrected counts
- Review regions, warnings, notes, verification status, edits, and timestamps
The selected image is copied to AppHelpMe's private application storage so the saved result can be reopened. The image, count, markers, and related result data are processed and stored locally on the device.
Grain Counter uses local image-processing code. It does not upload the selected image or counting result to an artificial intelligence service, analytics provider, advertising provider, or developer-controlled server.
Grain Counter uses the operating system's file picker. It does not open the camera and does not request camera permission, unrestricted storage access, or access to the user's entire photo library for this feature.
Deleting a saved Grain Counter result removes its local database record and the corresponding app-owned image when that image can be safely identified as belonging to Grain Counter. The original image selected from outside AppHelpMe is not deleted.
Clearing application storage or uninstalling the app may also remove locally stored Grain Counter images and results. Copies intentionally exported or shared outside AppHelpMe are controlled by the user and the selected destination application.
The automated grain count is an assistive estimate that the user can review and correct. It is not a guaranteed scientific measurement.
### BLE Rice Scale and BLE Auto
When the user deliberately starts a BLE scale feature, AppHelpMe may use Bluetooth Low Energy to:
- Scan for compatible electronic scales or user-started test simulators
- Connect to a selected scale or simulator
- Receive numeric scale readings
- Advertise a test scale or relay when the user starts simulator or BLE Auto mode
- Exchange notifications and control messages directly among participating nearby devices
- Display connection, role, relay, and subscriber status
Depending on the selected BLE role, AppHelpMe may temporarily process or transmit:
- Nearby BLE device names
- Platform-provided device identifiers
- A custom BLE advertised name selected by the user
- A four-digit connection identification code
- Numeric and normalized weight readings
- Temporary protocol version, role, session, source, event, and reading-sequence identifiers
- Capture-control messages
- Connection and subscriber status required for the active session
The four-digit identification code helps users distinguish nearby AppHelpMe BLE transmitters. It is not a password, authentication credential, security PIN, or guarantee that a nearby device is trusted.
A custom BLE advertised name and the four-digit identification code may be visible to compatible nearby devices while advertising is active. Users should not include names, phone numbers, addresses, or other personally identifying information in a custom BLE advertised name.
BLE Auto uses a versioned capture event so an opted-in follower device can validate and save the corresponding weighing entry. A raw weight reading alone does not trigger an automatic save.
Temporary session, source, sequence, and event identifiers are used to reject mismatched, stale, replayed, echoed, reordered, or duplicate events.
BLE communications occur directly between the compatible electronic scale, test simulator, and participating nearby devices. AppHelpMe does not route BLE scale readings or capture-control messages through a developer-controlled server and does not retain a server-side copy.
AppHelpMe does not use BLE scale data for:
- Targeted advertising
- Analytics based on nearby devices
- Physical-location tracking
- Movement tracking
- Behavioral profiling
- Tracking users across applications or websites
On supported Android, IOS versions, AppHelpMe may request Bluetooth scan, connect, and advertise permissions. On supported Apple devices, AppHelpMe may request Bluetooth access.
These permissions are used only for the nearby scale, simulator, relay, and BLE Auto functions deliberately started by the user.
Other people operating participating nearby devices may see a scale reading or resulting saved entry. Users should connect only to devices they recognize and control. Wireless communication and third-party electronic scales cannot be guaranteed to be completely secure.
BLE discovery results, connection information, identification codes, and protocol session state are normally temporary. They are cleared when the relevant session ends, the user leaves the BLE role, all Bluetooth connections are closed, or the app process terminates.
Weighing entries intentionally captured by the user, or saved through a validated BLE Auto event on an opted-in follower device, are stored locally and remain until deleted under AppHelpMe's applicable retention behavior.
### Screen-awake behavior
AppHelpMe may temporarily keep the screen awake while the Rice Scale weighing page is visible and the app remains in the foreground.
This behavior does not collect, store, or transmit personal data. It ends when the relevant page closes, the app leaves the foreground, or the operating system terminates the app session.
### Combined local-data retention
Data created through Grain Counter, BLE Rice Scale, and BLE Auto generally remains on the user's device until the user deletes it, clears application storage, or uninstalls AppHelpMe.
AppHelpMe does not guarantee recovery after data deletion, application-storage clearing, device loss, operating-system reset, or app uninstallation.
Information intentionally exported, shared, copied, or backed up by the user may remain with the selected destination application or storage provider after the local AppHelpMe copy is deleted.
### User control
The user controls whether to:
- Select an image for Grain Counter
- Save or delete a grain-counting result
- Start BLE scanning or advertising
- Connect to a nearby BLE device
- Join a BLE Auto role
- Choose a custom advertised BLE name
- Export or share supported data
Refusing an optional permission prevents the related feature from operating but should not prevent the user from accessing unrelated AppHelpMe Manager that do not require that permission.
## 1. Introduction
This Privacy Policy applies to the AppHelpMe mobile application, including localized names such as **AppHelpMe: Farm Manager **, **Farm Manager**, and **Cân Lúa & Nhật Ký**.
AppHelpMe is developed by **Phan Hoang Sang**.
- Android application ID: `com.apphelpme.app`
- iOS bundle identifier: `com.apphelpme.app`
- Android version: `2.4.1`, build `154`
- iOS version: `2.4.1`, build `154`
- Website: https://www.apphelpme.com/
- Website: https://www.apphelpme.com/
AppHelpMe is a local-first toolkit for rice weighing, fertilizer calculations, field records, calendars, and everyday calculations.
The app does not require an AppHelpMe account, registration, login, or password.
## 2. Information entered by users
Depending on the tools used, users may enter or create the following information.
### Rice Scale
- Farmer and group names
- Optional phone numbers
- Weighing records
- Weight, tare, impurity, price, deposits, and payments
- Payment status
- Weighing history
- Voice and display preferences
### Fertilizer Calculator
- Fertilizer names and formulas
- N-P-K values
- Quantities and target weights
- Land area and application rates
- Stock quantities
- Fertilizer mixing calculations
- Saved results and generated reports
### Field Journal
- Field names and codes
- Crop seasons and varieties
- Planting and harvest dates
- Farming activities and notes
- Materials, products, suppliers, prices, and quantities
- Expenses and harvest information
- Photos, captions, and cover images
- Local backup and export information
### Lunar Calendar
- Saved dates
- Titles, notes, labels, colors, and attachments
- Calendar preferences
- Reminder settings where supported by the platform
### Utility Calculator
- Expressions and calculation results
- Optional notes
- Saved and pinned calculations
- Ordering preferences and timestamps
### Random Code Generator
- User-entered source text
- Optional titles
- Generated codes
- Saved history and generator settings
The app may calculate totals, balances, fertilizer quantities, nutrient values, and other results from information entered by the user.
Users are responsible for having an appropriate reason or permission to enter information about other people, including names and phone numbers.
## 3. Local storage
AppHelpMe is designed primarily as an offline, local-first application.
User-created records are stored on the device using:
- Private application storage
- Local databases
- Application preferences
- Local image and file storage
Photos selected by the user may be copied into the app's private storage so they remain available to the related feature.
Core features do not require an internet connection or an AppHelpMe account.
AppHelpMe does not automatically upload user records, photos, calculations, journal entries, or calendar data to a developer-controlled server.
## 4. Optional folder storage
Android version 2.0.1 may offer an optional Pro feature for copying Field Journal photos to a folder selected by the user.
Depending on the operating system and installed file providers, available locations may include:
- On-device storage
- iCloud Drive on supported Apple devices
- Google Drive through the system file provider
- OneDrive through the system file provider
- Other compatible file providers
The user must deliberately choose the folder through the operating system's file picker.
AppHelpMe only uses the folder and files for which the operating system grants access. It does not request unrestricted access to the user's entire Google Drive, OneDrive, iCloud Drive, or device storage.
AppHelpMe does not request:
- A Gmail address
- Google OAuth authorization
- Access to Gmail messages
- Google Drive passwords
- Google Drive security credentials
If a provider application requires sign-in, that sign-in is handled by the provider application or the operating system, not by AppHelpMe.
Selecting a folder does not automatically upload photos. Photos are copied only after the user explicitly starts synchronization.
In the current iOS release, version 1.2.3 build 72, Drive Pro is not publicly offered. Feature availability may differ between platforms and app versions.
## 5. Folder synchronization and image metadata
When optional folder storage is available and enabled, AppHelpMe may:
- Copy selected Field Journal photos to the selected folder
- Create or use app-managed subfolders
- Read files inside the selected folder
- Store file names, file sizes, file types, checksums, and provider references
- Create thumbnails for local display
- Reconnect restored journal images using stable app-generated image identifiers
- Read an original image temporarily when the user requests a full export or backup
The app may store a stable, app-generated image identifier in the file name or available file metadata. This identifier helps reconnect the correct image after a backup restore, device change, folder move, or provider change.
AppHelpMe does not automatically delete files from the selected provider folder during synchronization or relinking.
Temporary full-size image copies used for backup or display are removed after they are no longer needed.
## 6. Backups and exports
Users may create JSON, ZIP, PDF, image, or other exports using system sharing and file tools.
A backup may contain:
- User-created records
- Journal and field information
- Calculation history
- Image identifiers
- File names and image metadata
- Synchronization status
- Non-secret provider references
A backup does not contain:
- Passwords
- Payment-card information
- Apple Account passwords
- Google Account passwords
- Apple or Google authentication tokens
- Refresh tokens
- Secret signing credentials
If the user chooses to include full-size images, AppHelpMe may first synchronize pending photos to the selected folder and then include accessible originals from local storage or that selected folder.
If the selected provider folder is unavailable, the full image backup may not complete. AppHelpMe should not silently create a backup that claims to contain images that could not be read.
A backup without images contains records and metadata but does not contain the original image bytes.
## 7. Disconnecting a file provider
Users may disconnect or change the selected folder from within AppHelpMe.
Disconnecting a provider:
- Stops new synchronization to that folder
- Removes the local folder connection or bookmark where supported
- Does not delete files already stored in the provider folder
- Does not delete local journal records automatically
- Does not delete user files from Google Drive, OneDrive, iCloud Drive, or device storage
The user may also disable or remove a provider through the operating system's Files or storage settings.
Provider sign-in, account management, and access revocation are handled by the provider and the operating system.
## 8. Purchases and paid features
Paid features are processed by:
- Apple App Store and StoreKit on iOS
- Google Play Billing on Android
Paid features may include separate one-time non-consumable purchases such as:
- Rice Scale Pro
- Drive Pro on supported platforms and builds
The app may receive product identifiers, transaction identifiers, purchase status, entitlement status, refund status, and revocation status.
AppHelpMe does not receive or store complete payment-card details.
If a purchase is refunded, revoked, or no longer valid, AppHelpMe may disable new Pro actions related to that purchase.
Refunding or revoking a purchase does not automatically delete:
- Existing journal records
- Local photos
- Files already stored in a provider folder
- Backups
- Remote files in Google Drive, OneDrive, or iCloud Drive
## 9. Device features and permissions
Depending on the feature selected, AppHelpMe may use:
- Photo and file pickers
- Local application storage
- Apple Files or Android system file providers
- Photo Library access
- System share sheets
- Text-to-speech and locally stored audio
- Local notifications or reminders where supported
- External websites or communication applications
These functions are activated only when the user selects the related feature.
AppHelpMe does not use:
- Camera capture
- Location tracking
- Contact-list access
- Microphone recording
- App Tracking Transparency
- Advertising tracking
- Health data
- Bluetooth tracking
Text-to-speech uses the device's system voice or a user-selected local audio file. The app does not record microphone audio.
## 10. Data sharing and third-party services
AppHelpMe does not sell or rent users' personal information.
Users may intentionally export, save, or share records, images, reports, and backups through the operating system's share sheet or another application selected by the user.
The selected destination application may process the shared information under its own privacy policy.
The services used by AppHelpMe may include:
- Apple App Store and StoreKit
- Google Play Billing
- Apple Photo Library
- Apple Files
- Android system file providers
- Google Drive or OneDrive provider applications when installed and selected by the user
- System share sheets
- The AppHelpMe website for optional guide, privacy, and support pages
Core calculations and local records are processed on the device.
AppHelpMe does not use:
- Firebase
- An AppHelpMe account server
- Google OAuth
- Google Drive API
- Advertising SDKs
- Analytics or tracking SDKs
- Artificial intelligence services
- A third-party payment processor
- A developer-controlled photo server
## 11. Regional and platform differences
The core tools are intended to work consistently across supported regions.
Differences may include:
- Language and localization
- Number and date formatting
- Currency and tax
- Store pricing
- System voice availability
- File-provider availability
- Local notification support
- Platform-specific Pro features
Google Drive, OneDrive, iCloud Drive, and other providers appear only when supported by the operating system, installed, enabled, and available on the user's device.
## 12. Agricultural and calculation information
AppHelpMe is a general agricultural record-keeping and calculation utility.
Fertilizer, cost, calendar, and weighing results are provided for reference and calculation assistance only.
Users should verify important results and adjust agricultural decisions according to actual field conditions and qualified professional recommendations.
Rice-weighing records do not replace official transaction documents, contracts, invoices, or procedures required by organizations or authorities.
## 13. Data retention and deletion
Local data remains on the device until the user:
- Deletes the related record
- Deletes related photos or files through the app
- Clears application storage
- Uninstalls the app
When a record containing an app-managed local attachment is deleted, its related private local attachment may also be removed.
Local thumbnails, temporary files, pending upload files, and caches may be removed when they are no longer needed.
Files exported or shared outside AppHelpMe are not automatically deleted when local records are deleted.
Files already copied to Google Drive, OneDrive, iCloud Drive, or another provider remain there until the user deletes them through that provider or confirms an explicit deletion action offered by AppHelpMe.
Users should create an appropriate backup before clearing app data, uninstalling the app, or changing devices.
## 14. Security
AppHelpMe uses the storage, access-control, and authentication mechanisms provided by the operating system and the selected service provider.
The app does not intentionally store account passwords, payment-card details, or authentication tokens in exported backups.
Users should protect their device, provider accounts, and exported backup files.
No storage or transmission method can be guaranteed to be completely secure.
## 15. Children
AppHelpMe is not specifically directed to children.
AppHelpMe does not knowingly collect children's personal information through a developer-controlled server.
Parents or guardians may contact us using the details below if they have privacy questions.
## 16. Changes to this Privacy Policy
This Privacy Policy may be updated when AppHelpMe's features, permissions, platforms, or data practices change.
The updated policy will be published on the official website or application listing with a revised effective date or last-updated date.
## 17. Contact
For privacy questions or requests, contact:
- **Developer:** Phan Hoang Sang
- **Email:** [email protected]
- **Website:** https://www.apphelpme.com/