1. Who we are
ZoroSoft provides PeekKeep for Android (com.rtsoftware.peekkeep). This policy explains its information handling and your privacy choices. No PeekKeep account is required. PeekKeep is independent of the apps whose notifications it saves; those services have their own policies.
2. Notifications and app selection
With Android notification access, PeekKeep can receive notifications, including sensitive content. It saves only those from apps you select. Capture can continue while PeekKeep is not on screen.
Depending on what Android and the source app expose, saved data may include app names, packages and icons; notification identifiers, categories, times and status; titles and text; sender and conversation details, avatars and message times; available original fields; accessible images, video, audio and other supported attachments; file types and capture-failure details.
Information about available installed apps is used to show the selection list and organize history locally. We do not upload your installed-app inventory or selected-app list to our servers or advertising services.
PeekKeep cannot read conversations directly inside another app, recover content it never received, bypass content hidden by Android or guarantee access to temporary media links. It does not need contacts, microphone or camera access to save media already attached to a notification.
3. Storage and security
History, attachments, app choices and settings stay in private app storage. Android restricts access by other ordinary apps. This data is excluded from Android backup and device transfer; notification history has no cloud synchronization.
Optional App lock uses Android biometrics or device credentials. PeekKeep receives only the authentication result, not your fingerprint, face template or credential.
These protections cannot guarantee security on an unlocked, rooted or compromised device. PeekKeep adds no separate encryption layer to history. Protect your device and share carefully. Local counters and timestamps control app-open ad frequency and review eligibility; they contain no notification text.
Daily summaries use a local capture log containing only internal record IDs and capture times. Deleting message history does not remove these counts; periodic cleanup removes log entries older than seven days. The last report date is stored to prevent duplicate summaries.
5. Advertising
PeekKeep uses Google AdMob. The Mobile Ads SDK collects and shares IP addresses, app/ad interactions, diagnostics and device or account identifiers for advertising, analytics and fraud prevention. IP addresses may indicate general location. Depending on settings and ad configuration, identifiers can include the Android advertising ID and app set ID. Advertising data is encrypted in transit.
PeekKeep does not supply notification text, attachments, sender details or selected-app lists to the advertising service. Where required, Google's consent choices appear before ad requests. When available, use Settings > Ad choices to change them. Android also provides advertising-ID controls; availability depends on region, device and Google services.
6. Usage analytics and crash diagnostics
Google Analytics for Firebase measures screen/feature use and action outcomes, such as opening conversations, searching, sharing, replying, deleting, changing settings or sending feedback. Selected-app counts are reported as ranges, without app names or package lists.
Analytics processes interactions, sessions, app/device information and general location Google derives from network information. When Analytics consent is unknown or declined, it may send limited measurement signals without Analytics-managed app-instance identifiers. Full measurement, including app-instance identifiers, is enabled when Analytics consent is granted or Google reports that consent is not required. Consent settings are saved and updated when a new choice is available. PeekKeep disables advertising-ID collection and ad personalization in Analytics. Where available, change your choice in Settings > Ad choices.
Firebase Crashlytics diagnoses crashes, unresponsive-app incidents and selected errors. Reports may contain stack traces, error types, app/OS versions, device information, installation identifiers and limited screen/action history. PeekKeep removes exception messages and limits repeats in handled-error reports. The Firebase SDK produces automatic fatal-crash and unresponsive-app reports.
We do not add notification/reply text, sender/conversation details, searches, saved files or locations, feedback text or installed/selected-app lists to custom events or handled-error reports. No PeekKeep account ID or contact information is assigned. Installation identifiers are pseudonymous, not fully anonymous.
These services send data to Google. Crashlytics retains crash data and related identifiers for 90 days before starting deletion; Analytics follows the property's retention settings. Deleting local history does not delete earlier telemetry. Contact us for privacy requests; without your name or email attached, we may be unable to identify your reports.
7. Voluntary feedback
Settings > Send feedback is optional. Reports contain your message/topic, a random report ID, submission time, app package/version/language and basic device details (manufacturer, brand, model, Android version). Notification history, media, contacts and persistent hardware IDs are not automatically attached.
Our server receives the report and IP address; hosting/security providers may also process request information and an approximate country from the connection. We use this to respond, diagnose problems, improve PeekKeep and prevent abuse.
Do not include unnecessary passwords or private messages. Emailing us provides your address and chosen content. Hosting/email providers may process support data for these purposes. Disclosure may occur when legally required or necessary to protect legal rights and service security.
Providers may process information outside your country, subject to their policies and applicable data-protection requirements. Google's policy explains its international processing.
8. Retention and deletion
Settings > Storage and retention offers 1, 7, 30 or 90 days, or no time limit; the default is 30 days. Storage limits still apply. Cleanup removes older items; device scheduling can affect when it runs.
Delete individual items, a conversation, one app's history or use Settings > Delete all messages. Associated saved files are removed as applicable. We cannot restore deleted history.
Pause capture, deselect apps or revoke notification access to stop new capture as applicable; existing history remains. Uninstalling or clearing app data removes local history, settings and pending feedback. We cannot retrieve that local history.
Delivered feedback and request information are retained as needed for investigation, support, improvement, abuse prevention or legal obligations. You can request deletion by contacting us. Local deletion/uninstall does not remove delivered feedback or previously collected telemetry.
Shared/exported files, sent emails, Play reviews and data held by advertising or other services follow the recipient's retention and deletion policies.
9. Your choices and privacy rights
You control selected apps, notification access, retention, App lock, sharing and feedback. Notification access is necessary for capture; revoking it grants no access to anyone else.
Depending on applicable law, you may request access, correction, deletion, a copy, restrictions on processing, object to processing, withdraw consent or complain to a data-protection authority. Contact us; we may need enough information to find your report and verify your request. Avoid unnecessary sensitive documents. Manage device-only history in the app because we have no server copy.
Where a legal basis is required, support processing rests on handling your request and our legitimate interests in maintaining/protecting the service, or consent/legal obligations where applicable. Advertising consent is requested where required; withdrawal does not affect previously lawful processing.
If you believe a child supplied personal information without appropriate permission, contact us so we can investigate and address it.
10. This website
This page has no ads, analytics scripts, forms or tracking cookies. Its language selector runs locally without sending text to a translation service or storing a tracking identifier. The app opens this hosted page in your browser using its selected language; you can change the language here.
Hosting/network-security providers receive normal connection data such as IP address, requested URL, time and browser information to deliver and protect the site. External links lead to services with their own policies. Access to the hosted page requires a connection; PeekKeep does not provide an offline Privacy page.
11. Policy updates
We may update this policy when features, providers or requirements change. The date above identifies the latest revision. Material changes receive additional notice or consent requests where required.
12. Contact us
For PeekKeep privacy questions, requests or concerns, contact ZoroSoft at realtimesoft.vn@gmail.com.
Mention PeekKeep and enough information to identify your request. Do not include unrelated private notification content.