Data & processing
Review retention, deletion, access, subprocessors, and the processing terms relevant to your account.
Request details →Trust & security · Evaluation dossier
Confidence starts with a specific answer.
Understand what the platform handles, which controls support your operation, and what your security or legal review needs to confirm. Product features, operating evidence, and contractual commitments are different things.
Reliability & operations
Ask for the applicable operational history, incident practices, measurement window, and contractual service levels.
Request details →Program & attestation scope
Request current evidence, its date, and the services it covers. A program in progress is not a completed attestation.
Request details →Reliability
One operating picture, down to voice.
Moja operates its own VoIP network alongside tracking, routing, analysis, and agent workflows. The call path can still involve carriers and service providers; review the scope that applies to your deployment.
99.99%
Published uptime figure
Retained from the company-approved website baseline. Request the operational history, measurement scope, and applicable SLA during evaluation; this figure is not itself a contractual service-level commitment.
Data handling
Start with what is processed.
Moja processes call metadata and attribution history, recordings where enabled, transcripts and analysis derived from recordings, and campaign configuration. Recording and analysis are metered capabilities; see the published pricing and your agreement.
PII redaction is available on the intelligence line. Confirm its coverage and configuration against your data-handling requirements.
The applicable agreement and privacy terms govern processing and improvement rights. Review retention, export, deletion, and access controls explicitly.
Compliance tooling
Keep evidence close to the call.
Litigator scrubbing
Check inbound numbers against known-litigator lists before a call routes. Priced per pull, on the published rate table — not a hidden add-on.
See the rate →Consent and disclosure, extracted
Define the questions once — was consent stated, was the disclosure read — and QAI answers them from every recorded call, with the transcript attached. Evidence, not a sampling estimate.
How Pulse QAI works →RTB parameter logs
Every real-time bid request keeps its full parameter log. What was received and what was answered is a lookup, not a reconstruction.
How RTB works →Attribution on the record
Every call carries its source and session history, so provenance questions — from a buyer, a client, or a regulator — get specific answers.
How tracking works →These are operating tools, not legal advice or a substitute for your compliance program. No feature alone makes an operation compliant.
Published program status · 28 August 2026
In progress is not a certification.
SOC 2 and HIPAA-related readiness work are in progress in the company-approved baseline. No completed attestation is presented here. Request current status, documentation, and applicable scope during your review.