Skip to content
Ramu
How it worksUse casesFeaturesPricingContact
LTEN
Get Ramu
Privacy policyTerms of useDelete account
On this page
  1. Who we are
  2. Two kinds of account
  3. What we collect
  4. Optional modules
  5. Why we use data, and on what basis
  6. Children
  7. Who sees what
  8. Who processes data for us
  9. How long we keep it
  10. Deleting your data
  11. Your rights
  12. Security
  13. Changes to this policy

Last updated: 22 October 2026

Privacy policy

Ramu shares signals, not someone’s life. This page explains, in plain words, what that means for your data.

In short
  • The person who checks in never signs up: Ramu makes an anonymous account tied to their phone.
  • Their circle sees check-ins and alerts — and module data only after they agree on their own phone.
  • Location only with consent: arriving at or leaving named places, and a location the person chooses to share. No live map, no route history, no list of apps, messages or calls.
  • No ads and no ad trackers. We never sell data.
  • Data is stored in the EU and deleted on a fixed schedule. You can delete your account in the app.

1. Who we are

Ramu is made by UAB „Novelmodus“, company code 307608314, Stasinės g. 6, Stasinės k., LT-58438 Kėdainių r., Lithuania (“we”). We are the controller of the personal data used in the Ramu app, in our support chat and on ramu.day.

Questions about this policy or your data: privacy@ramu.day, or the chat on our contact page. Our director, Mažvydas Skuodas, is responsible for data protection and answers these messages. The law doesn’t require us to appoint a data protection officer at our size; we will if that changes.

2. Two kinds of account

Sender account — for the person who checks in. Ramu makes it automatically when they choose “I’m checking in”. It has no email and no password and lives on their phone (and on any phone added with a 6-digit code). It ends when they choose “I want to stop using Ramu” on the phone (24 hours later), or when a manager in their circle deletes it.

Circle account — for the people who look after someone. You sign in with an email address (with a password or a sign-in link), or with Apple or Google. Circle accounts are for people aged 18 or older. A person who checks in can add a sign-in later (“Also watch someone”); it is then one account with both roles.

3. What we collect

About the person who checks in: the name the circle gives them and, if entered, their phone number; their check-in times and time zone; each “I’m fine” and “I need help”, with the time; and who in the circle answered an alarm, and when.

About people in the circle: email address or Apple / Google sign-in; name; an optional phone number, so the person who checks in can call you; which circles you are in and whether you manage them; notes you write during an alarm (up to 500 characters); the Terms version you accepted; and your plan status from the App Store or Google Play.

About every phone that uses Ramu: a push token (to send notifications), a random ID for the phone, iOS or Android, the app language and when the app was last opened. When a new phone is added with a code, its model name (e.g. “Pixel 8”) is shown to the manager who confirms it. Managers also see which phones are signed in to the account of the person they look after. Our servers see the IP address of each request; we store it in active sign-in sessions and in the log of code attempts.

Where an Android install came from: after a circle account signs in on Android, the app once reads the campaign details Google Play passed on at install (for example “utm_source=…”), so we can see which campaigns work. No advertising ID is read, and nothing is read in sender mode. On iPhone we only see campaign totals in App Store Connect.

Crash reports: when the app fails, a report goes to Sentry: app version, phone model and system, and what the app was doing. Emails, phone numbers, codes, tokens and coordinates are removed before it is sent, and no account ID is attached.

Support: when you write to us in the app, by email or in the website chat, we keep the conversation and the name and email you give. From the app we also see your plan, app version, language, platform and how many people you look after — not their names, check-ins, medicines or places. Please don’t send health details in the chat.

Website: ramu.day has no analytics and sets no cookies of its own. Cloudflare, which serves the site, processes your IP address to deliver it. The chat loads only when you open it; Chatwoot then keeps a cookie and some data in your browser so your conversation continues.

4. Optional modules

Each module is off until the person who checks in says yes on their own phone, on a screen that shows exactly what will be shared. Before suggesting a module, a manager confirms that they are the person’s parent or legal guardian, or that the person is 14 or older.

A module can be switched off at any time on that phone. The circle loses access at once, and the data is deleted 30 days later — or immediately with “Switch off and delete now”. We keep a record that consent was given and withdrawn, with the times and the version of the consent screen.

