Pyli Windows Privacy Policy
This policy covers the Windows 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. Craigish may separately offer an optional Android reference-testing server containing only a harmless demo; its records and choices are described in the Android reference-testing notice. It has no access to this Windows server's builds or records.
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 Windows app and server process
The companion runs a server on the developer's own computer, or connects to a configured external relay. Selected APK files, sizes, SHA-256 checksums, package/app labels and versions, build titles, release notes, recipient device IDs and timestamps are stored on that server to identify builds and restrict downloads to selected phones. The operator sees phone-generated delivery and installation receipts, including attempt IDs, status, timestamps, app version and generated installer or error detail.
The server stores device IDs, chosen device labels, optional model/platform information, pairing and last-seen timestamps and active/revoked status. Invitations have labels, hashed codes, expiry and used/revoked state. An invitation link contains the server origin and an eight-character single-use code that expires after about 15 minutes. Free-text labels and notes may identify people. Local settings include hosting mode, origins, bind address, local-development and startup preferences. Network addresses are used for in-memory rate limiting, not persisted in the app's data records.
Connections, sharing and protection
Builds travel from the developer to the configured server and selected phones; receipts return to that server. Pyli sends none of this information to the publisher. Build titles and notes travel in upload request parameters, so consider your proxy or tunnel's logging practices. Production phone connections require HTTPS. An explicit development setting permits HTTP to loopback or private-network addresses for testing.
Windows encrypts credentials with OS-protected storage and restricts private state to the current Windows user and SYSTEM. The server stores hashes of invitation codes, device tokens and developer credentials, denies revoked credentials and used/expired invitations, and separates phone-facing routes from local administration/upload routes. APKs and metadata are not encrypted by Pyli at rest; the operator manages disk protection, machine security and backups. These protections cannot prevent invited recipients from keeping or sharing downloaded files.
Retention, archive and deletion
Current defaults retain up to ten ready builds per developer and expire builds 30 days after upload. Expired or excess ready builds lose phone access and their APKs are removed during upload-time sweeps; expiry is an access cutoff, not a guarantee of physical deletion at an exact moment.
Archive withdraws new downloads but retains the server APK, metadata and receipts. Archived APKs count toward storage limits and are not removed by the ready-build retention sweep; delete them deliberately when no longer needed. Restore requires an eligible retained payload and available capacity. Delete removes the APK while preserving marked metadata and receipts. Permitted receipts from earlier downloads remain accepted after archive or deletion.
Pairing, invitation and receipt records remain until managed by the operator; there is no complete-erasure tool. Local files, backups and logs require deliberate operator management. Revoking a device or invitation stops future authorized access but does not erase server history or files and apps already on phones. Removing or uninstalling the companion does not guarantee erasure of its server records or backups. Phone-only archive/hide/cache controls do not delete server records. Ask the operator about retention and 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.