PRIVACY POLICY
Ramz Care
There is a second Ramz app on Google Play,
Ramz (com.sanadtech.ramz), which is free
to install. It has its own policy at
sanadtech.us/ramz/privacy. Ramz Care is
the same app, bought once as a paid app instead. The two hold your
data in exactly the same way; they differ in how they are paid
for, and that is the only reason the two policies differ. In this
app it means two things a reader of the other policy would not find
here: the purchase can be
shared through Google Play Family Library, and the
app is often
set up by one person on another person's phone.
The short version
Ramz Care keeps reminders and photographs on the phone it is installed on, in the app's own private storage, and nowhere else. There is no account, no server, no analytics, no advertising and no tracking. The app makes no network calls and declares no network permission at all. It works with the phone in aeroplane mode.
Two things a careful reader should know before going further. Nothing is carried to a new phone — reminders and pictures are deliberately kept out of Android's backup, so a new device starts empty. And whoever's phone it is on, that phone holds the only copy. The person who bought the app cannot see it, and neither can we.
What Ramz Care stores, and where
Everything the app holds lives on the device it is installed on, inside storage that belongs to the app and that other apps cannot read.
| What | Where on the phone | Backed up by Android? |
|---|---|---|
| The reminders — the words written, when they should arrive, how they should reach the person (quiet notification or full-screen alarm), and whether each one is live, done or archived | A database in the part of storage the phone can read before it is first unlocked after a restart (see “A note on the lock screen”) | No. Android never backs this area up |
| The photographs — the picture taken or chosen, the version the app composes with the words on it, and a small thumbnail | The app's private files | No. The app excludes them on purpose |
| A delivery record — for each time a reminder was due: whether it arrived, and if it did not, what the phone looked like at the time (the phone's make, whether battery saving was restricting the app, the app's standby state, whether notifications were allowed, whether Do Not Disturb was on); the date of each check the app ran; and what the last full-screen alarm was allowed to do | The same database as the reminders | No |
| The language setting | The same pre-unlock area | No |
| The theme, and whether a tip or a setup prompt has already been shown | Ordinary private app storage | Possibly — see below |
About “possibly”: Android offers to back up an app's ordinary private storage to the Google account on the phone, if Android backup is switched on. The app does not stop that for the small settings above. So, on a new phone signed into the same Google account, the theme choice may come back even though the reminders and pictures will not. That backup is Android's, held by Google under Google's terms; the app never sees it and cannot delete it. We state it because a policy that says “nothing leaves the phone” without this sentence would be very slightly untrue.
The delivery record exists for one reason: Android will sometimes block a reminder without telling the app, and Ramz Care promises to tell the person when that happened and what to change. It cannot do that without writing down what the phone looked like at the time. The record never leaves the phone.
A note on the lock screen
Reminders, the delivery record and the language setting are kept where the phone can reach them before it is first unlocked after a restart. That is what lets an 8 am reminder arrive on a phone that rebooted overnight and nobody has unlocked yet. The trade-off, stated plainly: that area is still private to the app and unreadable by other apps, but it is not additionally sealed with the lock-screen PIN or pattern the way the rest of the phone is. The photographs are not in that area; they are in the sealed part.
What Ramz Care never collects or shares
- No account. No sign-up, no profile, no login. The app does not know who is using it, and it does not know who bought it.
- No server. There is nothing of ours for the data to go to.
- No network use — and no network permission. The app makes no network calls, and because it contains no purchase library, its permission list carries no network permission at all.
- No analytics, no crash reporting, no advertising, no advertising identifier, no tracking.
- No location. The app does not ask for, read or store location.
- No reading of the gallery, contacts, calendar, messages, files or other apps.
- No sharing or selling. Nothing is sold, shared, transferred or disclosed to anyone, because the app holds no copy of anything to share.
The permissions Ramz Care asks for, and why
Ramz Care asks for as few permissions as an alarm-style reminder app can. Each one changes only how a reminder reaches the person; none of them moves data anywhere.
-
Notifications (
POST_NOTIFICATIONS) — so a reminder can appear at all. -
Exact alarms (
SCHEDULE_EXACT_ALARM) — so a reminder can arrive at the minute chosen rather than “some time around then”. If it is declined, the app still delivers, less precisely, and says so. -
Full-screen alerts
(
USE_FULL_SCREEN_INTENT) — so a reminder marked as an alarm can take over a locked screen. If the phone or Google Play withholds this, the reminder arrives as an ordinary notification instead. -
Run after restart
(
RECEIVE_BOOT_COMPLETED) — so reminders are re-armed after the phone reboots. It does nothing else.
Those four are the only permissions that affect anyone. For
completeness: the app's manifest also contains one private,
signature-level permission named
com.sanadtech.ramz.care.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, which a Google user-interface library (AndroidX Core) defines and
uses to protect its own internal broadcast receivers. It grants nothing
outside the app and no access to anyone's data. We list it because it is
in the manifest, and a policy that quietly omitted it would be tidier
than it is true.
Camera — no permission, on purpose
When Take a photo is tapped, the app asks the phone's own camera app to take the picture and hand back that one file. Ramz Care itself never holds camera access and cannot open the camera on its own; it receives one image, which it copies into its private storage. The camera app's own permission prompt may appear, and that is that app's, not ours.
The photo library — no permission either
Choose a picture uses Android's system photo picker. One image is picked; the app receives only that image and cannot see, list or search the rest of the gallery. A picture can also be sent to Ramz Care from another app's share menu — the app copies that one picture and nothing else.
How this app is paid for
Ramz Care is a paid app, bought once on Google Play. There is nothing to buy inside it: no unlock, no subscription, no limit on the number of reminders, and no purchase library in the app.
Google Play handles the purchase entirely. The payment happens on Google Play before the app is installed; the card or other payment details go to Google and never to us. We do not see, store or process them. The purchase is governed by Google Play's terms and Google's Privacy Policy.
What the app keeps about the purchase: nothing. Because Google Play sells the app itself rather than something inside it, the app has no purchase record to keep and never asks Google whether it was bought. Google Play decides who may install it.
What Google may show us. Google Play gives developers basic order records for refunds and support. We cannot see the payment method, and we do not receive a buyer's name or email address from a purchase. Refunds are Google's to process, under Google Play's refund rules.
Family Library
Ramz Care is opted into Google Play Family Library, so one purchase can be installed by the members of the buyer's Google family group — the person it was bought for included — with no further purchase. This is worth being precise about, because it is the reason the paid app exists.
- Family Library is Google's mechanism, run by Google. Who is in a family group, who manages it, and which purchases are shared are all held by Google under Google's terms and Google's Privacy Policy. The app takes no part in it and cannot see it.
- We do not know the family group exists. We are not told who bought the app, who it was shared with, or how many phones it is on. Nothing in the app reports back.
- Each phone is on its own. A shared install on a second phone starts empty and holds only what is created on that phone. There is no link between family members' copies — no syncing, no viewing of one phone's reminders from another — because there is no server to carry it.
Set up on someone else's phone
Ramz Care is designed to be set up sitting beside the person whose phone it is. In privacy terms:
- The phone holds the only copy. Reminders and pictures created on it belong to that phone and stay there. The person who bought the app, the person who set it up, and we ourselves cannot see them from anywhere else.
- Nothing can be managed from a distance. There is no remote view, no remote editing and no activity report, because there is no account and no server. That is a limitation of the app, stated deliberately rather than sold around: a carer who needs to change a reminder changes it on that phone.
- The person's own controls apply. Notifications, exact-alarm and full-screen permissions are granted on that phone, by whoever is using it, and can be withdrawn there.
Children
Ramz Care is not directed at children, and we do not knowingly collect personal information from anyone, of any age — the app collects none.
That sentence carries weight beyond politeness, so here is why it is there. Google Play asks every developer to declare who an app is for, and an app that is aimed at children — or that a reviewer judges to be aimed at them from its words and pictures — comes under Google Play's Families policies and the children's-privacy laws behind them, with obligations a small offline utility does not carry today. Ramz Care is a tool that adults set up, for themselves or for someone they care for.
This app can reach a child's phone in one specific way that the free app cannot: a parent may share a Family Library purchase with a child's supervised Google account. If a parent chooses to install Ramz Care on a child's phone, that is the parent's decision, made through Google's family controls; the app treats that phone exactly as it treats any other — nothing leaves it, and nothing reaches us.
Deleting the data
- Delete a reminder in the app and it is gone, together with its picture if no other reminder uses it. When the picture would otherwise be lost, the app offers to save the original photograph to the phone's own gallery first; if that is accepted, the copy stays on that phone and the app has nothing further to do with it.
- Uninstall Ramz Care and everything the app stored on that phone is removed with it. Uninstalling on one family member's phone does not affect another's.
- There is no account to close and nothing for us to delete on anyone's behalf: we never had a copy.
Two things uninstalling does not touch, because they are not ours: the purchase itself, which lives in the buyer's Google Play account and family group, and any Android backup of the small settings described above, which lives in the phone owner's Google account.
A new phone starts empty
Reminders and pictures are not carried to a new phone, and this is a choice rather than an accident. Reminders live in the pre-unlock area Android never backs up, so the app excludes the pictures too — restoring pictures without the reminders they belong to would give you files that look like data and are not. Because Ramz Care is so often set up for someone else, this matters more here than in the free app: if the person's phone is replaced, the reminders have to be set up again, by someone sitting beside them, exactly as they were the first time.
Your rights, honestly stated
Laws in some places — the European Union and United Kingdom's data-protection rules, and several United States state privacy laws among them — give you rights to see, correct, delete or move personal data that a company holds about you, and to object to its sale.
Ramz Care's position under all of them is the same, and it is unusual: we hold nothing about you to act on. We cannot look you up, because there is no account and no identifier that reaches us; we do not sell or share personal information; and the only copies of the data are on the phone the app is installed on, where they can be deleted at any time. If you write to us with a request under one of these laws, we will answer, and the answer will explain that there is nothing held.
We have not appointed a data-protection officer or an EU/UK representative, because we do not process personal data in a way that requires one. If the app ever gains an account or a server, this section will be rewritten before that feature ships, not after.
Changes to this policy
If this policy changes, the effective date at the top changes with it. Because the app collects nothing, a change here means a change in what the app does, and that will also be described in the release notes for the version that makes it.
Contact
SANAD Technologies LLC
Support: hello@sanadtech.us
Privacy requests:
privacy@sanadtech.us
30 N Gould St STE N, Sheridan, WY 82801, United States
This policy is governed by the laws of the State of Wyoming, United States, without regard to conflict-of-law rules — to the extent a policy about data that is never collected needs a governing law at all.