Security overview

RichestDevs is deployed on Cloudflare Workers with D1-backed application data. Production traffic is served over HTTPS.

Account access uses Better Auth session handling where authentication is needed. Boost purchases do not require an account; payment integrity is handled separately through Stripe Checkout and verified webhooks.

Store metadata lookups and purchase actions are validated server-side. Supported store hosts and URL shapes are restricted, expensive write paths are rate limited, and Turnstile is verified before quote and Stripe Checkout creation when configured.

Stripe Checkout handles payment entry. Public ranking spend changes only from verified Stripe webhook events. Webhook event IDs are stored for idempotent processing, pending checkouts do not reserve a listing, and browser redirects do not activate or boost a listing by themselves.

Public outbound redirects resolve only to the canonical store URL saved for the listing. Reports and administrative hide controls are available so problematic listings can be removed from public ranking without deleting their payment audit history.

Security practices evolve with the product. Dependencies, access controls, logs, payment configuration, and deployment settings should be reviewed regularly as RichestDevs changes.