Understand the data behind a decision

Veltor evaluates repeat benefit claims using customer-supplied identifiers and retained benefit history. Your application continues to own authentication, payments, and delivery.

What Veltor receives

Decision requests require email and IP. Depending on your integration, they can also include recipient IDs, scoped payment fingerprints, verified-phone HMACs, browser observations, and registered custom identifiers. Do not send raw card numbers, raw phone numbers, postal addresses, or arbitrary metadata.

Storage and access

Matching identifiers use keyed hashes scoped to the organization and test or live environment. Retained original evidence is encrypted by the application. Dashboard readers see masked identifiers unless their organization grants reveal permission. Reveals and sensitive actions are audited.

Application data uses Supabase Postgres. Private imports and exports use Cloudflare R2. Resend delivers account email. Upstash Redis protects traffic capacity, and QStash dispatches background work. The application uses one US East deployment region.

Retention

Detailed evidence defaults to 90 days, with 30- and 60-day options. Retry responses are retained for 7 days. Compact grant and matching history remain for the eligibility lifetime; once-ever benefits have no automatic matching-history expiry. Audit records remain for a year, operational records for 30 days, completed import files for 7 days, and generated exports for 24 hours.

Browser collection

Collection requires explicit customer enablement and a consent hook. The browser SDK uses a derived fingerprint and a first-party random browser ID. Raw browser attributes are not transmitted to Veltor, and FingerprintJS monitoring is disabled. Browser evidence does not establish a unique person.

Deletion and recovery

Organization owners and explicitly authorized members can preview deletion scopes. Removing matching history changes future eligibility. Cleanup preserves unrelated recipients and leaves redacted audit records. A restricted deletion journal is kept outside the database so completed deletions can be reapplied after restoration.

Database backup restoration, object recovery, and provider configuration are release checks. Veltor does not claim a measured recovery time or a security certification.