Effective date: October 19, 2026
Last updated: October 19, 2026

On this page: 1. Scope · 2. Information · 3. Uses · 4. Cookies and providers · 5. Sharing · 6. Amazon integration · 7. Automation and AI · 8. Retention and deletion · 9. Security · 10. Your rights · 11. International visitors · 12. Children · 13. Updates · 14. Contact

1. Who we are and what this policy covers

Zeugma Trade LLC (“Zeugma Trade,” “we,” “us,” or “our”) is a New Jersey business engaged in trade, sourcing, and online retail. This policy explains information handling for zeugmatrade.com, direct business correspondence, and the planned private Amazon integration described below.

The public website currently provides business information and a mailing address. It does not offer visitor accounts, a contact form, or an online checkout. Purchases through Amazon or another marketplace involve that marketplace’s services and privacy notice as well as any separate notice applicable to our handling of transaction records. This policy does not replace a marketplace’s own terms.

Our role. We are responsible for decisions about our business correspondence and the website information we control. In privacy laws, that role may be called a “controller” or a “business.” Providers can have separate responsibilities for information they handle for their own purposes. The planned private software does not currently offer a data-processing service to other sellers.

What “personal information” means. This is information that identifies a person or can reasonably be linked to a person, including a business contact’s name or individual email address. Company or product information can also be personal information when it identifies someone. Removing a name alone does not necessarily make a record anonymous.

2. Information we receive

Information you choose to provide. When you contact us, we receive the details you include, which may be your name, business name, contact information, product or sourcing requirements, and correspondence. Please provide only information relevant to the inquiry. Do not send passwords, API credentials, payment-card details, government identification, or other sensitive information in an ordinary inquiry.

Technical information from visits. Loading a webpage sends requests to our hosting service and any external resources used by the page. Those services may receive your IP address, browser and device information, page or resource requested, referring page, access time, and diagnostic information. Cookies or similar identifiers may also be involved, depending on the service and browser settings.

Business records. If a correspondence develops into a business relationship, relevant communications and transaction documents may be maintained for that relationship. Information requested for a different purpose will be explained when it is requested.

Sources of information. Correspondence comes from you or from people communicating with us on behalf of your business. Technical information arises when your browser requests website resources. Relevant transaction records may come from the business or marketplace involved in the transaction. Any future Amazon API records would come through the separately authorized connection described in Section 6.

Optional and necessary details. You can read the public website without submitting an inquiry. If you request a reply or a transaction, we may need a contact method and enough relevant detail to respond or carry out that request. Please do not include another person’s information unless you have a valid reason to provide it.

3. Why information is used

• To deliver the website, display its content, and support its layout.
• To respond to inquiries and manage requested business communications or transactions.
• To operate hosting, diagnose errors, understand site performance, and address misuse or security concerns.
• To maintain appropriate business records, handle privacy requests, resolve disputes, and meet applicable legal obligations.

Information supplied for a privacy request will be used to evaluate, verify, respond to, and document that request, rather than to add the requester to a marketing list.

Communications preferences. You may ask us to stop optional follow-up correspondence by replying to the message or using the privacy contact below. A request to stop promotional contact does not prevent a reply you request, a required legal notice, or a communication needed to resolve an existing transaction.

Legal grounds, where required. When a law such as the GDPR applies, the appropriate ground depends on the purpose: taking steps you request toward a contract or carrying it out; meeting a legal obligation; legitimate interests in responding to business inquiries, keeping the website secure, or maintaining necessary records, subject to your rights; or consent when required. A legitimate-interest ground does not remove a separate requirement for cookie consent. You can ask which ground applies to a particular use. Where consent is the basis, you can withdraw it without changing the lawfulness of earlier processing.

4. Cookies, browser storage, and external services

The website uses local storage for layout behavior, including remembering layout measurements for the page header. Local storage remains in the browser until it is cleared by the browser, the website, or the user. Hosting-related scripts may also use cookies or similar technologies for operation, measurement, or security.

GoDaddy services. The site loads GoDaddy hosting-related scripts, including performance and traffic-measurement resources. GoDaddy may process technical information in providing these services. Its own activities are described in the GoDaddy Privacy Notice.

Google Fonts. Font resources are requested from Google domains. These requests disclose connection information to Google so it can deliver the resources. See the Google Privacy Policy.

Google Maps and other links. Our address button is a link to Google Maps, not an embedded map. Google Maps opens when you choose the link. Once you visit an external website, that provider’s privacy practices apply.

Browser controls can block or clear cookies and local storage and restrict external requests. These controls operate separately from requests you send us and may affect the site’s appearance or functionality. Browser privacy signals do not necessarily identify records held in separate business correspondence; contact us for help with those records.

