Privacy, in product terms.

Haulwhistle stores the name and email address on an account, whether the email has been verified, and account timestamps. Its sign-in system also keeps the account and session records needed to authenticate access. Session records can include an expiry time and, when available, the request IP address and browser user-agent. Account and session data are used to sign users in and associate workspace records with the signed-in account.

A shipment record can contain its reference, carrier, tracking identifier, saved tracking feed description, saved shipment-email source description, expected arrival date, and expected check-in interval. The app also stores source status details and last successful check timestamps when present. These fields organize shipment context and let the app compare available source evidence with the expectations saved for that shipment.

Shipment records are associated with the account that saved them. The workspace supports editing and archiving a shipment; archiving removes it from the active shipment list but does not itself delete the stored record. The current product does not define a general automatic deletion or retention schedule.

When present, source update records include a source type, event and arrival timestamps, and update detail. Exception reports can store a report status, explanation, and evidence, along with each exception's type, source, title, explanation, and evidence. Haulwhistle uses those records with a shipment's saved expectations to show whether an exception is confirmed, unconfirmed, or clear.

No compatible tracking-feed or shipment-email connector is currently installed or authorized. Saved source descriptions do not monitor a feed or mailbox, and incoming update requests are rejected without changing shipment data. See the shipment data explanation for the current behavior.

A user can save a recipient email and choose missed-check-in or arrival-delay triggers for a shipment. Follow-up attempt records include the shipment and exception context, attempt time, outcome, and a sent time when the outbound email transport confirms a send request. A status request is sent only after the user triggers it, outbound delivery is configured, a recipient and matching trigger are saved, and a matching exception is confirmed.

The email can include the shipment reference, saved carrier and tracking identifier, and the confirmed exception title and context. A recorded send reflects the response from the outbound email transport; it is not a record that the recipient read the message.

Checkout is hosted by the payment integration. Haulwhistle uses the returned subscription status, account email, and monthly amount to check paid access. The integration can also return a plan and current billing-period end, and the app may store subscription observations and billing notice outcomes. Payment details entered on the hosted checkout page are handled by that checkout provider.

Haulwhistle uses account and shipment information to provide the workspace, evaluate exception evidence when available, and carry out a user-triggered status request under the conditions above. If a request is sent, its shipment and exception context goes to the recipient saved for that shipment through the configured outbound email service. Billing status checks are handled through the hosted payment integration.