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 social-post URLs submitted for a requested server download. Source domains can be included in usage diagnostics:

• The capture list — for each audio file the page loaded: its URL, filename, format, size, duration and the domain that requested it. This is cleared when the browser closes.
• 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.

Standard media capture, previews and ffmpeg conversion run in your browser. Media files are downloaded from the source site. For the optional server-assisted social-download flow, the server retrieves the public post requested by you; 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 subscription and payment identifiers issued by Paddle.
• 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. 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 makes to our own account and billing endpoints.

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.
• 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.

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.

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.

4. The permissions the extension asks for

Chrome shows you four. This is the complete list and what each one is for:

• webRequest — to observe that the page just fetched an audio 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.
• 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 TikTok/Instagram downloads that you explicitly request, 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.

For a requested TikTok or Instagram download, we process the public post URL, desired format, a pseudonymous device identifier, a hashed IP address and, when signed in, your account identifier. The resulting media file is stored outside the public web directory and deleted automatically after one hour. Job metadata is retained for quota enforcement and operational security.

6. Payments

Audio Catcher Pro is sold by Paddle, acting as merchant of record. Checkout happens on Paddle's own pages.

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 Paddle we receive only your email address, the name you entered at checkout if any, the subscription and payment identifiers, and the status of the subscription — which is what tells the extension whether to unlock Pro.

Paddle processes your payment data as its own controller, under its own privacy policy. Any tax calculation and invoicing is likewise handled by Paddle.

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 and rate-limit logs, to keep accounts secure and the service available. 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. The capture list clears when the browser closes; 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.
• Social-media output files — for one hour after processing, then automatically deleted.
• Billing records — retained as long as tax and accounting law requires, typically five years.
• Usage analytics — individual events are deleted after 90 days. What outlives them is a daily count per domain, feature and error code, which contains no device identifier and describes no individual.

9. Who else sees it

Service providers receive data as needed for their functions:

• Paddle — payment processing and merchant-of-record duties.
• Resend — sending the transactional emails we do send: a link to set your password, a password reset, and the migration notice for legacy supporters. We send no marketing email.
• 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.