Skip to main content

Settings

The /settings page shows your tenant's metadata and links to the two policies you can edit yourself: storage and decision thresholds.

Tenant

  • Tenant name, slug and plan are read-only. Plan, billing and feature changes go through ops@drukverify.com; the contact link on the page goes to the same address.

Storage policy

/settings/storage controls what the platform keeps after a request and for how long:

SettingEffect
store_resultsKeep OCR, fraud and liveness results for result_ttl_days. Off means the response is the only copy.
store_source_imagesKeep the uploaded document images, and for CIDs the automatic card crops used for side matching, for source_image_ttl_days. Images are only kept when results are kept too.
store_liveness_framesKeep the frames submitted to liveness checks for liveness_frames_ttl_days.

Test-mode data is short-lived regardless of these values.

Decision thresholds

/settings/thresholds lists the decision variables your tenant may tune, grouped by feature. Each variable shows the platform default, the range you may set, and your tenant's current override; clearing an override goes back to the platform default. Variables that ops keep platform-only do not appear here.

The tenant-editable variables today:

GroupVariableDefaultRange
Livenessliveness_anti_spoof_threshold0.40.35 to 0.9
Fraudfraud_overall_threshold0.550.4 to 0.8
Faceface_match_threshold0.450.35 to 0.75
Faceface_dedupe_threshold0.550.4 to 0.9
OCRocr_min_long_side / ocr_min_short_side550 / 350 px450 to 800 / 300 to 500
OCRocr_min_chroma50 to 7 (0 turns the black-and-white check off). Measured on the most colourful half-percent of pixels, so a card on white paper is judged on the card, not the paper.
OCRocr_cid_ghost_min_cosine / ocr_side_binding_min_cosine0.420.35 to 0.6
OCRocr_portrait_ghost_min_cosine0.350.25 to 0.5
OCRocr_ghost_min_face_px / ocr_ghost_min_det_score60 px / 0.640 to 100 / 0.4 to 0.8
OCRocr_accept_unbound_sidesoffon/off
OCRocr_cid_card_croponon/off

Each variable's description on the page says which direction is stricter. Every change is recorded with who made it and when; admins see the change history on the same page. Changes take effect on the next request; there is nothing to redeploy.