EasyMyLife Privacy Policy

Covers every app published by EasyMyLife · This page last revised 19 November 2026

How to read this. Part 1 is what holds for every app we make. Part 2 has one section per app, and that is where you will find what your app actually collects — because the answer differs enormously between them. Some of these apps have no internet permission at all and are incapable of sending us anything; one is a synced ledger that necessarily stores your records on our servers. Jump straight to yours:

At a glance

App Package Account needed? Does your data leave the device?
BATNIX in.easymylife.batnix Optional Only if you sign in
KhataBox in.easymylife.mykhata Required Yes — it is a synced service
KeeMu in.easymylife.keemu No EasyMyLife account To your own SIP provider
Keemu GPS Camera in.easymylife.gpscamera None Nothing
Udta Tir in.easymylife.udtatir None Nothing
Torch Light in.easymylife.flashlight None Nothing — no internet permission
AutoRules — Phone Automation in.easymylife.myautosmsresponces None Nothing — no internet permission

Part 1 — What applies to every EasyMyLife app

Who we are

These apps are published by EasyMyLife, which is the developer and the data controller for them, and the entity responsible for this policy. You can reach us at easymylife.in@outlook.com — the same developer contact shown on the Google Play listings. Write to us about anything in this document, including a request to see, correct, export or delete your data.

What is true of all of them

The shared EasyMyLife account

Two of these apps — BATNIX and KhataBox — sign you in to one EasyMyLife account, and each keeps its own data against it. This is convenient, and it has one consequence worth stating up front: deleting your data in one app does not delete the account itself, because that would destroy data belonging to an app you never asked to leave. To remove the login and everything attached to it, write to us and say so; we will confirm with you before anything is removed. The apps that need no account are unaffected by any of this.

Google Play

If you installed an app from Google Play, Google collects its own information about installation, updates and crashes, independently of the app and outside our control. See Google's Privacy Policy and your Play Store settings.

Security

Data held on your device sits in the app's private sandbox, protected by Android's application isolation and by your device's own lock screen and encryption. Where an app talks to our servers, it does so over HTTPS. For the apps that send us nothing, there is no server-side store of your information to breach at all.

No system is perfectly secure and we do not claim otherwise. Keeping your device updated and lock-screen protected remains the most effective safeguard. If we become aware of a breach affecting your personal data we will notify affected users and the relevant authority as required by law.

Children

These apps are intended for a general audience and are not directed at children under 13 (KhataBox is for adults and says so in its own section). We do not knowingly collect personal information from children. A parent or guardian who believes a child has supplied personal information, or that a child's details have been recorded by someone else using one of these apps, may contact us and we will remove it.

Your rights

Depending on where you live, you may have rights under laws such as India's Digital Personal Data Protection Act, the GDPR (EEA/UK), or the CCPA/CPRA (California), to access, correct, delete, port or object to the processing of your personal data. We do not charge for these requests and we do not discriminate against anyone who makes one.

For most of the apps on this page we hold nothing about you at all, so there is nothing on our side to retrieve or correct — everything is on your device and fully under your control. Where we do hold data, the app's own section says how to see, export and delete it.

Changes to this policy

This policy is updated when an app's handling of data changes, and the date on the relevant section changes with it. If a future version of an app collects something not described here, this policy and that app's Google Play Data Safety declaration are updated before that version is released. Each app's section carries its own "last updated" date, so you can tell which promises changed and which did not.

Contact

Questions about this policy, about an app's handling of data, or to make a data request: easymylife.in@outlook.com.

Part 2 — App by app

Each section below applies only to the app it names, and is the operative policy for that app.

BATNIX

Cricket scoring · Android application in.easymylife.batnix

Last updated 19 November 2026

BATNIX is a cricket scorebook, and it has two modes that differ completely in what leaves your phone. As a guest — the default — you need no account and nothing is sent to us at all. If you sign in, your cricket records sync to our servers so you can reach them from another device and not lose them if the phone goes missing.

Scoring as a guest — no account, no upload

