Picolarm

Picolarm Privacy Policy

Last updated: 2026-07-09

Developer: Pico Alarms LLC
Privacy contact: support@picolarm.io
App: Picolarm for Android
Distribution: Google Play

1. Summary

Picolarm does not require an account. We do not operate a Picolarm server, cloud alarm database, analytics pipeline, or user profile system.

Most information in Picolarm stays on your device, including your alarm labels, alarm images, alarm schedules, alarm history, and app preferences.

Starting with Android Version 11, Picolarm includes Google AdMob and Google Play Billing:

  • Google AdMob, to show banner ads to eligible free users.
  • Google Play Billing, to manage an optional subscription that removes ads and lifts the free alarm-creation limit.

When those Google services are used, some information may be collected or processed through the app by Google, as described below.

2. Version scope

This policy describes the latest available Android version of Picolarm.

Version 10 and earlier: Picolarm was designed to operate fully offline. Those versions did not include Google AdMob, Google Play Billing, Picolarm accounts, Picolarm servers, analytics SDKs, crash-reporting SDKs, advertising SDKs, or runtime network calls by Picolarm.

Version 11 and later: Picolarm includes Google AdMob and Google Play Billing. The advertising and subscription sections of this policy apply only to versions that include those features.

An iPhone version of Picolarm is in development. Before an iPhone version is released, this policy and any App Store privacy disclosures will be reviewed and updated to describe the actual iOS implementation.

3. Information stored locally on your device

Picolarm stores the following information locally on your device so the app can function:

  • Alarms you create, including alarm time, label, repeat schedule, snooze settings, difficulty settings, sound settings, active/inactive status, and related alarm configuration.
  • Images you select for alarms, which may be copied into Picolarm's private app storage so the alarm can display the image when it fires.
  • Alarm history, such as whether an alarm fired, was snoozed, or was dismissed.
  • App preferences, such as default alarm settings, theme settings, onboarding state, alarm defaults, sound settings, haptic settings, and other local configuration choices.
  • Subscription or entitlement state, if you purchase a subscription, so the app can determine whether to remove ads and lift the free alarm-creation limit.

Your alarm labels and selected images may reveal personal or sensitive information depending on what you choose to enter or select. Picolarm does not upload your alarm labels, selected alarm images, alarm schedules, alarm history, or app preferences to a Picolarm server.

Depending on your device settings and operating system behavior, local app data may be included in device backups controlled by Android, Google, your device manufacturer, or another backup provider. Picolarm does not operate those backup services.

4. Information Picolarm does not collect through its own account or server system

Picolarm does not operate its own account or server system to collect:

  • Names.
  • Email addresses.
  • Usernames or passwords.
  • Contact lists.
  • Calendar data.
  • Precise location.
  • Cloud copies of your alarm photos.
  • Cloud copies of your alarm labels.
  • Cloud copies of your alarm schedules.
  • Cloud copies of your alarm history.
  • First-party analytics profiles.

However, Version 11 and later include Google AdMob and Google Play Billing. Those services may process information through the app as described in this policy.

5. Advertising — Google AdMob

In Picolarm for Android Version 11 and later, Picolarm may show a banner ad on the home screen to free users after they have created 5 alarms.

Picolarm is designed not to show ads while an alarm is actively firing, ringing, or during the alarm-dismissal interaction.

Picolarm does not intentionally send your alarm labels, selected alarm images, alarm schedules, alarm history, or app preferences to Google AdMob or to another advertising network.

However, when AdMob is included and ad requests are made, the Google Mobile Ads SDK may automatically collect and share information through the app. Depending on device settings, region, consent choices, SDK configuration, and Google's policies, this may include:

  • IP address, which may be used to estimate general location.
  • Android advertising ID, app set ID, and other device or account identifiers where applicable.
  • Device type and device information.
  • App and ad interaction information, such as app launch, taps, ad requests, impressions, clicks, and related events.
  • Diagnostic and performance information, such as SDK performance, app launch time, hang rate, or energy usage.
  • Information used for ad delivery, ad measurement, analytics, frequency capping, fraud prevention, security, and abuse prevention.

Picolarm does not use AdMob mediation networks unless this policy is updated to identify those additional ad partners.

6. Advertising consent and privacy choices

Picolarm may be required by law, platform policy, or Google policy to obtain advertising consent or provide advertising privacy choices before requesting certain ads.

Picolarm will not request production AdMob ads in jurisdictions where an advertising consent or privacy-choice flow is required unless that required flow has been implemented and completed, or unless another legally permitted ad-serving configuration is used.

