PRIVACY POLICY
Ramz
There is a second Ramz app on Google Play,
Ramz Care (com.sanadtech.ramz.care),
sold as a paid app so that a household can share it through Google
Play Family Library. It has its own policy at
sanadtech.us/ramz/care/privacy. The two
apps hold your data in exactly the same way. They differ in how they
are paid for: this app sells a one-time unlock through Google Play,
which brings a purchase permission and a network permission with it,
and Ramz Care sells nothing inside the app and has neither. That is
the only reason the two policies differ — the sections “The network
permission, explained” and “How this app is paid for” are where it
lives.
The short version
Ramz keeps your reminders and your photographs on your phone, in the app's own private storage, and nowhere else. There is no account, no server, no analytics, no advertising and no tracking. Ramz's own code makes no network calls, and your reminders work with the phone in aeroplane mode.
Two things a careful reader should know before going further:
- Nothing in Ramz is carried to a new phone. Your reminders and pictures are deliberately kept out of Android's backup, so a new device starts empty. We would rather say it here than have you discover it.
- The app lists a network permission. It arrives inside Google's purchase library, which sells the one-time unlock, and not from anything Ramz does. “The network permission, explained” says exactly what that does and does not mean.
What Ramz stores, and where
Everything Ramz holds lives on your device, inside storage that belongs to the app and that other apps cannot read.
| What | Where on the phone | Backed up by Android? |
|---|---|---|
| Your reminders — the words you wrote, when they should arrive, how they should reach you (quiet notification or full-screen alarm), and whether each one is live, done or archived — and, if you have snoozed one, the time it is due back | A database in the part of storage the phone can read before you first unlock it after a restart (see “A note on the lock screen”) | No. Android never backs this area up |
| Your photographs — the picture you took or chose, the version Ramz composes with your words on it, and a small thumbnail | The app's private files | No. Ramz 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 |
| Your settings — the language you chose, and how long a snooze lasts | The same pre-unlock area | No |
| Your theme, and whether you have already seen a tip or a setup prompt | Ordinary private app storage | Possibly — see below |
| The free period and the unlock — the date the app first ran (used only if the phone cannot say when Ramz was installed, which is what starts the free period), whether you have seen the notices about that period, and a yes-or-no marker that the unlock was bought (see “How this app is paid for”) | 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 you have Android backup switched on. Ramz does not stop that for the small settings above. So, on a new phone signed into the same Google account, your theme choice may come back even though your reminders and pictures will not. That backup is Android's, held by Google under Google's terms; Ramz 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 promises to tell you 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 and snooze settings are kept where the phone can reach them before you first unlock it 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 your lock-screen PIN or pattern the way the rest of the phone is. Your photographs are not in that area; they are in the sealed part.
What Ramz never collects or shares
- No account. No sign-up, no profile, no login. Ramz does not know who you are.
- No server. There is nothing of ours for your data to go to.
- No network use by Ramz. The app's own code makes no network calls of any kind. The network permission it lists arrives with Google's purchase library; see “The network permission, explained”.
- No analytics, no crash reporting, no advertising, no advertising identifier, no tracking.
- No location. Ramz does not ask for, read or store your location.
- No reading of your gallery, contacts, calendar, messages, files or other apps.
- No sharing or selling. Nothing is sold, shared, transferred or disclosed to anyone, because Ramz holds no copy of anything to share. The one exception is the purchase itself, which Google handles — see “How this app is paid for”.
The permissions Ramz asks for, and why
Ramz asks for as few permissions as an alarm-style reminder app can. Each one changes only how a reminder reaches you; 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 you chose rather than “some time around then”. If you decline it, Ramz still delivers, less precisely, and says so — the app shows “about 6:00 pm” instead of “6:00 pm”. -
Full-screen alerts
(
USE_FULL_SCREEN_INTENT) — so a reminder you 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 your reminders are re-armed after the phone reboots. It does nothing else.
Three more arrive with the one-time unlock, and are explained in the
next section: Purchases
(com.android.vending.BILLING), which lets Google Play sell
something inside the app, and the two network permissions that come
with Google's purchase library
(INTERNET and ACCESS_NETWORK_STATE).
Those seven are the only permissions that affect you. For completeness:
the app's manifest also contains one private, signature-level permission
named
com.sanadtech.ramz.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 your 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 you tap Take a photo, Ramz asks the phone's own camera app to take the picture and hand back that one file. Ramz itself never holds camera access and cannot open the camera on its own; it receives one image, which it copies into its private storage. You may see the camera app's own permission prompt, which is that app's, not ours.
Your photo library — no permission either
Choose a picture uses Android's system photo picker. You pick one image; Ramz receives only that image and cannot see, list or search the rest of your gallery. You can also send a picture to Ramz from another app's share menu — Ramz copies that one picture and nothing else.
The network permission, explained
The app's permission list shows android.permission.INTERNET
and android.permission.ACCESS_NETWORK_STATE. A reader who
has just been told nothing leaves the phone is entitled to ask why, so
here is the whole answer.
- Where they come from. The unlock is sold through Google's official Play Billing library. That library, and the Google components it relies on, declare the network permissions. Android merges every library's permissions into the app's list, so they appear under Ramz's name.
- What they let happen. Android grants a permission to the whole app, which means Google's purchase library can use the network when it needs to — to reach Google Play, and to send Google whatever Google's library reports to Google.
- What Ramz does with them: nothing. No line of Ramz's own code opens a connection, and Ramz has no server to connect to. Ramz never hands your reminders or pictures to the purchase library, and the library has no way to read the app's storage.
- What we cannot promise, and will not pretend to. We cannot inspect or vouch for what Google's own library sends to Google, or how often. That traffic is Google's, governed by Google's Privacy Policy, and it exists in every Android app that sells anything through Google Play.
If you want an app that holds no network permission at all, that is Ramz Care: it is paid for up front, contains no purchase library, and a test fails its build if the purchase library ever reaches it.
How this app is paid for
Ramz is free to install, and free to keep using. For fourteen days after you first install it, nothing is limited. One-off reminders stay free after that, without limit. After fourteen days, a reminder that repeats needs a single one-time purchase, made inside the app; repeating reminders you already made keep working. There is no subscription, and nothing that renews. The full rules are in the Ramz terms of use.
Google Play handles the purchase entirely. The payment screen is Google's; your 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 Ramz keeps about the purchase. A yes-or-no marker on the phone that the unlock was bought, so the app can check it offline without asking again. On a new phone, or after reinstalling, the app asks Google Play whether the unlock belongs to your Google account and writes the marker again; that is Google's normal “restore purchases” mechanism and needs nothing from you.
What Google may show us. Google Play gives developers basic order records so that refunds and support requests can be handled — an order reference, which product was bought, the amount and the country, in whatever form Google chooses to present them. We never see your payment method. Whatever Google shows a developer about a purchase reaches us from Google, not from the app, and the app sends Google nothing about you.
Refunds are Google's to process, under Google Play's refund rules. If Google tells the app a purchase was refunded or revoked, the app removes its marker; a Play Store the phone cannot reach never removes one.
Family sharing is not available for the unlock. Google Play does not let in-app purchases be shared through Family Library. That is why the paid app, Ramz Care, exists — see its policy.
Children
Ramz 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 is a general reminder tool for adults. If that ever changes, this policy changes with it, and the app's Play declaration changes first.
If you are a parent or carer setting Ramz up on a younger person's phone, the app treats their phone exactly as it treats yours: nothing leaves it, and nothing reaches us.
Deleting your 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, Ramz offers to save the original photograph to your phone's own gallery first; if you accept, that copy is yours, on your phone, and Ramz has nothing further to do with it.
- Uninstall Ramz and everything the app stored on the phone is removed with it, because it all lived in the app's own storage.
- There is no account to close and nothing for us to delete on your behalf: we never had a copy.
Two things uninstalling does not touch, because they are not ours: the record of your purchase, which lives in your Google Play account (that is what lets you reinstall without paying again), and any Android backup of the small settings described above, which lives in your Google account and is managed from your phone's backup settings.
One thing uninstalling does not touch, because it is not ours: any Android backup of the small settings described above, which lives in your Google account and is managed from your phone's backup settings.
A new phone starts empty
Your reminders and your 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 Ramz excludes the pictures too — restoring pictures without the reminders they belong to would give you files that look like data and are not. If you rely on Ramz, know that moving phones means setting your reminders up again.
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'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 your data are on your own device, where you can delete them yourself 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.
The one exception is a purchase of the unlock: the order record Google Play shows us, described under “How this app is paid for”, is held by Google and reaches us from Google, not from the app. If a request concerns it, we will act on it as far as Google Play lets a developer do so, and tell you plainly where that stops.
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 Ramz 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 Ramz 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.