PLAY · REVIEW · IMPROVEEditorial snapshot · 2026.10.04

PICKLARY / PRIVACY

Privacy

What this edition sends, saves and does not collect.

Operator and contact

Picklary is operated by Shawn. This notice describes the public v1.1.0 tools-restoration build dated October 6, 2026. Tournament content retains its separately stated October 4 cutoff. Contact iam4na2@gmail.com with privacy questions.

Hosting and external images

The site is a static website intended for Netlify hosting. Hosting infrastructure can process normal request information such as IP address, requested URL, browser information and timing for delivery and security. This code does not add an analytics tracker or a visitor-account system.

Some product and athlete images are loaded from the linked original source or its image CDN. Your browser must contact that host to display the image; that host may receive your IP address and request metadata. The image elements request no-referrer behavior. The media credits page identifies the sources. External links become subject to the destination’s privacy practices when opened.

Local video and notes

Selecting a video creates a local browser object URL. The review worksheet and Clip Lite do not upload source video bytes to Picklary or an external processor. The worksheet exports notes; Clip Lite can export encoded MP4 video, clip ZIPs and a JSON cut list. Playback and processing depend on the browser, codec and device memory.

Notes remain in page memory until you choose “Save here.” That button writes to localStorage on this browser and site origin. “Load” reads it; “Delete all” removes the saved worksheet and clears the current list after confirmation. The site cannot retrieve that local copy for you. Clearing browser site data also removes it. Do not save sensitive notes on a shared device.

The practice priority check does not transmit or persist its answers. Product filters and comparison choices run in page memory. There are no community-registration forms in this edition.

Clip Lite requests the pinned FFmpeg core JavaScript and WebAssembly from unpkg.com on first export unless the operator packages them locally. The provider receives ordinary download-request metadata such as IP address, not your video bytes. The core runs in a local browser worker. No request is made merely to use the self-check. Browser caching is controlled by the browser and resource headers.

The court-based DUPR self-check stores no answers on a server. Opting into local history saves up to 20 result records under picklary.dupr.history in this origin. Existing compatible older records can be displayed. Clear history or clear site data to remove them. The JSON export includes your chosen answers and the non-official estimate.

Email, retention and deletion requests

When you email the operator, the operator receives your address and the contents you choose to send. Email may be retained while resolving your request and for relevant site administration. Ask for correction or deletion using the same email address; retention required for an applicable obligation may limit deletion. Do not email personal information that is unnecessary for your request.

Advertising and changes

Google AdSense ownership metadata and an ads.txt file are present, but this build does not load an AdSense ad-serving script and does not implement advertising cookies. Before enabling advertising, the operator needs to review the applicable consent requirements, install an appropriate certified consent platform where required, and update this notice to describe the actual implementation.

This notice must change when the site adds forms, analytics, accounts, an image proxy or an advertising integration. The current version should not be used to describe those future features.

Earlier community forms

Earlier editions included community submission forms. This edition no longer accepts those submissions. Replacing a website does not by itself delete data previously received by a hosting provider. For a correction or deletion request relating to an earlier submission, contact the site operator and identify the relevant form without sending unnecessary sensitive information.