Frequently Asked Questions | Rocket Vetting
Rocket Vetting FAQ
We’ve gathered common questions about Rocket Vetting’s secure program integrity platform, including RVP private vetting, RVC collaborative alerts, RVC-CM case management, tokenization, security, and customer-controlled outcomes. If you don’t see your question here, please contact us. For pricing details, see our Pricing page. To understand the full flow, visit How It Works.
Rocket Vetting Platform
Rocket Vetting uses one secure tokenized pipeline to support private and collaborative program integrity workflows.
Rocket Vetting is a program integrity platform that identifies potential deceased, duplicate, and anomalous records using secure tokenized processing. Customers control all review, validation, investigation, and action.
RVP is Rocket Vetting Private, a private LADMF deceased reconciliation service. RVC is Rocket Vetting Collaborative, a privacy-first collaborative detection model that supports pull and push alerts. RVC-CM is Rocket Vetting Case Management, an optional RVC add-on for alert review, research tracking, and resolution workflow.
No. RVP and RVC use the same secure tokenized Rocket Vetting pipeline. Customers can start with RVP and later expand to RVC without changing the core integration model.
Yes. Rocket Vetting is designed to operate autonomously and continuously, 24×7, after setup. Processing does not require ongoing manual support from the customer.
RVP — Private Vetting
RVP provides private, pull-based LADMF deceased reconciliation.
RVP compares customer-submitted or scheduled roster data against SSA Limited Access Death Master File (LADMF) data and returns potential deceased-match indicators for customer review.
RVP generates pull-based LADMF alerts only. These include potential deceased-match alerts, roster-based reconciliation alerts, and recurring scheduled processing alerts.
No. RVP alerts are generated only from customer-submitted or customer-scheduled data. RVP does not generate collaborative, network-triggered, duplicate-participation, or address-anomaly alerts.
No. RVP is private vetting. It does not require participation in the RVC collaborative network.
RVC — Collaborative Vetting
RVC extends Rocket Vetting into privacy-first collaborative detection.
RVC helps participating organizations identify potential deceased participants, duplicate participation, cross-program overlaps, cross-jurisdiction overlaps, address anomalies, and collaboration-driven changes.
RVC generates both customer-triggered pull alerts and network-triggered push alerts. Pull alerts are created when a customer submits or updates data. Push alerts are created when another participating organization’s update creates a new potential match against existing tokenized records.
Yes. Because RVC is collaborative, new alerts may be generated when another collaboration member’s data changes and creates a new potential match against your existing tokenized records.
RVC may generate deceased match alerts, duplicate participation alerts, cross-program overlap alerts, cross-jurisdiction overlap alerts, address anomaly alerts, and collaboration change alerts.
No. RVC identifies potential match indicators only. Customers control all review, investigation, validation, eligibility decisions, benefit actions, voter record actions, and resolution.
RVC-CM — Case Management
RVC-CM is an optional add-on for customers using RVC.
RVC-CM is Rocket Vetting Case Management. It is a lightweight intranet add-on for RVC customers who want structured workflows for alert review, research tracking, and resolution management.
RVC-CM is positioned as an add-on to RVC because collaborative alerts create the strongest need for structured investigation and resolution workflow. Customers that start with RVP can later expand to RVC and add RVC-CM.
RVC-CM can help organize alerts into cases, track research notes and findings, record case status, and document customer-controlled resolution outcomes.
No. RVC-CM supports workflow only. Customers remain responsible for all investigation, validation, eligibility decisions, benefit actions, voter record actions, and final resolution.
Security & Tokenization
Rocket Vetting is designed to minimize exposure of sensitive data.
Sensitive roster data is tokenized inside the customer’s controlled environment, inside their firewall, before secure transmission to Rocket Vetting.
Tokenized data is transmitted using secure, key-based SFTP with encrypted transport and host verification.
Yes. RVP and RVC use the same secure tokenized pipeline. Customers can begin private and expand collaborative without changing how data is prepared or transmitted.
No. Rocket Vetting does not sell, mine, profile, enrich, or commercially exploit customer roster data.
Inbound roster files are purged after successful result retrieval according to lifecycle controls. Minimal audit logs and processing metadata may be retained for security, compliance, billing, and operational integrity.
No. Rocket Vetting is designed around outbound secure transfer. The customer launch process runs inside the customer environment.
Customer Control & Results
Rocket Vetting detects potential matches. Customers control outcomes.
No. Rocket Vetting is a detection and data comparison platform only. It identifies potential matches and indicators. Customers are responsible for independent review, validation, investigation, and action.
No. Rocket Vetting does not certify or declare that any individual is deceased. LADMF-derived and supplemental indicators are returned as potential match information for customer review.
Yes. Output Data represents potential match indicators only and may contain inaccuracies, false positives, or incomplete information. Independent customer review is required before any action is taken.
The customer decides. Rocket Vetting does not determine eligibility, suspend benefits, remove participants, change voter records, or direct program action.
Returned alert or match data may include roster identifier, supplied data echo where applicable, alert type, verification method, match quality indicator, date of death when applicable, and supporting indicators such as LADMF-derived verification data, cemetery reference indicators, or obituary reference indicators when available.
Pricing & Pilots
Rocket Vetting pricing depends on product mode, scale, and deployment model.
Pricing depends on the selected offering, pilot terms, subscription plan, order form, or invoice. RVP, RVC, and RVC-CM may be priced differently based on scope, participation, scale, and support requirements.
Yes. Pilot programs may be offered to validate performance, workflow fit, and program value before broader deployment.
Yes. RVP and RVC use the same secure tokenized pipeline, allowing customers to begin with private LADMF reconciliation and later expand to collaborative detection if they choose.
RVC-CM is an optional add-on to RVC. It is available when customers want structured workflow for alert review, research tracking, and resolution management.
Visit the Pricing page or contact Rocket Vetting to discuss RVP, RVC, RVC-CM, pilot, annual, or enterprise options.