Privacy

Privacy Policy

This policy explains how Enreship LLC collects, uses, stores, shares, protects, retains, and deletes information across the Enreship website and shipping and fulfillment service.

Last updated: September 17, 2026

1. Scope and company identity

Enreship LLC (“Enreship,” “we,” or “us”) operates the Enreship service. This policy applies to our public website, account and support interactions, and data processed when a seller connects an authorized commerce or carrier account.

The Amazon integration described here is in development and planned. It is not live, approved, endorsed, or available for production use. If approved, United States sellers will authorize Enreship through Amazon's OAuth flow. Canada and Mexico are planned only after localization and operational testing.

2. Information we collect

Depending on how you use Enreship, we collect:

  • Account and business information, such as name, business email, telephone number, company, and authentication information.
  • Seller-authorized store, listing, inventory, order, shipment, package, rate, label, and tracking information.
  • Support messages and information you submit through a contact or service request.
  • Technical information needed to operate and secure the service, such as IP address, device/browser details, request timestamps, and diagnostic events.
  • Payment and billing records associated with paid services; payment-card processing is handled by the payment provider rather than stored as complete card data by Enreship.

For the planned Amazon integration, Restricted PII is limited to the recipient's name, delivery address, and phone number when Amazon makes it available and when it is required for shipping. Enreship does not request Amazon buyer passwords or use Amazon PII for advertising, marketing, profiling, or unrelated analytics.

3. How we use information

  • Provide, maintain, troubleshoot, and secure the Enreship service.
  • Import seller-authorized orders and manage listings and inventory quantities.
  • Obtain carrier rates, create labels, confirm shipments, and return tracking updates.
  • Respond to support, account, quote, and legal requests.
  • Maintain business records and enforce applicable agreements.

If Amazon approves production access, planned merchant-fulfilled functions will include seller-authorized order import, listing/inventory-quantity synchronization, carrier rates and labels, shipment confirmation, and tracking updates. Planned FBA functions will include inbound shipments to Amazon fulfillment centers and FBA inventory/shipment status. These Amazon functions remain planned until implemented and approved.

4. Sharing and service providers

We disclose information only to operate the service, follow seller instructions, complete a shipment, comply with law, or protect rights and security. Amazon Information is never sold or brokered.

The following data flows are supported by repository configuration. A provider receives Amazon Information only if the Amazon integration is approved, a seller authorizes it, and the provider is required for the selected operation.

ProviderData and purposeAmazon PIIRestrictions
Amazon Web Services, Inc. (AWS S3)Application objects, including generated shipping files where the workflow requires object storage.May be stored only when required for a seller-authorized shipping workflow.Used under Enreship's AWS account and instructions; subject to Enreship retention and deletion rules.
Planck ProofAPI base URL, OpenAPI specification, scoped test identities and credentials, test traffic, security findings, and the request/response evidence needed to reproduce a finding; used for regular agentic API penetration testing.Amazon Restricted PII is not authorized for routine testing. Any approved engagement that could encounter it requires a documented policy-compliant need and handling controls.Limited to authorized Enreship assets and written test scope; subject to the engagement's confidentiality, access, retention, and deletion terms.
United Parcel Service, Inc. (UPS)Recipient and parcel details required for rates, labels, delivery, and tracking.Yes, when the seller selects UPS.Limited to the selected shipment and the carrier's service terms.
FedExRecipient and parcel details required for rates, labels, delivery, and tracking.Yes, when the seller selects FedEx.Limited to the selected shipment and the carrier's service terms.
United States Postal Service (USPS)Recipient and parcel details required for rates, labels, delivery, and tracking.Yes, when the seller selects USPS.Limited to the selected shipment and applicable postal terms.
DHLPlanned rates, labels, delivery, and tracking operations.No. DHL support is coming soon.No Amazon Information is sent unless the integration is implemented and the contracting entity, permitted data flow, and applicable terms are documented.
OnTracRecipient and parcel details required for supported rates, labels, delivery, and tracking.Yes, when the seller selects OnTrac.Limited to the selected shipment, the carrier's service terms, and Enreship's retention and deletion requirements.
UniUniRecipient and parcel details required for configured rates, labels, delivery, and tracking.Yes, when the seller selects UniUni.Limited to the selected shipment, the carrier's service terms, and Enreship's retention and deletion requirements.
Veeqo (an Amazon company)Ship-from and ship-to names/addresses, parcel details, Amazon order number and order lines for configured rate and label workflows.Yes. Production configuration enables this provider.Limited to configured rate and label workflows under the seller's instructions. Amazon Restricted PII remains subject to Enreship's 30-day post-delivery deletion maximum.

Excluded systems: Functional Software, Inc. (Sentry) is configured for error monitoring, Atlassian Jira is configured for support issue tracking, and Hostinger SMTP is configured for transactional email. These systems are not authorized by this notice to receive Amazon Information. Sentry default PII and request-body collection are disabled, structured Sentry logs and performance transactions are disabled, and before-send filters remove user, request, response, breadcrumb, exception-message, tag, extra, and transaction-name data that could contain customer information. Support and email data boundaries must remain enforced before Amazon production launch.

GOFO and DHL are planned integrations and do not receive Amazon Information. Services described as excluded above are configured not to receive Amazon Information.

5. Retention and deletion

Amazon Restricted PII will be retained only as long as required to complete shipping and support the delivery workflow, and in all cases for no more than 30 days after delivery, unless a documented legal obligation requires a longer period. The same maximum applies through backup-expiration and backup-lifecycle controls.

Following seller revocation, application termination, or loss of authorization, Enreship will stop new collection, revoke or invalidate access tokens, and delete Amazon Information as required by applicable Amazon policy, subject only to a documented legal exception. Information in backups will become unavailable through the enforced backup lifecycle rather than being restored to active systems.

Other business records are retained for the period needed for the purpose collected, legal obligations, disputes, and enforcement. You may request deletion by contacting Enreship; some records may be retained when required by law.

6. Seller authorization and revocation

Connected-store access is initiated by the seller through the platform's authorization flow. For the planned Amazon integration, Enreship will use OAuth and request only the roles needed for the approved functions.

A seller may disconnect an integration through Enreship and, where available, through the marketplace's authorization controls. Revocation stops future API access; deletion then follows the rules above. See the Amazon SP-API data handling page for the planned Amazon-specific workflow.

7. Protection and incident handling

Enreship uses technical and organizational safeguards appropriate to the data and service. Public source configuration confirms authenticated application access, role-based authorization, HTTPS service endpoints, AWS object storage, and application monitoring. Enreship also uses Planck Proof for regular agentic API penetration testing. This policy does not claim certifications, a fixed penetration-test cadence, vulnerability-scan frequency, log-retention periods, backup test frequency, or specific incident-notification timing that could not be verified from the available documentation.

No internet service can guarantee absolute security. Report a suspected security or privacy issue promptly to info@enreship.com.

8. Privacy rights and choices

Depending on your location, you may have rights to request access, correction, deletion, portability, or information about disclosures, and to appeal a denied request. Enreship does not sell Amazon Information and does not use Amazon shipping PII for targeted advertising.

To submit a request, email info@enreship.com. We may verify your identity and authority before completing the request.

9. Contact

Enreship LLC
933 Hylton Rd, Pennsauken, NJ 08110, United States

Email: info@enreship.com
Phone: 917-426-9625
Contact form: enreship.com/contact