Publicvoid Apps Privacy Policy

Privacy owner: Publicvoid Apps

Developer: Publicvoid Dev

Country/region: Indonesia

This policy explains privacy practices for covered applications provided by Publicvoid Dev. Applications may be provided at no cost and as-is. Their features, local data, and third-party services can differ, so this policy does not claim that every covered application behaves identically.

Applications Covered

This policy covers Publicvoid applications that link to this shared policy URL, including:

• MenuCost;
• MotoIngat;
• Renungan Pagi App; and
• wallpaper applications published by Publicvoid Dev.

An application's store listing, in-app notice, permissions, and the app-specific section below provide additional context. A service named in this policy is not necessarily present in every covered application or version.

Information Collection and Use

Covered applications may ask users to provide information needed for their features. Some information may remain only on the device, while third-party libraries may process technical or usage information. The applicable behavior depends on the application and version. Publicvoid Apps does not sell user-provided MenuCost business data and does not make a portfolio-wide claim that no data is collected.

Third-Party Services

Depending on the application and version, third-party services may include Google Play services, Google Mobile Ads (AdMob), Google Analytics for Firebase, Firebase Cloud Messaging, or OneSignal. These providers may process information under their own terms, such as IP address, device or advertising identifiers, app interactions, diagnostics, push-notification tokens and interactions, and consent signals. Not every covered application uses every listed service.

• Google Privacy Policy
• AdMob privacy information
• Firebase privacy information
• OneSignal privacy information

Log Data

If an application or third-party service encounters an error, technical log or diagnostic data may be processed. Depending on the service, this may include an IP address, device model, operating-system version, application configuration, event time, and related statistics. Publicvoid Apps does not claim that the same logging service is present in every covered application.

Cookies and Similar Technologies

Covered Android applications do not necessarily use browser cookies directly. Third-party code, advertising services, or external websites opened from an application may use cookies or similar technologies under their own policies and user controls.

Service Providers

Third parties may help provide, maintain, advertise, secure, or analyze a covered application. They may process information only as permitted by their role, terms, and applicable law. The providers used can vary by application and version.

MenuCost

Local business data

MenuCost stores ingredients, recipes or menu data, quantities, prices, costing data, selling prices, preferences, and settings locally on the user's device. MenuCost has no user account and no custom MenuCost backend. Cloud backup and device-transfer backup are disabled. Local data remains until the user edits or deletes it, clears MenuCost storage, or uninstalls the application.

Advertising and consent

MenuCost uses Google Mobile Ads for banner and interstitial advertising and Google's User Messaging Platform (UMP) for consent and privacy choices where applicable. Google's SDK may process or share technical and usage information such as IP address, approximate location inferred from network information, device or advertising identifiers, app interactions, diagnostics, and consent signals for purposes described by Google, including advertising, analytics, security, and fraud prevention.

MenuCost's own ingredient, recipe, price, and costing records are distinct from data processed by Google's advertising services: the reviewed MenuCost source does not send those business records to a Publicvoid Apps backend. The MenuCost source reviewed on August 21, 2026 contains no separate analytics or tracking SDK beyond the processing associated with Google Mobile Ads and UMP.

Network and offline use

MenuCost requests internet and network-state access for advertising and consent. Its core ingredient, recipe, costing, pricing, insights, settings, and in-app guide features are designed to remain usable offline. Advertising and consent services may be unavailable without a network connection and must not block core use.

MotoIngat

MotoIngat is an offline-first motorcycle service and expense tracker for Android. It helps an owner record maintenance history, fuel fill-ups, running costs, and service reminders for their own motorcycles.

Information stored on your device

MotoIngat stores the following only on your device, in the app's private storage:

• motorcycles you add (nickname, brand/model, year, type, notes);
• odometer readings;
• fuel records (date, odometer, volume, cost, fuel type, full/partial tank, notes);
• service records (date, odometer, service type, parts/labour/other costs, workshop name, notes, next-due date or odometer);
• other expense records (date, category, amount, optional odometer, notes);
• reminders (title, linked service type, due date and/or due odometer, advance thresholds, completion state); and
• app settings (language, theme, currency, distance unit, reminder defaults).

This information is not transmitted to Publicvoid, is not synchronised to any cloud service, and is not shared with any advertising partner. Every calculation in the app — fuel economy, cost per distance, monthly totals, reminder status — runs on your device from the records you entered.

No account

MotoIngat has no sign-in, no user account, no profile, and no identifier that Publicvoid could use to recognise a person or a device across installations.

No Publicvoid backend or cloud sync

