Kylone · privacy
Privacy
A headend handles other people's content all day, so the question of what it tells its maker deserves a precise answer. This page gives it, function by function, for the unit, for the central portal and for this website, and says who to write to.
October 2026. This page describes Kylone Headend v4.2 units and the services around them. The licence agreement refers to it for the data collected under its licence validation clause.
1. Who is responsible
Kylone Inc., 1349 W Peachtree Street NW, Suite 1910, PMB 658, Atlanta, GA 30309, USA, is the controller of the data described here. Write to info@kylone.com for anything on this page. Kylone does not sell personal data and does not pass it to third parties for their own purposes; providers that host Kylone's servers process data only on Kylone's behalf.
2. What a headend unit sends, and does not send
A unit works without any connection to Kylone. Every contact listed below is tied to one function. Two of them serve the licence and the branding of the unit and carry the installed version and the licensed features only; every other contact has a switch. The unit sends no usage statistics, no logs and no credentials to Kylone: the statistics reporting of earlier versions was removed in version 4.2.0. The content the unit receives and delivers, the channel line-up, the programme guide, the viewers and their devices never leave the unit to Kylone, through any of these channels.
| Function | What is sent | When | Switch |
|---|---|---|---|
| Licence activation | The unit's registration key, which is derived from hardware identifiers of the server, and in return the licence key. Kylone records the registration key, the licence key, the product and the customer it belongs to. | Once, by hand: you send the registration key, Kylone answers. Automatically after a reinstall of a unit that was activated before. | Not applicable: the exchange serves the activation only and carries nothing else. |
| Licence validation and branding | The installed version and which licensed features are in use, as the licence agreement states; the unit downloads its branding bundle. Nothing about content or viewers. | Periodically, from the first activation, whether or not remote support is allowed. The answer can carry one instruction: that Kylone has deactivated the licence of this unit (expired, evaluation ended without a purchase, or a breach of the licence agreement), on which the unit removes its licence and stops delivering. | No switch: the exchange carries the version and the licensed features only. A unit that cannot reach Kylone keeps working as it is. |
| Remote access | An IPsec tunnel from the unit to Kylone's remote access network, inside which the customer reaches their own units and Kylone engineers reach a unit at the customer's request. The tunnel carries management sessions, not content. | Only while the switch is on. | System Settings, "Allow Remote Support Connection"; off stops the tunnel service on the unit. |
| Software updates | Plain downloads of version information and packages from Kylone's download server. The request carries no identifier of the unit; the server sees the address it comes from, as any web server does. | When you check for or install an update. | Not applicable; nothing is sent. |
| Channel logo pack | A plain download of the logo pack from Kylone's tool server. No identifier. | When you fetch logos. | Not applicable. |
| Time and public address at boot | Time from the public NTP pool, and one request to Kylone's tool server that answers with the public address the unit is seen from, which the unit keeps locally for its network setup. | At boot, when the unit is online. | Follows the unit's online state. |
| Operating system updates | Package downloads from the distribution's repositories or your own mirror. Not Kylone's servers. | Manual update, or daily with the automatic security updates switch on. | System Settings. |
| Monitoring and alerts | SNMP, the metrics endpoint and the update emails go to the operator's own systems and addresses, never to Kylone. | As configured by the operator. | The operator's configuration. |
An isolated unit without any of these connections runs for the life of its licence. Nothing on the unit degrades, expires or reports because Kylone cannot be reached.
3. The central portal
Kylone keeps a central portal for the customers who want it: branding of their units, a private remote access network of their own units, automatic re-activation. A customer account is created there only for those purposes and holds the customer's name, the contact details of the people who operate the account, the units with their registration and licence keys, product and version, and the logos and names the customer provided for branding. The customer reaches their own account and their own units with their own login; nobody else's units are visible to them. The account and its data are kept while the customer uses the services and are deleted on the customer's request.
4. This website
- No analytics, no advertising, no tracking cookies. The site sets no cookies of its own and loads no third-party analytics or social media scripts. Scripts and fonts are served from kylone.com; two compatibility scripts are fetched from a public CDN only by Internet Explorer 8 and older.
- The contact form sends your name, email address, subject and message as an email to Kylone and stores nothing else. The email is kept as long as the conversation it belongs to needs it.
- Server logs. The web server keeps the usual access logs, address, time and page, for operation and security, and they are not used to profile visitors.
- Links to GitHub and to social networks lead to those services and their own policies.
5. Your rights and how to use them
You can ask what Kylone holds about you or your organisation, have it corrected or deleted, and object to a use of it, by writing to info@kylone.com. A request about a unit or a central account is answered to the account's contact, so that nobody else can act on your data. Where the law of your country gives you further rights, they apply as written there.
Changes to this page are dated at the top. A change that affects what a unit sends comes with the release that makes it, and is noted in the release notes.