Privacy Policy

Morvyn is an Android app with the package name com.himikolab.morvyn, developed and published by Himiko Lab.

App name

Morvyn

Developer

Himiko Lab

App homepage

morvyn.himikolab.my.id

Contact

hi@himikolab.my.id

Morvyn has no server of its own. Himiko Lab holds no database of your app content and cannot see anyone's notes, schedule, finances, or habits. All user data is stored on the device itself, in a local database (Room/SQLite), and in your own Google account only if you turn on backup.

There is one exception: the sign-in record. When you sign in with Google, Firebase Authentication creates an account in Himiko Lab's Firebase project holding your email address, display name, Google profile photo URL, a user ID (UID), and the dates the account was created and last signed in. Himiko Lab can see that list of accounts in the Firebase console. It holds none of your app content, and you can delete it yourself from inside Morvyn: see "Deleting your account".

There is no tracking at all. The app uses no Google Analytics, no Firebase Analytics, no Crashlytics, no advertising SDK, and no third-party tracking SDK. No behavioural profile is built, and no data is sold or shared for advertising. The Google SDKs used for sign-in, notifications, configuration, and the document scanner do send limited technical data to Google, each as described in its own documentation: the details are under "Notifications, app configuration, and other Google services".

Morvyn keeps its contents in a local database inside your device. What lives there:

• Notes
• Tasks
• Schedule and agenda entries
• Habits
• Finance records and their categories
• Alarms and reminders
• News articles you saved
• News reading history
• Weather records
• Deletion history: schedule and task items you delete are kept for 7 days so you can restore them, then dropped automatically
• Note attachments: images, PDF files, document scans saved as PDF, and drawings
• Your profile: name, photo, gender, date of birth, and time zone
• The place on a finance record, when you fill it in from where you are (see "Location, weather, and places")
• Your last known position: a single value shared by Home, Weather, Earthquake, and the transaction place in Finance (see "Location, weather, and places")
• Earthquake data: your earthquake notification settings and a copy of the latest earthquake data (see "Earthquake information")
• The text recognised (OCR) on PDF pages, kept in the app's cache
• The Google account storage figures last read, while Drive is connected (see "Google Drive backup")

All of it is local, apart from your own backups. Not one item on that list is sent to Himiko Lab.

Morvyn uses Firebase Authentication for Sign in with Google. It serves one purpose: proving that the account requesting a backup is yours. This is a prerequisite for the backup feature.

Signing in creates an account in Himiko Lab's Firebase project. It holds your email address, display name, Google profile photo URL, a user ID (UID), and the dates the account was created and last signed in. Firebase Authentication also collects your IP address, for security and abuse prevention, as stated in Firebase's data disclosure documentation.

You can delete that account from inside the app at any time: see "Deleting your account".

It is optional. Morvyn remains fully usable without ever signing in.

Backup is optional and uses the drive.appdata scope. Backup files are stored in your own app data folder inside your Google Drive.

Backups also include the PDF files in your Notes, which are kept in the same app data folder.

Besides your app data and those PDF files, a backup holds your profile (name, gender, date of birth, time zone, profile photo) and your app settings (theme, language, temperature unit, currency, daily reminder, the sort order and filters in Notes, Earthquake settings, pen colour history, and PDF reading positions).

Some things are deliberately left out of the backup: the weather, news, and exchange rate caches; your last known position and the Wi-Fi country code; the connection status of Drive and Calendar; and PDF passwords.

That folder is hidden from other apps, and Himiko Lab has no access to it. You can delete its contents yourself at any time through your Google Drive settings.

Account storage figures. While Drive is connected, Morvyn reads two figures from your Google account through the Drive API: the storage in use (the total across all Google services) and the storage limit. They are shown to you in Settings, under Backup, as "Google storage". This uses the same drive.appdata scope; no new scope is requested. The figures are kept only on your device, together with the backup settings, and are not sent to Himiko Lab or to anyone else. They are removed when you disconnect Drive or switch accounts. Because they are stored with the app's settings, they can be included in the Android system backup described under "How your data is protected", like any other setting.

Calendar sync uses the calendar.events scope. It is two-way, optional, and off by default.

