BB10 Revival Launcher
Privacy Policy

01Scope and contact

This policy covers how BB10 Revival Launcher handles data for its local desktop, Hub, built-in tools and optional services. The project is maintained by an independent developer. Contact: ethan9456@gmail.com.

The app does not require a separate launcher account. Mail connections use your existing mail accounts. Removing an account from this app or revoking access does not delete your account with that service.

02Desktop and app data

To show apps, search, folders and Active Frames, the app reads launchable app names, icons and package identifiers on your device. It stores layout, folders, preferences and a record of apps opened from this launcher locally. This data is not sent to the developer and does not indicate that another app is currently running.

The app does not capture other apps, record the screen, or use accessibility services or overlays to obtain other app content.

03Notifications and social messages

BB10 Revival Launcher reads notification sources, titles, text, times and opening actions for the combined Hub view, including while Hub is closed. Social replies and full conversations are handled by the source app.

Ordinary notifications stay in memory. Keep notification text saves text from supported installed communication apps, up to 1,000 entries per conversation and 5,000 on the device. A conversation shortcut ID supplied by the source may be saved to open that app. Replies saved by earlier versions are retained. Stop future storage in Hub general settings; clear existing records in Local notification records.

Notification content is not sent to the developer or backed up to the cloud. Disabling storage does not stop notifications; hiding previews does not stop storage. Notification access can be revoked in Android settings at any time. Declining does not affect the basic desktop.

04Gmail access, messages and attachments

Gmail requires Google authorization. The gmail.modify scope supports reading, search, compose, reply, forward, send, read/unread status, archive and moving mail to Trash. The phone connects directly to Google over HTTPS. Google receives the account, queries, mail and attachment data needed for each action.

Loaded messages and summaries are cached in memory. Local drafts, signatures, account names and copies of selected attachments are stored in app-private storage. Downloaded, photographed or prepared-for-export attachments may remain in private cache. Files are shared with another app or location only when you choose to open or save them there. Pickers do not grant access to your entire gallery or storage.

You do not provide your Gmail password to the developer. Google manages authorization. Access tokens are used for requests and are not written to a local mail database.

Formatted mail uses native text in memory and does not run scripts. External images are off by default for each message. Loading them sends an HTTPS request to the site specified by the message; it may receive your IP address and identify that the message was read. Images have size and count limits and remain only in this screen’s memory. Some embedded images require opening attachments. Original plain text remains available for replies and export.

05iCloud, Yahoo and AOL mail

These services connect directly to their mail servers using encrypted IMAP/SMTP and an app-specific password you create with the provider. The servers receive your account, app-specific password and data needed for mail actions. There is no developer mail relay, and certificate checks are not bypassed.

App-specific passwords are encrypted with an Android Keystore device key in app-private storage and decrypted in memory for login and sending. Account addresses and provider names are local settings. Mail summaries and bodies are held in memory; drafts, signatures, selected attachments and download cache are in private storage.

This version uses manual refresh, without background push for these services. Whether SMTP sent mail is saved depends on the provider; this version does not create another sent copy. Messages are shown as text, without automatically loading remote tracking images.

06Microsoft mail access and data

Outlook.com, Hotmail and Microsoft 365 / Exchange Online use Microsoft's sign-in page and Microsoft Authentication Library (MSAL). Delegated User.Read, Mail.ReadWrite and Mail.Send permissions identify the signed-in account, read and manage mail, and send messages. Only the mailbox authorized by the signed-in user is accessed. Organization policies may restrict access. On-premises Exchange Server is not supported.

The phone connects directly to Microsoft sign-in services and Microsoft Graph over HTTPS. Microsoft receives sign-in, device and connection information, plus mail, recipients, attachments and queries needed for your actions. MSAL manages the on-device authorization cache. This project does not copy access tokens to a mail database, require a Client Secret or ask you to give a password to the developer.

Microsoft accounts support manual refresh and optional local automatic mail checks that you can disable. Mail summaries and loaded bodies are held in memory; drafts, signatures, selected attachments and downloads are in private storage. Sending requires confirmation. If the result is uncertain, the draft is retained and you are asked to check the provider before retrying to avoid duplicate mail.

07Local background mail and optional Gmail cloud push

When automatic checks are enabled, the phone contacts Google or Microsoft directly for new mail in connected accounts. Checks run while using the desktop or Hub; Android schedules background checks while Hub is closed or the screen is off. Battery saving, offline conditions or system scheduling can delay updates; instant push is not guaranteed. Sync position, deduplication identifiers, preferences and update times remain on this device. The first check does not notify all old mail. Disable checks in each mail account’s automatic mail settings. The optional cloud push described below applies only to Gmail.

