Within: Journal & Reflection
Privacy Policy
Effective October 12, 2026
This Privacy Policy explains how Byeshe (“we,” “us,” or “our”) handles information when you use Within: Journal & Reflection (the “Application”), a freemium Android app with advertising and optional paid features or subscriptions. Features and providers may vary by version, region, and configuration. No Application account is required. Contact play@byeshe.com for privacy questions.
Journal, insights, and personal content
Entries can include the question, written content, mood, tags, word count, and timestamps. The Application also stores your display name, custom prompts, personal cards, weekly reviews, meditation activity, and preferences. Local calculations support insights and progress displays. There is no required account or account-based cloud journal synchronization.
Reminders, widgets, and app lock
Optional notification permission supports journaling reminders. Exact-alarm access supports precise reminders where Android permits; boot-completed handling restores scheduled reminders after restart. Reminders can still be delayed by system restrictions. Widgets can display selected journaling or personal-card content on your Home screen; consider who can see your device. Optional app lock uses Android biometric or device-credential authentication. The app receives the result, not biometric templates or your credential. The interface lock is not separate encryption of exported files or the database.
Backup, import, and sharing
User-initiated JSON export can include entries, cards, weekly reviews, and preferences; import reads the file you select. Exported JSON is readable content and should be protected. Shared reflection or weekly-review images are created in app cache and sent to your selected destination. Copies held by recipients, document providers, or backups are managed separately. No camera, microphone, contacts, or location access is requested for journaling.
Android permissions
Optional permissions can be declined or revoked in Android settings. Features depending on that access may be limited. Reading this policy does not grant permission, and revoking access does not automatically erase saved records.
| Permission | Purpose and scope |
|---|---|
android.permission.ACCESS_ADSERVICES_AD_ID | Allow integrated advertising services to use supported Android advertising identifiers, attribution, topics, or custom audiences, subject to system privacy controls. |
android.permission.ACCESS_ADSERVICES_ATTRIBUTION | Allow integrated advertising services to use supported Android advertising identifiers, attribution, topics, or custom audiences, subject to system privacy controls. |
android.permission.ACCESS_ADSERVICES_CUSTOM_AUDIENCE | Allow integrated advertising services to use supported Android advertising identifiers, attribution, topics, or custom audiences, subject to system privacy controls. |
android.permission.ACCESS_ADSERVICES_TOPICS | Allow integrated advertising services to use supported Android advertising identifiers, attribution, topics, or custom audiences, subject to system privacy controls. |
android.permission.ACCESS_NETWORK_STATE | Check network connectivity for app and integrated-service requests. |
android.permission.ACCESS_WIFI_STATE | Allow integrated libraries to read permitted Wi-Fi technical state; this does not expose Wi-Fi passwords. |
android.permission.FOREGROUND_SERVICE | Allow declared foreground work where used by the app or integrated libraries; this permission alone grants no camera, microphone, or location access. |
android.permission.INTERNET | Connect to advertising, configuration, analytics, attribution, billing, and diagnostic services. Feature-specific network use is explained above. |
android.permission.POST_NOTIFICATIONS | Show optional journaling reminders; Android lock-screen settings control visibility. |
android.permission.READ_BASIC_PHONE_STATE | Allow integrated libraries to read basic cellular and software state; this does not grant access to contacts, call logs, or call audio. |
android.permission.RECEIVE_BOOT_COMPLETED | Reschedule reminders after device restart; no access to other apps’ content. |
android.permission.SCHEDULE_EXACT_ALARM | Optional special access for precise reminder scheduling where supported. |
android.permission.USE_BIOMETRIC | Use Android authentication for the optional app lock; no biometric-template access. |
android.permission.USE_FINGERPRINT | Legacy Android authentication support; the app receives authentication results only. |
android.permission.VIBRATE | Provide haptic feedback where used. |
android.permission.WAKE_LOCK | Support limited ongoing work or integrated-library scheduling; it does not grant access to personal records. |
com.amazon.privacypass.ATTEST | Allow integrated advertising services to use authenticity or fraud attestation where supported. |
com.android.vending.BILLING | Google Play purchases and subscription entitlement checks; Google handles payment credentials. |
com.android.vending.CHECK_LICENSE | Store-license verification where used by integrated libraries. |
com.byeshe.reflection.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION | An AndroidX signature-level guard for internal broadcasts; no additional access to personal records. |
com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE | Obtain installation source and click or installation timing from Google Play for attribution. |
com.google.android.gms.permission.AD_ID | Access the resettable advertising identifier for advertising, measurement, attribution, and fraud prevention, subject to Android privacy controls. |
Local storage, backup, and support
Journals, cards, and weekly reviews are kept in an app-private Room database. Prompts, reminder choices, app-lock settings, and other preferences are saved locally. Android backup and device-transfer features may include eligible app data, depending on your device and backup settings. This is separate from a Byeshe server upload. Manage backup copies through Android or your backup provider.
If you contact support, we receive your email address, message, and attachments you choose to send. We use them to respond and resolve your request.
Advertising and privacy choices
The ad-supported version uses Google AdMob and mediation partners. They may process IP address, approximate region, advertising and app identifiers, device and operating-system information, network state, ad requests, impressions, clicks, interactions, and diagnostics. Processing supports ad delivery, measurement, attribution, personalization where permitted, security, and fraud prevention. Non-personalized ads can still involve technical data processing.
Google’s User Messaging Platform handles advertising consent where applicable. When required and available, you can revisit consent through Settings → Privacy options. Availability depends on region, provider, and configuration. You can also adjust Android advertising privacy settings, including advertising ID and supported advertising features. An ad-removal purchase changes ad display according to its offer; configuration, purchase validation, analytics, and other technical communications can continue.
Advertising partners may include Google AdMob, Meta Audience Network, AppLovin, Pangle, Liftoff Monetize (Vungle), Mintegral, InMobi, BidMachine, and Unity Ads and ironSource. Providers serving a particular request depend on mediation configuration and availability.
Analytics, configuration, attribution, and diagnostics
Firebase Analytics is enabled by default. It can process launches, sessions, screen views, feature interactions, settings changes, ads, and purchases, together with app-instance or available advertising identifiers, app version, device information, and approximate region. We use it to understand use, improve features, and measure conversions. Events can describe starting or saving a reflection, whether a mood was selected, and writing duration. Journal text, custom prompts, personal tag values, and weekly-review content are not intentionally included in those events or supplied to advertising providers.
Firebase Remote Config retrieves app and advertising configuration using installation identifiers and technical requests. Firebase Crashlytics uploads crash and non-fatal error diagnostics, such as traces, error messages, identifiers, app version, and device state. Reports may be cached until a later launch and are not guaranteed to be anonymous. The Application has no dedicated in-app switch for Analytics or Crashlytics.
Google Play Install Referrer supplies installation source and click or installation timing. Meta App Events and TikTok Business services may process installation, launch, and conversion events and available identifiers depending on configuration. Purchase events can include order or transaction identifier, product, quantity, currency, and attributed value, which can differ from the amount charged. See Firebase privacy information, Google’s Privacy Policy, Meta’s Privacy Policy, and TikTok’s Partner Privacy Policy.
Purchases and subscriptions
Google Play processes payments. The Application and purchase services may process product identifiers, purchase tokens, order identifiers, purchase time, subscription status, and entitlements to acknowledge purchases, restore access, prevent fraud, and provide support. We do not receive your full payment-card number or payment credentials. Purchase conversion events may be sent to Firebase Analytics, Meta, and TikTok as described above. Clearing app data or uninstalling does not cancel a subscription.
Sharing, external destinations, and international processing
Advertising, technical, attribution, and purchase information is processed by the providers above for the described purposes. We may disclose information held by us to providers assisting us, where legally required, to protect rights and safety, or in a business transfer subject to applicable protections. Providers may process information outside your country under their policies and applicable safeguards. Exported backups and shared images can contain private journal content. The recipient or storage provider handles the copy under its own privacy practices.
These pages use Firebase Hosting, which processes IP addresses and technical requests for delivery and security. The pages contain no advertising or analytics scripts, external fonts, or tracking cookies.
Retention, deletion, and your rights
Local content has no automatic time-based expiry. Delete individual content using available app controls, or clear Application storage or uninstall to remove app-private data. Shared-image cache files can remain until cleared by the app or Android. Exported JSON, shared images, and Android backup copies require separate deletion. Restoring or importing a backup can bring content back.
Support correspondence and purchase-related information held by us are retained as needed to resolve requests, maintain entitlements, prevent fraud, and meet legal obligations, then deleted when no longer needed. Advertising and technical providers have their own retention periods. Local deletion does not recall events or diagnostics already sent, erase store transaction history, or cancel subscriptions.
Contact play@byeshe.com to request access, correction, deletion, or rights available in your location, including objection, restriction, portability, or withdrawal of consent. We may need to verify your request. We cannot remotely retrieve or delete information held only on your device. Contact us for help with information processed on our behalf; providers’ independent processing follows their policies. You may also contact your local data-protection authority.
Security and children
We use reasonable safeguards, but no storage or transmission is completely secure. Protect your device, email, and backups. The Application is not directed to children under 13. Minors must meet applicable age requirements and obtain guardian permission where required. If you believe a child has provided personal information to us, contact us so we can take appropriate action.
Changes and contact
We may update this policy and its effective date when features or data practices change, with additional notice or consent where required. For privacy questions, contact Byeshe at play@byeshe.com.