When you turn it on, Morvyn reads and writes events on a single calendar that you choose yourself. Events pulled from Google Calendar are stored on your device (and in your own backups, if you turn backup on); events you create or change in Morvyn are sent to your Google calendar.

Calendar data is never sent to anyone other than Google, and never passes through a Himiko Lab server, again because no such server exists.

You can disconnect at any time from Settings inside Morvyn, and revoke the permission from your Third-party access page in your Google Account.

Firebase Cloud Messaging

Delivers announcement notifications from the developer. Devices subscribe to a topic; the system is not used to identify individual people. It sends your app version for that topic subscription.

Firebase Remote Config

Fetches app configuration values. To work out which values apply, it sends your country code, language code, time zone, platform and OS version, the Firebase App ID, the package name, and the SDK version.

Firebase Installations

Used by both services above. It creates a per-installation identifier (FID). According to Firebase, a FID does not uniquely identify a person or a device.

Google Play in-app updates

Morvyn asks the Play Store whether a newer version is available. The minimum version it compares against comes from Remote Config.

ML Kit Document Scanner

Powers Scan document, through Google Play services. According to ML Kit's data disclosure page, the SDK sends device information (manufacturer, model, OS version), app information (package name, version), a per-installation identifier, performance metrics, API configuration, and error codes to Google, for diagnostics and usage analytics, encrypted with HTTPS and not passed on to third parties. The scan itself is saved on your device, as a PDF in Notes.

ML Kit Text Recognition

Lets the PDF reader recognise the text on scanned PDF pages, so that it can be searched and selected. Morvyn uses the bundled version: the models (Latin, Chinese, Japanese, Korean, Devanagari) ship inside the app and run on your device, with no model download. Morvyn itself does not upload the PDF pages or the recognised text anywhere. The recognised text is kept in the app's cache folder on your device, and is encrypted when the PDF is password-protected. That cache is left out of every backup and is removed by "Clear cache" in Settings. Like the other ML Kit SDKs, the library does send technical data to Google. According to Google's ML Kit data disclosure page, that is device information, application information, per-installation identifiers, performance metrics, API configuration, feature input and output size, feature version, event types, and error codes, used for diagnostics and usage analytics, encrypted in transit with HTTPS and not transferred to third parties.

Morvyn's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In practice, for data obtained through the drive.appdata and calendar.events scopes:

• It is used only to provide user-facing features: the backup and calendar sync that you switch on yourself, and showing you your own Google account's storage usage.
• It is not transferred to anyone. There is no intermediary to pass through, because Morvyn has no server.
• It is not used for advertising, and not used to build any kind of profile.
• No human reads it. Himiko Lab has no technical route to it: backup files sit in your own hidden folder on Drive, and calendar data never leaves your device except to reach your own Google calendar or your own backups, if you turn them on.

Encryption in transit. All communication between Morvyn and Google services (Google Sign-In, Google Drive, Google Calendar, Firebase) uses HTTPS with TLS encryption.

Storage on your device. Your data lives in Morvyn's private app storage, which the Android sandbox keeps inaccessible to other apps. On devices with a screen lock, Android also encrypts this storage.

Google access tokens. Morvyn does not store your Google password or long-lived access tokens. Short-lived tokens are requested from Google Play services only when a backup or calendar sync runs, and are used only for that request.

Google Drive backup. Backups are written only to your Drive's hidden app data folder (drive.appdata scope). Morvyn cannot see or modify any other file in your Drive. Google encrypts the files at rest.

Android system backup. If Android backup is on, Morvyn's local database and settings may be included in your device backup to your Google Account. Morvyn only allows this backup when the device has a screen lock, so that Android can encrypt it end-to-end with your lock screen credential. Your sign-in session is never included.

Least privilege. Morvyn requests only two Google scopes, drive.appdata and calendar.events, and only after you turn on the matching feature. Calendar access is limited to the one calendar you choose. The account storage figures shown in Settings are read with the same drive.appdata scope.

Retention. Events pulled from Google Calendar stay on your device until you delete them or disconnect Google Calendar in Morvyn's Settings, which removes them from Morvyn. Turning sync off only pauses it. Backup files stay in your Drive until you delete them. Disconnecting Morvyn does not delete them; see "How to delete your data". Deleting your account from inside Morvyn does delete every Morvyn backup in your Drive: see "Deleting your account". Because Himiko Lab has no server, there is no copy with us to retain or delete.

