Legal / Privacy
Privacy policy
Clap Studio has no analytics, no tracking and no advertising, and it never uploads anything without a click. This website sets no cookies and loads nothing from other sites.
Pending
The legal part of this policy is not published yet. It will come from a legal text service and name who is responsible for your data, why each item is kept, your rights and how to use them, and where to complain.
What follows is already complete and exact: every connection the app makes, what it sends, who keeps it and for how long. Questions go to [email protected].
What never leaves your Mac
- Your samples and recordings. Audio files are read where they are; analysis (similarity, categories, moods, species in field recordings, noise reduction) runs on your Mac with models that ship inside the app.
- Your library. The database, collections, tags, cues, trims, drum patterns and melodies stay in
~/Library/Application Support/ClapStudio/. - What you play into the microphone. Listen (search by humming) uses the recording for one search and deletes it. Nothing is kept or sent.
- How you use the app. There is no usage counting, no phoning home and, once a Mac is activated, no licence check: the app works offline for good.
Update checks and downloads
- Servers:
api.github.com(the latest public release),github.com,objects.githubusercontent.comandrelease-assets.githubusercontent.com(the download and its checksum, which GitHub redirects to its file servers). Once the signed update feed is switched on, the check downloadsrelease-feed.jsonfromgithub.cominstead of askingapi.github.com; the servers and what is sent stay the same. - When: when the app opens and once a day while it is open, when you choose Check for Updates…, and when you click Update. Development builds never check.
- Sent: your IP address and the request header
User-Agent: ClapStudio/<version>. Nothing about your samples or library. - Kept: GitHub keeps its server logs under the GitHub General Privacy Statement. The app stores only the date of the last check and a release you chose to skip, on your Mac.
- Switch: Check for updates automatically in Settings > General (and Settings > Privacy), on by default. When it is off the app never checks by itself; Check for Updates… still works when you ask.
Maps and place search
- Servers: Apple's map servers, chosen by Apple's MapKit framework (the app names no host itself).
- When: only while a map is on screen (the Places tab, Recorded at in a field recording's properties, the place picker) and when you type into place search.
- Sent: your IP address, the area the map shows, and the words you type into place search. Apple says Maps does not tie these to your Apple Account.
- Kept: by Apple, under the Apple Privacy Policy and Maps & Privacy.
- Switch: none: Places needs a map. Nothing is fetched until you open one, and the places themselves are read from your files on the Mac.
Opening a place in Maps
- Servers:
maps.apple.com, opened by the Maps app (or your browser). - When: only when you click a recording's map or choose Open in Maps.
- Sent: the coordinates and the recording's name, which Maps shows as the pin's label.
- Kept: by Apple, as above.
Help, questions and problem reports
- Servers:
clap-studio.tommasoamici.comfor the user guide, andgithub.com, in your browser. - When: only when you choose Clap Studio Help, Ask a Question… or Report a Problem… in the Help menu.
- Sent: Clap Studio Help opens the guide on the website, which sends only your IP address and the page you read, kept in the website's logs as below. Report a Problem… opens a new issue form with the app version, macOS version and Mac model already filled in. Nothing is posted until you click GitHub's own submit button.
- Kept: everything posted on GitHub is public and needs a GitHub account. It goes through GitHub, GitHub's terms and privacy statement apply, and it stays until you or a moderator delete it. Never post licence keys or personal data there; use email for anything private.
Email to support
- Servers: none from the app: Email Support… opens a draft in your own mail app, which sends it through your mail provider when you click Send.
- When: only when you choose Email Support…, or paste Copy Diagnostics into an email yourself.
- Sent: what you write. The draft starts with the app version, macOS version and Mac model. Copy Diagnostics adds model status, the number of files in the library and the app's recent log, with no file paths or file names. You see all of it before you send.
- Kept: while helping you and for up to two years after, then deleted; emails about a purchase are kept as long as Dutch tax law requires for the invoice (7 years). (To confirm with the business and legal roadmap.)
Crash reports you choose to send
- Servers:
crash-reports.example.invalid(placeholder until the server is deployed), run by the seller on the same server as the licence service. - When: only when you click Send in the window that appears after the app crashed or stopped responding. macOS collects the diagnostic on your Mac (MetricKit); nothing is sent automatically, and Don't Send deletes it.
- Sent: exactly the report shown in the preview: app version, macOS version, Mac model, the kind of crash and where in the app's code it happened. File paths and file names are removed before the preview, so what you see is what is sent. Copy Report lets you email it yourself instead.
- Kept: stored as a plain file, not linked to you, and deleted automatically after 90 days. Your IP address is held in memory only to limit repeated uploads (at most one hour) and is never written to disk or logs.
Licence activation
- Servers:
licence.clapstudio.example.invalid(placeholder until the licence service is deployed). - When: once per Mac, when you activate a licence, and when you deactivate a Mac. After that the app never needs the network again.
- Sent: the licence key, a salted hash of the Mac's hardware identifier (the identifier itself never leaves the Mac), the computer name if you choose to send it, the app version and your IP address.
- Kept: the key, Mac hash, computer name and activation dates, for as long as the licence exists, so the 5-Mac limit and gift redemption work. IP addresses are used only to limit abuse and are not stored. The rules are in the payments roadmap.
Buying, gifts and managing Macs on the website
- Servers:
clap-studio.tommasoamici.com, the website, in your browser. - When: only when you click Buy Licence…, open a gift link, choose to manage your Macs, or use offline activation. The app hands the link to your browser.
- Sent: your IP address, and the gift code when you open a gift link. The website's pages remove the gift code or link token from the address bar once read, and send only what you type in them to the licence service above: Redeem a gift sends the gift code and your email address, Get a link to your Macs and Send my licence key again send your email address, the emailed link to your Macs sends its token (and the Mac you remove), and Activate a Mac offline sends the request code, which holds what online activation sends: the key, the Mac's hash and its computer name. No cookies are set and nothing is stored in the browser.
- Kept: the website's server logs are deleted after 14 days. Payment details go to the shop that sells the licence, not to the website. The licence service keeps what Licence activation lists, plus the email address a gift was redeemed with, and management-link tokens (hashed, for 24 hours).
Outside the app
These are not made by the app, but they are part of buying it and getting help.
- The merchant (checkout). When you buy a licence, the merchant of record (who sells it to you, and handles payment, VAT, invoices and refunds) receives your name, email, billing country, payment details and IP address. The merchant is the seller and keeps them under its own privacy policy. The licence service receives only the order number, your email and the licence it creates.
- The website. The web server keeps standard access logs (IP address, page, time, browser) to keep the site running, and deletes them after 14 days (to confirm when the site is deployed). The site has no cookies, analytics or third-party scripts.
- GitHub. The public repository (issues, discussions, release downloads) is hosted by GitHub; see above.