Privacy Policy

Effective Date: June 10, 2026
Last Updated: June 16, 2026

RadStorm Technologies LLC ("RadStorm Technologies," "Company," "we," "us," or "our") respects your privacy. This Privacy Policy explains how we handle information in connection with:

the Block Guard Android app ("App"), and
the Block Guard website and related web pages, tools, and APIs ("Website").

Because the App and the Website use data differently, this Privacy Policy is divided into separate sections. Part A applies to the Android App. Part B applies to the Website. Part C contains general provisions.

Contact Information

RadStorm Technologies LLC
30 N Gould St. Ste N
Sheridan, WY 82801
Email: support@blockguard.app
Privacy Contact: privacy@blockguard.app
Website: https://blockguard.app

Part A - Block Guard Android App Privacy

1. Scope

This section applies only to the Block Guard Android app.

Block Guard is designed as a privacy-first call, text, and phishing-protection app. The App performs its core protection functions locally on your device whenever possible. However, some optional or supporting features involve limited network communication, including advertising, consent management, crash reporting if enabled by the user, premium subscription verification, hosted spam-reference updates, and normal carrier or Google Play services.

2. Information the App May Access or Use

Depending on your device, Android version, granted permissions, enabled features, and how you use the App, Block Guard may access or use the following categories of information:

phone numbers associated with incoming, outgoing, missed, blocked, allowed, or reported calls;
call metadata such as date, time, duration, call type, caller ID, call-log details, and blocking outcome;
SMS and MMS message content, sender and recipient information, attachments, conversation metadata, and timestamps, when Block Guard is used as a messaging app;
contacts, contact names, and phone numbers from your device contacts, used for caller/sender identification, allow rules, contact-based blocking exceptions, and display inside the App;
user-created block lists, allow lists, whitelists, area-code rules, keyword rules, text-blocking rules, preferences, profiles, schedules, and settings;
notification-related data needed to display or manage call and message alerts;
microphone audio only when you choose to use a voice-message or voice-recording feature;
purchase and subscription information provided by Google Play Billing, including purchase tokens used to verify premium access;
a Google Account identifier obtained through Google Sign-In, only if you choose to restore a previous paid-app purchase, used to confirm and remember your premium entitlement across your devices;
app diagnostic information if optional crash reporting is enabled;
advertising and consent-related identifiers or device information used by Google Mobile Ads, Google User Messaging Platform, or related Google services for ad delivery, consent management, fraud prevention, frequency capping, measurement, or compliance.

3. Local Processing and On-Device Storage

Block Guard is designed so that core call, text, contact, spam, phishing, blocking, and messaging data remains on your device.

The following are processed and stored locally by the App, unless you choose to export, back up, share, send, or otherwise transmit them through your own device, carrier, Android system, or another app:

call history and call-blocking records;
SMS and MMS conversations;
blocked message logs;
contact display information;
block lists, allow lists, rules, schedules, profiles, and preferences;
local spam-detection or learning data;
phishing and suspicious-message decisions;
message attachments and local media used by messaging features.

Block Guard does not operate a cloud inbox, cloud message sync service, cloud call-log sync service, or cloud contact backup service for App data.

4. How the App Uses Data

The App uses data to:

provide call screening, call blocking, caller ID, spam detection, and related phone-protection features;
send, receive, display, and manage SMS and MMS messages when Block Guard is used as a default messaging app;
identify, label, block, silence, or warn about unwanted calls, unwanted texts, suspicious messages, or phishing links;
display contact names alongside calls and messages;
manage allow lists, block lists, whitelists, profiles, schedules, quiet hours, and other rules;
maintain local call/message history and logs;
provide analytics, summaries, weekly reports, and protection recommendations inside the App;
improve on-device spam-detection behavior based on local blocking actions and labels;
verify premium access and manage purchases through Google Play Billing;
show ads to eligible non-premium users where allowed by user consent and applicable law;
request and manage privacy choices related to ads where required;
diagnose app crashes only if crash reporting is enabled;
maintain security, prevent abuse, enforce our terms, and comply with applicable law.

5. Network Communication from the App

The App may use Internet access for the following limited purposes:

As with any internet connection, our servers may automatically log limited technical information for these requests, such as IP address, request time, requested endpoint, and user agent, as described in Section 10.

Hosted reference updates