Morvyn requests location permission (ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION) for three features. There is no background location permission (ACCESS_BACKGROUND_LOCATION), and the permission itself stays optional.

Weather

Latitude and longitude are sent directly to the weather data providers as part of the request: api.open-meteo.com (Open-Meteo), with api.openweathermap.org (OpenWeather) as the fallback.

The place on a finance record

In Finance you can fill the transaction place from where you are. What the record keeps is the place name, or the coordinates when no place name is available, and it goes into your backups along with the rest of the record.

Earthquake

Your last known position is used to work out how far away an earthquake was, and which source to read. The Earthquake menu can also ask for the location permission itself, through its "Allow location" button, and approximate location is enough. With the permission granted, the menu reads the phone's position when it is opened or refreshed, which happens only while the app is open and the menu is on screen. The next section explains it in full.

Geocoder

To turn coordinates into a place name (Weather, Home, Finance, and the "Your location" caption in Earthquake) or a country code (Earthquake), Morvyn uses the Android system geocoder. On phones with Google Play services, that service is provided by Google, so the coordinates reach Google.

One last position, shared. Morvyn keeps a single "last position" on your device, shared by Home, Weather, Earthquake, and the transaction place in Finance. Whichever of the four obtains a position saves it. When a new position is saved (the first one, or one that has moved more than about 3 km), Home and Weather refresh the weather for it. So the coordinates are sent to Open-Meteo (fallback: OpenWeather) and to the system geocoder, even when the position was obtained in the Earthquake menu or while filling in a transaction place in Finance.

Those coordinates are not stored on any server by Morvyn, and are not tied to your identity. Declining the permission means the weather, the transaction place, and the distance to an earthquake will not pick up your location automatically.

Morvyn has an Earthquake menu, a small card on the Weather screen, and an "Earthquake info" notification. This is earthquake information, not an early warning system.

The data comes from BMKG (data.bmkg.go.id) for users in Indonesia, and from the U.S. Geological Survey (earthquake.usgs.gov) for users outside Indonesia. Morvyn downloads their data files whole, including the shake map images, and sends none of your position to them. Both institutions see an ordinary request only, your IP address and ordinary request information, exactly as the news publishers do.

The distance to an earthquake is worked out on your device, from the last position obtained by Home, Weather, the Earthquake menu itself, or filling in a transaction place in Finance. That stored position is not sent to BMKG or USGS, it is not part of your Android system backup, and it is not part of your Drive backup.

With the location permission granted, the Earthquake menu reads the phone's position itself when it is opened or refreshed. That happens only while the app is open and the menu is on screen. The permission can be granted from the menu's "Allow location" button; it stays optional, and approximate location is enough. The system geocoder turns the position into the place name shown as "Your location".

The last position is one value shared with Home, Weather, and Finance. When a new one is saved (the first one, or one that has moved more than about 3 km), Home and Weather refresh the weather for it, so the coordinates are sent to Open-Meteo (fallback: OpenWeather) and to the system geocoder even when the position was obtained here in the Earthquake menu. "Location, weather, and places" above has the details.

Which of the two sources is read depends on your country, and Morvyn works that out in this order:

• The system geocoder, on your last known position.
• The country of your mobile network.
• The country code broadcast by nearby Wi-Fi routers. This is read only when precise location permission is granted and location services are on, only while the app is open, and it is kept on the device for at most 3 days.
• Your phone's language setting.

None of that uses your IP address, so a VPN does not change it, and all of it is processed on your device.

A background check roughly every 15 minutes uses the position and country already stored; it does not read a new location. A copy of the latest earthquake data is kept on your device, and left out of your backups, so the menu still has something to show when you are offline.

The notifications can be turned off and tuned in the Earthquake menu: radius, minimum magnitude, large earthquakes, and BMKG tsunami potential.

The news feature fetches RSS feeds directly from each publisher's own site, with nothing in between. That means those publishers can see the request coming from your device (your IP address and ordinary request information), exactly as if you had opened their site in a browser.

Notes behave the same way with links. When a note holds a link to a site, Morvyn fetches that site's icon (favicon) directly from the site, with no third-party service in between, so the site sees the request coming from your device (your IP address and ordinary request information) exactly as a news publisher does.

