1. Local App Data
FillRam is an Android memory-pressure testing and benchmarking utility. It reads physical RAM, swap, low-memory state, timing, app allocation, device model, Android version, and app version. Calibration and Benchmark can record frequent samples in a local SQLite database and may read Android process-exit information to classify an unfinished calibration. FillRam does not upload these readings, samples, settings, or test history to an ex4.dev server.
Selected settings, the current calibration, the latest Free Benchmark result, saved or interrupted Pro history, and cached Pro entitlement state are stored in FillRam's private app storage. FillRam does not identify which other apps Android removes from memory. A text or CSV report leaves FillRam only when you explicitly export it through Android's share sheet; an export can include device, calibration, result, and sample-timeline data.
2. Google Play Billing
FillRam uses Google Play to display subscription products and prices, start purchases, restore active purchases, and acknowledge them. Google processes your Google account and payment details under its own policies.
FillRam reads the product, purchase state, and purchase token needed to provide and acknowledge Pro. FillRam does not receive your card or bank details.
3. Free-Tier Advertising
After Google Play confirms that no active Pro entitlement exists, the Free tier may initialize Appodeal and its mediated advertising partners. These partners may process advertising identifiers, IP address, device and network details, ad events, diagnostics, measurement, and fraud-prevention signals under their own policies.
FillRam does not request precise or approximate location permission. While an active Pro entitlement is confirmed, FillRam does not request or cache banner ads. FillRam also suppresses banner requests while calibration, Benchmark execution, or Benchmark result screens are active.
For more information, see the Appodeal Privacy Policy and Google Privacy Policy.
4. Privacy Choices
Where Appodeal's consent manager reports that a privacy entry point is required, FillRam shows a Privacy choices item in its menu. It opens the provider's consent, re-consent, or opt-out form. This entry point can remain available after Pro is active so you can review earlier advertising choices.
5. Retention and Deletion
You can delete individual local history entries or clear history from the History screen. Recalibration replaces the previous valid calibration only after the new calibration is accepted. FillRam keeps one latest completed Free Benchmark result and can keep up to 100 entries in each Pro history section under the app's current retention rules.
AI explanations are cached separately in private app storage, with up to 20 cached explanations. Deleting a history entry does not necessarily remove its cached explanation immediately. Clearing FillRam's app storage or uninstalling it removes local settings, calibration, samples, history, cached AI explanations, and cached entitlement state. Google Play retains subscription and transaction records under Google's own policies.
6. On-Device AI
On supported Android devices, FillRam Pro can use Google's ML Kit GenAI Prompt API and Gemini Nano to explain a completed performance benchmark. FillRam provides benchmark-derived categories, cautions, and application-selected guidance to the on-device model, not raw memory contents, payment details, or advertising identifiers. FillRam does not send prompt content or generated explanations to an ex4.dev server.
On-device processing does not mean that Google services never use the network. Compatibility checks and model delivery may contact Google services. ML Kit collects operational and usage data, including device and app information, identifiers, performance, API configuration, input and output sizes, feature versions, configured languages, events, and error codes for diagnostics and usage analytics. Google states that this SDK data is encrypted in transit using HTTPS.
Requesting an explanation is optional. Availability checks can also occur when opening results or the Pro screen, before an explanation is requested. For details, see Google's ML Kit data disclosure and the Google Privacy Policy.
7. Contact
For privacy questions, contact contact@ex4.dev.