What browser controls do. Some cookies end with a session; others remain until they expire or are removed. Clearing cookies and local storage does not automatically delete logs or correspondence already held elsewhere. Preferences may need to be set separately on each browser or device. Necessary connection and security records can be generated even when cookies are blocked.

5. When information may be shared

Information may be processed by providers involved in hosting the site, delivering external resources, maintaining communications, storing business records, or supporting a requested transaction. A provider may act on our instructions for a service and may separately process technical information under its own notice.

Relevant information may also be disclosed to professional advisers, to comply with a binding legal obligation or valid legal process, or when necessary to address fraud, misuse, a dispute, or a threat to rights or safety. If ownership of the business changes, relevant records may be considered or transferred as part of that transaction, subject to applicable obligations.

A new purpose that requires notice or permission will be addressed before the corresponding processing begins. The specific restrictions on Amazon information are described below.

Scope of disclosure. The information relevant to a hosting issue, a professional adviser, and a transaction may differ. A disclosure should be limited to its purpose and applicable requirements. Links to external websites do not authorize those websites to receive your business correspondence from us. This policy does not grant permission for an unrelated use of personal information.

6. Zeugma Repricer and planned Amazon API access

Current status. Zeugma Repricer is our internal pricing and inventory software project. Its Amazon Selling Partner API (SP-API) connection is planned; this website does not currently provide a public seller-account connection or access to a live Amazon-connected repricer. The following statements describe the boundaries for a future authorized integration, not a claim that Amazon has approved the application.

Purpose and information. The initial integration is intended for Zeugma Trade’s own seller operations. Depending on Amazon’s approval and the features enabled, relevant records may include seller and marketplace identifiers, product identifiers, listings, offer prices, inventory quantities, sales summaries, fee information, and application activity records. Access will be limited to information needed for the authorized functions. Buyer names, shipping addresses, and other restricted buyer information are not part of the planned repricing scope.

Use and disclosure limits. Information obtained through Amazon will be used for the permitted seller functions. It will not be sold, repurposed for buyer advertising, or pooled into products for other sellers. Any necessary disclosure to a service provider must be permitted by Amazon, limited to the authorized task, and subject to an assessment of that provider’s data protections.

Authorization and control. The seller account owner must authorize an integration using Amazon’s supported process. Removing authorization will end future access through that authorization. Credentials belong in protected application infrastructure, not public webpages, browser-delivered code, or ordinary messages.

Before activation, the actual data fields, service providers, storage arrangements, deletion procedures, and safeguards must be confirmed. The notice will be revised if the integration’s scope changes. Amazon’s Data Protection Policy, Acceptable Use Policy, and other applicable agreements govern the permitted handling of Amazon information.

Disconnecting and deleting are separate steps. For a future active connection, the seller can remove the application’s authorization through Amazon’s supported account controls and contact us about retained application records. Revoking access stops future authorized retrieval; records already received must also be addressed under the deletion rules below. Deleting our copy does not delete the original listing, order, or seller-account record held by Amazon. Never provide your Amazon password in a privacy request.

Changes to service scope. Offering the software to other sellers would require a separate review of seller notices, permissions, provider arrangements, and account controls before onboarding. This page does not invite third-party sellers to submit credentials or marketplace exports.

7. Automated processing and possible AI features

The public website does not provide an AI manager or make account-level pricing decisions for visitors. Optional AI assistance is part of the Zeugma Repricer development plan. Before an external AI service receives operational data, the provider, information involved, purpose, and applicable restrictions must be assessed and disclosed. API secrets and buyer personal information are outside the planned AI inputs. A future feature must respect seller-granted permissions and Amazon’s data-use restrictions.

Human and automated actions. A future repricing function may calculate or submit prices within the seller’s authorized settings. That planned operational automation is different from decisions about an individual’s credit, employment, or other legal rights. Before any feature involving personal information is introduced, its inputs, effects, and available controls must be described. This notice does not authorize sending personal information or Amazon records to an AI service for unrelated model training.

8. Storage, retention, and deletion

Business correspondence and related records may be held in the communication, document, or other business systems used for the relationship. Website logs and technical records may be held by hosting and resource providers. Storage locations and retention periods can differ among those systems.

Retention depends on the reason a record was collected, whether an inquiry or transaction remains open, relevant accounting or legal requirements, and any dispute or preservation obligation. We do not promise a single retention period for every record. You can ask about a particular record or request deletion using the contact details below. Provider-managed logs or backups may require provider involvement; deletion requests are subject to applicable legal limits.

