- You require proven enterprise compliance artifacts (SOC 2 Type II, ISO 27001, a detailed DPA, and explicit data residency commitments) and cannot accept that such documentation is not publicly available.
- You require extensive third-party validation such as published SLAs, widely available enterprise references, or presence on major enterprise review platforms.
- Your organization lacks the security maturity to manage phishing/impersonation operational risk (domain controls, user training, transaction policy controls).
- Your user population is unwilling to adopt additional workflows associated with privacy tooling (shield/unshield operations, careful key management).
- Your regulatory posture treats privacy tooling as high risk irrespective of vendor compliance positioning.
Publicly observable limitations from accessible sources
- Pricing and fee structures are not clearly documented in public vendor materials reviewed, which can hinder procurement and ROI modeling.
- Limited independent security and audit evidence was found in public sources; buyers should request audit reports and security assessments.
- Brand impersonation and scam activity have been reported, increasing operational risk for end users.
Roadmap / token status ambiguity
- Public FAQ material referenced a statement that the project did not have a token at the time of the documentation and had plans to launch one in the future. Buyers should confirm current token status and any token-related incentives or risks.