Privacy Policy
HeatSentry collects what we say we collect. We do not sell your data.
Information we collect
Today. If you join our waitlist at heatsentry-os.polsia.app/#waitlist, we collect the email address you submit, the optional name and use-case (parent / pet owner / fleet operator / other) you include, and the timestamp of your submission. That is the full set of fields on the form.
When the device ships. Once you have a HeatSentry unit installed in a vehicle, the device will collect:
- Cabin temperature readings and occupant-detection readings (movement, weight, CO2) sampled while the vehicle is parked.
- The emergency-contact list that the device owner designates in the setup flow — names and phone numbers you add yourself.
- The vehicle's last-known location at the moment an alert is dispatched, included in the message we send to your contacts and (if the chain escalates fully) to emergency services.
We do not collect trip history, driving behavior, or anything else while the vehicle is in motion. The device sleeps while you drive.
How we use it
The waitlist email is used to notify you when HeatSentry ships to your area, and to share pre-launch product updates relevant to your selected use case (roughly a handful of emails per year — not a marketing drip).
Future SMS study data is used for safety research only. It is never marketed, never sold, and never used to target you with third-party advertising. Aggregated, de-identified findings may inform our product design and our published safety research. An individual record is never resold or shared in identifiable form.
The third-party-data-sale stance. We do not sell your data. We do not share it with data brokers. We do not share it with advertisers. Cellular carrier traffic and emergency-services dispatch are operational transfers — they are how the alert chain actually works — not a sale.
SMS study data handling
The SMS study will only send messages to numbers the device owner has explicitly added through the setup flow. HeatSentry does not import contacts, does not scrape address books, and does not auto-add anyone.
Every study message includes clear opt-out instructions and a per-message STOP key. An inbound STOP:
- Removes that number from your HeatSentry contact graph immediately.
- Triggers a one-tap confirmation back to the device owner so they know the contact has opted out.
- Creates a suppression record on our side so we will not re-add the number without fresh, explicit consent from that contact.
The suppression record is the only thing we retain for an opted-out contact — we keep it so we never accidentally re-add them, but it is not used for any other purpose.
Sharing and sale of data
We do not sell your personal information to anyone. We do not share it with data brokers. We do not share it with advertising networks, attribution platforms, or social-media pixels.
The limited transfers that do happen are operational, not commercial:
- Cellular carriers — required to deliver the SMS and call alerts in the escalation chain.
- Emergency services (911 in the United States) — only if the full alert chain goes unanswered, and only with the vehicle's last-known location.
- Service providers who host our database (Neon, a Postgres provider), our alert infrastructure, and our email — bound by data-processing terms that limit use to running the service.
Data retention and deletion
Waitlist records are kept until you request deletion. To request deletion, email heatsentry-os@polsia.app from the address you used to sign up, and we will process it within 30 days.
Once the device ships, device telemetry (temperature and occupant readings) is kept in identifiable form for 90 days and then rolled up into aggregated, de-identified summaries. Individual telemetry records are not retained after rollup.
If you stop using HeatSentry, we will delete your account and associated data on request, within 30 days. Deletion of a HeatSentry account also drops you from the waitlist and any pilot program you are enrolled in.
Security
Data in transit between your browser, the HeatSentry device, and our servers is protected by TLS. Data at rest is stored encrypted on Neon. Access to the production database is limited to a named operator list and protected by short-lived credentials.
No security claim is absolute. We work to keep your data protected, and we will notify affected users without undue delay if a security incident exposes their information.
Children
The HeatSentry waitlist form is not directed at children under 13, and we do not knowingly collect information from anyone under 13 through it. HeatSentry as a product is designed for caregivers managing children or other occupants — it is the caregiver who signs up, sets up the device, and designates the contact list, not the occupant.
Changes to this policy
If we make material changes to this policy — for example, expanding the data we collect, changing how long we keep it, or adding a new operational transfer — we will post an updated version on this page, bump the last-modified date at the bottom, and update the sitemap entry so search engines see the new revision. For significant changes we will also email waitlist subscribers.
Contact
Privacy questions, deletion requests, and suppression-record corrections all go to heatsentry-os@polsia.app. We respond to every request we receive.
Last revised: 2026-07-25.
Ready to protect your family?
HeatSentry runs in the background. No app to open. No subscription. Just a sensor that watches, detects, and escalates — so you don't have to remember.
Join the Waitlist