Where an advertising consent or privacy-choice flow is required and available in the app, Picolarm will display that flow before requesting affected ads. Depending on your location, device settings, and choices, Picolarm may show personalized ads, non-personalized ads, limited ads, contextual ads, or no ads.

Where required and available in the app, Picolarm will provide an in-app privacy-options entry point so you can review or change advertising privacy choices.

You may also be able to manage advertising choices through Android or Google settings, including resetting or deleting the Android advertising ID or changing ad personalization settings.

If you subscribe to Picolarm's paid plan, Picolarm is designed not to request or display AdMob banner ads while your subscription is active.

7. Subscription and Google Play Billing

Picolarm offers an optional $1/month subscription through Google Play. The subscription removes ads and lifts the free alarm-creation limit while active.

Purchases are processed by Google Play and Google Payments. Picolarm does not receive your full payment card number, bank account number, or payment account credentials.

To provide subscription features, Picolarm may receive limited purchase and entitlement information from Google Play Billing, such as whether a purchase succeeded, whether a subscription is active, expired, canceled, refunded, revoked, or otherwise unavailable, and purchase or entitlement identifiers used by Google Play Billing.

Picolarm uses this information to:

  • Provide paid features.
  • Remove ads for active subscribers.
  • Apply or remove the free alarm-creation limit.
  • Verify entitlement status.
  • Prevent billing-related abuse.

You can manage or cancel your subscription through Google Play.

8. Permissions

Picolarm may request or use the following Android permissions, depending on Android version and enabled features:

  • Notifications — to show alarm notifications and foreground alarm notifications.
  • Exact alarms — to schedule alarms at the selected time.
  • Receive boot completed — to re-register alarms after the device restarts.
  • Full-screen intent — to show full-screen alarm alerts when needed.
  • Wake lock — to help alarms alert properly when the device is locked or idle.
  • Set alarm — to support alarm-related Android functionality.
  • Foreground service / media playback foreground service — to keep alarm audio and alarm UI active while an alarm is firing.
  • Vibration — to provide optional haptic feedback.
  • Internet / network access — for Google AdMob, Google Play Billing, advertising consent or privacy-choice messages, subscription status, and related platform services in versions that include those features.
  • Picolarm may also include the Android Advertising ID declaration where required for Google AdMob. The Android advertising ID may be used by Google AdMob for advertising where permitted by Android, Google Play policy, device settings, consent choices, and applicable law.

Picolarm uses the Android photo picker and camera-related system flows when you choose or take an image for an alarm. Depending on Android version and the method used, Picolarm may not need broad photo-library permission to let you select an image.

Picolarm does not request permission to read your contacts, access precise location, record audio, or access your calendar.

9. Third-party services and SDKs

Picolarm for Android Version 11 and later uses:

  • Google AdMob.
  • Google Play Billing.

Picolarm does not currently use third-party analytics SDKs, crash-reporting SDKs, remote configuration SDKs, social login SDKs, cloud database SDKs, additional ad networks, or AdMob mediation networks.

If Picolarm later adds analytics, crash reporting, cloud backup, account login, remote configuration, additional ad networks, attribution SDKs, or other third-party services that materially change data practices, this policy will be updated before or when those features are released.

10. Sharing, sale, and targeted advertising

Picolarm does not sell your alarm labels, selected alarm images, alarm schedules, alarm history, or app preferences.

Picolarm does not operate a data broker business and does not maintain a Picolarm advertising profile database.

However, when advertising services are used, Google AdMob may collect or receive identifiers, IP address, app/ad interaction information, diagnostic information, and related information through the app. Some privacy laws may treat certain advertising-related disclosures as a "sale," "sharing," "targeted advertising," or similar regulated activity, even if personal information is not sold for money.

Where required by applicable law, Picolarm will provide a privacy-choice mechanism or configure available platform or ad SDK controls to honor applicable opt-out rights before enabling affected advertising processing.

Picolarm does not currently operate a website, account portal, or browser environment for receiving browser-based privacy preference signals.

11. Children's privacy

Picolarm is not designed for children under 13 and is not intentionally marketed to children under 13.

We do not knowingly collect personal information from children under 13. We also do not intentionally use child-directed advertising, child-directed store listing language, or child-directed marketing imagery.

If we become aware that a child under 13 is using Picolarm in a way that causes personal information to be collected through advertising or another third-party service, we will take steps appropriate to the situation, which may include disabling affected ad delivery, restricting affected features, deleting information within our control, or updating the app and policy to comply with applicable children's privacy requirements.

Parents or guardians who believe a child has provided personal information through Picolarm may contact us at support@picolarm.io. Because Picolarm does not operate user accounts or a Picolarm alarm server, most alarm data exists only on the user's device and can be deleted by deleting alarms, clearing app data, or uninstalling the app.