You can install the app and score a complete match without creating an account or going online. In guest mode everything sits in a private database inside the app's own sandbox on your device, and the part of the app that uploads records is switched off entirely — not merely deferred. Teams, players, matches, ball-by-ball deliveries and scorecards created as a guest are never transmitted to us, and we have no way to see them.

The app does create a random identifier for the installation, so records can be labelled with the device that produced them. As a guest, that identifier stays on the device with everything else.

If you later sign in, the app asks whether you want to import your guest matches into your account. That import happens only if you choose it. You can decline and keep those matches purely local.

Signing in

There are two ways to sign in, and you pick one:

The login is shared with the other EasyMyLife apps. Signing in to BATNIX creates or reuses one EasyMyLife account, and the other apps listed on this page key their own data to it. This matters most when you come to delete things — see below.

After sign-in the app holds a session token so you are not asked to sign in on every launch. On your device it lives in Android's encrypted preference storage, not ordinary settings. On our side only a one-way hash of the token is kept, so the stored value cannot be used to impersonate you. Signing out revokes that token on the device you signed out from.

What is stored when you are signed in

DataWhy
Account details — your name, your email address or mobile number, profile picture, account identifier To identify your account, sign you in on another device, and show who you are in the app
Cricket records — teams, players, matches, innings, every delivery, dismissals, scorecards and results This is the app. Your scorebook, kept safe and reachable from your devices
Correction history — deliveries that were undone or edited, with what they said before and after So a disputed scorecard can be explained. A corrected ball is never silently rewritten
Photos — a team logo or a player photo, if you add one Shown on team and player screens. Optional; the app works fully without any
Details of other players — the names you type, and optionally their mobile numbers and photographs So a squad is a squad and not a list of initials. See the note below
Device details — a random per-installation identifier, device make and model, app version To sync the right records to the right device, stop two phones fighting over the same match, and diagnose problems
Push token — issued by Firebase Cloud Messaging Only if notifications are enabled, so we can tell your device that new match data is waiting. Optional; declining changes nothing else
Crash reports and diagnostic data So a crash gets fixed instead of being suffered in silence — see the next subsection

Names of other people

A scorebook is mostly about other people, so the names you type into BATNIX are usually not your own. Enter only what is reasonable for recording a cricket match — a playing name is enough — and make sure you are entitled to record teammates and opponents this way; only add a mobile number or a photograph with that person's agreement. We treat those details purely as part of your scorebook: they are never used to build a profile of those people, never matched against other accounts, and never used for marketing. If someone asks you to remove their name, you can edit or delete the player in the app, or write to us.

Crash reporting

BATNIX includes Firebase Crashlytics (Google). When the app crashes it sends a report containing the state of the app at the moment it failed: the error, the sequence of calls that led to it, your device model, the Android version, and the app version. It does not send the contents of your matches.

This is the one thing BATNIX collects that is neither your account nor your cricket data, so it is stated plainly rather than buried: it is active for every user of a release build, including guests, and it is the reason this app — unlike most of the others on this page — cannot claim to contain no third-party SDK.

What is not collected

Scoring without a network

BATNIX is built to work with no signal, because cricket grounds often have none. Every ball is saved to the device first, and the screen only reports success after that save has committed. If you are signed in, records upload later when a connection is available; if you are a guest, they are never uploaded. A match can be started, scored and completed from first ball to last with the phone entirely offline.

Third-party services

These process data on our behalf, to make the app work. There are no other third-party SDKs in the app and no other processor.

Getting your data out

Open Settings → Export my data. You get a single file containing every match, ball by ball, in a readable format you can keep anywhere. It is built on your phone and works with no connection.

Deleting your data

As a guest, it is entirely in your hands: delete an individual team, player or match in the app; clear the app's data in Settings → Apps → BATNIX → Storage; or uninstall, which removes the app's private storage completely.

With an account, open Settings → Delete my BATNIX data. This permanently removes every team, player, match and ball you have recorded, from your phone and from our server. It cannot be undone. You can also request deletion by email, without installing the app. Deleting individual matches, teams or players in the app syncs that deletion to our servers too.

