myOS

Privacy Policy

Effective: August 11, 2026 Last updated: August 28, 2026

myOS is a personal organization and self-improvement application. This Privacy Policy explains how information is accessed, stored, processed, backed up, and used when you use myOS.

At a Glance

  • Your personal content is stored primarily on your device.
  • Local backup export and restore are available from files you choose.
  • Optional Premium Google Drive backup uses your own Google Drive app data folder.
  • App notifications, calendar reminders, microphone recording, and Google Drive access are permission-based.
  • myOS does not sell your personal journal or organizational content.
  • Feedback, roadmap, changelog, voting, and comments are handled by the public Featurebase portal.
  • Firebase Analytics is not active in the current app build.
  • Firebase Crashlytics may help diagnose release-mode crashes and technical problems.

Information Stored on Your Device

Most personal information you create in myOS is primarily stored locally on your device. This includes your planning, tracking, journal, finance, workout, and preference data. This personal content is not intentionally uploaded to Firebase Analytics or Firebase Crashlytics.

  • Journal entries
  • Journal images, audio attachments, and voice notes saved into app storage
  • Habits and habit progress
  • To-do items
  • Mood records
  • Sleep, weather, and period-tracking records where you use those journal tools
  • Workout and gym information
  • Finance records you create in the Finance module
  • Goals and targets
  • Rewards
  • Reminders
  • Categories
  • App preferences and settings
  • Local data may be lost if you clear app data, uninstall myOS, reset or lose your device, or remove local storage without a backup.

Local Backup and Restore

myOS lets you export a local .mbk backup file and import a backup file you select. Local backup is available without Premium. Importing a backup replaces the current local app data with the data from the selected backup file.

  • You control where exported backup files are saved or shared.
  • Anyone with access to an exported backup file may be able to access the data inside it.
  • Keep exported backup files in a safe place and delete old copies you no longer need.

Google Drive Backup and Restore

Where available to eligible Premium users, Google Drive backup and restore lets you store supported backup data in your own Google Drive app data folder after you authorize Google access. myOS does not intentionally store a copy of your Drive backup on myOS servers. Google Drive sync may upload, download, compare, or replace backup data as needed to keep the selected Google account and local app data aligned.

  • myOS uses Google Sign-In for Drive authorization.
  • The current implementation uses the Google Drive appDataFolder scope.
  • The Drive backup file is named myos_google_drive_backup.json.
  • The backup file is stored in your Google Drive account, not in a public myOS database.
  • Auto cloud backup can be enabled by Premium users and may wait for Wi-Fi if that setting is turned on.
  • When switching Google accounts, myOS may clear the previous account local data before connecting the new account so data is not silently uploaded to the wrong account.
  • You can revoke Google Drive access through your Google account settings.
  • Drive backup depends on Google Drive availability, internet access, and your Google account permissions.

Permissions and Reminders

myOS asks for device permissions only when a feature needs them or when you enable them from Permissions. App notifications are used for habit, todo, and workout reminders. Calendar access is used only when you choose a calendar reminder. If you deny a permission, the related feature may not work until you allow it in device settings.

  • Notification permission is required for app reminder notifications.
  • If notification permission is denied, myOS should not save a reminder as though it can notify you.
  • Calendar permission is used for calendar reminder creation, editing, and cleanup where supported.
  • Exact alarm access may be requested or used on Android when available; otherwise reminders may use inexact scheduling.

Microphone, Photos, and Attachments

Journal media features can use files or recording tools you choose. Microphone access is used only when you record a voice note. Picked images and audio files are copied into app storage for use inside journal entries.

  • Microphone permission is required only for voice recording.
  • Image and audio attachments are Premium-gated features in the current app.
  • Media files stored in app storage may be removed if app data is cleared or the app is uninstalled.

Feedback and Feature Requests

If you voluntarily submit a bug report, feature request, or other feedback, myOS opens the public Featurebase portal at https://myos.featurebase.app. Featurebase hosts the feedback workflow, including feature requests, bug reports, voting, comments, public roadmap items, statuses, and changelog information. myOS no longer stores these user-facing feedback submissions in Firebase Firestore.

  • Content you enter into Featurebase, such as titles, descriptions, comments, votes, and reactions.
  • Any name, email, account profile, browser, device, usage, or technical information Featurebase collects according to its own policies and settings.
  • Featurebase content may be public or visible to other users depending on the portal feature and your submission choices.
  • Please do not include passwords, payment information, or highly sensitive personal information in feedback.