The publishers contacted include Detik, Antara, CNN Indonesia, CNBC Indonesia, Tempo, Republika, Sindonews, Okezone, JPNN, BBC, The Guardian, Al Jazeera, ABC News, The New York Times, The Independent, France 24, Channel News Asia, and the South China Morning Post. Each is governed by its own privacy policy.

The finance feature fetches exchange rates from open.er-api.com. None of your data is sent there, only a request for rates.

INTERNET

Fetching weather, news, earthquake data, exchange rates, and the icons of links in your notes, and running Google sync.

ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION

Showing the weather around you, filling in the place on a finance record, and working out the distance to an earthquake. Optional.

ACCESS_WIFI_STATE

Reading the country code broadcast by nearby Wi-Fi routers, for the Earthquake feature.

POST_NOTIFICATIONS

Showing reminders and alarms, announcements from the developer, and earthquake information.

SCHEDULE_EXACT_ALARM

Sounding alarms at the exact time.

RECEIVE_BOOT_COMPLETED

Re-arming reminders after the device restarts.

USE_FULL_SCREEN_INTENT, SYSTEM_ALERT_WINDOW

Showing the alarm screen.

FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE

Keeping an alarm ringing.

VIBRATE, WAKE_LOCK

Vibration, and waking the screen when an alarm goes off.

Three more permissions are declared by the Google and AndroidX libraries Morvyn is built on, and are not used by any Morvyn feature: ACCESS_NETWORK_STATE, USE_BIOMETRIC, and USE_FINGERPRINT. The last two come from androidx.biometric, which the Google sign-in library brings along. Morvyn does not use fingerprint or biometric authentication.

Morvyn is not directed at children under 13. Himiko Lab does not knowingly collect data from them, and collects data from no one at all, because there is no server to receive it.

For the same reason there is nothing for us to delete on request: a child's data lives on the device they used, and in that device's own backups if backup was turned on. It can be removed by clearing that app's data and deleting those backups. The sections below explain how.

The main way is from inside the app: Settings > DATA > Delete Account. The row appears only when you are signed in with Google. You are asked to pick your Google account once more as verification, and the delete button becomes active after 10 seconds, so there is time to read what it says.

What happens when you delete your account from the app:

• Your Firebase Authentication account in Himiko Lab's project is deleted, with the email address, name, UID, and sign-in record it held.
• Every Morvyn backup in your Google Drive is deleted, and Morvyn's Google Drive permission is then revoked. Those backups cannot be recovered.
• Google Drive and Google Calendar are disconnected. Events in your Google Calendar stay where they are; the copies in Morvyn that came from Google are released.
• Data on your phone is not deleted. You can clear it yourself with "Delete All Data".
• If deleting the backups fails, with no internet connection for instance, the account is not deleted and you can try again.

If the app is no longer installed, send an email to hi@himikolab.my.id from the Google address you signed in with. Himiko Lab deletes that Firebase Authentication account within 14 days of the request. The backup files in your Drive are yours to delete, through the connected-apps settings in Google Drive, because Himiko Lab has no access to your Drive.

Your Morvyn account

Settings > DATA > Delete Account, inside the app. See "Deleting your account" above.

All local data

Use "Delete All Data" in Morvyn's Settings, clear the app's data from Android Settings, or uninstall the app. Deleting your account does not remove the data on your phone.

Google Drive backup

Two ways: delete your account from inside the app, which deletes the backups along with it, or disconnect Drive in Morvyn's Settings and then delete the app data through the connected-apps settings in Google Drive.

Android system backup

Clearing Morvyn's data on the device does not remove a copy that is already in your device backup. Manage or delete that backup through the backup settings on your device or in your Google Account.

Calendar data

Turning sync off only pauses it; events already pulled stay in Morvyn. Disconnecting Google Calendar in Morvyn's Settings removes the events that came from Google from Morvyn. Events in Google Calendar itself remain yours and can be deleted there. Copies in your backups are deleted through the two backup items above.

Revoke Google access

Through your Third-party access page in your Google Account.

If this policy changes, the new version is published on this page and the effective date at the top is updated with it.

Questions about this policy can be sent to hi@himikolab.my.id.