Privacy.
quiver collects as little data as possible and never sells your personal data. The details below explain exactly what's collected, by whom, and how to have it removed.
Who runs quiver
Quiver Audio ApS is a registered trade name of Bjørn Aagaard Skalkam ApS, a Danish private limited company (Anpartsselskab) registered at Stampesgade 4, 5. th., 1702 Copenhagen, Denmark, CVR / VAT DK37697850. We are the data controller for the personal data we collect ourselves. Contact support@quiver.fm for any privacy question.
What we collect ourselves
The newsletter. If you sign up, we use your email address to send new plugins, updates and occasional offers from quiver. New subscriptions need email confirmation. Buttondown stores your subscription status, the signup form you used (footer or after purchase), and the date and version of the permission you gave. We also provide your network address to Buttondown to help prevent signup abuse. You can unsubscribe from every newsletter or ask us to remove your address. Buying a plugin, requesting a trial or allowing advertising cookies does not subscribe you.
The notify list. If you ask to hear when a plugin is ready, we store your email address and which plugin you picked. We also send Buttondown the signup page's address when your browser provides it. We don't ask for your name. The list is hosted by Buttondown. You can unsubscribe from any email, and we delete your address on request.
Trials, purchases and your account. When you start a trial or buy a plugin we store your email address, which plugin, when, the Paddle transaction id and the licence we issued (the licence file carries your email, which is how the plugin shows who it is registered to). That is what lets us send your licence, let you download again and answer support questions. Signing in uses a link we email you; a sign-in cookie keeps you signed in.
Email it to my computer. On a phone you can ask us to email you a plugin's link for later. We send that one email and keep the address and the time of the request, and a one-way scrambled form of your network address, only to stop the form being misused, for 30 days. If a creator's link brought you, the address is noted against it as described below.
Who sent you. Some musicians and creators share a link
to quiver and get a share of what we earn when someone they sent buys.
The buyer pays the same price either way. If you arrive through such a
link, we set one cookie of our own, q_vid, holding a random
id, for up to 90 days, and record that the creator's link was used
(never your IP address). If you then start a trial or buy, we note which
creator sent you, and we may link that to your email so the creator is
credited if you buy later from inside the plugin. Creators see counts
and amounts, never who you are. The optional "did someone send you?"
field does the same with whatever you type.
If you're a creator we write to. We contact musicians and creators whose public work fits what we make, at the business address they publish, to offer a free licence. For that we keep your public name, channel link, that public address, a note about your work and where we are in the conversation (sent, claimed, declined). We write at most twice, and every email has a "not for me" link: press it and we never write again. Ask us and we delete what we hold.
Support email. If you write to support@quiver.fm, the contents of that thread are stored in our inbox so we can answer you. Threads are kept for as long as is useful and deleted on request.
Cookies and tracking
Our own cookies. The site remembers your cookie choice
in your browser's local storage, which stays on your device. Signing in sets a
sign-in cookie. Your cart is saved in this browser's local storage so your
selection follows you between pages and visits. It contains only the
selected plugins. Removing a plugin, completing its purchase, or
clearing this site's browser data removes that selection. This is used
for shopping, independently of your marketing choice. A creator's link
sets q_vid, as described above. With marketing permission, a tagged link from an ad or a post is remembered in this
browser for up to 90 days and sent with a checkout or trial request.
Without that permission, tags in the current URL can follow public product links
during your navigation, but are not saved for a later visit. The page of quiver gate remembers that you've pressed its
randomize button.
Source-specific product links. Addresses such as
/carve/meta, /carve/ytshorts,
/carve/reddit and /carve/tiktok use a shared source
label to help us compare which entry routes lead to purchases or trial requests.
The label follows public product navigation and is recorded with your checkout
and order, independently of marketing permission. This flow does not save an
attribution cookie or browser-storage record, use a unique click or visitor id,
or send the label to an advertising network without marketing permission.
It does not establish that you clicked an ad, and does not recognise you on a later visit.
If you allow marketing when starting checkout, this browser also keeps a random receipt for up to 48 hours. It confirms that payment has completed before browser purchase reporting, and lets a later "no thanks" choice cancel unsent checkout and purchase events. It is sent only to quiver, never an ad network, and cannot be used to access your account or licence. With permission naming TikTok or Reddit, their ad click IDs can also be saved in this browser for up to seven days. A refusal clears them.
Marketing tracking is opt-in. Meta, Google Ads, TikTok and Reddit tags load only after you allow "Marketing" in the cookie bar. They can use cookies and browser and network details to measure visits and conversions from our ads. With that permission, our server reports checkout starts and completed purchases to Meta. Meta purchase matching uses a one-way hash of your email. Google Ads receives confirmed purchases with their amount, currency and transaction id, and confirmed trials when that measurement is configured. TikTok receives public-page visits and confirmed purchases with their plugins, amount, currency and transaction id. TikTok stays off account, licence and trial-confirmation pages. Automatic advanced matching and enhanced data postback are disabled. We do not send your email to Google Ads, TikTok or Reddit for enhanced conversion matching. Reddit receives public-page visits, product views, opened checkouts and confirmed purchases with product IDs and an event ID. Confirmed purchases also include their amount and currency. Reddit's first-party cookies are disabled. For a confirmed trial signup, this tab can keep an opaque event receipt for up to 30 minutes, only with permission, and report it when you return to a public page. The receipt contains no email, licence or confirmation token. Reddit stays off private pages. Its automatic advanced matching and enhanced metadata sharing are disabled. An older choice does not enable a newly added partner until you make a fresh choice naming it. Turning off marketing reloads a page that has loaded Reddit so its previously loaded code stops running. If your browser cannot save a refusal, we remember it within the current tab so refreshing does not turn marketing back on. With the original checkout permission, our server can report a confirmed purchase to TikTok or Reddit after you leave the shop, using that partner's ad click ID or TikTok's existing browser ID. This does not load their tags on private pages or send those pages' addresses. We do not add your email, network address or browser description to these server events. Failed Meta, TikTok and Reddit purchase deliveries may be retried with the original event time and transaction id for up to 47 hours. The queued matching details are removed after acceptance or expiry. A later withdrawal stops unsent events when received by our server; it does not undo events already sent. With it off, nothing is loaded and nothing is shared with Meta or any other ad network. You can change your decision any time from cookies in the footer.
Website measurement. We count normal requests for our homepage and product pages in hourly totals. These counts do not use a visitor ID or cookie, and we do not save network addresses, browser details, referrers or URL query strings in this measurement. Known automated requests and prefetches are counted separately. Requests are not unique visitors or proof a page finished loading. With marketing permission, we also count visible page views, actual cart additions, checkout attempts and opened payment windows. These events contain only fixed page, product and source categories. A random ID for each event prevents retry double counting; it does not identify a visitor or session and is removed through scheduled maintenance after 48 hours. Hourly totals are retained for 365 days. We do not send these internal events to advertising platforms. Our ordinary server counts help us operate and improve the shop; browser events stop when you turn off marketing. We do not use Google Analytics, session recordings or fingerprinting.
Services we use
Buttondown (newsletter and release notifications)
Signups and the emails we send are handled by Buttondown. They store your email address, subscription status, signup permission and basic engagement data (opens, clicks) for sending what you signed up for. Older release-notification requests can also include the selected plugin and signup page's address. Those requests stay separate from permission for the ongoing newsletter.
Paddle (payments)
Purchases are made through Paddle.com, our reseller and merchant of record: they take payment, handle tax and send receipts, under their own privacy policy. We never see your card details. Paddle's checkout script loads when you interact with Buy or open a payment link. That script also loads ProfitWell, a Paddle service that measures payments and checkouts for Paddle, under Paddle's privacy policy.
Supabase and Resend (accounts and email)
Accounts, licences, the records above and the plugin records below are stored with Supabase. Licence and sign-in emails are sent through Resend and Supabase.
Meta (only if you allow marketing)
With your consent, the Meta pixel loads in your browser. Our server reports checkout starts with the selected plugins, amount, currency, transaction id, browser details, network address and Meta cookie values when available. It reports completed purchases with the bought plugins, amount, currency, transaction id and your email as a one-way hash for matching. Meta (Facebook and Instagram) processes that under its privacy policy. Without your consent, nothing reaches Meta.
Google (email)
Our email runs on Google's Gmail: the emails we write to creators go out through it, and replies and support email are read and kept there.
Google Ads (only if you allow marketing)
With your consent, Google Ads tags measure visits, confirmed purchases and, when configured, confirmed trial requests. A purchase event includes its amount, currency and transaction id to prevent duplicate reporting. Google can use advertising cookies and browser and network information under its privacy policy. Without marketing consent, we do not load Google Ads tags or send Google Ads conversion events.
Hosting and fonts
The website is hosted by Vercel, which sees your IP address and user-agent in standard server logs. Fonts are served from our own site, so no font service sees your visit.
What the plugins collect
Current versions of the paid plugins send their signed licence to quiver during activation and daily status checks when online. The licence contains your email address, product and licence identifier. We use it to confirm access and issue a permit for up to 30 days of offline use. We also keep a record of every licence check for 30 days: its time, a one-way scrambled (salted) form of the network address it came from, and the computer's device id (below) when the plugin sends one. We use it to limit how often checks can be made and to answer support questions. Checks from a computer that was turned away are recorded too. Our hosting provider sees the request's network address in standard server logs. The plugin also checks quiver for available updates using its product and release channel.
Your computers. Paid plugins (quiver gate after version 1.3.0, quiver roll, quiver mangler and quiver carve) also send these when they activate and check: a device id, which is a one-way scrambled form of the computer's hardware id or, when that is unavailable, a random identifier stored on your computer. The result is different for each plugin, so it can't link your plugins to each other or recognise your computer anywhere else; the name your computer reports, so you can tell your computers apart; whether it is a Mac or Windows; and the plugin's version. We keep them with the dates that computer first and last checked. We use them to let a licence work on up to 3 computers at once, to show you your computers, and in the record of checks above. You see your computers at quiver.fm/account and can remove them there (a computer still in use up to 3 times a month; one you no longer use at any time), or ask support@quiver.fm to remove one for you. Removing a computer deletes its name straight away; if that computer checks in again later, it reports its name again. A computer's whole record is deleted once it hasn't checked in for 90 days. We also note when a computer is removed from a licence, for 90 days, to limit how often that can be done.
None of the plugins collects usage telemetry, DAW analytics or per-session reports. If that ever changes, we'll update this page first. Crash reports are not collected automatically. If you choose to email us a report, you decide what's in it.
Why we may use your data
The law asks for a reason for each use. Ours:
- A contract with you: sending your licence and download, your account and sign-in, a trial you asked for, the licence checks and the computers each licence is on, the one email "Email it to my computer" sends, and answering you when you write.
- Our legitimate interest, weighed against yours: keeping the site, the forms and the licences from being misused (the scrambled network addresses and the 30-day records of checks), crediting the creator whose link sent you, comparing the shared source-specific entry routes recorded with orders and trial requests, and writing to creators about our plugins at the business address they publish.
- Your consent, which you can withdraw at any time: the Meta and Google Ads tags and the conversion events we report to those services, browser storage of campaign tags for later visits, and the notify list.
Outside the EU
Some of the providers above are based in the United States, or use people and servers there: Vercel, Supabase, Resend, Buttondown, Meta and Google. Where your data goes to the United States, the transfer relies on the EU-US Data Privacy Framework for a provider certified under it, and otherwise on the European Commission's Standard Contractual Clauses in our agreement with that provider.
Paddle processes payment data under its own privacy policy. Its controller companies are based in the United Kingdom, United States, Ireland and Canada. Its privacy policy explains its international transfers and safeguards.
Your rights
Under the EU General Data Protection Regulation, you can ask us to:
- tell you what data we hold about you (right of access);
- correct anything that's wrong (right of rectification);
- delete what we hold (right to erasure);
- export your data in a portable format (right to portability);
- object to or restrict how we use it.
Email support@quiver.fm and we'll respond to the request within one month. You can also lodge a complaint with the Danish Data Protection Authority (Datatilsynet) if you're not satisfied.
Changes
If this policy changes materially we'll note it here and update the "last updated" date below.
Last updated: 21 October 2026