Privacy Policy

What ShipSignal does

ShipSignal tracks packages across carriers: you give it a tracking number and it returns a delivery timeline.

The Muse gateway endpoints are stubs: timelines are hashed from the tracking number in-memory, and no carrier API (UPS, USPS, FedEx, DHL, or any other) is called. Real tracking happens in the ShipSignal product, which is a separate service.

What we collect

• Tracking numbers: the numbers you submit for tracking.
• Parcel timelines: the placeholder status events the gateway returns for a tracking number.
• Job metadata: timestamps, carrier guesses from number shape, watch flags, and your API key identifier.
• Standard web logs (IP, user agent, request path) from the host/CDN.
• We do not sell personal information or run advertising pixels.

What we do with it

Gateway stub timelines go nowhere: they are generated in-memory from the tracking number and never sent to a carrier or any third party. No carrier API is wired to the gateway stubs today. Watch flags stay on the in-memory record; they do not subscribe you to carrier notifications. If you use the ShipSignal product, its own privacy notice governs that service.

Retention

Gateway state is in-memory and ephemeral: it disappears when the serverless instance recycles. There is no durable database on the gateway.

Keys

Bearer API keys authenticate agents. Treat them as secrets. Telep IO can revoke a key by removing it from the gateway configuration.