One thing to be clear about: your EasyMyLife login is shared with the other EasyMyLife apps, and each of those keeps its own data against it. Deleting your BATNIX data does not delete that login, because doing so would destroy data belonging to apps you never asked to leave. To delete the login itself and everything attached to it, write to us and say so; we will confirm before anything is removed.

Signing out, or uninstalling, does not by itself delete your account. Routine encrypted backups may retain copies for a short period before being overwritten in the normal cycle, and we keep only what the law requires us to keep. Otherwise your scorebook is kept until you delete it — we do not expire matches, because a scorebook from five seasons ago is the point of keeping one.

Security and your rights, specific to BATNIX

Traffic between the app and our servers uses HTTPS; cleartext is disabled. On our servers, session tokens are stored only as one-way hashes, and every request is checked to confirm that the records being read or written belong to the account making the request.

As a guest we hold nothing about you, so there is nothing on our side to retrieve, correct or export — it is all on your device and fully under your control. With an account, you can view and correct most data directly in the app, export it yourself, and delete it yourself.

BATNIX is not directed at children under 13. Junior cricket being what it is, a scorer may well record the names of children as players. Those names are part of someone's scorebook, not accounts and not profiles. A parent or guardian who believes a child's information has been recorded inappropriately may write to us and we will remove it.

Permissions

PermissionPurposeOptional?
INTERNETSigning in and syncing your records when you have an accountNo — granted at install. Unused in guest mode, apart from crash reports
ACCESS_NETWORK_STATEDetects whether there is a connection, so uploads wait for one instead of failingNo — granted at install, no personal data access
POST_NOTIFICATIONSShows notifications about your synced matchesYes — everything works if you decline
FOREGROUND_SERVICE
FOREGROUND_SERVICE_SPECIAL_USE
Keeps a match in progress running reliably while the app is not on screenNo — granted at install, no personal data access

Those are the only permissions the app declares. In particular it does not request ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, READ_CONTACTS, RECORD_AUDIO, READ_PHONE_STATE, or access to your device's files outside its own storage.

Back to the top

KhataBox

Ledger, invoices and expenses · Android application in.easymylife.mykhata · also published on its own page

Last updated 19 November 2026. This section explains what information KhataBox (operated from easymylife.in) collects when you use the service, how we use it, and the choices you have.

Who we are

KhataBox is a personal ledger that lets you and the people you invite to your workspace track money owed to and from your contacts. The service is operated by the easymylife.in team. If you have any question about this policy, write to us at easymylife.in@outlook.com.

Information we collect

Account information (from Google Sign-In). When you sign in with Google, Google shares your Google account ID, the email address on that account, your display name, and your profile picture URL. We use these only to identify your KhataBox account and to show your name and picture inside the app. We do not receive your Google password and we do not request access to Gmail, Drive, Calendar, Google Contacts, or any other Google service. (The app can import from the contact list stored on your phone — that is a separate, device-level permission you grant in Android, described below, and it never touches your Google account.)

Workspace content you create. When you use the app you enter records yourself — workspace name and currency, the names, phone numbers, email addresses, addresses, tax identifiers and notes of the contacts you trade with, the transactions (amount, date, description, payment method, optional receipt image) you log against them, and your invoices, quotations, expenses and products. You may also attach pictures: a photo for a contact, and a logo and signature for your business. You are responsible for the accuracy of what you record and for the consent of any individual whose contact details or photograph you store.

Technical information. Like any web service, our servers record the IP address, browser user-agent, and timestamp of each request in standard access logs. When the Android app signs in it also tells us which version of the app it is, so that we can keep older installations working correctly. We use these for security monitoring and to diagnose problems. We do not use third-party advertising or analytics trackers.

How we use your information

We use the information above only to operate KhataBox: to authenticate you, to render your workspace, to show your data back to you and to other members of your workspace, to send transactional email (sign-in links, workspace invitations, password resets), and to keep the service secure. We do not sell your information, we do not rent it, and we do not share it with advertisers.

Permissions the Android app asks for

