MotionGuard: Motion Alarm Privacy Policy

# MotionGuard: Motion Alarm Privacy Policy Last updated: September 16, 2026 Developer: Quinn Favo / Quazmoz Public policy URL: https://consultant.quinnfavo.com/privacy/motionguard ## Overview MotionGuard is an Android and Wear OS alerting utility. Monitoring begins only after the user explicitly arms a session. The free alarm works without a MotionGuard account or developer-operated cloud service. Optional lifetime purchases and optional rewarded advertising use the third-party services described below. ## Information stored locally MotionGuard may store the following information locally on the user's devices: - Arming preferences, including selected trigger types, sensitivity, and settle delay. - Onboarding completion state. - Last-session recovery state used to explain whether monitoring stopped, was disarmed, or triggered. - Trigger-history records containing arm, trigger, and disarm times; trigger type; sensitivity; coarse movement evidence; charging state; and whether the phone queued a best-effort Wear message. - Local metadata needed for the paired Wear OS experience. Raw continuous accelerometer samples are processed in memory and are not retained in release trigger history. MotionGuard does not store a separate local Pro Boolean or rewarded-ad expiration timer. RevenueCat CustomerInfo is the entitlement source. Local safety/session data is excluded from Android backup and device-transfer extraction. ## Motion sensor processing While a motion-enabled session is active, MotionGuard processes accelerometer samples in memory to establish a baseline and detect configured movement. The release app does not retain a continuous raw accelerometer trace. Trigger history keeps only bounded, coarse evidence needed to explain an event to the user. ## Purchases and RevenueCat The optional lifetime Pro purchase is processed by Google Play. MotionGuard does not receive or store payment-card or bank-account details. RevenueCat processes the app's anonymous customer identifier, product and transaction information, entitlement state, app/device information, network requests, and related diagnostics needed to validate purchases, restore ownership, and provide entitlement state. Purchase tokens are handled through the Google Play and RevenueCat SDK path and are not logged or persisted by MotionGuard application code. RevenueCat automatic device-identifier collection is disabled in the MotionGuard client configuration. MotionGuard does not configure RevenueCat attribution integrations or send custom subscriber attributes. ## Optional rewarded ads, Google AdMob, and Google UMP MotionGuard includes Google Mobile Ads on the Android phone only. There are no banner ads, forced interstitial ads, or app-open ads. A rewarded ad is not requested automatically at launch. MotionGuard loads a rewarded ad only after the user explicitly selects Watch an ad on the Pro surface and only when Google User Messaging Platform reports that ads may be requested. Ads are not shown while the phone is arming, armed, alarming, or disarming. Google AdMob may process information including advertising or device identifiers where available and permitted, IP address, approximate location inferred from IP, ad interactions, impression and revenue information, app/device information, diagnostics, and performance data for ad selection, delivery, measurement, security, and fraud prevention. MotionGuard does not sell this data and does not include Firebase Analytics. Google UMP requests current consent information and displays a Google-certified consent form where required. For users in the EEA, UK, and Switzerland, the consent flow can present choices for consent, refusal, and managing options according to the published Google CMP configuration. Ads are requested only when UMP reports that they may be requested. If UMP requires an ongoing privacy entry point, MotionGuard exposes Privacy choices in the app. Declining ad consent, or being unable to complete the ad consent flow, does not block the free alarm or the lifetime-purchase option. For a completed rewarded ad, the SDK attaches RevenueCat verification data to AdMob server-side verification. AdMob calls RevenueCat; RevenueCat verifies the event and, if valid, grants the Pro entitlement for the configured 8-hour Advanced Guard Pass. MotionGuard does not grant access solely from the local earned-reward callback. ## Google Play Data Safety summary For the current release, the Play Data Safety declaration covers the following third-party SDK data paths: - Purchase history for Google Play and RevenueCat purchase, restore, and entitlement processing. - Approximate location inferred from IP address in the optional Google AdMob path; MotionGuard does not request Android precise- or approximate-location permission. - App interactions related to the optional rewarded-ad flow and reward verification. - Diagnostics used by the advertising and entitlement providers for measurement, reliability, security, and fraud prevention. - Device or other IDs used by the Google advertising stack where available and permitted. The optional AdMob-related categories are tied to the user-requested rewarded-ad path. Users can use the free core alarm and can choose the lifetime-purchase path without requesting a rewarded ad. ## Wear OS companion The optional Wear OS companion exchanges status and trigger information with the user's paired phone through Google Play services Wear Data Layer. This can include session state and configuration, timestamps, session identifiers, coarse trigger information, and the phone's current Pro status. The phone remains authoritative. Watch-originated Disarm remains available independently of Pro status. No RevenueCat, AdMob, or UMP SDK is included in the Wear OS module. ## Permissions and information MotionGuard does not request The phone application uses permissions needed for the user-started foreground monitoring service, notifications where Android requires them, vibration, network access required by Google Play/RevenueCat/AdMob/UMP, and the accelerometer hardware capability needed for motion monitoring. MotionGuard does not request location, camera, microphone, contacts, SMS, call logs, AccessibilityService, device-administrator, or broad external-storage access. The advertising SDK contributes the Android advertising-ID and Privacy Sandbox advertising-services permission surface on supported Android versions. Its transitive WorkManager runtime can also contribute WAKE_LOCK. MotionGuard application code does not acquire a wake lock for motion monitoring and does not auto-arm after boot. MotionGuard has no developer-operated account system, general-purpose analytics SDK, third-party attribution SDK, third-party crash-reporting SDK, or marketing-notification SDK. ## Retention and deletion Local trigger history remains until the user chooses Clear trigger history, clears Android app storage, or uninstalls MotionGuard. The in-app Clear trigger history action removes local trigger-history records only. Clearing app storage or uninstalling removes local settings, history, and other MotionGuard-owned local state. Google Play purchase records and RevenueCat transaction or entitlement records are retained under those providers' terms and legal requirements. Reinstalling MotionGuard or using Restore can recover lifetime ownership from the applicable provider records. Google AdMob and Google UMP retain or process advertising and consent information under Google's policies and the user's applicable consent choices. ## Security and third parties Network traffic used by Google Play, RevenueCat, Google AdMob, and Google UMP uses the providers' network services. MotionGuard does not operate its own general-purpose user-data backend. Relevant providers include Google Play services, Google Play Billing, Google AdMob, Google User Messaging Platform, and RevenueCat. Each provider may process information under its own privacy, retention, and security terms. ## Children MotionGuard is a general-purpose utility and is not directed to children. MotionGuard does not knowingly collect personal information from children through a developer-operated account or backend service. ## Changes to this policy This policy and the Google Play Data Safety declaration must be updated before MotionGuard adds materially different analytics, attribution, crash reporting, accounts, backend processing, ad formats, or data-handling behavior. ## Contact For privacy questions or support, contact: Quazmoz@vivaldi.net