Privacy Policy

Accounts are optional for boost purchases. If you sign in, RichestDevs processes account and workspace information for authentication, account security, and showing boosts purchased while signed in.

When a supported store URL is submitted, RichestDevs processes the store-native app identifier, canonical store URL, app name, icon, developer name, store category, platform, and related listing data. Public ranking pages display listing information, confirmed spend, rank, and aggregated outbound click counts.

Payments are completed through Stripe Checkout. RichestDevs records transaction references and status information needed to fulfill and audit a boost purchase, including the listing, target and charged amounts, currency, the email collected by Stripe Checkout, Stripe customer identifiers when present, Checkout Session and Payment Intent identifiers, and confirmation timestamps. If you were signed in at checkout, the payment may also be associated with your user account. Payment-card entry is handled by Stripe Checkout rather than the RichestDevs application.

RichestDevs can record outbound store clicks, their source, listing reports, request timestamps, network information, browser details, rate-limit data, and service logs needed to operate, protect, and troubleshoot the application. Public-site traffic is measured with Simple Analytics, which records page-level analytics without cookies, IP addresses, or persistent visitor identifiers.

RichestDevs uses Cloudflare infrastructure for application hosting and data services, Stripe for payment processing, and Simple Analytics for privacy-friendly public-site traffic measurement. Authentication and security components are used to manage sessions, verification, and abuse prevention.

Information is retained for as long as needed to provide the service, maintain payment and security records, resolve disputes, prevent abuse, or meet applicable obligations. Public listings can be hidden while transaction history remains available for payment and audit purposes.

Account holders can control information they submit through their account and workspace. Browser-level controls remain available for local preferences and cookies. Listing reports provide a way to flag public entries that require review.