Pyli - Phone Portal · Android

Pyli Android Privacy Policy

Effective date:
Publisher: Craig Gauthier, publishing as Craigish

This policy covers the Android side of Pyli's private Android build-delivery workflow. Pyli requires the Android companion and a developer-operated server, usually on Windows, plus independently configured secure connectivity.

Who handles your data

Craig Gauthier, publishing as Craigish, distributes Pyli. Normal delivery uses a developer-operated server, not a central publisher service. The publisher receives no builds, pairing details or delivery receipts from those independent servers. The server operator is the developer who runs the server, or an external relay operator the developer chooses. That operator controls server records, backups and connectivity. The optional, separate reference-testing environment below is operated by Craigish.

Phones usually reach the server through an independently configured VPN, tunnel or reverse proxy such as Tailscale, Cloudflare Tunnel or ZeroTier. Those providers may process network information and logs under their own practices. Windows, Android, Microsoft Store and Google Play may process installation, update or diagnostic information under their own policies. This policy covers Pyli, not those services.

What the Android app processes

Pyli connects to the developer's configured server address using a fresh eight-character, single-use invitation that expires after about 15 minutes. It receives a device ID and access token and sends the chosen phone label, optional model/platform information, last-seen requests, and app-generated delivery or installation receipts to that same server. A label can identify a person.

The app downloads the builds offered to this phone: APK bytes, file size and SHA-256, package/app label and version, build title, release notes and timestamps. It stores this information, local delivery attempts, queued receipts, seen-build identifiers and inbox/notification preferences in private app storage. Receipts include attempt IDs, status, timestamps, app version and generated error or installer detail; you do not enter free-text receipt messages.

The phone does not upload your personal files or access location, contacts, photos, media, browsing history, health or financial data. It does not use an advertising identifier or third-party SDK. Android checks package signatures and requires your approval to install; installation-source permission may be required. Play builds cannot update Pyli itself through its own delivery inbox.

To offer Open app, Pyli checks locally whether Android can launch the specific delivered package. This can also happen from delivery history. Pyli does not inventory installed apps. Install outcomes still go to your configured server.

Optional notifications

New-build notifications are off by default. Enabling them saves your preference on this phone and, on Android 13 or later, requests notification permission. Alerts are generated locally from server polling, not a third-party push service, and show a generic new-build count rather than titles. Android scheduling and permission settings affect delivery; alerts are not guaranteed to be instant. Installation-approval reminders are separate. Notifications can be controlled in the app and Android Settings.

Connections and protection

The phone talks only to its configured paired origin. The publisher receives this traffic only if you choose Craigish's reference-testing server. Production builds require HTTPS and disable cleartext traffic. The delivery journal is in backup-excluded private storage. The access token is encrypted using Android Keystore with the paired origin bound to it. APK downloads are checked for size and SHA-256 but are not encrypted by Pyli at rest. Protect your phone and share files only with permission.

Optional reference testing

When made available to invited testers and store reviewers, Craigish's clearly labelled reference server contains only the harmless Pyli Review Demo APK. It has no customer's builds or production accounts. You can use this environment without running a Windows server or joining a private VPN; normal delivery continues to use your chosen developer's server.

If you choose the reference server, Craigish receives your chosen device label, optional model/platform information, server-issued device identifier and token hash, pairing and last-seen activity, and download/install receipts, including generated installer results and app version. Use a non-personal device label. These records operate and troubleshoot the reference test; they are not used for advertising, tracking or sale. Generated diagnostic results help investigate delivery failures. Google Play categorizes that troubleshooting purpose as Analytics; Pyli contains no analytics SDK.

The reference website uses an eight-hour, secure, HTTP-only sign-in cookie to authorize its panel and create ordinary 15-minute, single-use invitations. Separate browser sign-ins receive isolated reference sessions. Sessions have limited capacity: an inactive slot may be recycled after at least 24 hours without observed activity when capacity is needed. Recycling removes that session's server records and access; it does not uninstall apps or erase phone progress. This is not a promise that all records are automatically deleted after 24 hours. The host may sleep or be offline, so continuous availability is not guaranteed.

For reference-record access, correction or deletion, contact craigish.com@gmail.com and identify your reference device label without sending access tokens or passwords. Craigish cannot delete records on other operators' servers. Tailscale Funnel provides the reference server's HTTPS route and processes connectivity under its own policies. The reference sign-in page links to its environment-specific privacy notice before pairing.

Retention, cleanup and reinstall

Archive and Remove affect only this phone's lists. Remove is reversible through Show hidden items and does not delete cached files, delivery history or server records. Active deliveries and attempts with unsent receipts remain visible. Delete downloaded file removes the local APK without uninstalling an app or erasing the delivery record.

After a confirmed installation, Pyli retains the verified APK in Android's cache for optional Reinstall. Reinstall uses Android's normal permission and approval process and creates a new attempt; an earlier server receipt is not overwritten. If the file is gone, another download is possible only while the server still offers the build. Android may clear cached files. The local journal holds up to 40 attempts; eligible older completed attempts and their cached APKs may be pruned when another attempt is added. Active attempts and pending receipts are protected.

Disconnect this phone abandons Pyli's pending install sessions, cancels its notifications, removes the sealed token and Keystore key, clears cached delivery files and the local journal. Uninstalling removes app-local data subject to Android's behavior. Neither action removes apps already installed, nor the server's device records or receipts. Server withdrawal or revocation also cannot erase previously downloaded or installed apps. Contact the server operator for server-side deletion.

Your choices and support

Use device labels, build titles and release notes that contain only information you intend the developer and invited recipients to see. Pyli has no advertising, analytics, crash-reporting or tracking SDK, sells no personal data, and has no donation or advertising integration in this release. Pyli is a developer tool and is not directed to children.

For server-record access, correction or deletion, contact that server's operator. For software questions or support correspondence, contact Craig Gauthier at craigish.com@gmail.com. Email support gives the publisher your email address and whatever you send; correspondence is used to handle your request and retained as long as needed for that purpose. The same address accepts requests to access, correct or delete support correspondence. Do not send credentials, invitation codes, APKs or server records unless necessary.

When this policy changes, its effective date is updated to match the software's actual behavior.