This page follows the things you may do here: read, play, bookmark and contribute. It also explains what remains after the browser tab is closed.
No account is needed to read Qorafendali. Page requests pass through the website’s hosting infrastructure, where ordinary technical information may be processed for delivery and security. The pages do not include advertising cookies, analytics scripts or social-media tracking widgets.
A favourite is a mark in your browser, not in a shared account. The current tab can hold saved titles, high scores and play counts. With your permission, local storage keeps them for your next visit on this device. We remember that preference for up to 180 days, and you can revisit it from the footer.
A submitted rating or comment goes to the server for this website. The JSON record includes the rating and, for a comment, its display name, message and date. Your message is intended to be read by others. Avoid private information: the public note is not a confidential support channel.
The review system uses a random cookie and stores its hashed identifier alongside your contribution. That first-party visitor cookie can remain for one year; a separate session token helps protect the form. Temporary submission counters are also held by the service. This identifies a browser rather than a verified person.
The browser that left a contribution can change or remove its rating, update its comment or delete it. Clearing site cookies can remove that link to the old entry. Clearing saved progress affects only bookmarks and scores, so public feedback is handled separately. For a removal request without the original browser, quote the page and public name in an email.
The contact page is a drafting aid, not a server-side inbox. Sending its draft uses your own email application. Posted feedback stays in the public collection until it is removed; hosting logs and email have their own retention arrangements. Contact the site for questions about those records or any of the practices described here.
Write to [email protected] or prepare a message on the Contact page. Please do not send passwords or browser security tokens.