For a future Amazon integration, information must be kept only while an authorized purpose or legal obligation justifies it. Amazon’s current rules generally require permanent removal of live information within 30 days after a deletion demand, revoked access, loss of entitlement, or termination. Any legally required exception must be limited to the records and purpose required by law. These procedures must be operational before production access begins.

How retention is assessed. An unanswered inquiry, a completed transaction, a security log, and a privacy-request record can have different retention needs. Relevant factors include the sensitivity and volume of information, whether the purpose is still active, legal recordkeeping requirements, and whether a dispute requires preservation. Information retained for a specific legal obligation should be limited to that obligation rather than reused for an unrelated activity.

Handling a deletion request. We first need enough information to identify the relevant records and confirm the requester’s authority. The response can distinguish records eligible for deletion from records subject to a legal exception or controlled independently by a provider. Backup copies may follow a different removal schedule from active records; this does not extend any stricter legal or Amazon requirement. Ask us if you need clarification about the systems or records covered by a response.

9. Security and incidents

The website uses HTTPS to protect communications in transit. Website administration requires authenticated access. Hosting and external resources also depend on their providers’ safeguards. These measures do not guarantee that every transmission or storage system is immune from compromise.

Before Amazon data enters production systems, the integration must have appropriate access restrictions, multifactor authentication, protected credentials, encryption, monitoring, and incident procedures. These are prerequisites, not a statement that an unlaunched application has already passed a security assessment.

Security incidents must be handled according to the information affected and applicable notice duties, including Amazon’s rules for an authorized integration. Do not send credentials or sensitive records when reporting a concern through ordinary correspondence.

Reporting a concern. Contact the address or email in Section 14 and describe the affected page or service, approximate time, and what you observed. Avoid including passwords, access tokens, full identity documents, or other people’s personal information. If additional sensitive evidence is necessary, ask for an appropriate way to provide it.

10. Your choices and privacy requests

Where applicable law gives you these rights, you may ask to access, correct, delete, or receive a portable copy of personal information, withdraw consent, or object to or limit certain processing. Some laws provide opt-outs for sale, targeted advertising, or specified profiling, and a right to appeal a denied request. Eligibility and exceptions depend on the law and circumstances.

Email hakan@zeugmatrade.com with the subject “Privacy Request,” or write to the postal address below. Identify your relationship with us, describe the request, and provide a way to reply. An approximate correspondence date or the email address you used may help locate records. We may seek proportionate information to verify identity or an authorized agent’s authority. Please do not send a password or an unrequested identity document.

Requests will be handled within applicable deadlines. If a request is denied, you may request review by writing “Privacy Appeal” and explaining your concern. Where available, you may also complain to a relevant regulator. We will not penalize you for exercising a legally protected privacy right.

For data controlled by Amazon, GoDaddy, Google, or another provider for its own purposes, you may also need to use that provider’s privacy-request process.

Verification and limits. Where available under law, an authorized agent may submit a request with evidence of permission; we may also need confirmation from the person concerned. A response must protect other people’s information and legitimate confidential records. If verification is insufficient, or an exception limits what can be provided or deleted, we will explain the applicable limit as required by law.

Timing, fees, and appeals. Applicable response periods depend on the jurisdiction and the type of request. If a lawful extension or fee is necessary, the reason will be explained as required before proceeding. Use the same contact channel for an appeal, identify the earlier request, and explain what you would like reconsidered. Withdrawing consent or objecting to one purpose does not automatically require deletion of records that must be kept for a different lawful purpose.

11. Visitors outside the United States

Zeugma Trade LLC operates in the United States. Visiting the website or communicating with us may involve processing in the United States and in locations used by our service providers. Privacy protections can differ between jurisdictions. Any additional safeguards required for a particular transfer must be addressed before that transfer. Visiting the site alone is not treated as consent to every possible use or transfer.

12. Children’s information

This business-information website is intended for adults and business contacts, not children under 13. It does not provide a child-registration feature. If you believe a child has sent us personal information, contact us so the situation can be reviewed and any required action taken.

13. Changes to this policy

This policy may change as the website, business communications, or software features change. The effective and last-updated dates identify the applicable version. Material changes will be described on this page, with additional notice or permission where required. A future live Amazon connection or public seller service will require a review of this notice before launch.

14. Contact Zeugma Trade

For privacy questions, requests, appeals, or security concerns, contact:
Zeugma Trade LLC — Privacy Contact
Email: hakan@zeugmatrade.com
78 New England Ave, Apt 37
Summit, NJ
United States

Please include a reply email or return mailing address and enough detail for us to locate the relevant correspondence. Use “Privacy Request” for a new request, “Privacy Appeal” for reconsideration, or “Security Concern” for an incident report. A request does not need to include sensitive information unrelated to the matter.

Return to Zeugma Trade