Privacy Policy

1. Who we are

Audio Catcher (on the Chrome Web Store: "Music and Audio Catcher") is developed and operated by Wesley Dionisio, an independent developer based in Brazil, trading as Sericell. For the purposes of the GDPR and the LGPD, that operator is the data controller for the limited personal data described below.

This policy covers the browser extension and the website at audio.wesleydionisio.online.

2. What stays on your device

Almost everything. The following is written to your browser's local extension storage (chrome.storage.local). Media URLs and filenames in the capture list stay local, except for public post links from supported social video platforms that you submit for a server-assisted download (section 5). Source domains can be included in usage diagnostics:

• The capture list — for each audio or video file the page loaded: its URL, filename, format, size, duration and the domain that requested it. It holds at most 1,000 entries and survives a browser restart; each entry is removed automatically six hours after it was first captured, and you can clear the list yourself at any time.
• Waveform data cached so a file you scroll back to redraws instantly.
• Your settings — default export format, volume, and which one-time tips you have dismissed.
• The free-conversion counter — a date and a number, so the daily MP3 quota can reset at your local midnight.
• Small bookkeeping values — a count of panel openings and a snooze date for the occasional Pro offer, a random identifier used for server-assisted social-link requests, and the details of such a request while it is in progress, so it can resume if the panel closes.

Media capture, previews and ffmpeg conversion of audio caught on regular pages run in your browser, and media files are downloaded from the source site. For a file you request from a link of a supported social video platform, the download may instead be prepared by our server from the public post; see section 5. The extension does not upload local audio files.

Content scripts inspect media elements and relevant media responses to detect and retrieve playable files. Requests made in the page can use its existing browser session. We do not send site cookies, form passwords or unrelated page content to our servers.

3. What we actually receive

If you never buy Pro: no identity, but some usage data

The free plan requires no account and no email address, and analytics events are not associated with your account. What does reach our server without an account is the pseudonymous usage data described under Usage analytics below, plus the request for current subscription prices. The random device identifier allows us to group usage events from the same installation; we do not use these events for advertising.

If you create an account or subscribe

We hold, on our own server:

• Your email address, and a name if the payment provider supplied one.
• A password hash (bcrypt). We never store or see your actual password.
• Your subscription state — plan, status, current period end, whether it is set to cancel — plus the billing provider’s customer, subscription, license and payment identifiers.
• Session records for each device you sign in on: a hashed refresh token, the device label, the IP address and browser user-agent of that sign-in, and when it was last used. We keep these so you can see and revoke sessions, and so a stolen token can be detected.
• A record of emails we have queued or sent you, and the outcome.

Security and rate-limit logs

Requests to our API endpoints are logged with the endpoint, method, IP address, browser user-agent, response code and timestamp — and, for sign-in and password-reset requests, the email address that was entered. This is what enforces rate limiting and lets us investigate abuse. These logs contain no captured audio and no browsing activity — only calls the extension and this website make to our own API. They are deleted automatically after 90 days.

Administrator actions

When we act on an account through our administration panel — for example granting or revoking Pro access, editing account details, resending a sign-in link, signing out its sessions or deleting it — the panel records which administrator did it, when, which account was affected and what changed. This audit log exists so that every change to your account can be accounted for. It is visible only to administrators.

Feedback forms

When you uninstall the extension, Chrome opens a short, optional survey on this website. The extension's Report a problem link opens the same form. When you choose Manage subscription in the extension's Settings, a short page on this website comes before the billing portal, with one optional question about why you might cancel and a button that skips it; the email confirming a cancellation links to the same question. Nothing is stored unless you press send. If you do, we store:

• Your answer — the reason you picked and any comment you typed (up to 500 characters). Please do not put personal information in the comment.
• The site you name, as a domain only — example.com, never the full address.
• Context the extension adds to the link — its version, its language, free or Pro, and, for the uninstall and problem forms, how long it has been installed and how many exports it completed, in rough bands such as "7–29 days" or "5–19".

We do not store your IP address, email address or any device identifier with the answer. The request itself is logged like any other API call (see the logs above), which is how repeated submissions are rate-limited. Answers are deleted after 12 months.

Usage analytics

The extension sends pseudonymous usage data to our own server. There is no Google Analytics, no third-party analytics provider, no advertising pixel and no third-party cookie — on this site or in the extension. Usage data is not sold or shared for advertising; our hosting provider processes it to operate the service. We use it to see which sources people actually download from, which features earn their place, and which downloads are failing so we can fix them.

What a usage event contains:

