Frequently asked questions

PALEOS.IO builds focused, local-first Android tools for people who want more agency over their data, attention, creative workflow, and device behavior. Each app is designed around a specific job rather than an attention-extraction business model.

Individual features, prerequisites, and compatibility differ by app and device. Review the relevant release page and setup material before relying on an advanced feature.

PALEOS.IO aims for core value that remains available without a constant account or cloud connection. Whether a particular release works entirely offline depends on its documented feature set and should be checked on that release page.

A feature that intentionally contacts a network service is not an offline feature while it is operating. Read each app’s current data and network disclosure for its stated behavior.

Permissions and data use should be limited to the feature being explained. Review the app’s release notes, manifest or permissions disclosure, and privacy information for the version you plan to install.

PALEOS.IO does not use advertising analytics, behavioral tracking, or engagement loops on this website. App-specific statements must be read as release-specific disclosures rather than as a promise about every Android device, export path, or future update.

Some optional advanced controls may need a separate Shizuku authorization to request Android operations that are not ordinarily available to the app. A release should identify the feature, prerequisite, intended operation, and useful baseline without elevated access.

Do not enable a privilege path merely to force a result. Confirm that you own or are authorized to administer the device, read the current instructions, and keep a recovery path.

Shizuku is an independently maintained open-source Android project. It can let an app make requests through the privilege context of a Shizuku service started with root or ADB-derived access chosen by the user.

Shizuku is not automatically root access, does not make a user-installed APK a privileged system app, and may provide different capabilities on different Android versions and devices.

ADB and wireless debugging are advanced Android features. Authorize only computers and networks you trust, review Android’s current instructions, and revoke debugging authorizations when they are no longer needed.

These features can change the security posture of a device. PALEOS.IO does not describe them as risk-free or universally compatible.

For Android 11 and later, Shizuku documents a wireless-debugging setup path. For unrooted Android 10 and earlier, its documented computer and ADB path generally applies. Follow the current official Shizuku setup guide because settings labels and supported behavior can differ by Android version and manufacturer.

After a reboot, Shizuku normally needs to be started again before a feature that depends on it can run. Whether any particular device setting remains applied is feature-, device-, firmware-, and OS-specific; verify it after restart and use the app’s restore guidance where available.

Availability, effect, and persistence can depend on the feature, Android version, device maker, firmware, and the privilege mode currently available. A release page should identify supported devices or known limitations when that evidence exists.

Do not assume a setting was applied or retained. Verify the visible device state and keep a way to restore the prior configuration.

Start from the relevant PALEOS.IO release page and follow its stated source or repository link. Before installing a direct release, compare the published package name, version, SHA-256 checksum, and signing-certificate fingerprint when those identifiers are provided.

Do not install a file whose stated identity information does not match, and do not treat a link or listing as a certification of third-party software. Android installation, permissions, and compatibility rules still apply.

Standard Android installation is the supported default. A user-installed APK does not become a privileged system app merely because a different installer is selected, and an installer cannot grant protected permissions that Android does not permit.

If a future PALEOS.IO release requires a named helper, its release page will explain the narrow, reproducible purpose, identity, permissions, update behavior, and recovery path.

Read the PALEOS.IO Privacy Policy for website and account practices, and use the relevant app release page for version-specific product information. External repositories, app stores, and linked services have their own terms, privacy practices, and security responsibilities.

Use the PALEOS.IO contact route for support, responsible security reports, or editorial notes. Do not send passwords, recovery codes, private keys, or other secrets.