Privacy notice

What Songlinks collects, why, and how long it is kept.

Effective 2026-10-18

Who we are

Songlinks looks up songwriters’ names in music rights registrations and groups the records that belong to the same person. It is in beta. It is run by Kane Technology Group, LLC. What you agree to when you use it is in our terms of use. You can reach us at alex@songlinks.to.

What we collect, and why

You do not need an account to use Songlinks. When you use the site or the API, our server records:

• When you look up a name or open a person page: the name or person ID, any song title you add to a lookup, your IP address, the browser or software you used (its user agent), the page that sent you (the referrer), the website that made the request if it came from another site (its origin, such as cwrcheck.com), a summary of the answer, and how long it took.
• For every request, including ordinary page views: the web address requested, which includes any name or song title in it, the result and the time. These lines record our load balancer’s address, not yours.
• When you check a list of IPI name numbers (the Check writers page, or /v1/writers): how many numbers you sent and how many matched a writer, how long it took, your IP address, your browser, and the address of the page that sent you with anything after its ? removed — but never the numbers themselves, which are left out of every log line, taken out of the page’s own address before Google Analytics records it, and sent to our database as separate values rather than in the text of its queries.
• When an AI assistant calls Songlinks for you (through our MCP server, for example as a connector in Claude): the assistant sends only what it puts in the call — a name and any song title, a person ID, or IPI name numbers — and never your conversation. We use those to answer. Our logs record which tool was called, what it was asked — the name and any song title, the person ID, or the one IPI name number, as a lookup on this site is recorded — whether it answered, how many results it gave and how long it took. When an assistant checks a list of IPI name numbers, we record only how many it sent and how many matched, never the numbers, as with the Check writers page (above). When an assistant first connects, we also record the name and version of its software as it reports them (for example “claude-ai”): that identifies the software, not you. The call reaches us from the assistant’s provider or your own software, and is logged like every other request (above), with our load balancer’s address.
• If you email, text or WhatsApp us: your message, and the address or number it came from. A WhatsApp link on a lookup or person page starts your message with the name you looked up or the person ID. You can change or delete that before you send it, and nothing is sent until you do.

If you create an account

An account is optional. It lets you save the writers you look after, by IPI name number, and share that list with the people you work with. You sign in with Google.

• From Google: your name, your email address (one Google has verified) and your Google account identifier. Nothing else from your Google account, and never your password.
• Your teams: each team’s name, who is in it, and each member’s role. When you sign up you get a team of your own. Everyone in a team sees the name, email address and role of everyone else in it.
• What a team saves: the IPI name numbers on its roster, where each was saved from (for example the Check writers page), any label a member types, the person the number led to when it was saved, and who saved it and when. If you give them, the IPI name numbers of your own companies (your publishing or administration companies), so that writers they represent are marked when you add writers by name. IPI name numbers identify songwriters. You save them to keep an eye on how the writers you represent or work with are registered, and what we show about them comes from public registration data.
• Invitations: the email address you invite, the role, when you made it and whether it was accepted. Songlinks does not send the invitation: you copy a link and send it yourself. We keep only a one-way fingerprint of the link’s secret, not the secret itself.
• What you record about your writers: your statements about which registrations belong to a writer, their history, the relationship you declared, and any note or spelling you type. Each statement is kept with the team, with who recorded it and which date of the registration data it was made against, and changing your mind keeps the earlier version. What you record here is yours and stays in your account. We may also use it, combined with other accounts' and never with your name or team, to improve how Songlinks groups registrations.
• A team’s history: when writers were added, labelled or removed, and when members were added, removed or given another role, and by whom, so that nothing a team saved is lost when it changes.
• A catalog review we prepare for your team: if Kane Technology Group reviews your catalog for you, we store the review with your team: the songs, writers, registrations, shares and recordings it found in public registration data, the names and IPI name numbers on the roster you sent, and the report and spreadsheet we sent you. On the site, only the members of that team can see it or download its files, and only we can add one. We keep a record of when each review was added or withdrawn in the team’s history.
• Your answers on a review, and a record of every action on it: what your team’s members answer on a catalog review (whether a registration is your writer’s, who collects a writer’s share, whether two registrations are one song, the status of each point and song, and any note), with who gave each answer and when. Changing an answer keeps the earlier one. We also record, with the team, each time a member opens a review or downloads its files. Your answers stay with your team: they never change the review, the registration data or anything another account sees.
• What you do with your account: our server logs account actions, such as signing in, creating a team, inviting someone, saving writers, recording statements, or opening a catalog review or downloading its files, with your account number, what was done, how many and when. The log never includes the IPI name numbers you save, check or match, the addresses you invite, or the labels, notes and spellings you type. Lookups and person pages you open while signed in are logged as they are for everyone, and are not linked to your account.
• Email from us: only if you tick the box on your account page, “Kane Technology Group may email me about registration problems in my catalogue”. It is unticked until you tick it, it is separate from having an account, and you can untick it at any time. We keep which wording you agreed to and when, and when you withdrew.

You can download everything you’ve recorded, at any time, from your account page: one ZIP file with your account, every team you are in, everything its members saved and recorded with every earlier version, and what the registration data holds about each saved writer. We make the file on our server and keep it for up to an hour so that you can download it, then delete it; deleting your account deletes it at once.

