Portly Privacy Policy
Effective August 2, 2026
Website analytics
The Portly website uses our self-hosted analytics service to measure anonymous page views and aggregate daily visitor counts. It uses no cookies, advertising profiles, session replay, or stable visitor identifier.
Direct app analytics
The direct-download Portly app sends two anonymous usage events to our self-hosted analytics service: one when an installation is first seen and one when the app launches. The event payload contains only the Portly version, macOS version, and processor architecture.
Like any web request, the source IP address and User-Agent reach the analytics server and are processed to calculate aggregate visitor counts. Portly sends no cookie or stable device identifier.
Portly does not send names, email addresses, device identifiers, project names, paths, commands, environment variables, server logs, or file contents. Analytics uses no cookies, advertising profiles, session replay, or third-party analytics provider.
App Store companion
Portly Companion does not collect, store, sell, or transmit personal data to the developer or to third parties. It does not include the anonymous analytics used by the direct-download Portly app.
Local communication
The app communicates only with an existing Portly service running on your Mac through the loopback address 127.0.0.1. It uses that local connection to display server status and send start, stop, and restart requests. These requests do not leave your Mac.
Local files
Portly Companion is sandboxed and does not read project files. The separately installed Portly service may keep its configuration and server logs locally on your Mac. Those files are controlled by you and are not uploaded by Portly Companion.
Support
For privacy or support questions, open an issue in the public Portly repository on GitHub.