Every permission below is asked for at the moment you first use the feature that needs it, never at launch, and each one is optional — the rest of the app keeps working if you decline.

Contacts (phonebook). Only when you choose “Import from phone contacts”. We read the names and phone numbers from your device so you can pick who to add to your khata. Only the entries you actually select are saved; the rest are read to draw the list and then discarded. We do not upload your phonebook, we do not read it in the background, and we never copy it anywhere other than into the contacts you choose to create.

Camera. Used to photograph a receipt, scan a product barcode, or scan a QR code (to join a workspace or sign in on the web). Receipt text recognition and barcode decoding happen on your device; the picture is not sent anywhere for analysis. A receipt image is uploaded only if you attach it to a transaction and save it.

Photos you attach. Pictures you pick for a contact, or for your business logo and signature, are stored on our servers so they appear on your other devices and on your invoices. They are kept in a non-public location under unpredictable filenames and are served only to people signed in to that workspace.

Microphone — via your keyboard’s voice input. The “Speak the entry” button hands over to the speech recogniser already installed on your phone (normally Google’s). That app records and transcribes the audio under its own privacy policy and returns text to us; KhataBox never receives or stores the recording, and the app does not hold the microphone permission itself.

Bluetooth. Only to send a receipt to a thermal printer you have already paired in Android settings. We list paired printers; we do not scan for nearby devices, and the app therefore does not request location access, which Bluetooth scanning would require.

Notifications. Used for payment reminders you set yourself. Reminders are scheduled on your device.

Google user data — limited use

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use the basic profile data Google returns (account ID, email, name, picture) solely to provide the sign-in feature you requested. We do not transfer that data to others except as required to operate the service, comply with the law, or with your explicit consent. We do not use it for advertising and humans do not read it except where you give us explicit consent to look at a specific item, or where it is necessary for security purposes (such as investigating abuse) or to comply with applicable law.

Who else can see your data

Workspace members. Anything you record in a workspace is visible to the other people you have invited to that workspace, according to their role — viewer, editor, or admin. A role is held per section, so the same person can be an admin of the invoices and a viewer of the khata. Workspace admins can see the list of members with each person's email address and their role in each section, and can change those roles or remove a member.

People you share a single record with. You can share one ledger, customer, or vendor with somebody who is not a member of your workspace, by giving them a short code or a QR code. That code is valid for ten minutes and can be used once. Using it does not let them into the rest of your workspace: they see only that one record — its name, contact details, balance, and the entries recorded against it — and, if you granted edit access, they can add and change entries on it. Their access lasts until you revoke it, not until the code expires. The app shows you everyone who currently has access to a record, together with the email address of the account they used, and lets you end any of it at any time.

What the other person sees about you. Someone who accepts a share or an invitation can see the name of the workspace the record belongs to. Equally, when someone accepts something you shared, their email address becomes visible to you — that is how you can tell who has access and decide whether to keep it.

Service providers. We rely on a small number of infrastructure providers to host the service (web hosting, database, transactional email). They process the data only on our behalf and under contract.

Legal requests. We will disclose information if required to do so by a valid legal process, or where we believe in good faith that disclosure is necessary to protect our rights, your safety, or the safety of others.

How we protect your data

All traffic to KhataBox is served over HTTPS. Passwords (for the email + password sign-in option) are stored hashed with a modern, salted algorithm and are never logged. Access to the production database is restricted to the operators of the service. No system is perfectly secure, but we work to keep yours safe and to notify you promptly if we ever become aware of a breach affecting your account.

Retention and deletion

Records you delete from inside the app (accounts, transactions) are soft-removed by default — they are hidden from your views but kept in the database for audit purposes. From the Profile page you can permanently delete your account and all the workspace data associated with it; this deletion is irreversible and is normally completed within seven days. You can also request deletion at any time by writing to easymylife.in@outlook.com from the email address registered on your account.

Pictures are deleted with the thing they belong to: removing a contact’s photo deletes the stored file, replacing a logo or a photo deletes the one it replaced, and deleting your account removes the image folder for every workspace it covered.

