LaterMe Privacy Policy
Effective date: 12 August 2026
Developer and publisher: Isplis
Application identifier: com.isplis.laterme
1. Privacy at a glance
LaterMe is designed to operate locally on your device. It does not require a LaterMe account, does not provide cloud synchronization, and does not send your journal content to Isplis. Journal content is stored in an encrypted application database on your device. LaterMe does not contain advertising, analytics, crash-reporting, or attribution SDKs. Optional voice transcription is designed to use only speech recognition that the operating system reports as available on-device.
2. Information stored by LaterMe
LaterMe stores the information you choose to create in the app, including entries, optional titles, prompt answers, reflections, lessons, drafts, revision history, archive state, and the local Search index. It also stores local preferences and app-protection information needed for onboarding, PIN protection, biometric-protection selection, and reset recovery.
The database encryption key and app-protection records are stored using operating-system protected storage. If you set a PIN, LaterMe stores a salted one-way verifier and security metadata rather than the readable PIN itself.
3. Information sent to Isplis
The LaterMe app does not send journal content, Search queries, voice recordings, transcripts, usage analytics, crash reports, advertising identifiers, or app-protection information to Isplis. The app has no LaterMe backend or account service.
If you choose to contact Isplis outside the app, such as by email, the information you send is handled by the communication service you use and is not part of LaterMe's local journal storage.
4. Journal and Search data
Entries, titles, answers, reflections, lessons, drafts, immutable revision history, and archive state are stored locally in the encrypted LaterMe database. Search is performed locally. Its index contains current searchable journal content and is stored in the same encrypted database; historical revisions are not separately added to the Search index.
Archiving keeps an entry and its related content on the device but removes the aggregate from normal journal and Search results. Restoring makes it active and searchable again. Permanent deletion from Archived removes the selected entry aggregate, including its drafts, revisions, reflections, lessons, and Search projection.
5. Voice input and transcription
Voice input is optional. When you start voice input, LaterMe records audio into a dedicated temporary application location and asks the operating system to transcribe it only when on-device speech recognition is available for the device and requested language. LaterMe has no remote or cloud transcription fallback. Availability depends on the operating system, device, installed recognition support, and language.
Temporary audio is not a durable journal record. LaterMe is designed to remove it after successful transcription, cancellation, or failure. It also clears stale temporary recordings during application startup and removes temporary recording state during full reset. If required cleanup fails, the voice feature blocks further use until cleanup succeeds.
6. Microphone access
LaterMe requests microphone permission only when you choose to use voice input. You can use the journal without granting microphone access. The operating system controls the permission prompt and lets you change microphone access in device settings.
7. PIN and biometric protection
PIN protection is optional and local to the device. LaterMe stores a one-way PIN verifier and related protection metadata in operating-system protected storage; it does not store a readable copy of your PIN.
If you enable biometric protection, LaterMe asks the operating system to authenticate you using biometrics already enrolled on the device. Fingerprint, Face ID, and other biometric templates remain managed by the operating system. LaterMe does not receive or store those templates; it receives only the authentication result exposed by the operating system.
8. Device storage and encryption
LaterMe stores its journal database in application-local storage and encrypts it with a 256-bit key kept separately in operating-system protected storage. This is intended to protect journal data at rest, but no application can guarantee protection against every device compromise, operating-system vulnerability, malicious modification, or loss of device credentials.
Temporary voice recordings are stored outside the durable journal database in an application-controlled temporary location for the limited transcription lifecycle described above.
9. Backups and device transfer
LaterMe is configured to exclude its private persistence from Android cloud backup and device transfer and marks its iOS persistence directory as excluded from backup. These controls are intended to prevent LaterMe journal data from entering platform app-backup or device-transfer mechanisms, to the extent the operating system enforces the configuration.
LaterMe does not provide its own cloud backup. Device vendors, operating systems, device-management software, forensic tools, or user-controlled copies may operate outside LaterMe's control.
10. Data retention and deletion
Drafts remain on the device until they are completed, discarded through available app behavior, permanently deleted with their owning aggregate, or removed by full reset. Committed edits create immutable revisions, so older revisions remain in local history until the owning entry aggregate is permanently deleted or all LaterMe data is reset.
Archive is not permanent deletion. Archived content remains locally stored until you restore it, permanently delete it from Archived, perform a full reset, or the operating system removes application data.
11. Full reset and uninstall
The in-app full reset is designed to remove the LaterMe journal database and sidecar files, its encryption key, app-protection data, reset metadata, preferences represented by those records, and temporary voice recordings. Reset recovery is designed to resume an interrupted reset when the app next starts.
Uninstall normally removes application-local files according to operating-system behavior. Some operating-system protected storage may follow platform-specific retention rules, so use LaterMe's full reset before uninstalling when you want the app to request removal of all LaterMe-managed local data. Because there is no LaterMe backend or cloud copy, Isplis cannot remotely restore deleted journal content.
12. Third-party services
LaterMe is built with Flutter and third-party software libraries for local database storage, encryption, secure storage, biometrics, file locations, and application composition. These software dependencies are not, by themselves, remote data-processing services.
The app does not integrate advertising, analytics, crash-reporting, attribution, social, remote journal, or cloud-synchronization services. Operating-system services provide protected storage, biometric prompts, microphone access, and on-device speech recognition under the controls and privacy terms of the device platform.
13. Analytics and advertising
LaterMe does not contain advertising and does not use advertising identifiers. It does not include product analytics, usage tracking, crash-reporting, or attribution SDKs.
14. Accounts and cloud sync
LaterMe does not require or offer a LaterMe account and does not provide cloud synchronization or remote recovery. The intended target-audience classification for the Google Play listing is maintained separately from this technical data-handling policy; this policy does not assign or infer an age group.
15. Security limitations
LaterMe uses local encryption, operating-system protected storage, optional local access protection, and backup-exclusion controls. These measures reduce risk but do not make any device or data impossible to access. Protect your device credentials, install operating-system security updates, and use full reset before transferring or disposing of a device when appropriate.
16. Changes to this policy
Isplis may update this policy when LaterMe's features, data handling, platform requirements, or legal obligations change. The updated policy will identify its effective date. Material product changes must be reflected in the in-app and public versions of this policy before the related release is distributed.
17. Contact
For privacy questions about LaterMe, contact Isplis at play.google@isplis.com or visit https://isplis.com.