HUXsentinel is a product of The Hat Protocol Inc., Nashville, Tennessee
HUXsentinel Privacy Policy 10/05/2026
Our privacy promise
HUXsentinel exists to protect people. That protection should never cost them their privacy. So we built HUXsentinel so that we do not need your data to protect you. It runs on your device, makes its decisions on your device, and encrypts anything it preserves before it leaves your device.
In plain terms:
● We never see your conversations. HUXsentinel evaluates them on the device. They are not sent to us or to anyone else.
● Nothing is recorded during ordinary use. Preservation begins only at a warning sign, and is deleted if the warning signs stop.
● We cannot read incident reports. Reports are encrypted on your device. We cannot read them, and we do not keep records of them.
● We hold no keys that could open a report, and we run no service that can open one.
● We do not sell, rent, or trade personal information. We show no ads, build no profiles, and run no tracking.
● Only what protection requires leaves the device: a content-free text alert and encrypted reports, sent only to the contact chosen at setup.
How Privacy by Design shapes HUXsentinel
Privacy by Design is a recognized framework of seven principles for building privacy into technology from the start. Here is how each one appears in HUXsentinel.
● Proactive, not reactive. HUXsentinel steps in before harm happens, and our architecture prevents privacy harm in the same way: data we never receive cannot be leaked, sold, demanded, or misused.
● Privacy as the default. Nothing is recorded during ordinary use. Alerts carry no content. You do not have to change a setting to be protected.
● Privacy embedded into design. Detection runs on the device. Reports are encrypted on the device. The relay that delivers alerts is built to store nothing. These are properties of the architecture, not promises layered on top.
● Full functionality. We do not trade safety for privacy. HUXsentinel protects the person on the device and preserves a record for authorities without exposing everyday life to anyone, including us.
● End-to-end security. From the first warning sign to delivery of a sealed report, protected material is either on the device, encrypted, or deleted. Preserved material that is not needed is deleted on the device.
● Visibility and transparency. HUXsentinel applies fixed, version-controlled rules, and each sealed report records the rules version used, so a result can be checked and reproduced. This policy states exactly what exists, where, and for how long (see the table below).
● Respect for the person. The person on the device stays at the center: alerts never reveal what was said or where, and the authority holder, not us, decides what happens next.
What exists, where it lives, and who can see it
This is a complete list of the information involved in HUXsentinel.
Conversations and on-screen activity
The protected device only
No one at The Hat Protocol
Not recorded during ordinary use
Shadow Buffer (preserved conversation and periodic screen images after a warning sign)
The protected device only
No one; not viewable on the device
Deleted if the warning signs stop; otherwise sealed into the reports below
Parent Report (CSIR #1)
Encrypted on the device; emailed encrypted to the alert contact
Only the alert contact, with the key from setup
As long as the alert contact keeps it
Sealed Agency Report (CSIR #2)
Encrypted on the device; emailed encrypted to the alert contact
Only designated law-enforcement or child-protection agencies
Device copy deleted after delivery is confirmed; the alert contact decides what to do with the delivered copy
Device location snapshot
Inside the encrypted reports only
Whoever can open the report
Same as the report
Alert contact (phone and/or email)
The protected device
Our relay and messaging providers, in transit only, to deliver a message
Until you change or remove it
Access code
The protected device, in non-readable form only
No one; we cannot recover it
Until changed
Relay rate counters
Our relay
Our systems only; no content, contact, or device identifier
Short-lived; automatically discarded
Delivery records at Twilio and SendGrid
Our messaging providers
The providers, to deliver the message
Deletion requested once delivery is confirmed
Messages you send us (email, contact form)
Our email inbox
The Hat Protocol team
Only as long as needed to respond
Payment information, if you buy a license
Our payment processor
The processor; we never see your full card number
As required by law and the processor
Your alert contact
At setup, you choose an alert contact, such as a parent, guardian, or trusted person, or yourself if you are an adult protecting your own device. Both a mobile number and an email address are required:
● Text message (SMS): the instant alert, so the contact knows within moments that something happened.
● Email: delivery of the encrypted incident reports. Reports are sent only by email, never by text message.
The contact's phone number and email address are stored on the protected device, not by us. When an alert or report is sent, our relay handles the contact only in transit to deliver it. The relay stores no message content, no contact information, and no report.
Alerts
Alerts state only that an incident occurred and when. For example: "HUXsentinel: Your child encountered a potentially dangerous conversation at 4:12 PM and has been disengaged from it. Reply STOP to opt out." Alerts never include conversation content, the type of threat, or the app or platform involved. HUXsentinel never sends your child's conversations anywhere. Alerts contain no content and are delivered by our messaging providers. We do not monitor, review, or keep them.
Incident reports
When HUXsentinel steps in, it seals two reports on the device, called CSIRs (Cryptographically Sealed Incident Reports):
● The Parent Report (CSIR #1) is encrypted to a key created for the alert contact at setup. Only that person can open it. It contains no images.
● The Sealed Agency Report (CSIR #2) is encrypted so that only designated law-enforcement or child-protection agencies can open it. Neither the alert contact, the person on the device, The Hat Protocol, nor our providers can open it.
Both reports are emailed to the alert contact in encrypted form. They pass through our relay and email provider only as encrypted files. Whether to forward the Sealed Agency Report, and to which agency, is the alert contact's decision alone. We offer options but never choose, and we never learn the choice. The person on the device cannot open either report.
Device location SnapShot for Jurisdiction
When a CSIR is sealed, HUXsentinel asks Windows for the device's approximate location once. Windows may consult Microsoft's location service to determine it, as it does for any app. Nothing is ever sent to The Hat Protocol.
The location is the device's approximate location, not the person's. It is read only when a report is sealed, never continuously. It is stored only inside the encrypted reports, and no address is recorded.
What we never do
● Sell, rent, or trade personal information, or share it for targeted advertising.
● Show advertising in HUXsentinel or use advertising or tracking technology in it.
● Collect analytics or usage data about what happens on a protected device.
● Read, review, or keep conversations, alerts, or reports.
● Use anyone's information to train artificial intelligence. HUXsentinel's detection uses fixed rules, not learned models.
● Hold a key, or run a service, that can open an incident report.
Requests from governments and law enforcement
We share information only with the device owner's consent or when required by law. Because reports are encrypted on the device and we hold no key to open them, we cannot disclose their contents to anyone, including in response to a legal demand. We hold no conversations, no location history, and no contact lists to disclose.
If we receive a legal demand for information about a licensee, we will review it for validity, narrow or challenge it where appropriate, and, where the law allows, notify the affected licensee before responding. [FOUNDER TO DECIDE: commit to publishing an annual transparency report of requests received.]
Children's privacy
HUXsentinel for children (KIDsafe) is installed and configured by a parent or legal guardian, who chooses the profile and gives consent at setup. We do not collect personal information from children. A child's conversations stay on the child's device, and any incident report is encrypted so that we cannot read it.
Parents and guardians may contact privacy@huxsentinel.com at any time with questions about their child's information. Because we do not hold a child's information, there is nothing on our systems to review or delete; reports and preserved material are under the parent's control on the device and in the delivered reports.
Text message (SMS) alerts
If you enable text alerts, you will receive safety alerts, verification messages, release codes, and notices that the alert contact was changed. Message frequency varies with incidents. Message and data rates may apply. Reply STOP to opt out at any time, or HELP for help, or email support@huxsentinel.com.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All of the categories of sharing described in this policy exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.
Service providers
We use a small number of providers, only for the purposes listed:
- Twilio: runs our alert relay and delivers text messages.
- Twilio SendGrid: delivers alert emails and encrypted reports.
- Payment processor: Stripe, processes license purchases.
- Website host: Porkbun hosts this website, built with Articulation.
Providers receive only what is needed to deliver each service and process it under their own privacy and security terms.
Website and cookies
This website sets only the cookies it needs to work: a session cookie, a session identifier, and a security token that protects our contact form. We use no analytics, advertising or tracking cookies. To display our typeface, your browser loads a font from Google Fonts, which means Google receives your browser’s request. Because we do not track visitors across websites, the site works the same way whether or not your browser sends a “Do Not Track” signal.
Security
● Reports are encrypted on the device before they leave it.
● Each report is sealed with cryptographic integrity checks, so any change can be detected.
● Access codes are stored only in a non-readable form.
● Provider keys are held by our relay, never on a protected device.
● We maintain a written information security program, reviewed at least once a year.
No system is perfectly secure. Our design limits what could ever be exposed, because we do not hold the information in the first place.
Your rights and choices
● Change or remove the alert contact; the previous contact is notified of the change.
● Reply STOP to any text alert to stop text messages. Because alerts are part of how HUXsentinel protects the device, we recommend updating the alert contact rather than stopping alerts.
● Uninstall HUXsentinel at any time.
● Ask what information we hold about you, or ask us to correct or delete it, by emailing privacy@huxsentinel.com. We will respond within 45 days. If we decline a request, you may appeal by replying to our response, and we will answer the appeal within 60 days.
We will not treat you differently for exercising any privacy right.
Changes to this policy
If we change this policy, we will post the new version here with a new effective date. If a change would reduce your privacy, we will give at least 30 days' notice before it takes effect.
Contact us
The Hat Protocol Inc., 41 Peabody St Nashville, TN 37210
Privacy questions and requests: privacy@huxsentinel.com