• What happened — a fixed event name from a published list, such as a download starting, completing or failing, or a button being clicked.
• The source domain only, reduced to its registrable form: cdn.assets.example.com is recorded as example.com. The reduction happens on your device, and the server does it again on arrival.
• Coarse attributes — export format, media type, a size band, a duration band, and an error code from a fixed list when something failed.
• Which in-panel prompt — when the extension shows an upgrade prompt, a request to rate it or a welcome tour step, a label from a fixed list for which one it was, whether it was opened, dismissed or clicked, and whether monthly or yearly billing was chosen.
• A random device identifier generated on your machine, which our server stores only as a keyed hash, plus your extension version and whether the device is on the free or Pro plan.
• Your browser's interface language, reduced to en, pt, es or other.

What a usage event never contains:

• Page addresses, media URLs, query strings, file names or page titles. URLs are stripped out even when they appear inside an error message.
• Your email address, account identifier or name. Usage data is never joined to your account — the plan label indicates free or Pro access, not an account identity.
• Any audio, any part of a page, or anything from a site you did not capture from.

Per-device summary. For each device identifier — in its keyed-hash form only — our server keeps a short summary: the first and last day it was active, the extension version it started with, the interface language it last reported, and the first day it reached each step, such as opening the panel, capturing audio, completing a download, seeing an upgrade prompt or opening checkout. We also note which days it was active. We use these only to measure activation and retention in aggregate — for example, how many installations from a given week were still in use a week later. They are never joined to an account. The summary is deleted 90 days after the device was last active, and each day's activity record after 90 days.

Turning it off. Open the extension's Settings and clear Help improve the extension. That stops collection immediately and discards anything still queued on your device. Everything else in the extension keeps working exactly the same.

This website. Our public pages tell our own server when a page is opened and when an install or pricing button is clicked — which page, its language, which button, the referring site as a domain only, any campaign tag in the link, and whether the window is phone- or desktop-sized — with no cookie, nothing stored on your device and no identifier, and we keep only daily totals of those counts, never your IP address (the request itself is logged like any other API call, as described above).

4. The permissions the extension asks for

The extension declares five. This is the complete list and what each one is for:

• webRequest — to observe that the page just fetched an audio or video file. This is the entire mechanism of the product.
• downloads — to hand a finished file to Chrome's download manager.
• storage — to keep the capture list and your settings on your machine.
• alarms — to remove captured entries automatically once they are six hours old.
• sidePanel — to open beside the page rather than in a popup.

The extension also requests access to all sites. It needs this because audio can be on any page and it cannot know in advance which one you will be working on. What it does with that access is narrow: it watches for media requests. Content scripts inspect media-related page elements and responses, and can retrieve media through the existing page session. They do not collect unrelated form fields or site credentials.

5. Where the extension connects

These are the only outbound connections the extension makes, besides the media URLs themselves:

• audio.wesleydionisio.online — our own API, for prices, account and subscription operations, for files you explicitly request from links of supported social video platforms, and for the pseudonymous usage data described in section 3 (unless you have switched it off).
• A small JSON file of site shortcuts, fetched to populate the panel's shortcut rail.
• Google's favicon service and icon.horse, to display site icons. They receive the requested domain and normal connection metadata such as your IP address. Google Fonts also receives normal connection metadata when loading the interface font.

The audio files you capture are requested from wherever the page you are on serves them, by your own browser, exactly as they would have been anyway.

When you request a file from a link of a supported social video platform, then depending on the platform the file is either prepared in your browser, from the page you have open, or the request goes to our server. In the second case we process the public post link, the file name you chose, the output format, a pseudonymous device identifier and your IP address (both stored only as keyed hashes) and, when signed in, your account identifier. A worker on our server retrieves the public media and converts it with FFmpeg. The resulting file is stored outside the public web directory and deleted automatically about one hour after it is ready.

The request record — the post link, the chosen file name, the format, its status and the hashed identifiers above — is kept to enforce the daily limits, prevent abuse and diagnose failures. It is not currently deleted on an automatic schedule; ask and we will delete the records linked to your account or device.

6. Payments

New Audio Catcher Pro subscriptions are sold by Freemius, acting as merchant of record, and checkout happens on Freemius-hosted pages. Subscriptions started before the provider change remain with their existing provider, including Paddle.

Card numbers, expiry dates and security codes never pass through this website, the extension or our server. We never see them and cannot store them. From the provider, we receive your email address, the name supplied at checkout if any, customer/subscription/license/payment identifiers, the selected plan, payment amount and currency, and billing status — information used to administer the account and determine Pro access.