If Picolarm is later designed for children, marketed to children, included in a child-directed store category, or treated as a mixed-audience app, we will update the app, store listing, SDK configuration, ads configuration, consent flows, and this policy as required before offering those features to children.

12. Regional privacy rights

Depending on where you live, you may have rights to request access, deletion, correction, portability, restriction, objection, withdrawal of consent, or opt-out of sale, sharing, targeted advertising, or certain profiling.

To exercise privacy rights for information controlled by Picolarm, contact support@picolarm.io.

Important limitations:

  • Picolarm does not operate user accounts.
  • Picolarm does not operate a cloud alarm database.
  • Most alarm data is stored only on your device.
  • We may not be able to identify or access your local alarm data unless you provide it to us.
  • Google controls many advertising, billing, payment, account, and platform records processed through Google services.
  • To manage Google account-level data, Google Play payments, subscriptions, or advertising settings, you may need to use Google, Google Play, Google Payments, or Android device settings.

If you contact us by email, we will use your email address and message contents to respond to your request, keep records of the request, comply with legal obligations, and protect our rights.

13. Legal bases for EEA, UK, and similar regions

Where GDPR, UK GDPR, ePrivacy, or similar laws apply, Picolarm relies on different legal bases depending on the data and context:

  • App functionality: processing necessary to provide the alarm features you request.
  • Local storage of alarm data: processing necessary to provide app functionality, with data stored on your device.
  • Advertising: consent where required, including for personalized ads and for access to identifiers or local storage where required by ePrivacy, platform policy, or applicable law.
  • Subscriptions and billing: performance of a contract, legal obligations, fraud prevention, and legitimate interests in maintaining entitlement records.
  • Privacy requests and support emails: legal obligations and legitimate interests in responding to requests and maintaining appropriate records.

Where consent is required, Picolarm will request it before the relevant processing begins. Where consent is withdrawn, Picolarm will stop the affected processing unless another legal basis applies.

14. Data retention and deletion

Picolarm stores local alarm data, selected images copied into app storage, alarm history, preferences, and local entitlement state on your device until one of the following occurs:

  • You delete the alarm or related content in the app.
  • You clear Picolarm's app data through Android settings.
  • You uninstall Picolarm.
  • The operating system removes app data according to platform rules.

Uninstalling Picolarm generally removes app-local alarms, images copied into app storage, alarm history, preferences, and local entitlement state from the device, subject to normal Android behavior and any device backups controlled by the user, device manufacturer, Google, or another backup provider.

Google may retain advertising, billing, payment, fraud-prevention, tax, accounting, analytics, and transaction information according to Google's own policies. Picolarm cannot delete information stored by Google in Google's own systems.

Privacy-request emails may be retained as long as reasonably necessary to document responses, comply with legal obligations, resolve disputes, and protect legal rights.

15. Security

Picolarm stores local app data using Android storage mechanisms such as app-scoped storage, local databases, and app preferences. Android app sandboxing helps protect app data from other apps.

Third-party platform services used by Picolarm may transmit data to Google or Google's service providers using Google's own security practices.

No method of storage or transmission is perfect. Choose alarm labels and images with that in mind, especially if your device is shared, unlocked, backed up, rooted, compromised, or accessible to others.

16. International processing and transfers

Picolarm does not operate its own international server infrastructure for alarm data.

Google and its service providers may process advertising, billing, payment, subscription, fraud-prevention, security, diagnostic, and related service data in countries where they operate.

Where required by applicable data protection laws, Picolarm will rely on appropriate legal mechanisms for cross-border data transfers, such as Standard Contractual Clauses, adequacy decisions, applicable data privacy frameworks, platform data protection terms, or other lawful transfer mechanisms.

17. Public feedback and privacy requests

Picolarm may provide a public GitHub issue link for general product feedback, bug reports, or feature requests.

Do not post privacy requests, billing information, alarm labels, selected alarm images, personal information, or sensitive information in public GitHub issues, public app reviews, or other public forums.

For privacy questions or requests, contact support@picolarm.io.

18. Changes to this policy

We may update this policy when Picolarm changes, when SDK behavior changes, when platform requirements change, or when legal requirements change.

Material changes, such as adding advertising, subscriptions, analytics, crash reporting, accounts, cloud backup, server-side storage, additional ad networks, attribution SDKs, or data-sharing features, will be reflected in this policy before or when the relevant app version is released.

If you are using an older version of Picolarm, some features described in the latest policy may not be present in your installed version.

19. Contact

For privacy questions or requests, contact:

Pico Alarms LLC
Email: support@picolarm.io
App: Picolarm for Android
Distribution: Google Play