PayloadPier
PrivacyTerms of useContact

CLEAR TERMS · OCTOBER 14, 2026

Privacy policy

What we process, why we need it, what we retain, and how to raise a privacy concern.

Evaluation preview

Public real-money purchases are not enabled. Test credits have no cash value. The private production environment is being prepared separately. x402 and MCP purchasing are not available yet.

Who is responsible

PayloadPier is a trading name used by an individual operator based in Ontario, Canada. Privacy requests and complaints go to the operator at support@payloadpier.com. Seller identity and commercial contact disclosures must be finalized before public paid sales.

Information and purposes

InformationPurpose and handling
Supplier files and JSON inputsProcess your requested comparison. The application processes source files and result bodies in memory and does not store them for later replay.
Account identityChatGPT sign-in supplies an account identifier, email and possibly a display name. We use identity to authorize account access; the billing ledger stores its account/owner identifiers.
Keys and usage metadataStore API-key hashes, names, scopes, caps and timestamps; request hashes, operation identifiers, usage references and charges support authorization, deduplication and billing.
Payment recordsStore payment references, customer/subscription identifiers, balances and entitlements. Stripe processes checkout details. PayloadPier does not store full payment-card numbers or card security codes.
Support messagesRetain voluntarily submitted tickets and email correspondence to investigate problems and respond.
Browser and infrastructure dataSaved mapping profiles remain in browser storage until removed. Hosting, authentication and payment providers may process cookies, IP addresses and technical logs under their own policies.

Service providers and international processing

We use ChatGPT Sites/OpenAI for hosting and sign-in, Cloudflare infrastructure for application execution and database storage, Stripe for payments, and Spaceship/Spacemail for support email. These providers process information needed to perform their services. Processing may occur outside Canada; we do not offer a Canada-only storage guarantee.

Limits on use and disclosure

We use information to operate the requested service, secure accounts, resolve support issues, reconcile billing and meet applicable record-keeping obligations. The application does not send supplier inputs to an AI model for comparison. We do not sell submitted supplier files or personal information, or use them to train AI models. Information may be disclosed where required by law or necessary to investigate fraud or protect the service.

Retention and browser storage

Uploaded sources and results are not retained by the application. Save your successful response: it cannot be retrieved later. Account, billing, security and support records persist; automatic deletion schedules are not yet implemented. We review retention and removal requests against ongoing service, security and legal record-keeping needs. Our providers may retain their own records separately. Remove saved mapping profiles in the workbench or clear this site's browser storage; neither action deletes server-side billing records.

Safeguards and your choices

Connections use HTTPS. Customer API keys are stored as hashes and displayed once; server payment credentials are protected separately. Access to account and operator records is checked server-side. No system can guarantee absolute security. Submit only data you are authorized to share, and avoid health records, identification documents, payment-card data or other unnecessary sensitive personal information.

You can revoke API keys and stop submitting data. Email support to request information about the personal data we hold, access or correction, removal where permitted, or to raise a complaint. We may verify account ownership without asking you to send an API secret, password or payment-card details. We will explain any records that cannot be removed and why. Withdrawing information needed for the service may prevent us from continuing to provide it.

Changes

This notice describes the current preview. We will update it when practices change and explain material changes before a new use of personal information requiring consent.

API portalIntegration guidePrivacyTerms of useContactsupport@payloadpier.com