YouTubePlaylistLength.xyz
Launch storage policy
This YouTubePlaylistLength.xyz cookies notice is effective August 29, 2026. The declared launch application does not set its own cookies or use persistent local storage to remember duration lists, invalid rows, playback speeds, progress, schedule dates, grouped labels, break rules, or results. It has no login, saved workspace, analytics vendor, advertising profile, or remote calculation history.
The tools still need temporary working state. While a page is open, its JavaScript can hold the current textarea, parsed ledger, and result in memory. That state supports interaction without becoming a cookie or a saved list. Reset clears it, while reload or closure ends the defined session.
Cookie, local storage, and memory are different
A cookie is a small value a site can ask a browser to return with later requests. Local storage retains values on a device until cleared or replaced. Session storage can last within a browsing session. In-memory state exists only in the active page process. The launch calculators use the last category and must not copy inputs into the other three.
For example, a user can paste 12:10, 8:35, and 940, receive a total of 2,185 seconds or 36:25, and then reset. No identifier is needed to perform that addition. Returning tomorrow does not restore the list. The operator cannot retrieve it, and a user should not depend on the page as a record.
The current service does not auto-save drafts, remember a last speed, persist selected watch days, maintain a recent-calculation list, or cache user inputs through a service worker. A materially different future feature requires updated public disclosure before it is enabled.
No analytics or advertising storage
The launch facts contain no analytics vendor, ad network, retargeting tag, social pixel, or behavioral profile. There is therefore no application purpose for analytics or advertising cookies. A future non-essential use cannot be added silently under this notice.
If a later version proposes material storage, the operator must document its purpose, provider, duration, and controls. Any consent required by applicable law must be obtained before activation. A vague banner cannot substitute for an accurate storage inventory.
Hosting and browser cache
The site is hosted through Vercel. Hosting and security layers may use technical controls, caches, or operational logs outside the application. This no-cookie statement applies to site-authored application storage and does not claim that every infrastructure request leaves no provider-managed record.
Browsers may cache ordinary static resources such as HTML, styles, JavaScript, the favicon, or the hero image. A cached asset is not a saved duration list. Calculator values must never be placed in asset URLs, request URLs, source maps, remote error reports, or metadata.
The final implementation should be tested in a clean browser profile. Inspect cookies, local storage, session storage, IndexedDB, cache storage, service workers, and outgoing requests before publishing this notice as an observed fact.
Records created outside the application
Copying a result can place text in clipboard history. Saving a screenshot, printing the page, pasting into a document, or emailing support creates a record controlled by another tool or provider. Clearing site data does not necessarily remove those records.
On a shared device, users should reset the page and manage clipboard or saved copies according to their own needs. Duration-only input is preferable because it reveals less than titles, course names, or account details.
Email communication is covered by the privacy notice, not by this temporary calculator-state rule. A support message may be retained for response or legal needs even though the calculation that prompted it was never stored remotely.
Browser controls
Browsers typically let users inspect and clear cookies and site data, block storage, use private browsing, and remove cached files. Labels and behavior vary. Because the launch tools do not depend on an account or persistent state, blocking application cookies should not prevent their intended use. Disabling JavaScript prevents interactive parsing, while the explanatory content should remain readable.
Extensions, clipboard tools, shared-device monitoring, operating-system features, and malicious software can observe visible values outside the site’s control. A no-cookie design is not a claim of absolute device security.
Trademark and independence
YouTube is a trademark of Google LLC. This independent site is not affiliated with, endorsed by, sponsored by, or operated by Google LLC or YouTube. It does not set a Google or YouTube login session, call a platform API, or use platform branding. Cookies that a visitor already has for another site are not read by this application.
Frequently asked questions
Will my last duration list return later?
No. Persistent calculator history is not a launch feature. Copy a summary under your own control if needed.
Does the site set an analytics cookie?
No analytics vendor or analytics cookie is declared for launch. The deployed network and storage panels must still be verified.
Is browser cache the same as saved calculator data?
No. Static assets may be cached without containing the manual duration lines or results.
Can clearing site data delete an email I sent?
No. Email is a separate communication system and is addressed in the privacy notice.
Finish, copy only if needed, then reset
Treat the active page as temporary scratch space. Inspect the result, create only the local record you need, and reset the tool before leaving a shared device.