Only if you separately configure and enable cloud push will your self-deployed Google Cloud service process the account, encrypted background authorization, message identifiers, sync position and device notification address. It uses Firebase Cloud Messaging to signal updates and does not store mail subjects or bodies. Google and Firebase handle operational device and connection data under their service rules. Cloud push is not required for local automatic checks. Disable and clear any cloud authorization before uninstalling the app.

08Limited use of Google data

Google API data is used only to provide the mail and notification features you use. It is not sold or used for advertising, credit evaluation or training general-purpose AI models. Developers do not have arbitrary access to your private mail.

BB10 Revival Launcher's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including Limited Use requirements. Content you choose to send, forward or share is delivered to the recipients or services you select.

09Permissions and built-in tools

Location: the compass reads coordinates in the foreground only and does not store or upload compass location.
Camera and files: used when you choose to take a photo, add a mail attachment or import wallpaper.
Alarms and timers: notifications, exact alarms, full-screen alerts, wake locks, vibration, volume and a foreground audio service support scheduling, ringing and restoring reminders after reboot.
Quick Settings: network, Wi-Fi, Bluetooth and permission to modify system settings support status display and actions you choose.
Desktop: wallpaper changes and uninstall requests happen only when you initiate them. Android still confirms uninstallation.

Hub does not make or answer phone calls, manage call logs, or send or receive SMS. Calls and SMS are handled by the phone’s existing apps. This app does not request SMS, call log or contacts access permissions. The desktop phone shortcut only opens the system dialer. Notification access is a separate authorization; notifications supplied by Android are handled as described in Notifications and social messages. You can revoke permissions in Android settings. Affected optional features may stop, while the basic desktop remains usable.

10Weather and location queries

Forecasts come from MET Norway under CC BY 4.0. Selecting or refreshing a city sends its coordinates directly to MET Norway over HTTPS. The provider also receives your IP address, request time and connection information identifying this app. Manual city selection does not access the phone's location.

Only choosing Use current location and granting permission obtains a single foreground location fix. Coordinates are rounded to two decimal places before querying. There is no background location tracking. Selected cities, coordinates, time zones and forecast cache are stored privately on the device; cities can be removed from the list. The developer does not receive weather locations, and no separate weather account is created.

Weather is forecast data, not live observation. The screen shows forecast publication and query times. Seven-day temperature ranges summarize available periods; feels-like temperature is estimated by this app. Source and license links are available on the weather screen.

The visual cover reads only the local forecast cache for the city selected in Weather, with no additional network or location request. Weather is hidden when unconfigured, unavailable or more than 24 hours old; no temperature is invented. The displayed value is a forecast near the current time. It can be turned off in cover settings.

11Retention, deletion and revocation

Desktop and tool settings remain until you change them, clear app data or uninstall. Active Frames history is local and is removed with app data or uninstallation.

Social history: stop new entries in Hub & messages. Existing entries remain until you clear individual or all histories from More in Hub's local history screen. This affects Hub only, not messages in the original apps.

Gmail: More → Discard draft removes a draft and its attachments. Remove current account and revoke access clears local account and draft data and asks Google to revoke authorization; cloud mail remains. If revocation fails, remove this app from Google's third-party connections page. Files already saved elsewhere or shared are not deleted; manage them separately.

Other mail accounts: Hub → Mail accounts → More beside an account → Remove account from this device deletes local account settings, encrypted app passwords, summaries, drafts and attachment cache. For Microsoft, the app also attempts to clear MSAL's local authorization cache and reports failure. Revoke provider-side access or app passwords separately in Microsoft, Apple, Yahoo or AOL account security settings. Removing a local account does not delete mail at the provider; exported or shared files require separate management.

Clear cache through Android storage settings. Android automatic cloud backup is disabled. Clearing app storage or uninstalling removes private local data and local feature settings. These are data management options; an app update does not require clearing data.

Reports received by support: Your sender address, description, device information and selected attachments are stored in the developer’s Gmail support mailbox. Any copies saved for troubleshooting are subject to the same rules. The developer uses this data only to provide support, diagnose problems and improve this App; original reports and attachments are not published. The email provider processes messages under its own service rules.

Received reports and attachments are retained as needed for troubleshooting, support and necessary maintenance, reviewed periodically and deleted when no longer needed. Issue summaries with identifying personal data removed may be retained as maintenance records. This manual management is separate from the phone’s seven-day attachment-cache cleanup; clearing the phone cache does not delete sent email.

To request deletion of reports and attachments held by the developer, email ethan9456@gmail.com with the report ID or other helpful details, such as the date and subject. You can write from the original sender address to help verify the request; no account password is required. After verification, the developer will delete the relevant messages and copies it holds. If retention is legally required, the reason will be explained and retention limited to what is necessary. The developer cannot delete your sent-mail copy or copies held by other recipients. Provider backups and removal processes are governed by that email service’s rules.

