Privacy Policy

1. Data You Create

You own the journals, plans, reflections, attachments, and other content you create or capture in Milogs. Milogs is local-first, so your data is stored primarily on your device. We do not claim ownership of your content.

Local-only mode stores data on your device without cloud sync. Authenticated sync mode can sync supported data across your devices.

2. Data Security

Milogs implements end-to-end encryption for private synced content, including media files, in authenticated sync mode. Local-only mode stores data locally on your device without cloud sync.

Google user data and other integration data are transmitted over secure HTTPS connections. Stored OAuth tokens are used only to operate the integrations you authorize, refresh access, revoke access, or perform deletion actions where supported.

3. Google API Services User Data

Milogs only accesses Google user data after you choose to use a Google feature and complete Google's authorization flow. Milogs may access the following Google user data:

• Google Sign-In: your Google account identifier, email address, display name, profile image, and authentication tokens needed to create and maintain your Milogs session.
• Google Drive: OAuth access and refresh tokens, token expiry, Google account identifier and email used to confirm the connected storage account, Drive file and folder identifiers, file names, MIME types, sizes, creation timestamps, app media file content uploaded through Milogs, and Drive storage quota usage needed to show storage status.
• Google Calendar: OAuth access and refresh tokens, token expiry, and the Milogs plan data needed to create, update, or delete Milogs calendar events in your primary Google Calendar, including event title, optional description, start time, end time, the Google event identifier, and a private Milogs plan identifier.

Milogs uses this Google user data only to provide user-facing features you request: Google Sign-In authenticates you, Google Drive stores and retrieves your Milogs media, and Google Calendar syncs Milogs plans that have due dates or reminder times.

4. Google Drive Storage

For Google Drive, Milogs requests the drive.file permission so the app can create and manage files and folders that Milogs creates or that you authorize for Milogs. We do not request broad access to your Drive.

For app media storage, we create or use a folder named "Milogs" and use that folder to store your app's media assets. Within this folder, the app can create, read, download, check metadata for, and delete files as needed to manage your media content. Milogs does not read your Google Drive files outside files and folders created or authorized for Milogs.

5. Google Calendar Sync

When you connect Google Calendar, Milogs uses the connection solely to sync your plans that have a due date or reminder time, so you can view them alongside your existing calendar events.

Milogs creates, updates, and deletes Milogs-created events in your primary Google Calendar. Milogs does not read, list, analyze, modify, or access existing Google Calendar events that were not created by Milogs.

6. Other Storage Providers

Milogs supports optional external storage providers, including Dropbox, Apple iCloud, Cloudflare R2, and AWS S3. When you connect an external storage provider, Milogs uses it to store and retrieve app media assets that you choose to keep with that provider.

7. Optional Finance Alert Capture

Milogs may offer optional finance alert capture inside the finance settings area. On Android, if you intentionally enable this feature and grant the required Android notification access permission, Milogs can read notification content from banking or payment apps to extract transaction details for your finance tracker.

This feature is off by default. Captured alerts are used only to create finance transaction drafts, review items, or transactions when you enable auto-save for a specific trusted pattern. Milogs does not use notification content for advertising, credit scoring, or unrelated analytics, and we do not sell any user data.

When possible, Milogs stores parsed transaction details, redacted previews, source metadata, and duplicate-detection hashes instead of raw notification bodies. You can opt out from finance settings at any time. Opting out clears the app's pending native alert queue and stops Milogs from processing alerts, even if Android notification access remains granted. You can also revoke notification access from Android system settings.

iOS does not provide an App Store-safe API for Milogs to automatically read notifications from other apps. On iOS, Milogs supports only manual alert parsing, such as pasting alert text into the finance settings parser.

8. Optional Cloud Sync

If you choose to use Milogs cloud synchronization, your encrypted data is transmitted to our servers to enable multi-device access. You can disable sync and delete cloud data through the app settings.

9. Anonymous Activity Tracking

To improve Milogs and keep internal usage records, the app pings our backend once per day when you access it. This ping is anonymous and does not include personal information, account IDs, or journal content. It only reports a non-identifiable installation ID, your platform, and app version so we can track daily, weekly, and monthly active users.

10. How We Share Data

We do not sell any user data. We do not transfer Google user data, finance data, notification-derived data, journal content, plan content, or usage data to advertising platforms, use it for advertising or retargeting, or use it to determine creditworthiness.

Milogs does not provide staff with an admin view for browsing your Google Drive content or Google Calendar events. If you ask us for help, we work from the details you choose to share with support. We would only access specific Google integration data if you ask us to help with that data, if access is necessary to investigate abuse or a security issue, or if we are legally required to do so.

11. AI and Machine Learning

Milogs does not use Google Workspace API data to create, train, or improve machine learning or artificial intelligence models.

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

12. Logout, Disconnect, and Account Deletion

Logging out removes signed-in account data from the device, including local encrypted sync caches and key material. After logout, Milogs runs in fresh local-only mode until you sign in again.

You can disconnect Google Drive or Google Calendar in Milogs settings. Disconnecting stops new sync activity and Milogs attempts to revoke the relevant Google token.

To delete your account, go to Settings, scroll to the end of the page, select Delete account, and complete two confirmation prompts. After confirmation, your account deletion request is processed immediately.

When deletion is confirmed, your media assets and messages are scrubbed from our servers immediately. Milogs removes stored Google tokens and integration references from Milogs and, when a valid Google Drive token is available, attempts to delete Milogs-managed Drive media files.

We retain limited account preference records for up to 30 days only to detect remaining signed-in instances on other devices and trigger remote deletion operations. After 30 days, those retained preference records are permanently deleted.

13. Changes to This Policy

We may update this Privacy Policy from time to time. If Milogs changes how it uses Google user data, we will update this policy and request consent where required before using that data in a new way.