The App may download read-only reference data from blockguard.app over HTTPS, such as known spam-number reference data and related checksum or integrity files. These downloads are designed so that your personal call history, message content, contacts, and blocking activity are not uploaded to our servers.

Phishing and suspicious-message detection runs on your device using the App’s local logic and any reference data shipped with or downloaded by your App version. The App does not upload your SMS/MMS message content, contacts, call history, or local phishing decisions to Block Guard servers for phishing analysis.

MMS and carrier communications

When you send or receive calls, SMS, or MMS, those communications are handled through your mobile carrier, Android system services, device manufacturer services, and the intended recipients. Block Guard does not route your personal calls or messages through Block Guard servers.

Google Play Billing and premium verification

When you purchase, restore, or verify premium access, the App uses Google Play Billing. The App may send a Google Play purchase token to a Block Guard verification endpoint to confirm whether a subscription is active. This verification is used only to determine premium access. We do not use purchase tokens to collect message content, call history, contacts, or blocking lists.

Our server stores a hashed version of the purchase token, along with limited subscription-verification metadata, rather than storing the raw purchase token. This helps us verify premium access while reducing the sensitivity of the data retained by our server.

Legacy purchase restore and account sign-in

If you originally purchased Block Guard as a paid app and choose to restore that purchase, the App lets you sign in with Google (using Android’s Credential Manager). Signing in is optional and is used only for this restore feature; it is not required to use the App.

When you restore, the App sends your Google ID token — and, the first time, your Google Play order ID — to a Block Guard endpoint over HTTPS. Our server verifies the order with Google Play and links your entitlement to your Google Account so your premium access follows you across your devices. We store only your Google Account identifier, a hashed (one-way) version of the order ID, and a premium-entitlement flag with timestamps. We do not store your name or email from the sign-in, and we do not collect your message content, call history, contacts, or blocking lists through this feature.

This sign-in uses Google Identity / Credential Manager only. Block Guard does not use Firebase Authentication, and the App has no general user-account system beyond this optional purchase-restore linkage. You can delete this data at any time (see Section 11).

Advertising and consent services

The App may use Google Mobile Ads and Google User Messaging Platform to request consent, manage ad privacy choices, and show ads to eligible non-premium users. These Google services may collect or process device information, advertising identifiers, approximate location inferred from IP address, app interaction information, diagnostics, and other data as described by Google, depending on your region, consent choices, device settings, and Google’s own policies.

Ads are not intended to be shown to users who have an active ad-free premium entitlement. Ad requests may be limited by route, screen, entitlement state, consent state, and app configuration.

Optional crash reporting

Crash reporting is disabled by default unless you enable it in the App settings. If enabled, the App may use Firebase Crashlytics to collect crash reports and diagnostic information, such as crash stack traces, device information, operating system version, app version, timestamps, and identifiers used to associate crash reports. Crash reports help us diagnose and fix app stability issues. Crash reporting is not used to collect your message content, contact list, call recordings, or full call history.

6. AI, Spam Learning, and Model Improvement

Block Guard may use your local blocking actions, spam labels, rule outcomes, and related in-app actions to improve on-device spam-detection behavior.

Spam-detection learning is designed to operate on-device.
Training examples are intended to use local features or labels, not full raw message bodies or full contact lists.
Contact names are not used for spam-model training.
We do not send call history, message content, contacts, or local spam-training data to Block Guard servers for model training.
If we introduce a future feature that transmits training-related data off-device, we will update this Privacy Policy and any required in-app disclosures before doing so.

7. Microphone and Voice Messages

If you choose to use a voice-message or voice-recording feature, the App may request microphone access. Microphone access is used only to record audio that you choose to create for that feature.

Block Guard does not continuously record audio, does not use the microphone for advertising, and does not upload microphone audio to Block Guard servers for analytics or training. Voice recordings may be stored locally, attached to messages, or sent through your carrier or selected sharing method when you choose to send or share them.

8. Ads, Consent, and Premium Access

Block Guard may show ads to eligible users who do not have an active ad-free or premium entitlement.

The App may request your advertising consent or privacy choices through Google User Messaging Platform where required. You may also have device-level advertising controls through Android, Google settings, or regional privacy controls.

Premium or ad-free users may receive an ad-free experience after the App confirms entitlement through local checks, Google Play Billing, and/or Block Guard’s subscription verification endpoint.

9. Optional Crash Reporting

