Barueri
Avenida Piracema, 1341, Tamboré, Barueri, SP, BR
SP, 06460-030, Brazil
Processing facilityApproximate location
Ingram Micro
6 Corporate Place Unit D, Piscataway, NJ, United States · 5 facilities
- Active certifications
- 5
- Facilities
- 5
- across 3 countries
- Countries with facilities
- 3
- Brazil, Canada, United States
Counted from the facility and certificate records published on this page. Each one is cited individually under Sources.
Participant roles
Data destruction and sanitization (service)
Public listing · L1
- Public listing: NAID AAA endorsements: Conventional Hard Drive Overwriting (Facility); Physical Hard Drive Destruction (Facility, Mobile); Solid-State Device Destruction (Facility); Solid-State Device Overwriting (Facility)
Industries served
Not yet researched. An industry is only assigned where a company states it on its own site, so nothing is inferred here.
At a glance
AI-generatedIngram Micro operates as a data destruction and sanitization specialist, holding NAID AAA certification across facilities in Brazil, Canada, and the United States.
Written from the sourced facts above by gemini-3.6-flash, prompt insight/v2, on 30 July 2026. No fact here appears without its own citation elsewhere on this page.
About
What the sources state about this company. Anything not researched yet says so.
- Description
- Not yet researched. Descriptions are read from a company's own website, reviewed, and cited in Sources below.
- Electronic components handled
- Not yet researched. Assigned only where a company states it, so nothing is inferred.
- Countries with facilities on record
- Brazil, Canada, United States
Facilities5
Sites as the registry publishes them. Address text is reproduced from the source.
Chandler
460 N 54th St Ste 8, Chandler, AZ, US
AZ, 85226-2537, United States
Processing facilityApproximate location
Mississauga
88 Foster Crescent, Mississauga, ON, CA
ON, L5R 4A2, Canada
Processing facilityApproximate location
Piscataway
6 Corporate Place Unit D, Piscataway, NJ, US
NJ, 08854, United States
Processing facilityApproximate location
Plainfield
2675 Reeves Rd Ste 190, Plainfield, IN, US
IN, 46168-7937, United States
Processing facilityApproximate location
The registry publishes coordinates without stating how precise they are, so these render as approximate locations rather than facility pins. Points are upgraded as they are reviewed.
Certifications5 active of 5 on record
Held certificates as the issuing registry publishes them, with the retrieval date for each.
NAID AAAUnversioned (the source states no standard version)
5 certificates across 5 facility records / issued under i-SIGMA
Certified for, across the covered sites
- Facility: Conventional Hard Drive Overwriting
- Facility: Physical Hard Drive Destruction
- Facility: Solid-State Device Destruction
- Facility: Solid-State Device Overwriting
- Mobile: Physical Hard Drive Destruction
| Covered site | Certificate number | Certified from | Valid until | Certified for at this site |
|---|---|---|---|---|
| Barueri | Not published | Not published | 31 May 2027 | Facility: Conventional Hard Drive Overwriting, Facility: Physical Hard Drive Destruction, Facility: Solid-State Device Destruction, Facility: Solid-State Device Overwriting |
| Piscataway | Not published | Not published | 31 December 2026 | Mobile: Physical Hard Drive Destruction |
| Chandler | Not published | Not published | 31 December 2026 | Facility: Conventional Hard Drive Overwriting, Facility: Physical Hard Drive Destruction, Facility: Solid-State Device Destruction, Facility: Solid-State Device Overwriting |
| Plainfield | Not published | Not published | 31 October 2026 | Facility: Conventional Hard Drive Overwriting, Facility: Physical Hard Drive Destruction, Facility: Solid-State Device Destruction, Facility: Solid-State Device Overwriting |
| Mississauga | Not published | Not published | 31 October 2026 | Facility: Conventional Hard Drive Overwriting, Facility: Physical Hard Drive Destruction, Facility: Solid-State Device Destruction, Facility: Solid-State Device Overwriting |
Verified against the i-SIGMA service locator (NAID AAA and PRISM), retrieved 28 July 2026. i-SIGMA service locator (fetched from /wp-admin/admin-ajax.php)
Sources27 field citations
Where each published field came from, when it was last retrieved, and how confident the record is.
| Field | Source | Last retrieved | Method and confidence |
|---|---|---|---|
| Company name | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Website | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Site country | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Coordinate precision | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Site address | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Site country | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Coordinate precision | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Site address | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Site country | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Coordinate precision | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Site address | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Site country | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Coordinate precision | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Site address | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Site country | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Coordinate precision | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Site address | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification status | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Certification version | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Certification status | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification version | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification status | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification version | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification status | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification version | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 12 October 2026 | Parsed from the registryL1 stated by the source registry |
| Certification status | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
| Certification version | i-SIGMA service locatorTechnical detailFetched from https://isigmaonline.org/wp-admin/admin-ajax.php. That endpoint is what the citation records, because it is the resource the data actually came from. It is a machine endpoint and does not render as a page. | 28 July 2026 | Parsed from the registryL1 stated by the source registry |
See something wrong? Request a correction or removal. No account needed.