Skip to content
LRC Maker

Privacy policy

Last updated: 14 October 2026

This policy explains what information LRC Maker (“we”, “us”) processes when you use lrcmaker.io (the “Service”), why, for how long, and the choices you have. LRC Maker is designed to work without accounts and to keep as little data as possible, for as short a time as possible.

Summary

  • No account, no sign-up, no lyrics history.
  • The server receives only the Spotify track ID (and any song details you type) and forgets the result after 10 minutes at most.
  • The JSON to LRC converter runs entirely in your browser; nothing you paste there is uploaded.
  • Our server logs contain no IP addresses, track IDs or lyrics.
  • We count page views with Cloudflare Web Analytics, which uses no cookies and does not track you across sites.
  • The Service shows ads from Google, which may use cookies — subject to your consent where the law requires it.

1. Who is responsible

The Service is operated by LRC Maker (“LRC Maker”). For any privacy question or request, write to [email protected].

2. Information we process

When you look up a song

  • The 22-character Spotify track ID taken from the link you paste. The rest of the link (for example tracking parameters) stays in your browser.
  • Any song title, artist name or length you type to correct the track details.

Technical data

Like every website, our servers receive connection data such as your IP address, browser type and the time of the request. We use your IP address only in memory to apply rate limits that protect the Service from abuse; it is discarded when the limit window ends and is not written to our logs.

When you contact us

If you email us, we receive your email address and whatever you include in your message.

What we do not collect

We do not ask for or receive your Spotify login, password or cookies, and we do not create user accounts or profiles. Lyrics you paste into the converter never leave your device.

3. How we use information and our legal bases

  • To provide the Service — identify the song, find matching synced lyrics and return the result to your browser (performance of the service you request / legitimate interests).
  • To keep the Service secure and available — rate limiting, abuse prevention and error diagnostics (legitimate interests).
  • To show advertising that keeps the Service free — see section 5 (your consent where required by law; otherwise legitimate interests).
  • To answer your messages and handle copyright or privacy requests (legitimate interests or legal obligation).

4. How long we keep information

  • Lookup results: in server memory for up to 10 minutes, then deleted. They are never written to disk or a database.
  • Song details (title, artists, album, length, artwork address) may be cached in memory for up to one hour to avoid repeated requests. This cache is not linked to any visitor.
  • IP addresses for rate limiting: only for the length of the limit window (minutes), in memory.
  • Server logs: request type, route, status and timing only; kept for a short period for troubleshooting.
  • Emails: as long as needed to handle your request, and then deleted unless we must keep them for legal reasons.

5. Cookies and advertising

LRC Maker itself does not need cookies to work. We show advertising served by Google AdSense to keep the Service free. Google and its partners may use cookies, device identifiers and similar technologies to show ads, limit how often you see them, measure their performance and prevent fraud.

Visitors in the European Economic Area, the United Kingdom and Switzerland are asked for consent through a consent message before ad cookies or personalised ads are used; where required, we also offer the choice to opt out of the “sale” or “sharing” of personal information for targeted advertising under US state privacy laws. You can change your choice at any time:

You can also block or delete cookies in your browser settings; the Service keeps working without them.

Website analytics

To understand which pages are used, we use Cloudflare Web Analytics. It counts page views and basic performance metrics in aggregate, does not set cookies, does not use your IP address to identify you, and does not track you across websites.

6. Who receives information

  • Hosting providers — Cloudflare (website delivery and protection) and the cloud provider that runs our lookup server process connection data on our behalf.
  • Lyrics and song-information sources — our server sends the track ID or song details (never your IP address or other personal data) to Spotify’s public interfaces and to LRCLIB.
  • Spotify’s image servers — album artwork is loaded by your browser directly from Spotify’s image CDN, which therefore receives your IP address, as with any image on the web.
  • Google — advertising, as described in section 5.
  • Authorities, where we are legally required to disclose information.

We do not sell your personal information for money.

7. International transfers

Our providers may process data in countries other than yours. Where required, transfers are protected by appropriate safeguards such as the European Commission’s standard contractual clauses.

8. Security

We use HTTPS everywhere, strict security headers, rate limiting, short retention and data minimisation. No method of transmission or storage is completely secure, but we work to protect the little data we handle.

9. Your rights

Depending on where you live (for example under the GDPR, UK GDPR, Brazil’s LGPD or US state laws such as the CCPA/CPRA), you may have the right to access, correct, delete or port your personal data, to object to or restrict processing, to withdraw consent, to opt out of targeted advertising, and to complain to your data protection authority. Because we keep almost no personal data and have no accounts, there is usually nothing stored that we can link to you — but we will answer every request. Write to [email protected]; we respond within 30 days.

10. Children

The Service is not directed to children under 13 (or under 16 in the EEA), and we do not knowingly collect their personal information. If you believe a child has sent us personal information, contact us and we will delete it.

11. Changes to this policy

We may update this policy. We will change the “Last updated” date above, and for significant changes we will add a notice on the website.

12. Contact

Questions or requests about privacy: [email protected].