Privacy &
visit statistics.
Your choice
Optional visit statistics help the site owner decide which projects, releases, and pages to improve. Choose Allow visit statistics to participate, or No thanks to use the site without these statistics. You can change your choice using Privacy settings in the footer. Browser Do Not Track and Global Privacy Control signals keep this tracking off.
What is recorded when you agree
A random visit code connects public page views in this browser tab. Statistics include the first page recorded after consent, subsequent public pages, referral website domain, approximate country when supplied by Cloudflare, broad browser and device category, download-link clicks, and successful preorder-notification or app-design submissions. Form contents, names, email addresses, account IDs, raw IP addresses, full browser identifiers, URL queries, and referral queries are not stored in the statistics database.
Court account pages, password resets, Ops, payments, and private downloads are excluded. Download clicks do not prove a completed download. A visit code is not a person, and declining visitors are not represented in these reports.
Storage and removal
Your yes/no preference is saved in this browser for 90 days. A visit code is stored only after consent, in tab session storage; it changes after 30 minutes of inactivity or four hours. Optional statistics are encrypted on the hosting computer and retained for up to 30 days, with hourly expiry checks. The report holds at most 5,000 visits and 50 events per visit.
Turning statistics off stops collection and requests removal of the recorded visit whose code is still available in this tab. Other open tabs also stop and request removal of their current visits. Old visits whose codes are no longer available expire under the retention policy. A code hash may be retained for four hours after removal to prevent delayed events recreating that visit.
If a removal request fails, this tab keeps the code only to retry removal while statistics remain off. Reloading a public page or returning to the tab retries the request. Closing the tab discards those codes; any remaining server records expire under the retention policy.
Anonymous release totals
Separately from optional visit statistics, the server counts full release-file responses it finishes serving. These counters contain only the public release filename, UTC calendar day, and aggregate count. They do not store IP addresses, browser identifiers, referral details, account information, or visit codes, and they do not use cookies or browser storage. Daily counts are retained for 90 days; aggregate per-file totals are kept while reporting is enabled. Partial or resumed transfers and interrupted responses are not counted. These totals cannot identify visitors or confirm that a file was saved or installed.
Hosting and accounts
Cloudflare carries and protects traffic to this self-hosted site. It and the hosting server necessarily process network information such as IP addresses to deliver requests and provide security; this is separate from the optional statistics database. Account, notification, and app-request information is kept separately for the features you choose to use. The optional visit code is not attached to those records.
Jester Feed likes and comments
Reading and sharing posts does not require an account. Liking a post sets a first-party functional cookie for up to one year so this browser can remember and undo its likes. A keyed hash, not the cookie token itself, is stored with liked posts. It is not used for cross-site tracking or optional visit statistics. Clearing cookies may let the same person like again; counts are not unique-person counts.
Comments require a signed-in Court account. Your username, comment, and posting date are public; your account email, real name, and addresses are not displayed with comments. Comments are stored separately on the hosting computer, linked privately to your account for permissions. You can remove your own comment text. The owner can hide or restore comments; hidden text remains available to the owner for moderation. Posts and interactions stay until removed or the service is retired; contact the owner for other removal requests. Short-lived keyed network and account hashes limit spam in server memory.
The owner’s optional English spelling checker downloads a dictionary from this site and checks text on the device. That spelling check does not send draft text to a spelling service. Saving a draft or publishing still sends the post to this site.
Digital purchases
Stripe handles payment details; this site does not receive or store card numbers. The private encrypted order record stores Stripe payment references, payment status, and the file version purchased. Essential secure cookies connect this browser to its purchase for up to 30 days and authorize a download for up to one hour. Raw cookie tokens are not stored in the order database. These cookies are used for purchase access, not optional visit statistics. If you lose access, contact the owner with your Stripe receipt.
Contact messages
The contact form sends your name, email address, selected topic, and message to [email protected] so the site owner can respond. These details are processed by the email service and kept in the owner’s mailbox; they are not added to visit statistics or a public page. Do not include passwords or payment details. To ask about a message you sent or request its removal, email the same address.
Saved auction records
Public auctions are currently paused. Existing bid amounts, times, and the account that submitted each bid remain in the encrypted customer database, separately from optional visit statistics. The owner can use those records to administer existing results and fulfillment. The system does not collect payment card details.
For privacy questions, email [email protected].