Privacy Policy
No accounts, no advertising, no stored files, and aggregate analytics only. This Privacy Policy spells out what remains, and for how long.
Updated
In brief
youtubetomp3.ink does not create accounts, does not ask you to sign up, and does not run advertising. Google Analytics is used only to count visits and conversions in aggregate. Personal information is not sold and is not shared. Converted audio and video are never kept — the bytes travel through to your device and are never written to a disk or a bucket on our side.
The only personal data in play is your IP address, kept in a counter that disappears in about a minute, plus the YouTube link you paste so the converter can do the work you asked for.
Everything below restates the same Privacy Policy with more precision. It covers the service at youtubetomp3.ink and no other product.
Data we handle
The YouTube link you paste
A YouTube URL is reduced to its video ID, then rebuilt as a canonical https://www.youtube.com/watch?v=… address. That rebuilt address is what our server sends to the upstream media provider so a downloadable file can be resolved. The link is not tied to you. Application logs keep only the video ID and the requested format — not the URL you typed, and not your IP address.
Your IP address
Each conversion has an upstream cost, so traffic is metered. Your IP address keys two short-lived counters — a sliding-window rate limit and a cap on concurrent conversions — and is used for nothing else. It is not stored beside a conversion, not written to a database, not used to build a profile, and not given to anyone except as set out under who else is involved.
Your download link
After a successful conversion you receive a link signed with HMAC-SHA256. The signature carries the video ID, the chosen format and an expiry time. It is checked in memory on each request. We never store the link, and it stops working once the expiry passes.
Mail you send us
A message to [email protected] includes your email address and whatever you put in the body. That correspondence is kept only while we still need it to handle the request.
MP3 encoding stays on your device
If you ask for an MP3 and the source is not already an MP3, encoding runs in your browser through a WebAssembly build of the LAME encoder. Audio is decoded and re-encoded locally. The finished MP3 exists only on your device and is never uploaded.
The source file still travels through our server on the way to you, because we proxy it instead of sending your browser to the delivery network. That is a deliberate privacy trade: we pay the bandwidth so the upstream delivery hosts never see your IP address.
How long anything lasts
The figures below are the settings on this deployment. Nothing here is backed up, exported or archived. Once it expires, it is gone.
- Rate-limit counter, keyed by IP
- 60 seconds
- Concurrent-conversion counter, keyed by IP
- 120 seconds
- Resolved source URL and file metadata, keyed by video
- 30 minutes
- Signed download link
- 15 minutes
- Converted audio or video files
- Never stored
- Application logs (video ID and format only)
- Host retention
The resolved-URL cache is keyed on the video and the output format, not on the visitor. Many people converting the same YouTube track share one entry, and that entry says nothing about who they are.
Who else is involved
Third parties are limited to what the converter needs in order to run. There are no advertising networks and no tag managers.
- Google Analytics. Your browser loads gtag.js from Google and reports page views and conversion milestones. Google receives your IP address and browser signals as part of that request. We use the data only in aggregate. Google Signals and Ads linking are not enabled, and the data is not used for advertising.
- Our media provider (FastSaverAPI). Our server sends it the canonical YouTube URL and receives a downloadable source in return. Your browser never talks to it, so it does not see your IP address.
- Cloudflare Turnstile. Where the anti-abuse check is switched on, your browser loads a challenge from
challenges.cloudflare.com. Cloudflare receives your IP address and browser signals to decide whether you are a bot. Our server sends your IP with the resulting token when it verifies the challenge. Cloudflare’s own privacy terms govern that processing. - Our hosting provider. Like any web host, it handles connection data such as IP addresses and timestamps in order to route traffic to us.
These providers may process data on servers outside your country. Where that happens, it happens under the provider’s own safeguards and terms.
We are not affiliated with YouTube or Google, and we do not send them anything that identifies you. The Terms of Service explain what that means for your use of this site.
Your rights
Depending on where you live, data protection law may give you the right to access, correct, delete, port or object to the processing of your personal data, and to complain to a supervisory authority.
In practice there is usually nothing for us to hand over. We hold no account, no history and no identifier for you. The only data keyed to you at all is a rate-limit counter that has already expired by the time you could ask about it. If you believe we hold data relating to you, write to [email protected] and we will look and tell you what we find.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in California law.
Security
- The site is served over HTTPS only, with HSTS.
- A strict Content Security Policy is applied to every response, along with frame, referrer and MIME-sniffing protections.
- Download links are signed and short-lived, so a leaked link stops working within minutes rather than remaining valid indefinitely.
- The download proxy will only stream from an allowlist of hosts, and rechecks that allowlist on every redirect hop.
- API credentials stay on the server and are never exposed to the browser.
No system is perfectly secure, and we cannot guarantee that one is. If you find a vulnerability, please report it to [email protected] before disclosing it publicly.
Children
The service is not directed at children under 13, and we do not knowingly collect personal information from them. There are no accounts and no profiles, so there is nothing for a child to sign up for. If you believe a child has sent us personal information by email, contact us and we will delete it.
Updates to this Privacy Policy
If this Privacy Policy changes, the date at the top of the page moves with it, and anything material is described rather than edited in silence. Continuing to use the service after an update means the updated Privacy Policy applies to you.
Contact
Privacy questions and requests go to [email protected]. The contact page lists what to include so we can answer in one exchange instead of several.