When you start checkout from the extension, the checkout request includes the internal LOCAL account metadata field and technical labels such as the extension screen and version. The provider returns billing identifiers used to link the purchase to your account. This metadata is not payment-card data. To sign you in right after paying, without creating a password first, the extension also receives a one-time code; our server keeps only a hash of it, tied to that one transaction, and it stops working after its first use or after 24 hours.

Freemius processes new-subscription payment data under its own terms and privacy policy: Freemius Terms and Freemius Privacy Policy. Paddle continues to process payments for subscriptions started before the provider change under its own privacy terms. The applicable provider handles checkout tax calculation and invoicing.

7. Why we are allowed to hold it

Under the GDPR and the LGPD, our legal bases are:

• Performance of a contract — your email address, password hash and subscription state exist so that we can give you the Pro access you paid for.
• Legitimate interests — session records, rate-limit logs and the administrator audit log, to keep accounts secure and the service available; pseudonymous usage analytics and optional feedback answers, to fix problems and improve the product. We have balanced this against your interests and keep the data minimal and short-lived.
• Legal obligation — retaining billing records for the period tax and accounting law requires.

We do not rely on consent for any of the above, and we do not sell or rent personal data to anyone.

8. How long we keep it

• The capture list and settings — on your device only. Each capture-list entry is removed six hours after it was first captured; uninstalling the extension removes the rest.
• Account data — for as long as your account exists. Ask us to delete it and we will, subject to the billing records below.
• Session records — until the refresh token expires (60 days) or you sign out, which revokes it.
• Files prepared on our server from social video links — deleted automatically about one hour after they are ready.
• Records of those requests — the post link, chosen file name, format, status and hashed identifiers; kept for quota enforcement, abuse prevention and diagnostics, and not yet pruned automatically. Ask and we will delete yours.
• Billing records — retained as long as tax and accounting law requires, typically five years.
• Feedback and cancellation answers — deleted automatically after 12 months.
• Website page counts — only daily totals are ever stored; they contain no identifier and describe no individual.
• Usage analytics — individual events are deleted after 90 days. The per-device summary is deleted 90 days after the device was last active, and each day's activity record after 90 days. What outlives them are daily and weekly totals — per domain, feature, error code, extension version, interface language and install day — which contain no device identifier and describe no individual.
• API request logs — deleted automatically after 90 days.
• Administrator audit log — kept while it is needed to account for changes made to accounts; ask and we will tell you what it holds about yours.

9. Who else sees it

Service providers receive data as needed for their functions:

• Freemius — processing new subscriptions and merchant-of-record duties. Paddle continues to process subscriptions started before the provider change.
• Resend — sending our emails: a link to set your password, a password reset, the migration notice for legacy supporters, a welcome and activation reminder after you subscribe, and notices about a failed renewal or a cancellation. Subscribers may also get an occasional offer — a yearly-plan discount, or a note some weeks after a subscription ends — each with a one-click unsubscribe link; unsubscribing does not affect the account emails.
• OVHcloud — hosting the server, located in Europe.

We do not sell personal data, do not share it for advertising, and do not disclose it to anyone else except where the law compels us to.

Because our host is in Europe and our operator is in Brazil, data may be transferred between those jurisdictions. The data involved is limited to the purposes described in this policy.

10. Your rights

Depending on where you live, you have rights to access, correct, delete, restrict or object to our processing of your data, to receive a portable copy, and to complain to a supervisory authority (the ANPD in Brazil, or your national authority in the EU/UK). Californian residents have equivalent rights under the CCPA, including the right to know and to delete — and, since we do not sell data, there is nothing to opt out of.

To exercise any of them, email contato@sericell.com.br from the address on the account. We respond within two business days and complete the request within 30 days. There is no charge.

You can also act without contacting us: sign out to revoke a session, cancel from inside the extension, and uninstall to remove everything held locally.

11. Children

The service is not directed at children and we do not knowingly collect personal data from anyone under 18. If you believe a child has created an account, write to us and we will delete it.

12. Security

The site and API are served over HTTPS only. Passwords are stored as bcrypt hashes and never in plain text. Access tokens are short-lived (15 minutes) and refresh tokens rotate on every use, are stored only as hashes, and are revoked automatically if an already-used token is presented again. The API accepts requests only from the published extension's origin, and sensitive configuration lives outside the web root.

No system is perfectly secure. If you find a vulnerability, please report it to contato@sericell.com.br rather than disclosing it publicly, and we will work with you on it.

13. Changes to this policy

We will update this page as the product changes. The date at the top always reflects the current version. If a change materially affects how we handle your data, we will notify account holders by email before it takes effect.

14. Contact

Wesley Dionisio — trading as Sericell
Brazil
Email: contato@sericell.com.br
Web: sericell.com.br
We reply within two business days.