Your choices and rights

You can sign out of KhataBox at any time, revoke KhataBox's access to your Google account from your Google Account permissions page, and update or delete the workspace data you have entered. Depending on where you live, applicable law may give you additional rights to access, correct, or export your data; to exercise any of these rights, contact us at the address above.

Children

KhataBox is intended for adults. We do not knowingly collect data from anyone under the age of 18. If you believe a minor has created an account, please contact us and we will remove it.

Changes to this policy

We may update this policy from time to time. When we make a material change we will update the date at the top of this section and, where appropriate, notify you the next time you sign in.

Back to the top

KeeMu

SIP / VoIP dialer · Android application in.easymylife.keemu

Last updated 28 June 2026

In short: KeeMu is a SIP/VoIP dialer that places calls through a SIP account you provide. Your data stays on your device. We run no server in the call path, we do not collect your personal data, and the app contains no advertising or analytics SDK.

Information the app handles

DataWhyWhere it is stored
SIP account details (username, password, domain, proxy, port) To register with and authenticate to the SIP server you choose, so you can place and receive calls. Stored locally on your device only. Sent only to the SIP server you configure.
Microphone audio Captured during calls and transmitted to the other party via your SIP provider. Not stored unless you turn on call recording.
Camera (video) Only used if you start a video call; transmitted to the other party. Not stored.
Contacts Read on your device to show a caller's name instead of a bare number. Read locally and shown in the app. Never uploaded or shared by us.
Call history (recents) To show your recent calls. Stored locally on your device.
Blocked numbers To auto-decline calls you choose to block. Stored locally on your device.
Call recordings (optional) Only if you explicitly enable recording. Disabled by default. Saved only in the app's private storage on your device. Not uploaded by us.
Network & device state To maintain connectivity and handle call and network changes. Used in memory; not collected by us.

How your information is shared

Call recording

Call recording is off by default. If you enable it, recordings are stored only in the app's private storage on your device. Recording calls may be subject to laws in your jurisdiction that require the consent of all parties. You are solely responsible for complying with applicable laws and for informing other participants. We have no access to your recordings.

Retention and deletion

Account details, call history, blocklist, and any recordings remain on your device until you delete them, clear the app's data, or uninstall the app. Disconnecting your account from within the app removes the stored account credentials from the device. Because your data lives on your device you remain in control: you can also revoke permissions in Android Settings at any time.

Security, specific to KeeMu

Your data is kept on your device and protected by Android's app sandboxing. Where your SIP provider supports it, you can configure encrypted transport (TLS/SRTP) in the app settings.

Permissions

PermissionPurpose
Microphone (RECORD_AUDIO)Mandatory — captures your voice for calls. The app cannot place or receive calls without it.
Contacts (READ_CONTACTS)Optional — displays caller names. If denied, calls simply show numbers.
CameraOptional — video calls only.
Notifications (POST_NOTIFICATIONS)Shows incoming and ongoing-call notifications.
Phone state / manage own callsHandles call state and self-managed VoIP calls.
Internet / network & Wi-Fi stateConnects to your SIP server and carries call media.
Foreground serviceKeeps an active call running reliably while the app is in the background.

Back to the top

Keemu GPS Camera

Location-stamped photos · Android application in.easymylife.gpscamera

Last updated 9 August 2026

In short: Keemu GPS Camera does not collect, transmit, or sell your personal data. Your photos and your location are used only on your device, to stamp the tag onto the picture you just took, and the photos stay in the app's private storage until you choose to share or delete them. We have no servers and no account system.

Information the app accesses

DataWhy the app needs itWhere it goes
Precise and approximate location (GPS) To read your current latitude and longitude, and to look up a human-readable address, so they can be drawn onto the photo you capture. Held in memory while the camera screen is open and written into the image you capture. Not stored separately, not transmitted to us.
Camera To show the live preview and take photos. Frames are shown on screen; the captured photo is saved to the app's own storage on your device.
Photos you capture They are the product of the app. Saved to the app-specific external storage directory that belongs to Keemu GPS Camera. Other apps cannot read this directory.
Your tag and layout settings To remember your chosen layout style and which fields (date, coordinates, address, app name) are shown. Stored in the app's private preferences on your device.

