PRIVACY POLICY

Ramz

Applies to the Google Play app Ramz: Picture Reminders, package com.sanadtech.ramz. Publisher SANAD Technologies LLC, 30 N Gould St STE N, Sheridan, WY 82801, United States. Effective 12 September 2026.

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 only in how they are paid for, and that difference is the only reason the two policies differ.

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. The app makes no network calls of any kind, and it works with the phone in aeroplane mode.

One thing 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.

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 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 language setting 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

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 your language setting 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

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.

Those four 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.

How this app is paid for

Ramz is free to install, and this version sells nothing. There is no subscription, no advertising, and no purchase inside the app. Because there is nothing to buy, Ramz contains no payment library, holds no purchase record, and declares neither a billing nor a network permission.

If a future version does offer a one-time purchase, it will be described here before it ships, together with any permission that arrives with it — and a feature that shipped free will stay free.

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

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.

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.

Back to Ramz