Updated October 27, 2026. This policy describes the website as currently implemented. The operator must add their identity and privacy contact before opening paid service.
Tool content
Text, HTML, keyword lists, and results are processed in the current browser tab. RankKit does not upload tool text to an application server or retain a content history. Leaving or resetting the page clears the workspace fields. Copying uses the browser clipboard; downloads are generated locally.
Local workspace storage
Local storage keeps the UTC daily counter, recent tool IDs and names, a local development plan preference, and a billing-session token if the billing service is connected. This enables the workspace experience. It does not store input text or results. Use Clear shortcuts to remove recent tool names; clearing site data in your browser removes all local records, including any billing-session token.
Connected billing service
When configured, the service stores a hashed session credential, payment customer and subscription references, and a daily usage ledger. A successful run may send its tool ID and combined character count; the actual tool text is not sent. The service needs subscription information to recognize the current plan and open the billing portal.
Stripe
Payments, billing email, payment methods, and receipts are handled on Stripe-hosted pages when billing is enabled. RankKit does not display card-entry fields or store full payment card numbers. Stripe processes information according to its own policies. Subscription events are verified by the connected billing service.
Hosting, analytics, and external services
No advertising or analytics scripts are included. The hosting provider may keep ordinary request logs, including IP address, requested page, and timestamp. Opening a generated external URL or using your email application is subject to that service’s privacy practices.
Support and retention
The contact form only composes an email when an operator support address is configured. It does not transmit messages through this website. Support correspondence and payment records may be retained by the operator and payment provider; the operator must publish the applicable contact and retention details before paid launch. Contact availability is shown on the contact page.