12Report a problem

Reports are optional and are handed to an email app only after you preview and confirm. They include a random report ID, report type, your description and optional steps, expected result and module names, app version, device manufacturer/model, Android/API version, languages and local system-modification hints. These limited hints cannot establish Root status or the cause of a problem. No root permission is requested, no command is run as root, and no installed-app inventory is collected. You may select up to five images/videos totaling 15 MB; only selected files are copied to private app cache and shared with temporary read permission. Cache older than seven days is cleaned when the report screen is next opened; Android may clear it sooner. Remove private information before selecting files. No mail, contacts, chat history, passwords, tokens or logs are attached automatically. The recipient is ethan9456@gmail.com. Your chosen email provider handles delivery; opening its composer is not proof of receipt. Copying copies text only. There is no report-upload server or automatic sending.

This project is maintained by an independent developer. Issues are prioritized according to their impact, reproducibility and available development resources. We do not guarantee a fix for every report, acceptance of every feature request or completion by a particular date. Completed improvements are summarized in release notes. This does not limit customer-support response or privacy-request obligations under applicable law or platform requirements.

Images or videos may contain location, capture information, audio or other original data that the App does not automatically remove. Review and remove anything you do not want to share before attaching them.

13Security and policy updates

Network services use HTTPS; traditional mail uses IMAPS or SMTP requiring TLS. Local data is in Android app-private storage, protected by the system sandbox and device security. This does not claim additional encryption of every local file. Notifications and attachments may contain sensitive information; adjust preview and retention preferences to suit your needs.

This version contains no advertising or behavioral analytics service. Changes to data use will be reflected in this policy, with new in-feature disclosures and consent where needed. Contact ethan9456@gmail.com about privacy or deletion.

14Double-tap to lock

This optional feature uses Android AccessibilityService only to lock the screen when you double-tap empty desktop space. It does not read screen content, watch typing, take screenshots, or collect or send personal data through this service.

If you agree, enable “BB10 screen lock” on the next Android accessibility settings screen. You can turn it off here or in Android settings. Waking and unlocking remain controlled by Android and your existing authentication.

15RSS and motion controls

RSS subscriptions, cached articles, read state and deduplication IDs are stored privately on this device. Checking a subscription sends its URL and your IP address to its provider over HTTPS. Background checking and article notifications are optional and off by default. Removing a subscription removes its local articles and identifiers. The app retains at most 500 articles and 2,000 recent identifiers per feed. Motion controls use local accelerometer and, when available, proximity readings only while the launcher is visible; readings are not stored or uploaded. Face-down locking uses the same limited screen-lock accessibility service. Hidden-app selections are local and do not restrict access through Android or other apps. Article reading uses native text layout and does not execute website scripts. Feed content may be stored in a bounded private device cache that the system can remove; the original article link remains available. Images can be disabled. Displaying images makes direct HTTPS requests to websites specified by the article, which receive the image requests and your IP address. Reading position and layout preferences stay on this device.

16Version integrity verification

Production releases perform version integrity verification automatically for security and protection against unauthorized modification. Google and the developer’s verification service process the app package, version, signing certificate, Play license status, device attestation and a random request code. Email, social messages and RSS content are not sent, and accounts are not bound to a phone. The verification service’s cloud platform may retain connection metadata such as IP addresses; Google handles verification data under its data policies.

17Local settings backup and restore

You can save desktop order, hidden apps, color, Hub display and reading preferences, and portable RSS subscriptions to a local file you select. Backups exclude account authorization, passwords, mail, social messages, article contents, font files and photos. RSS addresses with query parameters or login information are skipped. The file is not encrypted and may contain app names, folder names and subscription URLs; keep it on your own device. Format and checksum validation precede restore; the checksum detects corruption and does not authenticate the file author. Restore merges RSS subscriptions, retains existing messages and articles, and does not change system permissions or sign-in. The app does not upload backups automatically.

18Local fonts and clock card

Supported font files up to 20 MiB can be imported. The app reads only your selected file, validates its format and copies it into private app storage without uploading it. Removing the imported font or app data removes the local copy. Users must ensure they have the necessary font rights. The clock card displays local clock state and the selected page. It does not capture other apps or add clock-data uploads.

19Visual wake cover

The optional foreground service prepares local time and wallpaper while the screen is off for the next wake. Swiping up hands authentication to Android with its existing PIN, password or fingerprint. The selected mode attempts to recover after the first user unlock following reboot or after an app update. Opening the launcher can restore it if background startup is restricted. A persistent notification provides Stop. The cover does not capture other apps or collect unlock credentials.

Project and rights notice

Updated: 2026-10-30

Independent project

BB10 Revival Launcher is a third-party project developed and maintained by an independent designer, focused on desktop organization, built-in tools and bringing messages together.

