LOMASE / YOUR PERSONAL JOURNAL

Privacy policy

Your reflections, your permissions, your choices. How Lomase handles journal records, media attachments, optional notifications and advertising attribution.

Last updated: November 17, 2026 · Applies to Lomase, its optional reflection attachments and the services described below.

Read the Terms of use

What stays on this device

This policy explains how the Lomase app developer (“we”) handles information when you use Lomase. Our contact for privacy questions is huangbidanmzz@163.com. Lomase is a personal time-recording and reflection tool, with optional photos, short videos and voice attachments.

Your journal is stored locally by default. The local journal does not require an account or automatically sync to a Lomase cloud service. Connected services can use a separate service user identifier; this does not create a cloud copy of your journal. Camera and microphone access are optional. Section 7 describes the separate data flows for optional remote notifications and permission-based advertising attribution.

Quick controls: decline a permission, remove an attachment and save the record, delete a session, export a backup, or erase all local data. See Backups & your data in Guide.

Information you create

Lomase uses these items to display and edit your journal, run timers, show trends, play attachments and produce the exports you request. The app does not send this journal content to Firebase, OneSignal or Adjust, use it for advertising, or run speech-to-text or AI analysis on it.

What you record may be sensitive. Images, voices, notes and ratings can reveal people, health-related circumstances or places. Decide what you want to keep and obtain permission before recording other people. No location permission is requested for these features.

Camera, microphone and photo selection

Permissions are requested when you choose the relevant feature, rather than as a condition of using the journal. The current attachment limits are 3 photos, 1 video of up to 30 seconds and 1 voice recording of up to 2 minutes per record.

If you decline: the affected capture feature is unavailable; you can continue with text reflections and the features that do not require that permission. You can change camera and microphone access in iOS Settings under Lomase or Privacy & Security. Changing a permission does not delete previously saved attachments.

Recording stops when the app goes into the background or an audio interruption occurs, and is not automatically restarted. Playback pauses when you leave the app. These features are not designed for background recording.

How media is prepared and protected

Photos are resized and re-encoded as JPEG for storage, with a longest edge of up to 1,600 pixels. This process removes the original photo GPS/EXIF metadata. Videos are compressed to MP4 and voice recordings are stored as AAC audio in M4A files. Overlong videos are rejected rather than silently shortened.

Metadata removal is limited. We do not promise to remove all metadata from videos or audio. A face, a spoken name, a landmark or a document in the content may still identify a person or place, even when photo metadata has been removed. Processing can reduce quality; keep originals separately if you need them.

Saved attachments use iOS file protection and are kept in the app’s private storage, outside the widget’s shared container. Temporary capture, conversion and sharing copies are cleaned up by the app during its normal lifecycle; cleanup is not a guarantee of forensic erasure.

Optional App Lock uses Face ID, Touch ID or the device passcode through Apple’s system authentication. Lomase receives the authentication result, not biometric templates. App Lock helps restrict access inside Lomase; it does not add a separate password to exported files or protect copies held in other apps. No storage or security control can guarantee absolute protection.

Sharing, exports and device backups

Individual sharing: using an attachment’s system share sheet passes the selected file to your chosen destination. That destination may be a cloud drive, a messaging app or another person, and its own practices apply.

Full backup: Export backup with attachments creates a .lomase file containing completed-session data and the attachment files. It is not password-encrypted by Lomase. A full backup can expose notes, tags, ratings, images and voices to anyone who can open it. Store it securely and remove unneeded copies from Files, downloads and cloud storage.

Other reports: CSV exports, PNG charts and PDF reports do not embed photo, video or voice attachments. They may still reveal session information; PDF reports can include notes when that option is selected. Review every export before sharing.

iOS backups: depending on device settings, Apple device backups may include local app data and attachments. This is distinct from a Lomase-operated sync service. Manage these copies in Apple’s backup and storage settings.

Widgets, Live Activities and local reminders

The widget shares the timer state and start, pause or resume commands needed to work with the app through an on-device app group. Attachment files are not placed in this shared container. App Lock hides timer information from the widget.

A Live Activity, where supported, displays the running session on the lock screen or Dynamic Island using on-device state. It ends with the session and is hidden when App Lock is on. People who can see your screen may still see information before it is hidden; choose device notification and lock-screen settings that suit you.

Local reminders are scheduled on the device and do not require Firebase or OneSignal. Notification permission can be changed in iOS Settings. Delivery depends on system settings and is not guaranteed.

Remote notifications and advertising attribution

You can separately enable supported remote-notification providers in Lomase Settings. Choosing a provider allows its SDK to process information needed for that service; it does not give it access to your journal attachments. Reading this policy does not enable a provider.

Turning a provider off: use its switch in Lomase Settings. The app disables future use and requests unregistration or opt-out as supported; network-dependent unregistration may need a connection. You can also disable notification display in iOS Settings, but doing so is not the same as switching off a provider’s data processing in Lomase.

Turning off a provider does not immediately erase information it already received. Provider retention, deletion procedures and any processing by their service infrastructure are governed by their policies. Their services may process data outside your country. We do not promise a particular storage country or a fixed provider deletion period.

Firebase privacy information OneSignal privacy policy

Advertising attribution with Adjust

