Privacy.

Your installation's record

Every copy of Hangly registers itself with its developer, in Google Firebase, so the developer can see how many people use Hangly, where, on what, and for how long. It is part of using Hangly: there is no switch to turn it off. The record holds:

• An installation ID: a random identifier made the first time Hangly runs. It never changes and is used for nothing else.
• Your nickname: what you typed when Hangly asked what to call you, never your account or computer name. You can change it in Customize → Appearance.
• Your city, region and country, worked out from your internet connection's address by Hangly's server. The address itself is never stored or logged, and nothing more exact than a city is kept.
• Your platform, processor and versions: of macOS or Windows, and of Hangly, including the version it started on and when it updated.
• When Hangly was first installed and last used, how many days it has been used, and how many times it has crashed.

Nothing is sent before you give a nickname. After that, the record is updated when something changes and at most once a day to say Hangly is still in use. On Windows, uninstalling sends one last update marking the record uninstalled. Customize → About → Installation shows what your copy holds. To have your record deleted, ask Sharan through the contact page.

Usage events

Hangly reports a few events to Google Analytics (Firebase Analytics on macOS), tagged with the installation ID and nothing else, never your nickname or city: that Hangly started or was updated, which charm and rope you choose (a charm you made yourself is reported only as “custom”), that you finished the welcome or opened the support page, that Hangly ran today, how an update went, and whether a card under the charm was shown, opened or dismissed (by its ID, never its text). Nothing else you do in Hangly is reported.

Crash reports

When Hangly crashes, it sends the error and where in the code it happened, with the app and system versions and the installation ID: through Firebase Crashlytics on macOS, and to Hangly's Firebase project on Windows, where your user folder and account name are removed from the text first.

Updates and announcements

About every hour Hangly checks for a new version: on macOS by fetching its update feed from this site, on Windows by asking GitHub, where its releases are published. The check carries nothing about you or your copy; like any web request, it comes with an IP address. Every Mac update is signed and checked against a key built into the app before it installs.

Every fifteen minutes or so Hangly also asks its server whether there is news to show under the charm, such as a new collection. That request carries only your platform: no installation ID, nickname or version.

Never collected

• Your email address, your account name or your computer's name.
• Your IP address, or any location more exact than your city.
• Images you turn into charms, or anything about them. They stay on your computer.
• Where your charm sits on screen, keystrokes, screen contents, or what you do in other apps.

Hangly shows no advertising, sells no data, and makes no network requests beyond the ones above.

Permissions

Hangly asks for no special permissions on either platform. It draws its own transparent window, and clicks pass through it everywhere but the charm.

Questions

If this page does not answer a privacy question, ask Sharan through the contact page. This page is updated before Hangly changes what it sends, not after.