Crash reporting is optional and can be controlled in the App settings.

When crash reporting is off, the App is designed not to send Firebase Crashlytics crash reports. When crash reporting is on, crash and diagnostic data may be sent to Firebase Crashlytics to help us identify, prioritize, and fix bugs.

Crash reports may include diagnostic information such as device model, operating system version, app version, crash stack traces, timestamps, and crash-related identifiers. Crash reports are not intended to include your SMS/MMS message content, contact list, call recordings, or full call history.

Block Guard does not use Firebase Authentication, Firebase Firestore, or Firebase Cloud Functions in the Android App.

10. Data Storage and Retention

Local App data

Most App data is stored locally on your device. Local retention depends on:

the features you use;
Android system behavior;
whether you delete items in the App;
whether you clear App data through Android settings;
whether you uninstall the App;
whether you use any in-app reset, clear, delete, backup, restore, or export feature.

Server-side data we may control

We may temporarily process or retain limited server-side information related to:

subscription verification requests;
hashed purchase-token records and limited subscription metadata;
for the optional purchase-restore feature: a Google Account identifier, a hashed order ID, and a premium-entitlement flag with timestamps;
technical request logs for App network requests, such as IP address, request time, requested endpoint, and user agent;
website/API requests;
support emails or privacy requests;
security logs;
abuse prevention;
legal compliance;
crash reports if optional crash reporting is enabled and sent through Firebase.

We retain information only as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer period is required or permitted by law.

11. User Controls and Deletion

You may control or delete certain App-related data through:

Android permission settings;
Android app storage settings;
Block Guard settings and feature toggles;
in-app delete, reset, clear, export, or backup/restore controls where available;
Google Play subscription controls;
Google advertising and privacy settings;
uninstalling the App.

If the App provides a Delete Learned Data, Reset AI Data, Clear Local Training Data, or similar feature, using that feature is intended to remove the corresponding locally stored training-related data maintained by the App on your device.

If you contact us with a privacy request, we will review it in accordance with applicable law and the data we actually control.

Deleting your purchase-restore data

If you used Google Sign-In to restore a previous purchase, you can delete the account data we store for that feature in either of these ways:

In the App, open Settings → Premium → Delete my restore data and confirm. After you sign in to verify it is your account, we remove your stored record.
Email privacy@blockguard.app from the Google Account associated with your purchase and ask us to delete your restore data.

Deleting this data removes your Google Account identifier, the hashed order ID, and the premium-entitlement record from our server. After deletion, premium access obtained through the restore feature is turned off on your devices; you can restore it again later by signing in and re-entering your order ID. We may retain limited security or transaction logs where required by law or for fraud prevention.

12. Data Sharing

Core App data

Block Guard does not sell your App data.

Block Guard does not intentionally transmit your SMS/MMS message content, full call history, contact list, local blocking lists, or local spam-training data to Block Guard servers for advertising, analytics, or model training.

Service providers

We may use service providers to operate limited App-related services, including:

Google Play Billing for purchases and subscription management;
Google Mobile Ads for advertising;
Google User Messaging Platform for consent and ad privacy choices;
Firebase Crashlytics for optional crash reporting;
hosting providers for blockguard.app, reference files, verification endpoints, and website/API services;
email or support providers if you contact us.

These providers may process data according to their own terms, privacy policies, SDK behavior, and legal obligations.

Legal and safety disclosures

We may disclose information if required by law, to protect rights or safety, to investigate misuse or abuse, to prevent fraud, to enforce our agreements, or in connection with a merger, acquisition, financing, asset sale, or similar transaction.

13. Android Permissions

Block Guard requests Android permissions only as needed to provide its features. Depending on your device, Android version, enabled features, and user choices, these may include permissions related to:

phone state, phone numbers, call screening, placing calls, answering calls, and call management;
call logs for call history, caller identification, blocking records, and default-phone functionality;
contacts for displaying names and applying contact-based rules or exceptions;
SMS and MMS for sending, receiving, displaying, filtering, or managing messages when Block Guard is used as a messaging app;
notifications for call, message, and protection alerts;
microphone access for user-initiated voice messages or recordings;
notification policy / Do Not Disturb access for quiet-hours and DND-related features;
Internet and network state for reference updates, MMS-related behavior, ads, consent, billing verification, optional crash reporting, and website/API communication;
billing and license checks for purchase, subscription, premium, or paid-app access;
foreground service, wake lock, vibration, and audio settings for call, messaging, alerting, and protection behavior;
boot completion so enabled protections, schedules, and background rules can be restored after device restart.

