Internal Cron

Integrity Retention Tick

Vetting Integrity v1 (PR5): purge raw IP + device hash older than 90 days from integrity_request_meta. Coarse evidence (country, ASN, hosting and VPN booleans, browser zone) stays so existing D signals remain explainable.

Runs whatever INTEGRITY_SIGNALS_ENABLED says: data captured while the flag was on must still age out after it is turned off. Idempotent (a second run touches nothing). Driven daily by .github/workflows/bench-freshness-cron.yml — external cron, never the in-process scheduler.

post/api/internal/cron/integrity-retention

Request

  • Base URL: https://api.ruzora.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.ruzora.com/api/internal/cron/integrity-retention
  • Auth: none declared

Headers

x-cron-tokenstring nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.