Privacy Policy
Shipal is a parcel-tracking connector for ChatGPT and Claude. This page describes exactly what Shipal sends, what it returns, what it logs, and what it does not collect. The intent is plain language — no dark patterns, no unannounced data flows.
1. What Shipal sends to 17Track
When you ask Shipal to look up a parcel, Shipal sends only the tracking number you provided to 17Track, which performs the carrier lookup. 17Track's own privacy practices apply to that request; see 17Track's privacy policy.
No other information from your conversation, no account identifiers, and no metadata about you is forwarded to 17Track.
2. What Shipal returns to your chat
The widget rendered in ChatGPT or Claude shows only the following fields, and the underlying tool response contains nothing else:
| Field | Description |
|---|---|
trackingNumber | Echoes the number you provided. |
carrier | Auto-detected carrier display name (e.g. DHL, UPS). |
status | Canonical shipment status (Delivered, InTransit, OutForDelivery, …). |
latestEvent | Description, timestamp, and a city-level location for the most recent tracking event. Street addresses are scrubbed before returning. |
daysInTransit | Days since the shipment started moving. |
estimatedDelivery | The carrier's delivery window when one is reported. |
| event timeline | The chronological list of tracking events, each with description, timestamp, and city-level location. Used to render the widget timeline. |
error | A typed error code when the lookup fails (e.g. not_found, rate_limited). |
Shipal never returns sender or recipient addresses, customer numbers, reference numbers, local numbers, or any other identifying field that 17Track may include in its raw response. These are stripped server-side before the response is shown.
3. What Shipal sends to analytics
Shipal sends a single anonymous event per tool call to its analytics backend (Yavio Analytics). The event contains only:
tool_status—okorerror.error_code— typed error code on failure, otherwisenull.carrier— the carrier name returned by 17Track.status— the canonical shipment status.user_intent— a categorical bucket the LLM picked for why the user is tracking, from a fixed enum:check_eta,worried_delay,confirm_arrival,general_status,delivery_problem,first_check,pre_purchase,other. This is a fixed-enum bucket, not free text — it cannot contain personal information.latency_ms— how long the call took.app_version— the Shipal release that emitted the event.
Shipal does not send to analytics: the tracking number, any address (sender or recipient), any free-text user input, your email address, your account ID, your IP address, or any other identifier. The Yavio ingest also independently rejects any payload that contains a tracking number, address, customer number, reference number, email, user_id, or IP at any depth.
4. Storage and retention
Tracking lookups are not stored by Shipal. Anonymous analytics events are retained for 90 days for aggregate usage reporting and then deleted.
5. Sharing
Shipal does not sell or share data with advertisers or other third parties. The two third parties involved in fulfilling a request are 17Track (the carrier-data provider) and Google Cloud (the host).
6. Your rights
Because Shipal does not collect personal identifiers, there is normally nothing to access, correct, or erase. If you believe an analytics event derived from your interactions should be removed (for example, if you can identify a specific timestamped event), email hello@yavio.ai and we will honor a deletion request within 30 days.
7. Contact
Shipal is operated by Yavio (yavio.ai). For privacy questions, write to hello@yavio.ai.
8. Changes
If this policy changes materially, we'll update the "Last updated" date above and note the change at the top of this page. Source-of-truth is always this page; if you read about a different policy elsewhere, this page wins.