Honesty Policy — What We Will and Will Not Claim

Why we publish this

Singapore enforcement under PDPA Section 24 (Protection Obligation) examines vendor operating reality. Our customers — banks, government, healthcare, data centres — face audits where vendor accuracy is itself part of the audit. We do not give them a tall claim to defend. This page is the exhaustive boundary between what we operate to and what we do not claim.

Certifications we do NOT hold

NAID AAA membership — we do not hold it. R2v3 (SERI Sustainable Electronics Recycling) — we do not hold it. e-Stewards — we do not hold it. ISO 14001 (Environmental Management) — we have not been third-party audited against it. ISO 27001 (Information Security) — we have not been third-party audited against it. ISO 45001 (Occupational Health & Safety) — we have not been third-party audited against it. Any OEM partner/authorized/certified designations — we do not hold any. Where a customer engagement specifically requires a certification we do not hold, we either decline, or partner with a certified subcontractor and document the partnership chain of custody on the engagement record.

Standards we DO operate to

NIST SP 800-88 Rev. 1 (Guidelines for Media Sanitization) — published by the U.S. National Institute of Standards and Technology, a public standard, freely citable as the methodology framework we apply for media sanitization. IEEE 2883-2022 (IEEE Standard for Sanitizing Storage) — published by IEEE, applied for SSD/NVMe firmware sanitize operations. DoD 5220.22-M (overwrite method) — applied where contractually specified. NAID-grade operational protocol — operational discipline equivalent to what NAID AAA audits against, applied across vetted operators, chain of custody, per-asset certificate paperwork; we do not pay for AAA membership therefore we do not claim it.

Dates we will not lie about

Maxicom Inc. was incorporated in Canada in 2008. We will not write "since 2001" or any other earlier date for the Singapore entity. Where the Maxicom group has older operations in other countries, those are referenced only on the relevant ccTLD or subpath site, not asserted on this site.

Volume / dollar / customer-count claims we will not make

No "1,000+ clients." No "10,000+ assets processed." No specific dollar amounts recovered for named customers. No fabricated case-study totals. Where we cite a metric (e.g. Reuse-First reuse rate band of 65-75% across our 2024-2025 cohort), it is an honest banded benchmark, not a precision claim. Case studies on this site reference engagement structure and outcome shape — not customer names (NDA-bound) and not invented numbers.

Timing promises we will not make

No "same-day pickup." No "quote in 2 hours" / "quote in 24 hours" / "Wanted Today." No "7-business-day payment terms" as a marketing promise. Engagement timing is governed by the signed Statement of Work. Where this site previously made such promises (live WordPress site prior to cutover), those were brought into line with this policy on the migration to the new build.

Regulator endorsement claims we will not make

We are not "PDPC-approved" — PDPC does not endorse vendors. We are not "MAS-approved" or "MAS-licensed" — MAS does not license ITAD vendors. We are not "NEA-licensed for e-waste" — we route e-waste through licensed recycler partners and document partner credentials per engagement. We align our operations to these regulators; we do not represent them.

Partnership / endorsement claims we will not make

We are not a partner of Dell, HPE, Cisco, NetApp, Intel, NVIDIA, AMD, Apple, IBM, Oracle, Fortinet, Juniper, Lenovo, Microsoft, VMware, or any other OEM. We do not hold dealer, reseller, authorized servicer, or certified-refurbisher status with any OEM. We are an independent secondary-market trading house. See /trademarks/ for nominative fair-use details.

How to verify any claim on this site

On request — written to purchase@maxicom.ca — we will provide: (1) a sample per-asset Certificate of Destruction naming the cited standards; (2) the licensed-recycler partner list for environmental disposal; (3) the operator-vetting summary; (4) a regulatory alignment matrix mapping our operating practice to NIST 800-88 · PIPEDA · OSFI B-13 · NAID-grade · IEEE 2883-2022; (5) the version date stamp of this Honesty Policy. NDA may be required for engagement-specific evidence.

Regulator alignment specific to Canada

This policy is written to align with the regulators that govern engagements in Canada: NIST 800-88 · PIPEDA · OSFI B-13 · NAID-grade · IEEE 2883-2022. Where the policy intersects sector-specific rules (OSFI B-13 for BFSI engagements; PIPEDA 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 Inc. entity contracting in Canada. 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-ca@maxicom.ca (or via the contact form at https://maxicom.ca/contact/). Standard response time: 5 business days for acknowledgement, 30 calendar days for resolution under PIPEDA. Where the matter requires regulator coordination (OSFI B-13 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.