
Command Alkon and GDPR
CertReports found no public GDPR evidence for Command Alkon as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Issued or listed
- 21 Jun 2019
- Scope
- Personal data is collected for purposes of operating effectively, providing products and services to customers, administering and managing relationships with customers; to process, evaluate and respond to requests, respond to inquiries and applications; to create, administer and communicate regarding accounts (including any purchases and payments); to operate, evaluate and improve business (including developing new products and services, managing communications, performing market research, analyzing products/services/websites, and performing accounting, auditing, billing, reconciliation, and collection activities); to ensure the safety of network services and resources; to comply with applicable legal requirements; for human resource administration, employment, benefits administration, and general business management; to process benefits, compensation, stock option, and bonuses; to evaluate workplace performance; to facilitate communications; to protect the rights of the company and others and to ensure the safety of the workplace (including by monitoring use of IT systems); to provide positive identification. The types of personal data collected may include, depending on the purpose, the following: human resources data; customer data; consumer data; visitor data; user activity data; personal data provided by consumers such as names, e-mail addresses, physical address, phone numbers, etc.; personal data collected through products such as details about employees, including their names, job titles, e-mail addresses, login credentials, telephone numbers, addresses, dates of birth, driver’s license numbers, etc.; personal data collected through websites and/or SaaS products such as information about equipment, actions and patterns (“User Activity Information”), including (i) details of use, including traffic data, location data through geo-location technology, logs and other communication data and the resources accessed and used and (ii) information about devices, including operating system, IP address, and other mobile sign-on data; cookies; personal data regarding employees such as contact information, including name, home address, telephone number, personal e-mail address, date of birth, employee identification number, marital status, performance evaluations, job duties, compensation, bank account information, human resource files, photograph, emergency contacts, as well as any other information voluntarily disclosed in an employment application and information that is necessary to process medical, stock, bonus, and other benefits provided. Personal information that is collected is sometimes shared with third party vendors who perform services for or on behalf of Command Alkon to assist with the above purposes for collection. Examples could include, but not be limited to, affiliates; contractors, service providers, consultants and other agents that provide assistance to our business; law enforcement or other government officials in response to a verified request.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Command Alkon Incorporated: Inactive | Live pagesha256 5bbda71c28 |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is Command Alkon GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags or the Cloud and hosting category) whose GDPR row is verified or vendor-stated, ranked by similarity.