It is not an official BlackBerry product. It is not affiliated with, endorsed, sponsored or supported by BlackBerry Limited or its affiliates, and has no partnership with them.

Names and trademarks

Trademarks and rights associated with BlackBerry, BB10 and other company, product or service names belong to their respective owners. Names are used only for identification, description or compatibility references. They do not imply that those owners provide or endorse this project.

Feature changes and maintenance

The developer reserves the right to add, change, restrict or discontinue individual features based on product direction, available maintenance resources, device and system compatibility, security needs, Google Play policies or third-party service requirements. Material changes will be explained in release notes or an appropriate in-app notice; urgent security issues or platform requirements may require changes before notice.

This statement does not guarantee that every feature will remain available indefinitely or that every device and system version will be supported. Functionality and store descriptions must remain consistent. Changes involving data use or permissions remain subject to applicable disclosure and consent requirements. This statement does not exclude rights protected by applicable law, rights relating to purchased content or applicable Google Play refund and support rules.

Original content and scope of rights

The developer asserts rights only in original content that the developer lawfully owns, including copyrightable text, images, icons, animations, documentation and concrete interface expression. This notice does not claim ownership of BlackBerry or other third-party software, trademarks, fonts, documents, user data or materials. General ideas, functions, methods of operation, color schemes and independently developed similar features are not claimed as exclusive property. Check the actual license applicable to each item before determining its permitted uses.

Unauthorized copying, adaptation and resale

Where the developer owns rights in original content and no open-source license, other permission or legal exception allows the use, permission is required to reproduce, extract, translate, adapt, repackage, distribute, make available online, sell or sublicense it, or incorporate it into another app, website, product or promotional material. Merely changing a name, color, icon, signature or a small amount of text does not itself grant rights to other protected content. These restrictions do not apply to acts already permitted by MIT or another valid license.

Copyright notices and attribution

When copying or distributing licensed content, retain the copyright, license terms and other notices required by that license. Do not falsely claim another person's protected work as your own original creation. Renaming or re-signing an app does not automatically remove existing license obligations. This notice does not impose a general disclosure obligation for information that applicable law or the relevant license does not require you to disclose.

Brand identity and impersonation

Without appropriate permission, do not use the MFE Studio or BB10 Revival Launcher name, logo, store presentation or other identifiers in a way that misleadingly suggests your product, modified version, website, sales or support service is officially supplied, approved, partnered with or endorsed by this project. Do not falsify official provenance, signer identity or official security certification. Factual references, compatibility explanations, reviews and other lawful referential uses are not categorically prohibited. BlackBerry and other third-party names and logos remain subject to their respective rights holders.

MIT and third-party licenses take precedence

The project's current LICENSE applies the MIT License to the original code within its scope. It permits use, copying, modification, merging, publication, distribution, sublicensing and sale subject to its conditions, including retention of the required copyright and license notices. This page does not withdraw, narrow or replace lawfully obtained MIT rights or add payment or advance-permission requirements to uses MIT already permits. Third-party code, packages, materials and fonts retain their own licenses; this project cannot claim them as exclusive property. If another statement conflicts with an applicable open-source license, that license governs the content within its scope.

Ordinary use and legal exceptions

This notice does not obstruct installation, operation, backup, fair use, criticism, teaching, compatibility research or security research where permitted by applicable law or license. It does not broadly override legally permitted activities. Installing the app does not transfer all copyright to the user, but statutory and existing licensed rights are preserved. Whether a use infringes rights depends on the actual content, use, permissions and applicable law.

Commercial cooperation and separate agreements

Enquiries are welcome about product-use arrangements, manufacturer preinstallation, branding, custom features, source-code customization and maintenance. Separate agreements should define scope, devices or models, quantities, territories, term, fees, updates, support, source delivery, ownership of modifications and redistribution rights. Delivery of source code or a one-time payment does not by itself transfer copyright. Exclusive licensing or an assignment of rights must be expressly agreed and can cover only rights the supplier may lawfully grant. This describes a cooperation channel; it does not convert existing MIT code to a per-device or proprietary license or promise indefinite maintenance, a reply to every report or a fix for every issue.

Permission enquiries and rights notices

For additional permission or a rights concern, contact ethan9456@gmail.com with the content, source or URL, intended use and verifiable basis for the rights concerned. Commercial enquiries may include intended models, quantities and support needs. Do not send passwords, private keys or unnecessary personal data. The developer reviews matters according to available resources and circumstances, without guaranteeing individual replies or a fixed response time. Silence does not grant permission that did not already exist; existing permissions are unaffected. For a dispute, lawful remedies may include correcting attribution, stopping infringement or removing infringing content. This notice does not automatically determine liability or impose a preset penalty.