Privacy Policy

What ShipLabel does

ShipLabel drafts a USPS shipping label from a sender address, a recipient address, and parcel weight and dimensions. A person reviews the USPS rate and pays postage plus a service fee through Stripe. EasyPost then purchases the label and returns tracking.

Demo mode returns stub rates and a stub label. Demo mode does not contact EasyPost or Stripe.

What we collect

• Sender and recipient names and US postal addresses, plus parcel weight and dimensions.
• The selected USPS rate, postage amount, service fee, Stripe payment reference, EasyPost shipment id, label URL, and tracking code after a paid purchase.
• Standard web logs (IP, user agent, request path) from the host/CDN.
• We do not sell personal information or run advertising pixels. We do not receive full card numbers.

What we do with it

In test and live mode, addresses and parcel details are sent to EasyPost to rate-shop USPS before payment. That call does not buy postage. After Stripe reports payment_status paid, EasyPost receives the buy request. UPS and FedEx are not requested.

Demo mode keeps the draft in the connector's local store and does not send it to EasyPost or Stripe. The fulfillment service, when used, stores drafts and claims in its own database (SQLite locally, Postgres in production), separate from the gateway's in-memory stubs for other connectors.

Retention

Paid drafts are kept so a retry cannot buy a second label and so the label URL and tracking code can be read back. Contact jon@telep.io about access or deletion. Deletion cannot recall a label EasyPost has already bought.

Keys

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