PlaylistLength.net
The public support channel
To contact PlaylistLength.net, write to support@playlistlength.net. The address is intended for questions about calculator behavior, corrections to published explanations, accessibility feedback, privacy requests, and responsible reports about the public site. A useful message identifies the page and describes what happened without attaching a private playlist or unrelated personal information.
PlaylistLength.net operates the site from 30 N Gould St Ste R, Sheridan, WY 82801, USA. Email is the public support channel. The service does not provide live chat, telephone support, social messaging, or a guaranteed response time. Messages can be reviewed in context and prioritized by impact, but sending an email does not create an emergency or real-time service relationship.
What to include for a calculator question
Most arithmetic questions can be reproduced with a small, non-sensitive example. Include the exact route, the labels of the fields you used, and the values needed to show the issue. State what result appeared and what you expected. A compact example is easier to verify than a screenshot containing an entire personal queue.
For instance, a useful report might say: “On /tools/playlist-gap-time-calculator, I entered 12 tracks and a 5-second gap. I expected 11 transitions, but the result counted 12.” That tells the reviewer which transition rule may be unclear. There is no need to include track titles, account names, URLs, or media files.
Before writing, check the explanation beside the result. Different tools intentionally use different models. The general calculator attaches a gap to a row. The gap-time calculator may ask whether a pause occurs between items or after every item. The crossfade calculator subtracts overlaps rather than adding silence. A result that differs across routes may reflect those visible assumptions rather than a defect.
Accessibility feedback that helps
Accessibility reports are welcome. Name the browser and operating system if they affect the issue, identify the control or heading involved, and explain the barrier. Examples include a missing form label, an unclear error message, a focus indicator that is difficult to see, a control that cannot be reached by keyboard, or an image whose alternative text does not convey its purpose.
Do not send medical details or other sensitive information to explain why a feature matters. Describe the interaction barrier itself. The interface uses semantic landmarks, associated labels, visible focus states, responsive layouts, and readable validation feedback as its accessibility baseline. If the current browser experience does not match that description, report the route, control, input method, and observed barrier.
Corrections and editorial evidence
When reporting a content issue, quote only the short phrase that needs attention and provide a reliable source if the claim depends on outside facts. Most pages on this site use arithmetic examples rather than changing statistics. A formula correction should show the calculation. A terminology correction should identify the ambiguous phrase and the context in which it could mislead a reader.
The editorial team does not accept fabricated testimonials, purchased-link requests, copied articles, or unsupported traffic claims as evidence. Requests to exchange sitewide links or insert unrelated commercial anchors are not appropriate support requests. A genuinely relevant resource can be considered on its merits, but contact does not guarantee publication.
Privacy requests
The launch tools do not create accounts, upload playlists, or persist calculation history. Even so, a person may contact the operator with a question about the public site or an email they previously sent. Clearly state the nature of the request and use the same email address involved when identity context is necessary. The operator may need enough information to locate the communication and may ask for reasonable verification before acting on a request concerning personal data.
Avoid sending passwords, payment details, government identifiers, health records, private media, authentication codes, or API keys. The site does not need those items to answer a calculator question. If a message contains unnecessary sensitive data, that makes support harder rather than more effective.
Security reports
For a responsible security report, describe the affected public URL, the observed behavior, the potential impact, and safe reproduction steps. Do not access data that does not belong to you, disrupt availability, run destructive tests, or publish exploit details before the operator has a reasonable chance to review them. The contact channel is not an authorization to probe third-party services or systems outside PlaylistLength.net.
Hosting headers, rate limits, content security policy, and browser dependencies can vary with the environment serving the page. Reports should identify the public route, browser, date, and environment actually observed so the operator can investigate the same behavior.
Frequently asked questions
Can I send a playlist URL for you to calculate?
No. The support channel is not a manual calculation service, and the tools do not fetch third-party playlists. Use non-sensitive sample durations when reporting a problem.
Is there a guaranteed reply time?
No response-time commitment is published for the launch site. Clear reports with reproducible details are easier to evaluate.
Where should a legal notice be sent?
Use the public support email and identify the nature of the notice in the subject. The operator may provide further routing instructions where appropriate.
Can I request a new calculator?
Yes. Explain the decision the tool should support, the minimum inputs, and how its result would differ from an existing route. A suggestion does not guarantee implementation.
Send only what is needed
Open your email client, name the affected route, provide a concise description, and remove private or irrelevant material before sending. The best support message makes the problem understandable while respecting your own data.