CallRules Privacy Policy

CallRules: Call Blocker · MJRed Dev LLC (trading as Plainform) · Effective 28 September 2026

1. Who we are

CallRules: Call Blocker ("CallRules") is published through Google Play by MJRed Dev LLC, trading as Plainform ("we", "us"). This policy applies to CallRules. You can reach us at mjred.dev@gmail.com.

2. Data we collect

CallRules has no user accounts or login and does not automatically upload app content or diagnostics to us. We cannot see information processed only on your device. We receive information only if you deliberately send it to us, such as by emailing feedback or a problem report.

We do not include advertising networks, analytics or crash-reporting SDKs, or any other third-party tracking libraries in CallRules.

3. Data CallRules processes on your device

CallRules needs access to certain information in order to function. That information is primarily processed locally. Any user-requested transfer to another service or app is described in section 5.

• Incoming and outgoing call information and contacts — to evaluate the directional blocking, Allow, Silence, and confirmation rules you create. This processing happens on the device. CallRules does not handle SMS or MMS, provide a cloud spam lookup, or automatically send phone numbers to the developer.
• Contacts — optional. With contacts access, CallRules reads your contacts on the device: when a call arrives, it looks up the caller's contact name, starred status, and contact groups to apply the contact whitelist and contact, contact group, and caller-name rules; when you choose a contact or group for a rule, run Rule check, or give a voice contact command such as “block calls from Uncle Bob”, it reads contact names, phone numbers, and group membership. Blocked-call notifications and call history show the caller's contact name, or the caller-ID name your carrier provides.
• Location — optional approximate or precise location is used to evaluate location-constrained rules. If you enable those rules, background location may be needed so they can work when the app is not open. CallRules also reads your current location once, on request, when you tap Use Current Location in the location picker (for a rule or a saved place) or give a voice place command such as “save this place as Home” or “move place Office to here”. CallRules processes that location on the device and stores it only as the coordinates and radius of the rule or saved place you confirm. Saved locations remain on the device unless you include them in a configuration export. Location is never used to infer or look up where a caller is.
• Microphone — optional, used only when you start a voice rule or problem-report dictation. On supported devices CallRules uses Android's on-device speech recognizer and does not silently substitute online recognition. Speech transcripts are not stored in diagnostics. Voice is optional: every voice action can also be done by typing a command or using the app's screens.
• Blocked numbers, whitelist entries, directional Call Rules, saved locations, settings, limited call history (including the caller's contact name or the caller-ID name your carrier provides), and an optional salted PIN hash may be stored in app-private storage. The PIN itself is not stored. Pending outgoing approvals and one-use redial authorizations remain in memory and expire automatically.
• Diagnostics — attaching a report requires your explicit choice. A report may include structured event identifiers, timestamps, screening outcomes and duration, permission or role status, location availability, purchase error codes, import failure codes, and sanitized crash stack frames. They exclude phone numbers, contact names, rule names and patterns, coordinates, speech transcripts, PIN data, purchase tokens, and raw exception messages. Reports describe CallRules's decisions; they cannot establish what a carrier or another phone component subsequently did.
• Exports and imports — configuration exports are created only when you request them and may include enabled and disabled rules, rule direction and per-rule PIN requirement, blocked numbers, whitelist entries, saved locations, and selected settings. Rules that target a contact, contact group, or caller name include the contact's name and Android contact lookup key, the group's name and account, or the name text, so they can be matched again after import. They exclude the PIN hash and attempt state, outgoing authorizations, purchase entitlements, Android permission grants, call history, and diagnostic history. Google Sheets imports occur only when you supply a published sheet URL.

4. Purchases

Paid features are sold as one-time in-app purchases through Google Play Billing. Payments are processed by Google; we never see or store your payment details. CallRules stores only the resulting ownership state for offline access and excludes purchase tokens from diagnostics and configuration exports.

5. Third-party services

We do not embed third-party trackers. CallRules uses or hands information to platform and third-party services only to complete actions you request:

• Google Play Billing — to process in-app purchases and verify entitlements.
• Android system geocoding (when requested) — may send the address query to the device's configured geocoder to return coordinates.
• Google Sheets import (when requested) — retrieves the published sheet URL you provide. The service receives the network request needed to return that sheet.
• Maps, email, and sharing apps (when you choose them) — receive the location, feedback, problem report, diagnostic attachment, or exported file you direct CallRules to hand off. You control whether to complete sending in the selected app. Opening another app does not by itself mean a report was delivered.
• Links you open — Online help, Online troubleshooting, and Privacy policy open plainform.app in your browser; Rate CallRules opens the Google Play listing; Share with friends passes a Google Play link to the app you choose; and the map button for a rule's location or a saved place opens Google Maps at those coordinates (in the Maps app with the place's label, or at maps.google.com in your browser). Visiting plainform.app is an ordinary web request to the site's host, GitHub Pages. CallRules adds no identifiers to these links.

6. Data sharing and sale

We do not sell or rent personal information. We do not automatically upload call data or diagnostics. Information is disclosed to a platform service or destination app only when needed for an action you request, as described in section 5.

7. Data retention and deletion

App-private data remains on your device and is removed when you uninstall CallRules according to Android behavior. Where CallRules offers an export or backup feature, copies you create are under your control and must be deleted through the app or location where you saved them.

While CallRules is running, it opportunistically removes diagnostic records older than seven days and generated sharing files older than 24 hours, and enforces a 1 MiB diagnostic-log limit when recording. Files may remain longer while CallRules is inactive. You can clear diagnostics and generated sharing files in the app at any time.

We do not maintain an account or app-content database about you. If you send us an email, you may contact us to request deletion of that correspondence.

8. Children

CallRules is a general-purpose utility and is not directed at children under 13. We do not knowingly collect information from children.

9. Security

App data is stored in private application storage protected by Android's sandbox. Network connections CallRules makes on your behalf use encrypted protocols where the destination server supports them.

10. Your rights

Privacy laws including the GDPR and the CCPA give you rights to access, correct, and delete personal data held about you. Most information described here remains under your control on your own device. For information you deliberately send us, contact us using the address below to exercise any applicable rights.

11. Changes to this policy

If this policy changes, we will update this page and revise the date at the top. Material changes affecting how CallRules handles data will also be noted in CallRules's release notes.

12. Contact

MJRed Dev LLC (trading as Plainform)
mjred.dev@gmail.com