Evaluate
Buyer guide for evaluating the privacy gateway from first contact to pilot sign-off.
What you are evaluating
- PII detection — does it detect your data patterns (Saudi IDs, IBANs, Arabic names, phone numbers)
- Privacy lane routing — do green, amber, and red lane assignments match your policy
- Compliance records — does it produce the processing records, transfer register, and subject rights tooling your team needs
- Integration effort — does it integrate with your applications without workflow changes
- Security readiness — does it meet your procurement and security requirements
Evaluation timeline
- Technical intro (1 day) — demo call, architecture review, security questionnaire
- Pilot setup (1-2 days) — deploy instance, issue API keys, verify health
- Integration test (1-2 weeks) — connect your application, process representative data, review dashboard
- Security review (parallel) — security team reviews documentation pack
- Pilot sign-off (1 day) — review results, agree on production terms or extend pilot
Integration quick-start
Integration is a single API endpoint. No SDK required.
POST /v1/process with Authorization: Bearer sv_your_api_key
Dashboard tabs overview
- Overview — health status, usage stats, lane distribution, provider status
- Compliance — processing records, transfer register, RoPA export
- History — per-request detail: text (redacted), lane, provider, timing
- Subject Rights — tenant-admin / super-admin search, export, delete, and rectify subject data
- Settings — API key management and tenant controls; billing statements live under Billing
Pilot sign-off criteria
- PII detection covers your data patterns
- Lane routing matches your compliance requirements
- Integration effort is acceptable
- Security posture meets your requirements
- Billing model works for your use case
Pricing · Deployment · Enterprise · Contact