glendor.com

What It Is

Glendor PHI Sanitizer is PHI de-identification software for the healthcare industry. Its goal is to automatically remove or mask protected health information before multimodal medical data is shared, aggregated, or used for research/AI. The page explicitly covers pixels and metadata in medical images, pathology data, reports, videos, photos, voice recordings, and other healthcare data. It mainly targets two scenarios: data leaving a customer’s network and data entering a customer’s network.

Core Capabilities and Deployment

Its biggest selling points are “Fully Automatic” and “At Source”: there is no need to manually redact items one by one, no need to build templates for different images or documents, and no requirement to send unredacted data to Glendor or any other third party. The software can run in the customer’s on-premises environment or customer cloud, and can either be embedded as a node in existing data workflows or used independently. For medical data security, this source-side de-identification model helps reduce the compliance and leakage risks associated with sending out raw PHI.

Compliance, Management, and Integration

The page mentions “No BAA required” and “1 min to install and start running,” suggesting a focus on low-friction deployment. However, it does not disclose certifications such as HIPAA, SOC 2, or ISO 27001, nor does it provide details on audit logs, access control, alerts, false-positive review, APIs, DICOM/PACS support, or cloud platform connectors. From a rigorous procurement perspective, a POC would still be needed to verify real-world de-identification accuracy, miss rates, traceability, and system integration costs.

Pricing, Pros, and Cons

The page does not provide information on pricing model, subscription term, usage-based billing, or enterprise licensing. Its strengths are multimodal coverage, automation, source-side processing, and avoiding third-party handling of unredacted data. Its weaknesses are the lack of public detail around commercial terms, performance metrics, compliance certifications, and service support. Compared with Google Cloud Healthcare API, Amazon Rekognition, or semi-automated services, Glendor places greater emphasis on not sending unredacted data offsite, but the publicly available information is still insufficient to judge its performance with complex Chinese medical records, rare formats, or large-scale production environments.

Who It’s For and Access from China

It is suitable for hospitals, imaging centers, medical AI teams, research institutions, and payer-side data analytics teams that need to clean PHI before data sharing, training set creation, or external data ingestion. The page does not specify access from China, payment methods, or localized support, so china_access can only be considered unknown. For deployment in Chinese healthcare scenarios, key evaluation areas would include network reachability, compliance with cross-border data transfer rules, Chinese-language and local-format support, and comparison with domestic medical data de-identification or privacy-preserving computing alternatives.