Publicvoid operates no server component for MotoIngat. There is no backend API, no telemetry endpoint, no crash-reporting service, and no analytics SDK in the app. Publicvoid does not receive your maintenance records at all.

Notifications

MotoIngat asks for the Android notification permission the first time you create a reminder, so it can alert you when a service is due. Reminders are evaluated entirely on your device. Declining the permission does not disable reminders — they still appear inside the app; you simply do not receive a system notification.

Backups and exports (only when you ask)

MotoIngat can produce three kinds of file, each only on your explicit request: a JSON backup of your records and settings, a CSV export of a motorcycle's records, and a PDF service-history export for a motorcycle.

Each file is written to a location you choose through the Android system file picker, or shared through the Android share sheet to an app you pick. Once a file leaves MotoIngat it is governed by wherever you sent it — your cloud drive, email provider, or messaging app — not by this policy. Publicvoid never receives these files.

Ad-frequency counters and consent state are internal to the app and are deliberately excluded from backup files.

Advertising: Google AdMob and the User Messaging Platform

MotoIngat is free and displays advertising supplied by Google AdMob. Consent is handled by the Google User Messaging Platform (UMP), which presents Google's own consent form where that is required in your region.

Your motorcycle and maintenance records are never sent to Google and are never used to target advertising.

To deliver and measure advertising, Google may collect and process information such as:

• advertising and device identifiers (for example the Android Advertising ID);
• device and app information (model, operating system version, app version, language);
• your IP address, and the approximate location inferred from it;
• advertising interactions, such as ad views and clicks;
• diagnostic information about ad delivery; and
• the consent and privacy signals recorded for your device.

Exactly what is processed depends on your consent choice and on Google's own policies, not on MotoIngat. Google's handling of this information is governed by Google's privacy policy and how Google uses information from sites or apps that use its services.

What Publicvoid can and cannot see. MotoIngat's own code never reads, stores, logs, or transmits your advertising identifier, and Publicvoid receives no per-user ad-interaction record through the app. As the AdMob publisher, however, Publicvoid can view aggregated reporting in the AdMob console — for example impression counts, click counts, click-through rates, estimated earnings, and breakdowns by ad unit, country, platform, and date. That reporting is aggregated and is not tied by Publicvoid to an individual person.

MotoIngat is a general-audience app intended for adult motorcycle owners. It is not directed to children, and it requests ads configured accordingly. MotoIngat does not ask for, infer, or store your age, and contains no age gate.

Your consent choices

Where consent is required in your region, Google's consent form is shown before personalised advertising is requested. You can review or change your choice at any time from Settings → Privacy & ads → Privacy options inside the app.

That control is enabled only when Google's consent framework reports that a privacy-options entry point applies to your region and current consent state. Where UMP does not require one, the row remains visible but is shown as unavailable. This is Google's determination, not a MotoIngat setting.

If you decline, are offline, or the consent service is unreachable, MotoIngat continues to work normally — you simply may not see ads.

MotoIngat retention and deletion

• Your records remain on your device until you delete them.
• Individual records can be deleted from History.
• Settings → Delete all data permanently removes every motorcycle, record, and reminder stored by the app on that device.
• Uninstalling MotoIngat removes the app's local storage, including all records and the ad-frequency counters.
• Backup or export files you saved elsewhere are not affected by deleting data in the app or by uninstalling it. Delete those yourself if you no longer want them.
• Publicvoid holds no copy of your motorcycle or maintenance records and therefore has nothing of yours to delete on that front.
• Data processed by Google for advertising is held by Google, subject to Google's retention practices and to the controls in your Google account — including Android's "Delete advertising ID" and ad-personalisation settings. Publicvoid cannot delete Google-held advertising data on your behalf, and the aggregated AdMob reporting described above is not deletable per person because it is not per person.

Renungan Pagi App

Renungan Pagi App, currently distributed on Google Play as Renungan Harian Pagi 2026, provides devotional readings, prayers, Bible verses, reflection content, images, and related material. Unlike MotoIngat and MenuCost, it is a network-backed content application: it connects to a Publicvoid content server to obtain current content, categories, application configuration, and advertising configuration.

Local favorites, history, and settings

The app stores preferences such as theme, text size, notification choices, and current application configuration. If you add a reading to Favorites, it stores a local copy of that item's title, category, date, description, image or video references, content type, and related identifiers in an on-device SQLite database. Search terms are kept in local search history until you clear that history. Images and other content may also be cached on the device.

You can remove individual favorites, clear search history and cached content from the app, or clear the app's storage through Android settings. The app does not provide a manual backup or bulk export feature. Android backup is enabled, so Android or the device provider may back up and restore eligible app data according to the user's device and account settings. Images that you explicitly download, or content that you share to another app, are outside the app's private storage and are not removed automatically when local app data is cleared.