Analytics

The current myOS build uses a no-op analytics service. Firebase Analytics is not included as an active SDK, and analytics methods do not send usage events in this build.

  • The app keeps analytics event names in code for compatibility, but those calls currently do not transmit analytics data.
  • If analytics is re-enabled in a future release, this policy should be updated before that release.

Firebase Crashlytics

Firebase Crashlytics may help diagnose crashes and technical problems in release builds. Crash reporting is best-effort and may include technical diagnostics needed to understand what went wrong.

  • Crash information
  • Stack traces
  • Device and operating system information
  • App version
  • Sanitized technical logs, custom keys, or identifiers where safe
  • Repeated errors may be deduplicated during an app session.
  • Private personal content is not intentionally attached to Crashlytics reports.

Advertising

The free version of myOS may display advertisements using Google advertising services such as AdMob. Advertising services may process technical, device, and advertising information as permitted by your settings, consent choices, and applicable law.

  • The app requests non-personalized ads where configured.
  • Premium users may receive an ad-free experience according to the Premium offering.
  • Banners may be disposed while the app is in the background and reloaded when the app resumes.
  • Advertising availability and personalization may depend on Google services and device settings.

Premium Purchases

Premium purchases use Google Play Billing. Google processes payment information, and myOS does not directly store complete card or payment credentials.

  • Technical purchase information may be processed as necessary to verify Premium entitlement.
  • The current active product configuration is the monthly Premium subscription; yearly and lifetime product IDs may exist for future use.
  • Promotional coupons may unlock limited-period or lifetime Premium access for eligible accounts.

Authentication

Firebase Authentication is not currently required for normal myOS usage. Google authorization may separately be required if you choose to use Google Drive backup or restore features.

App Lock

Premium users may enable app lock features such as biometric or pattern protection. Biometric authentication is handled by the device operating system. myOS does not receive or store your actual fingerprint, face, or other biometric template.

Artificial Intelligence

myOS does not currently send personal journal content to OpenAI, Gemini, Claude, or other generative AI providers for processing. If AI functionality is introduced in the future, this policy should be updated before that feature is used.

Information Sharing

myOS does not sell your personal journal or organizational content. Some service providers may process information only as needed to provide app functionality, diagnostics, billing, backup, advertising, feedback, or connected-account features.

  • Firebase Core and Firebase Crashlytics
  • Google Sign-In and Google Drive
  • Google Play Billing
  • Google AdMob
  • Device operating-system permission, notification, biometric, calendar, and file-picker services
  • Featurebase for public feedback, roadmap, changelog, voting, and comments

Data Security

myOS uses reasonable safeguards appropriate for the app features it provides. No electronic storage or transmission system can be guaranteed to be completely secure, so you should keep your device, Google account, and backups protected.

Data Retention and Deletion

Different categories of information are retained in different places depending on the feature you use.

  • Local data remains on your device until you delete it, clear app data, uninstall myOS, reset the device, or otherwise remove local storage.
  • Local .mbk backup files remain wherever you save or share them until you delete them from that location.
  • Google Drive backups are controlled through your Google Drive and Google account.
  • Feedback submitted through Featurebase is retained and managed through Featurebase according to the portal settings and applicable Featurebase policies.
  • Crashlytics information is subject to the applicable Firebase and Google service configuration and retention settings.
  • You can contact myOS Support about information directly controlled by myOS.

Children's Privacy

myOS is a general personal organization app and is not designed to collect personal information from children. If you believe a child has provided information that should be reviewed or removed, please contact myOS Support.

Third-Party Services

Google, Firebase, Drive, Play Billing, advertising functionality, and Featurebase may be governed by their own terms, privacy policies, settings, and account controls. You should review those policies for details about their practices.

Changes to This Privacy Policy

This Privacy Policy may change as myOS functionality, service providers, legal requirements, or operational needs change. The updated date will be revised when meaningful changes are made.

Contact

For privacy questions or requests about information directly controlled by myOS, contact myOS Support at myosappsupport@gmail.com.