Every page on the site also runs Google Analytics, which records for us:

• the address and title of each page you open, and the page that sent you. A page’s address includes any name and song title you looked up and any person ID you opened;
• your browser, device, operating system, screen size and language, and your approximate location (city, region and country), which Google works out from your IP address. Google says Google Analytics does not log or store the IP address itself;
• some of what you do on a page, such as scrolling most of the way down it or following a link to another site;
• which buttons and links you click and which forms you send, recorded by the control’s name (for example “save writers”) and, for a link, the kind of page it leads to. Never what you typed, and never a name, IPI name number or person ID shown on the button or in the link;
• a random identifier kept in a cookie, so that a return visit counts as the same visitor (see Cookies, below).

We use this to keep the service running, to see which names it answers badly, to understand who uses it and how they find it, and to spot abuse such as automated scraping.

How long we keep it

• Server logs expire after 30 days and are then deleted automatically.
• If you have an account, what it stores is kept until you delete it. Deleting your account, from your account page, deletes at once your account, your email choice, your place in every team, and every team where you are the only member, with its roster and invitations. In every other team, what you saved, answered and recorded stays, without your name on it. If you are the only owner of a team that has other members, you are asked to make one of them an owner first. A team’s invitations, statements, history and catalog reviews are kept until the team is deleted, and deleting a team deletes them at once. If we withdraw a review, the team stops seeing it at once, and we keep it as the record of what we delivered. Our database’s automatic backups can hold deleted data for up to 7 more days.
• Our database’s performance monitoring and error logs can keep the queries a lookup runs, which can include the name searched, for up to 7 days. The same is true of a call from an AI assistant: its query can include the name, IPI name number or person ID it sent.
• If we limit how many lookups one address may make, the server also holds your IP address in memory for up to about ten minutes after your last lookup.
• Access logging is switched off on our load balancer and on Amazon CloudFront, so neither keeps a record of its own.
• Google Analytics keeps the detailed record of each visit for 2 months. Totals built from it, such as page views per day by country, are not removed at 2 months.
• Email you send us is kept in Google Workspace until we delete it. Texts and WhatsApp messages are kept until we delete them.

Who handles it for us

• Amazon Web Services hosts the site, the API, the database and the logs in the United States (US East, Ohio), and delivers the pages through Amazon CloudFront.
• Google Workspace handles email to alex@songlinks.to.
• Google signs you in, if you create an account, and so knows that you signed in to Songlinks.
• Google runs Google Analytics for us. How Google uses information from sites that use its services: policies.google.com/technologies/partner-sites.
• Namecheap runs the DNS for our domain names.
• Texts and WhatsApp messages reach us through your phone carrier or WhatsApp.

Cookies

Google Analytics sets two cookies on songlinks.io: _ga, which tells one visitor from another, and _ga_VVKXBQQFCQ, which keeps track of a visit. Each is set to last two years, and browsers cut that short if you do not come back (Chrome to 400 days, Safari to 7 days). Songlinks runs no advertising scripts.

Songlinks sets cookies of its own only when you choose to sign in, never on an ordinary visit. sl_oauth lasts ten minutes and checks that the sign-in coming back from Google is the one that started here. sl_member lasts 14 days and is how the site knows your account, if you have one; signing out removes it. sl_admin lasts 24 hours and is set only for someone signing in to Songlinks’ internal admin console. Signing in to the console also stores the name, email address and Google account identifier that Google gives us, so that a decision recorded there names the person who made it.

When you save writers from the Check writers page, open an invitation link, or open a match link with an IPI name number in it, the page keeps the numbers or the link in your browser’s session storage for that tab, so that they survive signing in. Your browser clears it when you close the tab. The match page also remembers, in your browser only, the relationship you last declared, so you need not choose it again.

Every page loads the Google Analytics script from Google (www.googletagmanager.com) and sends what it records to Google. Apart from that, the pages load nothing from anyone else’s servers, except the API documentation pages (/v1/docs and /redoc), which load their viewers from jsDelivr and an icon from fastapi.tiangolo.com; /redoc also loads fonts from Google. Those services see your IP address when you open these pages.

Songwriters shown on the site

Songlinks shows songwriters’ names as registered, their IPI name numbers, and the works registered to them, taken from public music rights-registration data. Which records belong to the same person is our model’s judgement: it can be wrong, and no person has checked it. Songwriters’ contact details are never shown.

If you are a songwriter and something here concerns you — because it is wrong, or for any other reason — email alex@songlinks.to.

Your choices, and how to contact us

If you have an account, you can download or delete what it stores yourself, from your account page. To ask about any other information we hold about you, or about this notice, email alex@songlinks.to. Our server logs are not kept by person, so it helps to tell us roughly when you used Songlinks and from which IP address.

To stop Google Analytics recording your visits, install Google’s Google Analytics opt-out browser add-on, or use a content blocker that blocks Google Analytics.

Changes to this notice

Songlinks is in beta and will change. When what we collect, how long we keep it, or who handles it changes, we will update this page and the date at the top.