The modules are part of the Family plan; one medicine reminder is free. On the free plan the other modules are paused: the yes is kept, but nothing is collected or shown until the circle is on Family again.

Phone activity — battery level and charging, low-power mode, step counts (iPhone), when Ramu was last used, app and system version, and whether notifications are allowed. Sent when the app opens and a few times a day in the background. Never apps, messages, calls, contacts or what is on the screen. The circle sees a summary (last sign of life, battery), not the raw readings.

Medicine — the medicine names and notes the circle enters, reminder times and days, and each answer Taken / Later / Skip with its time. This is health data: we use it only with the explicit consent given on the phone. The medicine name appears in reminders on the person’s own phone, never in notifications to the circle. Ramu gives no medical advice.

Location: places — with consent, Ramu collects the phone’s location data (precise and approximate), also in the background when the app is closed or not in use, to notice when the person arrives at or leaves the places a manager set up. A place is a name, a map point and a radius (chosen from an address or from the manager’s own location, read once on the manager’s phone), with weekday timetables. The phone itself works out whether it is inside a place; only “arrived at / left” a place with the time is sent to our servers and shared with the circle — never a route or a live location. On Android an ongoing notification shows while places are watched.

Location: Where I am — one location (to about a metre, with the nearest address worked out on the phone) is collected and shared with the circle when the person taps “Share where I am” or “I need help”, and once when they aren’t back at a place in time. The circle sees only the latest one.

Location data is used only for these features. We don’t sell it, use it for advertising, or share it with anyone outside the circle except the providers below that store or deliver it for us. Location access can be withdrawn at any time in the phone’s settings, or by switching the module off.

5. Why we use data, and on what basis

Running Ramu — check-in reminders, alerts, help requests, circles and plans. For circle accounts: our contract with you (GDPR Art. 6(1)(b)). For the person who checks in: their own and their circle’s legitimate interest in knowing they are fine (Art. 6(1)(f)); they choose to check in and can stop at any time.

Optional modules — consent given on the phone of the person who checks in (Art. 6(1)(a)); for medicine, explicit consent to the use of health data (Art. 9(2)(a)). Withdrawing consent doesn’t affect what happened before.

Security and fixing faults — limiting code attempts, keeping sign-ins safe, crash reports: our legitimate interest in a safe, working service (Art. 6(1)(f)).

Knowing which campaigns work (Android install source) — our legitimate interest (Art. 6(1)(f)). You can object, and we will delete it.

Support — our contract with you, or our legitimate interest in answering people who aren’t users yet.

Legal obligations and claims — keeping what the law requires, or what we need to establish or defend a claim (Art. 6(1)(c) and (f)).

We don’t sell data, show ads or build advertising profiles. We make no decisions about people by automated means; alerts simply follow the times and rules the circle sets.

6. Children

Children may check in with Ramu — for example a pupil with places on a school timetable. Circle accounts are only for adults (18+).

In Lithuania a child can agree to an online service alone from the age of 14. For a child under 14, only their parent or legal guardian may set up Ramu and agree to modules for them; managers confirm this before suggesting any module. The child still sees what is shared and says yes on their own phone. A parent or guardian can ask us to see or delete their child’s data.

7. Who sees what

Everyone in a circle sees the name and phone number of the person who checks in, their check-ins and alerts, and each other’s names and phone numbers. The person who checks in sees who is in their circle.

Module data is visible to the circle only while the module is on and included in the plan. Arrival and leaving notes go only to the people who asked for them. Notes written during an alarm are for the circle, not the person who checks in. On the free plan the circle sees the last 7 days of history. The circle never sees a live location or a route — only arrivals at and departures from places, and the latest shared location.

The Ramu team doesn’t look at a circle’s data except to answer your request, to fix a fault, or when the law requires it.

8. Who processes data for us

These providers run parts of Ramu for us, under data processing agreements, and may use the data only for that:

Supabase — database, sign-in and server functions; servers in Frankfurt, Germany.

Expo (650 Industries) — delivers push notifications through Apple and Google, and delivers app updates. A notification carries its text: for example a name, a time, a place name, battery level, a note written during an alarm, or the start of a support reply.

