Anti Tapes Privacy

Privacy

This page describes what the code does. Written from the site and the studio as they are, by Anti and without a lawyer. It is part of the terms. If what Anti keeps changes, this page changes with it.

The short version

No accounts, no cookies, no advertising, and no tracking of people. This site and Anti Studio are static pages: sound and themes are made in your browser, and nothing you make or set is uploaded. Only purchases and license recovery reach a server, as described below.

Two things come from outside Anti's own files. Cloudflare, which serves these pages, counts visits: see Visit counts below. And the engine's React example loads React from a public CDN.

What stays in your browser

The site and the studio keep your choices in your browser's storage, on your machine. None of it is transmitted:

Clearing this site's data in your browser removes all of it, and Anti holds no copy: download or save a theme you want to keep.

Theme links

A theme link from the studio carries the whole theme after the #. Nothing is uploaded: there is no theme server, and the fragment stays in the URL. Whoever has the link has the theme.

The microphone

The studio's voice section uses the microphone only when you switch it on, to drive the listening meter and the drone. It is off by default. The signal feeds a level analyser and nothing else: it is never recorded, never played back, and never leaves your machine. The capture is released when you switch it off, scroll the section away, or leave the page.

Visit counts

Cloudflare serves these pages and adds its Web Analytics script to them, loaded from static.cloudflareinsights.com. It tells Anti, as totals: which page was opened, the page that linked to it, the country, the kind of browser, system and device, and how fast the page loaded. The page address is sent without anything after a ? or a #, so a theme link's contents are never part of it.

It sets no cookie and stores nothing in your browser. Cloudflare says it does not fingerprint visitors and that it discards the IP address instead of storing it. Nothing in these counts can be tied to you, to a theme or to a purchase. Blocking the script changes nothing about how the site or the studio works.

When you buy

Checkout runs on Stripe. Your payment details go to Stripe, never to Anti: Anti does not see, receive or store card numbers. Stripe's handling is covered by Stripe's privacy policy.

Anti keeps one purchase row: your email, the checkout session id, the tier, the licensed brand, the terms version the purchase was made under and your agreement to it, Stripe's payment reference (so a refund can mark the row), and the date. When a payment is refunded, Anti also keeps that payment reference and the time of the refund for thirty days, so a refund that arrives ahead of its purchase is not lost. It names no person.

The row exists to send your license key, and to send it again when you ask. The key is permanent, so recovery re-sends the same key to the address that bought it. The recovery endpoint answers the same whether or not an address has purchases, so it cannot reveal who is a customer. For an address with purchases, Anti also keeps the time of the last recovery mail, to limit resends; for any other address, nothing is kept. Your email is used for nothing else: no marketing list, not shared, not sold.

The public register

A registered identity (part of bespoke work) publishes an entry: the brand name, the theme's fingerprint, its signature seed, and the date. The entry is agreed with the client before it is added. Being public and dated is what lets anyone check the exclusivity commitment.

Mail

Mail to hello@anti.fyi is kept as ordinary correspondence. Ask and it is deleted.

Questions

For questions, or to have what Anti holds about you corrected or removed, write to hello@anti.fyi. Unless you have mailed us or bought a license, Anti holds nothing.

Anti Tapes, est. 2016. hello@anti.fyi