Trademark Notice & Nominative Fair Use
All product and company names referenced on this site are trademarks of their respective owners. Maxicom Global Pte Ltd is independent and not affiliated with, endorsed by, or in any partnership relationship with any original equipment manufacturer.
What this notice covers
This site references the trade names and product lines of original equipment manufacturers (OEMs) in order to identify the equipment we buy back, refurbish or remarket. Such references are made under the legal doctrine of nominative fair use — we use only as much of the mark as is necessary to identify the product, and we do not suggest sponsorship, endorsement, or partnership.
OEM trademarks we reference (non-exhaustive list)
Dell, Dell PowerEdge, Dell EMC, Dell Technologies, PowerVault, Compellent — trademarks of Dell Inc. or Dell Technologies Inc. HPE, Hewlett Packard Enterprise, ProLiant, Synergy, Apollo, Aruba, 3PAR, Nimble, MSA — trademarks of Hewlett Packard Enterprise Development LP. Cisco, Cisco UCS, Cisco Nexus, Catalyst, Meraki — trademarks of Cisco Systems, Inc. NetApp, FAS, AFF, ONTAP — trademarks of NetApp, Inc. Intel, Xeon, Core, Optane — trademarks of Intel Corporation. NVIDIA, GeForce, Quadro, Tesla, H100, A100, L40 — trademarks of NVIDIA Corporation. AMD, EPYC, Radeon, Threadripper — trademarks of Advanced Micro Devices, Inc. Apple, Mac, MacBook, iMac, Mac mini, macOS — trademarks of Apple Inc. IBM, Power, PowerVM, AIX, Storwize — trademarks of International Business Machines Corporation. Oracle, SPARC, Solaris, Exadata, ZFS — trademarks of Oracle Corporation. Fortinet, FortiGate — trademarks of Fortinet, Inc. Juniper Networks, MX, EX, SRX — trademarks of Juniper Networks, Inc. Lenovo, ThinkSystem, ThinkPad — trademarks of Lenovo Group. Microsoft, Windows, Windows Server — trademarks of Microsoft Corporation. VMware, vSphere, ESXi — trademarks of VMware LLC. Other product names not listed here remain the property of their respective owners.
What we do NOT do
We do not display the logos of any original equipment manufacturer anywhere on this site. We do not describe ourselves as an OEM-authorized partner, OEM-certified vendor, OEM-recognised reseller, or OEM trade-in program. We do not represent OEMs in any commercial capacity. We do not use OEM marketing taglines, slogans, or branding elements. We do not claim certifications issued by OEMs that we do not hold.
Legal basis for nominative use
The nominative fair use doctrine (United States: New Kids on the Block v. News America Publishing; United Kingdom and Commonwealth jurisdictions including Singapore: similar common-law and trade-mark statute principles) permits the use of another party's trade mark to identify that party's products or services where (1) the product cannot be readily identified without using the mark, (2) only as much of the mark is used as necessary, and (3) the use does not suggest sponsorship or endorsement by the mark holder. This site uses OEM trade marks under this doctrine. Singapore Trade Marks Act references for non-infringing use of registered marks have been considered in the drafting of this notice.
Reporting a concern
If you are a trade mark holder and believe a use on this site does not satisfy nominative fair use, please write to purchase@maxicom.sg with the URL, the mark concerned, and the basis for the concern. We will review and respond within 10 business days.
Regulator alignment specific to Singapore
This policy is written to align with the regulators that govern engagements in Singapore: NIST 800-88 · PDPA · MAS TRM · NAID-grade · IEEE 2883-2022. Where the policy intersects sector-specific rules (MAS TRM for BFSI engagements; Singapore PDPA for personal-data processing), the more specific rule prevails. The policy is reviewed quarterly by the Maxicom compliance desk and updated within 30 days of any regulator material change. The version date stamp is in the page footer.
Where this policy applies
To the Maxicom Global Pte Ltd entity contracting in Singapore. Cross-jurisdictional engagements (where assets route between Maxicom operating regions) are governed by the SOW jurisdiction clause, which typically points to the contracting entity's jurisdiction. Where customer policy specifies a different jurisdiction (rare but possible), the SOW addendum names the applicable governing law and the dispute-resolution forum.
How to exercise your rights or report a concern
Written request to compliance-sg@maxicom.sg (or via the contact form at https://www.maxicom.sg/contact/). Standard response time: 5 business days for acknowledgement, 30 calendar days for resolution under Singapore PDPA. Where the matter requires regulator coordination (MAS TRM for BFSI; data protection authority for personal-data matters), we escalate within 48 hours. Confidentiality is preserved throughout.
Document retention and version control
This policy is stored in the Maxicom compliance vault under controlled access. Version history is maintained for the lifetime of operations. Material changes are notified to active customers via the master service agreement notification clause; non-material changes are published to this page with the updated date stamp. The current version was reviewed by the compliance desk on the date stamp shown in the footer.
Authoritative references
Primary sources for the standards and frameworks referenced on this page. Maxicom maps every engagement to these recognised authorities.
Frequently asked questions
How does this policy interact with my company's own policy on the same topic?
Both policies apply to their respective scope. Maxicom's policy governs how we (the disposition vendor) handle the data and operations within our scope; your company's policy governs your own obligations. Where the two intersect (typically in the master service agreement), the SOW addendum specifies which prevails for the engagement. Singapore PDPA compliance is jointly held — Maxicom as Data Processor, you as Data Fiduciary/Controller.
Where can I see Maxicom's sub-processors / sub-contractors?
Sub-processor list available on NDA via the contact form. The list includes licensed-recycler partners (with their certifications), trader-channel partners (for cross-border resale routing), and IT-infrastructure partners (Cloudflare for site hosting, dedicated email-delivery provider, etc.). Where a sub-processor change affects your engagement, we notify under the SOW notification clause.
What happens if a regulator changes the rules during our engagement?
Maxicom tracks regulator updates across the four operating regions. Where a change affects an active engagement (revised certificate format, new retention period, etc.), the engagement protocol is updated mid-cycle and affected certificates are re-issued at no additional charge. This policy is updated on the same cadence; the update date stamp tracks revisions.
How do I escalate a complaint to the regulator if Maxicom's response is not satisfactory?
For personal-data complaints under Singapore PDPA, the relevant data protection authority. For BFSI engagements, escalation to MAS TRM. For e-waste / sustainability matters, the relevant environmental regulator. We do not impede regulator escalation; we cooperate with regulator inspection.
Related practices, regulators & markets
IT Asset Disposal (ITAD)
ITAD
→Data Destruction
Data destruction
→Dell Server Buyback
Dell server buyback
→HPE Server Buyback
HPE server buyback
→Banking & Finance
Banking
→Government & Public Sector
Government
→NIST SP 800-88 Rev. 1
NIST 800-88
→IEEE 2883-2022
IEEE 2883
→Send the asset list. We will send the number.
A photograph of the rack works. A spreadsheet works better. SGD settlement, against PO.