Content server, searches, and interactions

To operate, the app sends network requests to the Publicvoid content server. These requests can include the app package, requested content or category, in-app search terms, and identifiers for content that is opened. Opening a reading can update an aggregate view count on the server. As with ordinary internet requests, the server and its hosting infrastructure may receive technical information such as IP address, request time, response status, and user-agent or device/app information. This information is used to deliver content, maintain the service, understand aggregate content use, diagnose errors, and protect the service.

The reviewed live configuration has sign-in and comments disabled. The current app therefore does not ask users to create a Renungan Pagi account or submit comments. Although dormant account and comment code exists in the application package, those features are not available under the reviewed server configuration. The policy must be updated before those features are enabled.

Push notifications

Renungan Pagi uses server-driven push notifications rather than local reminder scheduling. OneSignal and Google Firebase Cloud Messaging may process a push subscription or installation identifier, notification token, device and app information, IP/network information, and notification-delivery or engagement events. The app requests Android notification permission where the operating system requires it. You can disable notifications through Android settings; doing so stops their display but may not immediately delete identifiers already retained by a push provider under its policy.

Advertising, analytics, and consent

The reviewed live configuration enables Google AdMob advertising, including banner, interstitial, and app-open placements, with no backup advertising network selected. The app also includes Google Analytics for Firebase and enables Google's User Messaging Platform (UMP) consent flow for AdMob where applicable.

Google's advertising, consent, and analytics services may process advertising or app-instance identifiers, IP address and approximate location inferred from it, device and app information, app and advertising interactions, diagnostics, and consent/privacy signals. OneSignal and Firebase may process the push-notification information described above. The exact processing depends on provider settings, region, device configuration, consent choices, and the providers' own policies.

Publicvoid may view aggregated content-use, Firebase Analytics, push-delivery, and AdMob reporting, such as reading or screen activity, content view totals, notification delivery or engagement, ad impressions and clicks, estimated earnings, country, platform, and date breakdowns. These reports are not the same as the devotional favorites and search history stored locally on your device.

Where Google requires a consent choice, UMP may present Google's consent form. The availability and wording of consent or privacy options depend on Google's determination for the user's region and current consent state; they are not universally available. The app does not claim that advertising processing is optional for every user.

Sharing, downloads, retention, and deletion

When you choose Share, Android sends the selected devotional title or app link to the destination app you select. When you choose to download an image, Android's download service saves it outside the app's private database. The receiving app, download location, or cloud service then handles that information under its own terms.

• Favorites, search history, preferences, and cache remain locally until removed through app features, Android storage controls, or uninstall. Android backup or explicitly downloaded files may remain separately.
• The current configuration has no enabled user account, so there is no active Renungan Pagi account-deletion flow.
• Server request logs, aggregate content-view counts, analytics, advertising, consent, and push-notification information are retained by Publicvoid's hosting providers or the applicable third-party provider under their operational and privacy policies.
• Uninstalling stops future app activity but does not by itself erase information already retained by a server, advertising/analytics provider, push provider, Android backup, or a destination to which you shared or downloaded content.
• For questions about Renungan Pagi or this processing, contact [email protected].

Wallpaper Applications

Wallpaper applications published by Publicvoid Dev may store preferences or requested content on the device and may use third-party services described above. Their exact permissions, advertising, analytics, diagnostics, network use, and data handling can differ by application and version. Review each application's current store listing, permissions, and in-app disclosures; this policy does not assert that all wallpaper applications use the same SDKs or collect the same data.

Retention and Deletion

On-device information is generally retained until it is removed through application features, Android storage controls, or uninstalling the application. Third-party providers control retention and deletion for information they process under their policies. Because MenuCost has no cloud account, it has no server-side MenuCost account-deletion workflow.

Security

On-device data is protected by Android's application sandbox. Publicvoid Apps values user trust and uses reasonable safeguards appropriate to the services provided, but no storage or internet transmission method is completely secure.

Links to Other Sites

Covered applications may link to websites or services not operated by Publicvoid Apps. Review those third parties' policies; Publicvoid Apps does not control their content or privacy practices.

Children's Privacy

Publicvoid Apps does not knowingly collect personal information directly from children under 13. If a parent or guardian believes a child has provided personal information directly to Publicvoid Apps, contact us so the concern can be reviewed. Application target audiences and third-party service behavior must also be checked in each current store listing.

Changes to This Policy

This policy may be updated when covered applications, third-party services, or legal requirements change. A published revision will update the effective date on this page.

Contact

Questions, suggestions, or privacy requests: [email protected].