TailChaser← Back home

Privacy

Last updated: 20 November 2026

This policy covers tailchaser.app and the TailChaser software itself. The site has nothing to collect; the software talks only to what you configure it to talk to.

Who we are

TailChaser is made by RF.Guru (rf.guru). RF.Guru™ is a registered trademark of Dielectricum. Questions about this policy: info@rf.guru.

This website

tailchaser.app has no accounts, no forms, no analytics, no advertising and no cookies. It doesn't load third-party scripts or fonts.

Like any web server, the hosting platform (Google Cloud Run) keeps short-lived request logs — IP address, time, the page requested and your browser's user agent — to operate and protect the service. We don't use them to identify or profile visitors.

The source and the issue tracker are on GitHub, which serves them under its own privacy statement.

The software

TailChaser has no account with us and no telemetry: a node never contacts RF.Guru. It connects to the reflector you name in its configuration, and to nothing else unless you turn that on.

With its login the node sends the reflector what you filled in about the station — callsign, place, sysop, position, frequencies and tones — as SvxLink nodes do, and the reflector's dashboards may show it. What is said on the talkgroup goes to the reflector as audio: that is its job. The node makes no recordings.

Spoken announcements are optional. When they are on, the text you wrote is sent once a day to the voice service you chose, with your token for it, over https only.

A tailchaser-sdrreceiver connects to the web SDR you name, as one of its listeners. Its owner sees that connection, with your address and the name you gave it, as with any listener.

Listening in is off unless you turn it on. When it is on, whoever can open the status page can hear the receiver and what is transmitted, in the browser, without a login.

The status page on port 8080 is read-only and has no login: anyone who can reach that port on your network can read it. The admin portal and the API on the same port ask for a password or a key, of which the node keeps only a hash, but they are plain HTTP: keep them on your own network or a VPN. All of it is readable in the source.

Changes

When this policy changes, the date at the top changes with it.