> This policy covers the paid Ramz Care app. The separate Ramz app (com.sanadtech.ramz) has its own privacy policy.
The short version
Ramz Care keeps your reminders and your photographs on the phone it is installed on, in the app's own private storage. You can explicitly export a personal backup or save a picture elsewhere. There is no account, no server, no analytics, no advertising and no tracking. The app works with the phone in aeroplane mode.
Two things a careful reader should know before going further:
- Phone transfer is your choice. Reminders and pictures stay out of Android automatic backup. From version 2.0.0 you can save a complete personal backup and import it on another phone. Imported reminders remain paused for review. See "Personal backup and phone transfer" below.
- Ramz Care is often set up by one person on another person's phone. Whoever's phone it is on, that phone holds its own copy. The person who bought the app cannot remotely see it, and neither can we. The section "Set up on someone else's phone" says what that means.
What Ramz Care stores, and where
The app’s working copies live in its private storage on the device. Files you explicitly export or save are stored in the location you choose, as described below.
| 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 — and, if one has been snoozed, the time it is due back | 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, plus 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 (see "Android automatic backup") |
| 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). Also 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 |
| Settings — the language chosen, and how long a snooze lasts | The same pre-unlock area | No |
| Settings — the theme, and whether a tip or a setup prompt has already been shown | Ordinary private app storage | Possibly — see below |
| The app's own first-run date | 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's own code makes no network calls, and because Ramz Care contains no purchase library, its permission list carries no network permission at all. (The free Ramz app is different in exactly this respect; its policy explains why.)
- 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 browsing of your gallery, contacts, calendar, messages or other apps. File access is limited to pictures and backups you explicitly select.
- No developer sharing or selling. We receive no copy of your reminders or pictures. Files you explicitly export or share go only to destinations you choose.
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.
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.
The requested permissions support reminder delivery. Ramz Care declares no purchase permission and no network permission.
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 provides developers with order records for refunds and support, such as an order reference, product, amount and country. These records come from Google, not from data uploaded by Ramz Care. We do not receive your payment-card details.
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. If a family member wants their reminders on another device, they can explicitly export and import a personal backup, then review and reactivate the paused reminders.
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:
- Each phone holds its own copy. Reminders and pictures created on it belong to that phone and remain private unless explicitly exported or saved. The person who bought the app, the person who set it up, and we ourselves cannot remotely 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.
Personal backup and phone transfer
You can explicitly save a backup through Android's document picker. It includes reminder titles, schedules, completion/archive status, full pictures, editable picture text and rotation data. It excludes purchase records, permissions, device settings and delivery/missed-alert reports. The archive contains personal text and photographs and is not password encrypted. Keep it somewhere you trust. A storage provider you select, including a cloud provider, may upload it under that provider's own terms. Ramz does not upload automatically and we receive no copy.
Import validates a private temporary copy before asking for confirmation, adds records without replacing current reminders and keeps imported reminders paused. Pending snoozes are cleared. Review schedules before reactivating them; past one-off dates must be edited. An unchanged backup already imported on that installation does not add duplicates. A different export adds another set, rather than synchronizing phones. The source phone keeps its reminders.
Temporary staging files are removed after completion, cancellation or a failed operation and stale staging is cleaned in the background when the app next starts after a process restart. Uninstalling Ramz removes its private copies, not the exported files in your chosen location. You must delete those files yourself, using that storage provider. The same applies to any copies you share.
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 is uploaded automatically, and nothing reaches us. If we ever design a version of Ramz for children, this policy changes with it, and the app's Play declaration changes first.
Deleting the data
- Delete a reminder in the app and it is gone, together with its picture if no other reminder uses it.
- Uninstall Ramz Care and everything the app stored on that phone is removed with it, because it all lived in the app's own storage. 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.
Uninstalling does not remove exported backups, saved pictures or copies shared elsewhere. Delete those using the storage provider or app holding them. It also does not remove the purchase itself, which lives in the buyer's Google Play account and family group (that is what lets the app be reinstalled or shared again without paying), and any Android backup of the small settings described above, which lives in the phone owner's Google account and is managed from that phone's backup settings.
Android automatic backup
Reminders and pictures are excluded from Android automatic backup. Reminders use device-protected storage so alarms can be re-armed before first unlock; restoring pictures alone would leave orphan files. The explicit personal backup feature described above transfers complete reminders instead. A new installation starts empty until you create reminders or choose to import a backup.
Access, deletion and privacy requests
Ramz Care does not send us your reminders, photographs or delivery records. You can view, edit and delete the private copies in the app, and export a personal backup when you want to move them. Exported or shared copies must be managed separately in the location you chose.
If you contact support or request help with a Google Play order, we may receive information you provide and the order information Google makes available. Contact us below for privacy requests about information we actually receive. We cannot remotely access or delete reminders or pictures held on your phone or by your chosen storage provider.
Changes to this policy
If this policy changes, the effective date at the top changes with it. Changes to how Ramz Care handles reminders, pictures or backups will also be described in the release notes for the version that makes them.
Contact
SANAD Technologies LLC, a limited liability company registered in the State of Wyoming, United States.
Support: RamzSupport@SanadTech.us
Privacy requests: privacy@sanadtech.us
Postal address: 30 N Gould St STE N, Sheridan, WY 82801, United States.
This policy is governed by the laws of the State of Wyoming, without regard to conflict-of-law rules, to the extent a policy about data that is never collected needs a governing law at all.