Some features require default-handler status, such as default Phone app, call-screening role, or default SMS app. If you deny or revoke permissions, or do not grant required Android roles, some features may not function correctly.

14. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information handled by the App and Website.

Where the App or Website transmits data to our services or service providers, we use HTTPS or other appropriate transport protections where available. However, no method of storage, transmission, or security is completely secure, and we cannot guarantee absolute security.

15. Children and Age Suitability

Block Guard is not directed to children under 13, and we do not knowingly collect personal information from children under 13 through the App. The App is intended for users ages 18 and older, consistent with its target audience and call/message-management functionality.

16. International Use

If you use the App from outside the United States, you understand that information processed by our service providers or by us may be processed in the United States or other jurisdictions, subject to applicable law.

17. Changes to This App Privacy Section

We may update this App Privacy section from time to time. When we do, we will revise the "Last Updated" date above and may provide additional notice when required.

Part B - Website Privacy

18. Scope

This section applies only to the Block Guard Website, including marketing pages, support pages, privacy pages, downloadable files, reverse-number-lookup pages, APIs, forms, and related content.

The data practices described in Part B apply to the Website and do not automatically apply to the Android App.

19. Information We May Collect Through the Website

Depending on how you use the Website, we may collect or process:

information you provide directly, such as name, email address, company name, phone number, or message contents if you contact us;
technical and usage data, such as IP address, approximate location, browser type, device type, operating system, pages visited, referral source, request timestamps, and interactions with Website content;
cookie, local storage, pixel, tag, identifier, consent-signal, or similar-technology data used for analytics, advertising, functionality, security, fraud prevention, measurement, or compliance;
advertising and analytics data, such as page views, ad impressions, clicks, interactions with ads or Website content, browser and device information, approximate location, IP address, and related request metadata;
phone numbers or lookup queries you submit to a reverse-number-lookup tool, if you choose to use that tool;
API request data, such as request path, headers, IP address, rate-limit information, and abuse-prevention signals.

20. Reverse Number Lookup Tool

The Website may offer a reverse number lookup or similar lookup tool. If you submit a phone number or lookup query, that query is sent to Block Guard’s Website server or API endpoint so we can normalize the number, check it against Block Guard-hosted lookup data, and return a result.

The lookup tool is designed to use Block Guard website-hosted data and logic. Unless we update this Privacy Policy, the lookup tool is not intended to send your lookup query to third-party lookup providers, data brokers, carrier-enrichment services, or external complaint databases.

We may use lookup request data to:

provide the lookup result;
check the query against website-hosted lookup data, spam-reference data, reputation data, or related Block Guard-maintained signals;
prevent abuse, scraping, spam, fraud, or excessive automated requests;
rate-limit requests;
diagnose and improve the lookup service;
maintain security logs.

Do not submit phone numbers or other personal information through the lookup tool unless you want that information processed for the lookup request.

21. How We Use Website Data

We may use Website-related information to:

operate, maintain, and secure the Website;
provide Website tools, lookup features, downloads, APIs, forms, and support pages;
respond to inquiries and support requests;
understand how visitors use the Website;
improve site content, performance, accessibility, and design;
measure traffic and engagement;
show, personalize, limit, measure, and report Website advertising, including Google AdSense ads where enabled;
request, store, communicate, and honor Website consent and privacy choices for analytics, advertising, and related technologies;
detect abuse, fraud, security threats, or technical issues;
maintain logs and rate limits;
comply with legal obligations.

22. Analytics, Tag Management, and Measurement on the Website

The Website may use analytics, tag-management, advertising, advertising-measurement, consent-management, or similar technologies, including Google Analytics, Google Tag Manager, Google AdSense, Google Privacy & messaging, Google consent mode, and related Google services, to understand traffic, show ads, measure engagement, support compliance, and improve the Website.

These technologies may collect or process information such as:

pages viewed;
ad impressions, ad requests, ad clicks, and advertising events;
time spent on pages;
device and browser information;
approximate geographic region;
referral source;
interactions with Website content;
cookies, local storage, pixels, tags, online identifiers, or similar identifiers;
consent choices and consent signals;
IP address and request metadata.

