# Privacy Policy

Last updated: 15 November 2026

CafeSignal is designed for a focused macOS job: check suitable cafe or guest Wi-Fi, verify whether access works, and handle simple captive portals with best effort while keeping data use narrow and understandable. CafeSignal is made by Duy Bui, an independent developer in Vietnam.

## Data used on device

CafeSignal reads local Wi-Fi state available on your Mac, including whether Wi-Fi is on, the current network name, nearby network names, security type, signal quality, and whether normal internet access appears available. This is used to rank cafe or guest Wi-Fi candidates and decide whether a connection, portal check, or work-readiness check may help.

## Permissions

CafeSignal may request Location permission because macOS uses that permission to reveal nearby Wi-Fi names and the current Wi-Fi network. You can revoke Location permission in macOS System Settings. Portal Autofill, Auto-Submit Simple Forms, and Auto Updates can be changed from the desktop app settings.

## Portal Assistant

If a cafe or guest network shows a captive portal, CafeSignal may open Portal Assistant and, when you enable it, fill simple public portal fields such as name or birth year. If Auto-Submit Simple Forms is enabled, those fields may be submitted to the network operator's portal. CafeSignal stops for passwords, accounts, payments, vouchers, CAPTCHA, OTP, member-only steps, and unclear required fields.

## Local storage

Portal Autofill settings and the anonymous analytics preference are stored on your Mac. Optional portal profile fields are stored in the macOS Keychain for this device. You can edit or clear those fields in the app's Form Values tab (name and birth year also in Portal Assistant). Routine Wi-Fi scan details are used for app functionality and are not kept as a server-side Wi-Fi history by CafeSignal.

## Feedback and diagnostics

When you choose Send Feedback, CafeSignal sends your message, optional reply email, privacy-safe diagnostics, and any screenshot you explicitly attach. Diagnostics include app/macOS versions and coarse connection outcomes, but exclude Wi-Fi names, BSSIDs, portal URLs, form values, IP/location data, and logs. Feedback is delivered by email through Resend and retained only as needed to respond and improve CafeSignal.

## Not collected

CafeSignal does not collect browsing history, Wi-Fi passwords, portal account credentials, payment details, personal documents, location history, advertising identifiers, or the contents of pages you visit after connecting.

## Sharing and third parties

The CafeSignal Mac app does not use advertising SDKs or cross-app tracking. If Anonymous Analytics is enabled, the app sends coarse usage events such as app launch, setting changes, connection-state category, portal automation outcome, supported field categories (for example name, email, or terms), aggregate field counts, blocker category, verification result, manual handoff, app version, build number, macOS version, locale, and an anonymous installation ID. These events are forwarded to Google Analytics and to PostHog (hosted in the EU). From version 1.1, the same switch also sends crash reports and update errors to PostHog: the error type, where in CafeSignal's own code it happened, the app version and channel (stable or beta), and basic device details such as macOS version, Mac model, screen size, language, and time zone. Crash reports pass through CafeSignal's server, which does not forward your IP address, and PostHog does not estimate a location from them. The app does not send Wi-Fi names, portal URLs, field labels, form values, browsing history, passwords, payment details, or location history.

## Website analytics

The public website (cafesignal.com) uses PostHog (hosted in the EU) to count page views and clicks on the download button. It runs through the website's own address, keeps its data in memory for the current page only, and sets no cookies and no other storage on your device, so it cannot recognise you on a later visit. PostHog receives ordinary request information such as your IP address and browser details and uses the IP address to estimate a rough location (country and city); it is not used for advertising. The website no longer uses Google Analytics. Payments and tips are handled on third-party sites (such as GitHub Sponsors) under their own privacy policies.

## Other services

Network operators may receive information you submit through their captive portal. Hosting, analytics, and update services (Cloudflare, and GitHub for older app versions) may receive ordinary request information such as IP address, user agent, requested URL, and timestamp when the app or website checks for releases or downloads.

## Updates

Direct-download builds use Sparkle to check for updates through the public appcast URL and download them from downloads.cafesignal.com. From version 1.1, each check includes the app's anonymous install ID (shown as "Mac ID" in the About tab) so that Macs which joined the beta can be offered beta builds; it is a random value, not linked to you, your Mac's hardware, or any network. A future Mac App Store build would use the Mac App Store update system instead of Sparkle. Auto Updates can be disabled from the desktop app settings when available.

## Retention and deletion

Local settings remain on your Mac until you change them, clear them, or remove the app data. Support emails are kept only as long as needed to respond and maintain support records. You can request deletion of support communications or any personal data CafeSignal controls by emailing support.

## Contact

For privacy questions, data deletion requests, or support requests, email [team@cafesignal.com](mailto:team@cafesignal.com).
