Privacy policy

Last updated 23 October 2026

Sipper is a phone app made by Ben Hybert. This page describes data handled by the apps, optional management service, browser extension and sipper.dev.

The short version

Standalone calling needs no Sipper account. Personal SIP details, contacts, call history and recordings stay in the app’s local storage, apart from optional iCloud sync. Signing in to a managed organisation uses the Sipper service and the information described below. Sipper contains no advertising or third-party analytics.

What the app stores on your computer

• Your SIP accounts, profiles, contacts, call history and settings, saved as files in Sipper's folder on your computer.
• Your SIP passwords. On a Mac they're saved in the macOS Keychain. On Windows they're saved in Sipper's folder, encrypted with Windows data protection so only your Windows account can read them.
• Call recordings, if you make any, saved in the folder you choose in Settings › Recording.
• A log of recent SIP activity for troubleshooting, kept in memory while Sipper is open. It's only written to a file if you choose Save in Settings › Diagnostics.

You can delete accounts, contacts, history and recordings in the app at any time. Deleting an account also removes its stored password.

Who the app connects to

• The SIP servers of the accounts you add, to register them, make and receive calls, and check for voicemail.
• For call audio, your provider's media servers or, when a call is set up that way, the other party's phone directly.
• A STUN server, only if you enter one.

These servers belong to your phone provider or organisation. Their own privacy policies cover the calls and call records they keep.

Managed organisations

If you sign in to a managed organisation, Sipper stores your name, email, membership, assigned licences and calling configuration. Authentication and device records include sign-in and request times, IP addresses, app and operating-system versions, configuration results and reported registration status. Your organisation’s administrators can inspect their management records; platform owners can administer the service.

Managed SIP credentials are encrypted on the service. Direct provisioning also delivers them to the app’s protected storage. Gateway mode keeps upstream credentials on the service and carries calls through Sipper’s gateway. Personal accounts and local recordings are not uploaded by managed provisioning.

Company directories, manual availability, Do Not Disturb and any colleague status you choose to share use the management service. Conversation content is available to its participants and encrypted in server storage; it is not end-to-end encrypted. Meeting media passes through the configured meeting service. Sipper does not provide server-side meeting recording.

When enabled, mobile notifications register a device token with Sipper and use Apple or Google delivery services. Message alerts contain a generic notice and opaque references, not message text. Message and call metadata expire under the service’s retention settings; backups have their own retention. Revoking a device stops new managed access but does not erase all account, audit or backup records.

iCloud sync

The Mac version you download from this site doesn't include iCloud sync, and the Windows version has no sync at all. If you build Sipper yourself with iCloud enabled and turn sync on, your profiles, accounts and contacts, plus your call history if you include it, are stored in Sipper's private container in your iCloud account, and your SIP passwords are synced by iCloud Keychain. Apple holds that data under its own terms; the developer can't access it. Recordings and settings specific to each Mac are never synced.

Microphone and notifications

Sipper uses the microphone only so the other side of a call can hear you. If you allow notifications, it uses them for incoming and missed calls. You can change both in System Settings on a Mac or in Settings on Windows.

Recording calls

Recording laws differ between countries, and many require you to tell the other person that a call is being recorded. You are responsible for following the law where you and the people you call are.

The browser extension

• It runs only when you click its toolbar button, and reads only the tab that's open at the time.
• On a FusionPBX extensions list, it opens the pages of the extensions you tick, on the same site, using the login you already have.
• It passes account details to the Sipper app on your computer and nowhere else.
• It remembers the last server, port and transport you chose for each phone system, in your browser's local storage. It doesn't store passwords.

This website

The public information pages use no analytics, third-party scripts, web fonts or advertising cookies. Hosting and network providers process technical information such as IP addresses to deliver requests. Management uses authentication cookies and stores security and administrative activity. Downloads and source code linked to GitHub are covered by the GitHub General Privacy Statement.

If you ask for support

Support is handled through GitHub issues, which are public. Do not include passwords, account exports, private server addresses or unredacted call logs. GitHub handles your issue and account information under its own privacy policy.

Changes to this policy

If this policy changes, the new version will be posted on this page with a new date.

Contact

Ben Hybert
Sipper support on GitHub