Google Tag Manager may help load and manage Website tags. Google Analytics may help measure Website traffic and engagement. Google Privacy & messaging, including European regulations messages where applicable, and Google consent mode may help request, communicate, and apply consent choices for analytics and advertising technologies.

These Website technologies are separate from the Block Guard Android App.

23. Cookies and Similar Technologies

The Website may use cookies, local storage, pixels, tags, identifiers, and similar technologies for:

basic functionality;
analytics and performance measurement;
remembering settings or preferences;
security and fraud prevention;
advertising, ad personalization, ad delivery, and ad measurement;
consent management and regional privacy compliance.

Third-party vendors, including Google, use cookies to serve ads based on a user's prior visits to this Website or other websites. Google's use of advertising cookies enables Google and its partners to serve ads based on visits to this Website and/or other sites on the Internet.

Ads shown on the Website may be personalized or non-personalized depending on your location, consent choices, browser or device settings, Google account settings, applicable law, and the policies of Google or other advertising providers. Google and other third-party vendors may process cookies, local storage, pixels, tags, identifiers, IP address, device and browser information, approximate location, page views, ad impressions, clicks, and consent signals for these purposes.

You can manage or disable cookies through your browser settings and, in some regions, through Website consent messages. Disabling cookies may affect some Website functionality or advertising behavior.

24. Third-Party Services and Links

The Website may include links to third-party websites, services, platforms, app stores, payment services, analytics providers, advertising providers, or public data providers. We are not responsible for the privacy practices of third parties. Your use of third-party services is governed by their own terms and privacy policies.

Third-party advertising and analytics providers may independently determine how they process information collected through their services, subject to their own policies, user controls, and legal obligations.

25. Website Data Retention

We retain Website-related information only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.

Server logs, API logs, lookup logs, security logs, analytics records, support messages, and abuse-prevention data may be retained for different periods depending on operational, legal, security, or compliance needs.

26. Website Privacy Choices

Depending on the tools we use and your location, you may be able to:

manage cookies through your browser settings;
use Website consent messages, including Google Privacy & messaging prompts where shown, to make or update analytics and advertising choices;
manage Google ad personalization through Google Ads Settings;
learn how Google uses information from sites and apps that use Google services at Google's partner-sites information page;
use industry opt-out tools, such as the Network Advertising Initiative opt-out or the Digital Advertising Alliance opt-out, where available;
use available opt-out or privacy controls offered by analytics or advertising providers;
contact us to request deletion of messages you submitted through the Website;
contact us about privacy rights available under applicable law.

27. Changes to This Website Privacy Section

We may update this Website Privacy section from time to time. When we do, we will revise the "Last Updated" date above.

Part C - General Provisions

28. Legal Bases and Regional Rights

Depending on where you live, you may have rights under applicable privacy laws, including rights to request access to, correction of, deletion of, or restriction of certain personal information.

To make a privacy request, contact us at privacy@blockguard.app. We may need to verify your request before responding.

29. California Notice

California users may have additional rights under applicable California privacy laws, including rights to know, access, delete, correct, and opt out of certain sharing or sale of personal information.

We do not sell personal information as the term "sell" is commonly understood. Some advertising or analytics technologies may be considered "sharing" or "targeted advertising" under certain privacy laws. Where required, we will honor applicable opt-out or consent choices.

Requests may be submitted to privacy@blockguard.app.

30. European Economic Area, United Kingdom, and Similar Regions

If you are located in a region with specific privacy rights, such as the EEA, UK, Switzerland, or similar jurisdictions, you may have additional rights under applicable law. These may include rights to access, correct, delete, restrict, object to, or request portability of certain personal information.

Where required, we rely on appropriate legal bases such as consent, contract performance, legitimate interests, legal obligations, or user-requested functionality.

31. No Sale of Core App Data

We do not sell your SMS/MMS content, call history, contacts, local blocking lists, or local spam-training data.

32. Changes to This Privacy Policy

We may revise this Privacy Policy from time to time. The updated version will be posted at this location with a revised "Last Updated" date. Continued use of the App or Website after an update means the updated policy applies to future use, subject to applicable law.

33. Contact Us

If you have questions about this Privacy Policy or our privacy practices, contact:

RadStorm Technologies LLC
30 N Gould St. Ste N
Sheridan, WY 82801
support@blockguard.app
privacy@blockguard.app