RevenueCat — keeps track of subscriptions bought in the stores. It receives an account ID, not your name or email.

Sentry — crash reports, stored in the EU (Frankfurt).

Resend — sends sign-in emails and our email replies, from Ireland.

Cloudflare — serves ramu.day and receives email sent to @ramu.day addresses.

Chatwoot — our support inbox: open-source software we run ourselves on servers in Frankfurt (Oracle Cloud, with the database at Supabase). Alerts about new messages to our team’s phones pass through the notification service of Chatwoot, Inc. in the United States, which receives the writer’s name and the first words of the message.

Apple and Google act as independent controllers when they sell subscriptions (we never see card details) and when you sign in with them. Their push services deliver notifications, and the phone’s own map and address search is used for places and positions.

Some of these companies are based in the United States. Where data leaves the EU/EEA, the transfer is covered by the EU–US Data Privacy Framework if the company is certified, or by the European Commission’s standard contractual clauses. Chatwoot’s notification service is not covered by such a safeguard; it receives only the short preview described above, for our support team. Ask us for details or copies.

We give data to authorities only when the law requires it.

9. How long we keep it

Circle account — until you delete it.

Sender account — until the person stops using Ramu (deleted 24 hours after “I want to stop using Ramu”) or a manager in their circle deletes it. A sender account that isn’t connected to any circle is deleted after 90 days without use.

Check-ins, help requests, alerts and alarm notes — 13 months.

Phone activity — readings 30 days; a daily summary while the module is on.

Medicine — answers 13 months; the medicine list while the module is on.

Location — place arrivals and departures 30 days, shared locations 7 days; places and timetables while the module is on.

A module that is switched off — its data 30 days, or none if “delete now” is chosen. The consent record stays while the account exists, as proof.

Code attempts with IP address — 30 days. Install source — 13 months. Store subscription events — 13 months; your current plan while the account exists.

Support conversations — 12 months after they are resolved, or until you delete your account. Crash reports — up to 90 days.

Deleted data disappears from our backups within 30 days.

10. Deleting your data

Circle account: in the app, Settings → “Delete my account”. Your account, memberships, alarm notes and support conversations are deleted, and your name is removed from the alerts you answered. If you were the last manager of a circle, another member takes over; if nobody is left, the person you looked after is disconnected and their sender account and data are deleted too. Deleting the account doesn’t cancel a subscription — cancel it in the App Store or Google Play first.

Sender account: on their own phone the person taps Settings → “I want to stop using Ramu”; no one has to allow it. The circle is told, and 24 hours later their account and history are deleted (they can change their mind until then). A manager can also tap “Delete account” in the person’s settings, which deletes them at once.

No longer have the app? See how to delete a Ramu account.

11. Your rights

You can ask us to show you the data we have about you and give you a copy (as a JSON file), to correct it (most of it you can change in the app), to delete it, to restrict its use, and to move it to another service. You can object to uses based on legitimate interest, and withdraw consent to a module at any time by switching it off.

Write to privacy@ramu.day or use the chat. We answer within one month. So that data only goes to the right person, we may ask you to confirm from your account’s email address or in the app.

If you think we handle your data unlawfully, you can complain to the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija), L. Sapiegos g. 17, LT-10312 Vilnius, ada@ada.lt, vdai.lrv.lt, or to the authority where you live. We’d be glad to hear from you first.

12. Security

Data travels encrypted and is stored in the EU. The database is closed by default: each person can read only what their role in a circle allows. Access to the servers is limited to the people who run Ramu.

If a security incident puts your data at risk, we tell the State Data Protection Inspectorate within 72 hours and, where the risk is high, tell you directly without delay — what happened, what it means for you and what we did.

13. Changes to this policy

When we change this policy, we update the date at the top. If a change matters for how your data is used, we tell you in the app before it applies, and ask again where consent is needed.

Ramu

A calm daily “I’m fine” from someone you care about. Made in Lithuania by Novelmodus.

RamuHow it worksUse casesPricing
HelpContactsupport@ramu.day
LegalPrivacy policyTerms of useDelete account
© 2026 NovelmodusLietuvių · English