Privacy Policy

AntiTheft Alarm — Android app
Effective: January 1, 2026 · Last updated January 1, 2026

The 30-second summary

AntiTheft Alarm runs 100% on your device.

We do not collect, store, transmit, or sell any personal data.

The app does not request the Internet permission — it literally cannot phone home.

No accounts, no sign-ups, no email collection.

No analytics, no crash reporters, no trackers, no third-party SDKs that send data off-device.

No cloud storage. No servers. Audio used for clap detection is processed in real-time on the device only and is never recorded or saved.

1 Who we are

This privacy policy describes how the AntiTheft Alarm mobile application (the “App”) handles information when you use it on an Android device. The App is published by EveryBitt (“we”, “us”, “our”). For any privacy-related question you can reach us at contact@everybitt.site.

This policy applies only to the AntiTheft Alarm Android app. It does not cover any third-party website, store listing, or service operated by another party.

2 What we do not collect

The App was built with a strict privacy-by-design approach. We do not collect, transmit, store, share, or sell any of the following:

The App also has no Internet permission declared in its Android manifest. Android itself prevents the App from opening any network connection. You can verify this in your device settings under Apps → AntiTheft → Permissions.

3 Information stored locally on your device

So that your settings persist between sessions, the App stores the following information in its private, sandboxed storage area on your device (which Android isolates from every other app):

This data never leaves your device. Uninstalling the App removes it entirely. You can also clear it at any time from Settings → Apps → AntiTheft → Storage → Clear data.

4 Permissions we request & why

The App asks only for the minimum permissions needed for it to function. Every permission is used solely on-device, in real time, for the feature described below — never to collect data about you.

PermissionWhy it is used
RECORD_AUDIOTo detect claps for the “Find by clap” feature. The microphone stream is analysed live, on-device, in memory only. No audio is ever recorded, saved, or sent anywhere. The mic is only active while the clap-detection mode is armed; you can revoke the permission at any time and the rest of the App will keep working.
CAMERA (flash only)To flash the LED on the back of your phone when the alarm fires, so the device is easier to find in low light. We do not open the camera, take pictures, or capture video. The flash permission belongs to the android.hardware.camera.flash feature.
POST_NOTIFICATIONSTo show the “AntiTheft is armed” notification so you always know when protection is active, and to deliver the alert when the alarm fires.
VIBRATETo vibrate the device as part of the alert.
WAKE_LOCKTo keep the CPU awake while the alarm is sounding, so the alert is not cut short.
FOREGROUND_SERVICE (microphone / mediaPlayback / specialUse)To run the armed-protection service reliably in the foreground while you are not in the App, so Android does not stop it. Foreground service notifications are visible to you at all times.
RECEIVE_BOOT_COMPLETEDTo show a notification after a reboot that lets you tap to re-arm protection. The alarm is not automatically re-armed without your action.
SET_WALLPAPERTo apply the bundled animated wallpapers you select to your home screen or lock screen.
READ_MEDIA_AUDIOTo preview and play the bundled alarm sounds; if you choose to use one as your ringtone, this lets the system read the file. No audio files on your device are scanned or uploaded.
Battery-optimisation exemptionOptional. If granted, Android stops killing the protection service in the background. You can revoke this at any time in system settings.

Notably absent: No INTERNET, no ACCESS_NETWORK_STATE, no ACCESS_FINE_LOCATION / COARSE_LOCATION, no READ_CONTACTS, no READ_SMS, no READ_PHONE_STATE, no READ_EXTERNAL_STORAGE beyond audio media.

5 Microphone & audio handling (in detail)

Because the clap-detection feature uses the microphone, we want to be specific about how that audio is handled:

6 Third parties & data sharing

We do not embed any third-party advertising SDK, analytics SDK, attribution SDK, crash-reporting SDK, tag manager, or tracker. We have no commercial relationship that would cause us to share information about you. We do not sell or rent any data because we do not have any data to sell or rent.

The only legally-required disclosure: if a court of competent jurisdiction were to order us to disclose information we hold about a user, we could only disclose what we have — which is nothing.

7 Children

The App is suitable for all ages. We do not knowingly collect any information from anyone, including children under the age of 13 (or the applicable minimum age in your jurisdiction). Because we do not collect personal data at all, the App is compliant with the U.S. Children’s Online Privacy Protection Act (COPPA) and the EU General Data Protection Regulation (GDPR), including its specific rules regarding minors.

8 Your rights under GDPR, CCPA and similar laws

Privacy laws around the world give you specific rights over your personal data — typically the right to access, correct, delete, port, restrict processing of, or object to processing of your data. Those rights apply to data a company holds about you.

Because we hold no data about you, there is nothing to access, correct, delete, port, restrict or object to. If you would still like written confirmation that we hold no data about a specific device or identifier, you may contact us at the address below and we will respond within thirty (30) days.

9 Security

Settings are stored in the App’s sandboxed private storage area, which Android isolates from other apps and from non-system processes. We follow Android best practices for permission scoping (minimum-necessary permissions, runtime prompts for sensitive permissions, on-demand foreground services) and ship the App with up-to-date target SDK and security patches.

That said, no method of storage on a mobile device can be made absolutely secure. If your physical device is compromised, the local settings file could in principle be read. Since the settings file contains no personal information, the only consequence would be that an attacker could learn your alarm preferences.

10 Changes to this privacy policy

If we ever change this policy in a way that materially affects your rights — for example, if we ever started to collect any data — we will update the effective date at the top of this page and announce the change inside the App. We will never silently change the privacy posture of the App. The simplest way to stay informed is to read this page when the App is updated.

11 Contact us

For any privacy-related question, comment, or request, please write to:

✉ contact@everybitt.site

Please mention “AntiTheft privacy” in the subject line so we can route your message quickly.