The app does not ask for or access your contacts, your microphone, your call or SMS data, your existing photo gallery, your device identifiers, or your advertising ID. It has no login, so it never collects a name, email address, or password.

What is not collected

Location, in detail

Location is requested at runtime and used only while the camera screen is in the foreground. The app requests ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION so that coordinates are accurate enough to be meaningful on a photo. It does not run in the background and does not request background-location access, so it cannot track your movements when the app is closed.

You can decline the location permission, or later revoke it in Settings → Apps → Keemu GPS Camera → Permissions. The camera continues to work; photos are simply captured without a coordinate or address tag. Turning off the “Show GPS Coordinates” and “Show Address” toggles inside the app has the same effect on what appears on the image.

Converting coordinates into a street address uses Android's built-in geocoding service. That lookup is performed by the Android operating system and, depending on your device, may be served by Google's location and geocoding services under Google's Privacy Policy. The app itself neither logs nor stores the result beyond drawing it onto your photo.

Your photos

Captured photos are written to the app's private external files directory. They are not added to your shared gallery, and no other app can read them without your involvement. A photo leaves the app only when you tap Share and pick a destination — a messaging app, email, cloud storage, or anything else installed. Once shared, the receiving app or service handles that copy under its own privacy policy, and we have no control over it.

Remember that a photo tagged with coordinates and an address reveals where it was taken. Consider that before sharing publicly.

Third-party services

The app includes the following Google components, and no others:

These are provided by Google and are governed by Google's Privacy Policy.

Retention and deletion

Because nothing is stored off your device, deletion is entirely in your hands:

Photos you have already shared to another app or service are outside our reach and must be deleted there.

Permissions

PermissionPurposeOptional?
CAMERALive preview and photo captureNo — the app's core function
ACCESS_FINE_LOCATIONPrecise coordinates for the photo tagYes — capture still works without it
ACCESS_COARSE_LOCATIONApproximate position when precise location is unavailable or deniedYes

Back to the top

Udta Tir

Game · Android application in.easymylife.udtatir

Last updated 26 June 2026

In short: Udta Tir collects nothing. There is no account, no analytics, no advertising and no tracking. Your high scores and settings are stored on your device only.

Information we do not collect

The app does not collect your name, email address, phone number, contacts, location, photos, microphone or camera input, device identifiers for advertising, or any other personally identifiable information. There is nothing to sell or share, and nothing is stored on our servers.

Information stored on your device

To make the game work, the app stores a small amount of data locally on your device only. It never leaves your device and is never transmitted to us or to any third party:

This data is removed when you uninstall the app or clear its data from your device settings.

Sharing a score card

The app lets you create a score-card image and share it using other apps on your device, for example a messaging or social app. This happens entirely at your request. The image is generated on your device and we do not receive a copy of it. Once you share it, the receiving app's own privacy practices apply.

Permissions

PermissionPurpose
VIBRATEHaptic feedback when an arrow hits you during play. No data is collected through this permission.
INTERNETUsed solely to check Google Play for an available app update. The connection is not used to transmit any personal information about you.

Google Play services

The app uses Google Play's in-app update mechanism to check for new versions. That interaction is handled by Google Play under Google's Privacy Policy.

Back to the top

Torch Light

Torch · Android application in.easymylife.flashlight

Last updated 18 November 2026 · Effective 15 January 2015

In short: Torch Light collects nothing. The app has no internet permission, so it is technically incapable of sending anything anywhere. It has no account system, no advertising and no analytics. Your settings are saved on your phone and are deleted when you uninstall.

Information the app accesses