Purpose and recipients: with your App Tracking Transparency permission, Lomase uses Adjust attribution services to measure which advertising sources bring people to Lomase and evaluate our acquisition campaigns. This measurement can link this app's device information with advertising engagement information from other companies. Attribution requests go to Adjust; attribution results are also sent to the server that operates Lomase's connected service. This is separate from notification delivery and does not mean Lomase displays third-party advertisements.

Information sent to Adjust: the advertising identifier (IDFA), when available after authorization; the identifier for vendor (IDFV); an installation identifier; app and bundle version information; device model and operating system; request timestamps, installation/session information and tracking authorization status. Network connections also expose an IP address. These identifiers allow attribution records to be associated with the same device or installation. Lomase does not include journal notes, tags, ratings, photos, videos or voice recordings in these requests.

Attribution results sent to our service: the advertising source, campaign, ad group or ad set identifiers returned by Adjust, when available, together with attribution client/version information, a device identifier, a service user identifier, the app version and bundle identifier. The service user and device identifiers associate the attribution result with the connected service session; these records are not anonymous. An unavailable attribution field is not replaced with an invented campaign value.

Your permission: attribution starts only after a connected service session is ready, the app is in the foreground and iOS reports that tracking is authorized. If permission has not been decided, the app requests it through the system dialog. If you decline or iOS restricts tracking, the attribution client does not start or send attribution reports. Reading this policy or enabling notifications does not grant tracking permission.

Withdraw permission: change Lomase's permission in iOS Settings under Privacy & Security → Tracking. Without authorization, the attribution client does not start new requests and the app does not submit new attribution results. Withdrawing permission does not recall requests already sent or delete records already received. Notification switches control their own providers and do not control attribution. You can continue using the local journal without granting tracking permission.

Retention and requests: attribution state and an installation identifier are stored on the device; the installation identifier is stored in the iOS Keychain and may remain after uninstalling. Erase all local data clears journal data and is not an attribution-record deletion control. Our service and Adjust handle information already received for the attribution purposes described above and applicable legal requirements. We do not specify a fixed retention period or promise that uninstalling erases server records. Contact huangbidanmzz@163.com to request access, correction or deletion of service-held attribution information; Adjust handles its own records under its privacy policy. Processing may take place outside your country.

Adjust privacy policy

Retention, removal and erasure

Local records and saved attachments remain available until you remove them, erase app data or otherwise remove the app’s local storage. The following controls have different scopes:

Deletion in Lomase removes the app’s copy. An older device backup or a file you later import can restore previously exported records. We cannot inspect or delete those external copies for you.

Your choices and privacy requests

You can view and correct local reflections in History, export a portable backup, delete records, withdraw optional camera or microphone access, switch off notification providers and withdraw tracking permission in iOS Settings. Permissions are feature-specific choices; accepting the Terms of use is not blanket permission for recording, tracking or optional provider collection.

Depending on where you live, applicable law may provide rights to access, correct, delete, restrict or object to processing, receive portable information, withdraw consent or complain to a relevant regulator. Local-app controls handle information held only on your device. We do not have a server copy of your journal to retrieve, inspect or erase remotely.

For a request that cannot be handled on the device, email huangbidanmzz@163.com with a brief description and the provider concerned, if any. We may ask for the minimum information reasonably needed to understand the request or verify authority. Do not send a full backup, private recordings, passcodes or other sensitive material unless a specific need and safe method have been agreed.

We will respond as required by applicable law and explain any practical limits. A provider may need to handle its own records under its policy. You do not need to delete your journal or stop using the text features to decline optional capture access.

Email, hosted pages and external websites

Contact messages: if you email us, your chosen mail service sends your address, message and any attachments you include. We use information received to answer, investigate and document the request, and retain it only as reasonably needed for that purpose or applicable legal obligations. Email service providers process delivery under their own terms. This page contains no message-submission form; merely viewing it does not send a support request.

Hosted policies: the app may load the online privacy and terms pages and use bundled copies if the online pages are unavailable. Loading a hosted page requires an HTTPS request; the hosting infrastructure receives ordinary request information such as IP address, request time and browser or app request details. These policy files do not contain scripts, advertising pixels or analytics tags, and the app does not attach journal content to policy-page requests.

External links: provider links open external websites, whose privacy and cookie practices apply. Visiting those sites is separate from using the local journal. This policy does not promise that independently operated sites or your chosen sharing destinations have the same settings.

Children and information about other people

Lomase is a general personal-recording tool. We do not knowingly seek children’s personal information through support messages or optional services. Where local law requires a parent or guardian’s involvement, obtain it before using those services. If you believe a child’s information has been sent to us, contact huangbidanmzz@163.com so the concern can be addressed.

A recording can contain someone else’s image, voice or private information. Obtain any consent required by law before capturing or sharing it. Local storage does not remove your responsibility to respect other people’s privacy.

Changes and contact

We will update this policy when the app’s features or information practices change and revise the date at the top. Material changes will be communicated as required by applicable law. If a new feature requires additional permission or consent, the corresponding choice will be requested; an updated policy alone does not grant camera or microphone access.

For privacy questions, rights requests or concerns about these descriptions, contact the Lomase developer at huangbidanmzz@163.com. For safe use, content responsibilities and service limitations, read the Terms of use.