Privacy Policy

1The short version

ReleaseKit is operated by Agent Creative, a small web studio in Connecticut, USA. In this policy “we” means Agent Creative and “the service” means this website and the ReleaseKit tool on it.

• Your song is opened and analyzed in your browser. It is never uploaded to us.
• We store what you choose to save: your account, your releases, and for a published release page your cover image and a short audio preview.
• We do not sell personal information and we do not run advertising or cross-site tracking.
• To see, correct or delete your data, write to us through the Contact page.

2What stays on your device

The song file you add is decoded by your browser and kept in your browser's own storage on your device so the tool can reopen it next time. The visualizer, the video clips and the announcement graphics are all made on your device. Recorded clips and downloaded graphics go straight to your downloads folder. None of these files are sent to our server.

You can remove what the tool keeps on your device at any time by clearing this site's data in your browser settings.

3What we store on our server

• Account: your name, email address and a password, which is stored only as a salted hash. Your account also holds how many releases you have saved and how many credits you have.
• Saved releases: artist name, title, genre, release date, platform links, the look you chose (style, colors, text), the part of the song you selected (as start time and length, not audio), your edited captions and a small thumbnail of the cover.
• Published release pages: your cover image, resized, and an audio preview of up to 30 seconds that your browser encodes from the part of the song you chose. These two files are public for as long as the page is published.
• Release page numbers: a count of page views, a count of clicks for each platform button, and the email addresses of people who use the “Notify me” box on your page, with the time they signed up.
• Messages: what you send through the contact form (name, email, message).
• Payments: a record that a purchase was completed and how many credits it added. Card details are entered on Stripe's checkout page and never reach our server.

4Visitors to a release page

When someone opens a published release page we count the view and any platform button they tap. To avoid counting the same person repeatedly and to slow down abuse, the server briefly keeps a one-way hash derived from the visitor's IP address; it expires within the hour and is not used for anything else. We do not set advertising cookies on release pages and we do not build profiles of visitors.

If a visitor types their email address into the “Notify me” box, that address is stored with the release and is visible only to the artist who owns the page, who is responsible for how they use it. Visitors who want to be removed from an artist's list can ask the artist, or ask us through the Contact page and we will remove the address.

5Cookies and browser storage

We use only what the service needs to work. When you sign in, WordPress sets login cookies so you stay signed in. The tool also uses your browser's local storage and IndexedDB to remember your working release, your song and the example track on your device. We do not use analytics or advertising cookies.

6Other companies involved

• Stripe processes card payments when you buy credits. Stripe receives your payment details and email address under its own privacy policy.
• OpenRouter is used only if the AI caption option is switched on for this site and you press “Write with AI”. In that case the release details needed to write captions (artist name, title, genre, release timing, the names of your platforms and the link to include) are sent to the AI provider. Your song and cover are not sent. The built-in caption templates send nothing anywhere.
• Our hosting provider stores the data listed above on our behalf and keeps standard server logs (IP address, time, page requested) for security.
• Email delivery: the server sends account emails and, if an artist has it switched on, a notice to the artist when someone signs up on their release page.

The platform buttons on a release page are ordinary links to services such as Spotify, Apple Music, YouTube, Bandcamp and SoundCloud. Nothing is loaded from those services until a visitor taps a button; after that, their policies apply.

7How long we keep things

We keep your account and saved releases until you delete them or ask us to. Deleting a release removes its stored cover, its audio preview, its numbers and its sign-up list from our server. Unpublishing a page takes it offline but keeps the release so you can publish it again. Contact form messages are kept for as long as needed to answer you and keep a record of the conversation. Backups are overwritten on a rolling schedule.

8Your choices and rights

You can edit or delete your releases in the tool at any time. To close your account, get a copy of your data, correct it or have it deleted, write to us through the Contact page from the email address on the account and we will act on it within 30 days. Depending on where you live you may have further rights under laws such as the Connecticut Data Privacy Act, the GDPR or the CCPA, including the right to complain to a regulator. We do not sell or share personal information for advertising.

9Children

The service is not directed at children under 13 and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact us and we will delete it.

10Security

Connections to the service are encrypted. Passwords are stored as salted hashes. Uploaded files are checked for type and size and stored under random file names. No system is perfectly secure; if we learn of a breach that affects your data we will tell you.

11Changes and contact

If we change this policy we will update the date at the top and, for significant changes, tell account holders by email. Questions and requests go through the Contact page.