DataWhy the app needs itWhere it goes
Your settings To remember your light mode (steady, blink or SOS), blink speed, auto-off timer, and whether the light turns on when the app opens. Stored in the app's private preferences on your device. Never transmitted. Removed when you uninstall.
Camera flash (LED) To switch the torch on and off, using Android's system torch control. Nowhere. The app does not hold the Camera permission, never opens the camera, and cannot take or read photos or video.
Whether a call is ringing (optional feature, off by default) Only if you switch on “Blink on incoming calls”, so the light can blink while your phone rings. Nowhere. Held in memory only while a call is ringing, and discarded when the call is answered or ends.

The app does not ask for or access your location, contacts, microphone, SMS, call logs, photo gallery, device identifiers, or your advertising ID. It has no login, so it never collects a name, email address, or password.

What is not collected

Notification access, in detail

“Blink on incoming calls” is switched off by default. If you choose to turn it on, Android asks you to grant Notification Access. This is used for exactly one purpose: to notice that a call is currently ringing, so the light can blink.

You can withdraw this access at any time by turning the feature off inside the app, or in Settings → Apps → Special app access → Notification access. Everything else in the app continues to work normally.

This approach was chosen deliberately: detecting a ringing call this way avoids requesting the READ_PHONE_STATE permission, which would give the app access to your phone number and call information that it does not need.

No internet access

Because the app does not declare the INTERNET permission, Android itself prevents it from opening any network connection. There is no mechanism by which your settings, your usage, or anything else could reach us or a third party. You can verify this in the app's permission list on Google Play or in Settings → Apps → Torch Light → Permissions.

Retention and deletion

Because nothing is stored off your device, deletion is entirely in your hands:

Permissions

PermissionPurposeOptional?
FOREGROUND_SERVICE
FOREGROUND_SERVICE_SPECIAL_USE
Keeps the light or the SOS signal running while the app is not on screenNo — granted at install, no personal data access
POST_NOTIFICATIONSShows the ongoing notification that lets you switch the light off from the notification shadeYes — the light still works if you decline
WAKE_LOCKKeeps blink and SOS timing accurate while the screen is offNo — granted at install, no personal data access
Notification access
(BIND_NOTIFICATION_LISTENER_SERVICE)
Detects a ringing call so the light can blink — see aboveYes — off by default, granted only if you enable the feature

The app requests no dangerous runtime permissions beyond the optional ones above. In particular it does not request CAMERA, INTERNET, READ_PHONE_STATE, or any location permission.

Back to the top

AutoRules — Phone Automation

Phone automation · Android application in.easymylife.myautosmsresponces

Last updated 13 November 2026

In short: AutoRules runs your rules on your phone. It holds no internet permission, contains no analytics or advertising code, and has no server. Nothing you write or store in it reaches us.

Messages the app reads

When you have a rule that reacts to text messages, the app reads the sender and text of incoming SMS in order to compare them against that rule. Messages that match no rule are discarded immediately and never stored. If you turn on “Save incoming messages”, matching messages are kept in the app's private database on this device.

Device information used by rules

Rules that are not about messages read only what they need, on this device, at the moment they run: the battery level, whether the charger is connected, the current ringer mode, and the time of day. A rule such as “when the battery falls to 20%, turn the ringer down” needs the battery level to notice that crossing. So that it can tell a real crossing from the same level being reported again, the app keeps the last battery level and charging state in its own private settings. Nothing else about the device is recorded, and none of it is built into a profile. The app does not access your location, your call log, or any advertising or device identifier.

Contacts

The app holds no contacts permission and cannot read your contact list. When you tap “Pick from contacts” while writing a rule, Android's own picker opens and hands back only the single phone number you chose, which is then saved in that rule. The rest of your contacts stay invisible to the app.

Messages the app sends

When a rule with a “send a text message” action fires, the app sends the text you wrote to the number you chose, using your device's SMS service. It never sends messages you have not configured, and rules without that action send nothing.

What leaves your device

Nothing. The app does not hold the INTERNET permission, contains no analytics or advertising code, and has no server. Your messages, rules and settings never leave the device except in a backup file you explicitly create and choose where to save.

Retention and deletion

Stored messages and rules remain until you delete them or uninstall the app. Uninstalling removes the app's database and its private settings, including the remembered battery and charging state, completely.

Back to the top