Pyli - Phone Portal Privacy Policy
Pyli normally delivers Android builds from a developer's own computer to invited phones. Each developer operates the server and chooses how phones reach it. The publisher does not receive those independent servers' builds or receipts. Craigish may separately offer an optional, clearly labelled reference-testing environment containing only a harmless demo, described below.
This policy covers the Windows companion app with its built-in server and the Android receiver app. It reflects the current source; it does not describe a future Mac or iOS version.
Android policy · Windows policy · Pyli website
Summary
A developer uploads an APK to the Pyli server running on their own Windows computer, creates a time-limited invitation, and chooses which paired phones may download each build. The phone reports delivery and install receipts back to that same server.
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.
The publisher receives no builds, pairing details, receipts or connection logs from independent developer servers. Choosing Craigish's optional reference server or sending support email does send the information described here to Craigish. The app has no advertising, analytics, crash-reporting or tracking components. Self-hosting is not a no-personal-data claim: device labels, invitation labels, build titles and release notes are free text that can identify people.
Who runs what
- The publisher (Craig Gauthier, Craigish) writes and distributes the software. The publisher does not operate normal developer delivery servers, but may operate the separate optional reference-testing environment described below. Direct support email is also covered below.
- The server operator is whoever runs the Pyli server — normally the developer on their own Windows computer. That operator controls the stored builds, pairing records and receipts, the machine's security and backups, and the route phones use to connect. A developer may instead point the app at an external relay; then that relay's operator controls server-side storage and handling under its own terms.
- The phone owner is the person invited to install builds. The Android app keeps a small local journal and talks only to the paired origin.
- Network providers. Phones usually reach the server through a route the operator chooses — for example a VPN, tunnel or reverse proxy such as Tailscale, Cloudflare Tunnel or ZeroTier. Those providers process connection information and may keep their own logs under their own privacy practices; Pyli neither selects nor controls them.
Windows, Android, the Microsoft Store and Google Play may process their own installation, update or diagnostic information under Microsoft's and Google's own privacy policies; this policy covers only the Pyli software.
Data the software processes
| Data | Purpose and location |
|---|---|
| Selected APK file, its size, SHA-256 checksum, package name, app label and version metadata | Verify and deliver the chosen build; the APK and metadata are stored on the configured server |
| Build title, release notes, recipient device IDs and timestamps | Identify the build and control which paired phones may access it; stored on the server |
| Device ID, chosen device label, optional model and platform, pairing and last-seen timestamps, active/revoked state | Pairing, device management and revocation; stored on the server. A label can identify a person |
| Invitation labels, hashed invitation codes, expiry and used/revoked state | Time-limited pairing; an invitation link carries the server origin plus an eight-character code that is single-use and expires after about 15 minutes |
| Delivery receipts: attempt IDs, status (downloaded, installing, installed, failed), timestamps, app-generated status detail such as an installer result or error, and the app's version | Show delivery and install progress to the developer; stored on the server. The phone owner does not enter free-text receipt messages |
| Pairing credentials | The server stores only hashes of invitation codes, device tokens and the developer credential. The Android app seals its device token with the Android Keystore; the Windows app encrypts developer credentials using OS-protected storage |
| Connection addresses | The server sees callers' network addresses and uses them for in-memory rate limiting (for example, pairing attempts); they are not written into the app's data records |
| Local settings | Configured origins, hosting mode, listener bind address, local-development and startup preferences; stored in a per-user private settings directory on the computer or in Android's private app storage on the phone |
The Android receiver does not access location, contacts, photos, media, browsing history, health or financial data, and it contains no advertising identifier, analytics or third-party SDK. It downloads the APKs the developer sent; it does not upload files from the phone.
Optional reference testing
When available to invited testers and store reviewers, Craigish's clearly labelled reference server serves only the harmless Pyli Review Demo APK, with no customer's builds or production accounts. Choosing it sends Craigish your device label, optional model/platform, server-issued device identifier and token hash, pairing and last-seen activity, and download/install receipts including generated installer results and app version. These records support the reference test without advertising, tracking or sale. Generated diagnostic results help investigate delivery failures. Google Play categorizes that troubleshooting purpose as Analytics; Pyli contains no analytics SDK. Use a non-personal label.
The reference website uses an eight-hour secure, HTTP-only sign-in cookie and creates ordinary 15-minute, single-use invitations. Separate browser sign-ins receive isolated sessions. At limited capacity, a session idle for at least 24 hours may be recycled to make room, removing its server records and access. This is not automatic deletion after 24 hours and does not uninstall apps or erase phone progress. Continuous availability is not guaranteed while the host may sleep or be offline.
Contact craigish.com@gmail.com for reference-record access, correction or deletion, identifying your reference label without sending tokens or passwords. Records on other operators' servers remain under their control. Tailscale Funnel provides the reference HTTPS route under its own policies. The reference sign-in page provides its own privacy notice; the Android policy also describes this optional environment.
How data is protected
- Windows keeps developer and server credentials in OS-protected storage and restricts the app's private state directory to the current Windows user and SYSTEM.
- Android keeps its delivery journal in backup-excluded private app storage and seals the device token with an Android Keystore AES key bound to the paired origin.
- The server persists only SHA-256 hashes of credentials and invitation codes, never the secrets themselves, and denies revoked devices and used or expired invitations.
- The phone-facing listener permits only pairing, device status, build listing/download and receipt routes; administration and upload routes are deliberately unreachable from it and bind locally.
- APKs and their metadata are not encrypted by the application at rest; the server operator is responsible for the machine, its disk protection and its backups.
These controls limit access through the app. They cannot prevent an invited phone owner from keeping or sharing a file they downloaded.
Retention and deletion
Current defaults retain up to ten ready builds per developer and expire builds 30 days after upload. Expired or over-limit builds lose phone access and their APK bytes are removed during upload-time sweeps; expiry is a delivery cutoff, not a guarantee of physical deletion at an exact moment. Deleting a build removes its APK file but keeps the marked metadata record.
Archiving a server build withdraws new phone downloads but retains its APK and metadata. Archived APKs count toward storage limits and are not removed by the ready-build retention sweep; the operator can delete them deliberately. Restoring requires an eligible retained payload. Archived and deleted records continue accepting permitted receipts from earlier downloads.
On Android, Archive and Remove affect only this phone's lists. Remove is reversible through Show hidden items; it does not delete downloaded files, history or server records. Active deliveries stay visible. Delete downloaded file removes the cached APK without uninstalling an app or deleting its delivery record. After a confirmed installation, the verified APK is retained in Android's cache for optional Reinstall, which uses Android's normal permission and approval process and records a new attempt. Android may clear cache. The journal holds up to 40 delivery attempts; eligible older completed attempts and cached files may be pruned when another attempt is added, while active attempts and unsent receipts are protected.
Pairing, invitation and receipt records remain in server state until the operator removes them; there is no complete-erasure tool in the current software. Local state, backups and log files require deliberate management by the server operator.
Revoking a phone or invitation stops future authorized access. It does not delete APKs already downloaded or installed on a phone, and it does not remove records already stored on the server. On the phone, "Disconnect this phone" abandons pending install sessions Pyli started, cancels its notifications, and removes the sealed pairing token, the Keystore key, cached partial downloads and the local delivery journal; uninstalling removes app-local data subject to the operating system's behavior. The server-side device record, receipts and other records are unaffected — ask the developer to revoke or remove them.
To request deletion of records held by a Pyli server, contact that server's operator. For questions the operator cannot answer, or about the software itself, contact the publisher below.
Your choices and support
Phone owners choose a device label at pairing; developers choose invitation labels, build titles and release notes. These are free text and can identify a person, so use only the detail you intend the other party to see. Receipts report only app-generated status detail — the phone sends no free-text message.
Optional new-build notifications are off by default. Your preference, seen-build identifiers and inbox hide/archive flags stay in private storage on this phone. Enabling notifications requests Android's notification permission on Android 13 or later. New-build alerts use local server polling, not a third-party push service, and show a generic count rather than build titles. Installation-approval reminders are separate. You can change notification access in Android Settings.
Support is handled by email. When you contact the publisher, he receives your email address and whatever the message contains, uses it to respond to and handle the request, and keeps the correspondence as long as needed for that purpose. Please do not send credentials, invitation codes, APKs or server records unless they are necessary for your request. You may use the same contact to ask for access to, correction of or deletion of your support correspondence; for personal data held by a Pyli server, the request is handled with that server's operator.
Pyli is a developer tool and is not directed to children.
When this policy changes, its effective date is updated and the page keeps matching the software's actual behavior.
Contact the publisher
Craig Gauthier (Craigish)
Email: craigish.com@gmail.com