← Back to home　·　Terms of Service　·　Disclaimer

Privacy Policy

This Policy explains how the KingsFinder operator (“we”) handles information related to kingsfinder.com. Contact: support@kingsfinder.com. Last updated: 21 October 2026.

Using the Service means you acknowledge this Policy. We do not sell your personal information. See also the Terms of Service.

1. What we process

Access is mainly via codes and trials; we usually do not require a name or phone number. We may process:

• Access codes and membership state: plan type (trial / month / year / lifetime, etc.), activation and expiry, revocation status—to grant and verify entitlements.
• Sign-in sessions: session id, sign-in time, device/browser User-Agent—to keep you signed in and limit concurrent devices.
• Cookies: after sign-in, a session cookie (commonly named like kf_m) identifies membership; lifetime about 90 days (see actual Set-Cookie). Not used for ads.
• Trial and abuse-control network identifiers: a salted hash of the network and the claim time, so each network can start a trial only once, until an admin resets it. IPv4 uses the full address, IPv6 uses the /64 prefix, and an IPv4-mapped IPv6 address uses the IPv4 inside it. The raw address is not stored. The browser also stores a cookie (kf_trial) used only to recognise that this browser already claimed a trial. Failed redeem attempts (IP + time) may be kept briefly to block brute-force guessing (typically cleared after ~24 hours).
• Optional contact data: email and message content when you write to support@kingsfinder.com; when card checkout (e.g. Creem) launches, the provider may collect email or billing details under its own policy—we receive only what is needed to activate membership (order id, plan, status) and do not store full card numbers.
• Local browser data: dashboard weight tweaks and some UI preferences stay in your browser (e.g. localStorage) and are not uploaded by default.

2. Purposes and legal bases

• Provide, maintain and improve the Service (sign-in, entitlements, trials, troubleshooting);
• Security and abuse prevention (device limits, guess-rate limits, anomaly detection);
• Perform the contract (activation, support, refund discussions);
• Comply with law and respond to lawful requests.

Where PIPL or similar rules apply, processing is typically based on contract necessity, consent, or necessity to protect network security and legitimate interests.

3. Storage and processors

The site runs on Cloudflare; membership data (codes, sessions) may live in Cloudflare storage such as D1. Information may be transferred and processed across global edge locations for delivery and availability. We require processors to apply security and confidentiality measures fitting their role.

4. Retention

• Codes and membership records: during validity and a reasonable period afterward for support, fraud prevention and accounting; after revocation or deletion on request, copies may briefly remain in backups.
• Sessions: end on sign-out, expiry or revocation; server-side session rows may be kept a limited time for abuse control.
• Failed redeem attempts: short retention (e.g. ~24 hours). Trial claim records (a salted network hash, not the raw address) are kept so the same network cannot start another trial; they can be reset on request or by an admin.
• Support email: as long as needed to handle the request, then archive or delete.

5. Cookies and similar tech

We use necessary session cookies for login—not advertising or cross-site tracking cookies. You can delete cookies in the browser; you will need to redeem or sign in again for membership features. Local storage may hold UI preferences on your device only.

6. Third parties

• Cloudflare: hosting, security and CDN; access logs under its privacy policy.
• Market data sources (e.g. Yahoo-style quote APIs, FRED, CFTC): we fetch public market/macro data, not sell or supply your personal identity to them for marketing.
• Payment providers (when card checkout is live, e.g. Creem): process payments; we do not handle full card numbers.
• We do not sell personal information or provide user lists for others’ independent marketing.

7. Your rights

Where applicable law allows, you may request access, correction, deletion, or restriction/objection to certain processing, and withdraw consent (without affecting prior lawful processing). Self-serve options:

• Sign out on this device on My Membership to drop that session;
• Email support@kingsfinder.com to revoke a code or delete related records (we may need to verify you are the rights holder).

We will respond within statutory time limits. Some data is required for contract or legal duties; deleting it may end membership access.

8. Children

The Service is for adults. We do not knowingly collect personal information from anyone under 18. Contact us to delete any such data collected in error.

9. Security and international transfers

We use reasonable technical and organisational measures (encryption in transit, access control, data minimisation). No system is perfectly secure. Because of Cloudflare and similar global infrastructure, processing may cross borders; we apply protections required by applicable law (e.g. contractual clauses or provider commitments).

10. Updates

We may update this Policy on this page with a new date. Material changes will be highlighted where practicable. Continued use means you acknowledge the updated Policy.

11. Contact

Privacy requests: support@kingsfinder.com
Externally we identify as the “KingsFinder operator”. If regulators or compliance need registered-entity details, email us with the purpose and we will provide what law allows.