AdsWizz Opt Out: Privacy Email and Podcast Ad Preferences
Use AdsWizz’s privacy contact to request an opt-out or deletion. Check podcast preference limits, device matching and the meaning of its timing claims.

To request an AdsWizz opt-out or deletion, contact dpo@adswizz.com using the privacy-rights route in its platform policy. Podcast listeners can also use the advertising-preference tool where it is supported. That tool’s scope is the relevant publisher or podcast platform, and its stated 48-hour processing is not a promise that every AdsWizz dataset is deleted within two days.
This guide uses the AdsWizz platform policy and public browser checks from September 22, 2026. The standalone podcast-preference page returned a 403 error in our session. The policy and its privacy-email route were accessible, so the steps below rely on those verified instructions rather than unseen form controls.
AdsWizz opt out quick facts

| Goal | Route | Scope to remember |
|---|---|---|
| Ask for deletion, access or a privacy opt-out | dpo@adswizz.com | Identify the platform/device context |
| Change supported podcast ad preferences | Publisher tool or AdsWizz podcast preference page | U.S. and Canada excluding Quebec, according to the policy |
| Adjust website tracking | AdsWizz cookie controls | Separate from platform data-rights requests |
| Understand processing time | Check the applicable request response | 48-hour wording belongs to the podcast preference tool |
| Reduce collection through an app | Review the app’s own privacy settings | Does not prove historical deletion elsewhere |
AdsWizz provides technology for audio advertising across podcasts, streaming and radio. Its platform notice describes device and cookie identifiers, IP addresses, playback logs, approximate location and advertising-related information. These records differ from a public directory listing of your home address.
The data broker overview explains that distinction. A name search that finds no public AdsWizz page cannot establish whether pseudonymous advertising data exists.
How to submit an AdsWizz request
Step 1: Start with the platform privacy policy
Read the AdsWizz platform policy if your concern involves ads delivered through an app, publisher or podcast. The corporate website privacy policy addresses a different context. Keep the relevant app or publisher name available so you can explain where the processing arose.
The policy identifies dpo@adswizz.com for privacy inquiries and rights requests. It describes rights that vary by location and circumstances. This is a practical account of the provider’s route, not a guarantee that every request must result in total deletion.
Step 2: Describe the data and action
Write a clear subject such as a platform-data opt-out or deletion request. Explain the action you want, the app or podcast service involved and your jurisdiction where relevant. Ask which identifiers are necessary to locate your records securely.
Because the platform processes pseudonymous identifiers, a name alone may not be enough. The inspected policy does not establish one universal required identifier set for every email request. Do not send a passport, entire browsing history or unrelated account password to compensate for uncertainty.
Step 3: Verify only through the official route
If AdsWizz asks for additional matching or verification information, check that the communication corresponds to the request you initiated. Ask why an identifier is needed if its relevance is unclear. Use the company’s published privacy contact to confirm an unexpected request before providing sensitive material.
No privacy email was sent for this article. We therefore cannot describe a verified confirmation sequence, guarantee a particular response time or claim that an agent accepted a test case.
Step 4: Retain the outcome and its limits
- Save the original request date, subject and relevant app or publisher.
- Keep any case reference and verification correspondence privately.
- Ask whether the outcome is a preference change, deletion or another action.
- Record which identifiers and publisher environments the response covers.
Our broader broker removal process helps track the difference between a submitted request and a completed action.
How the podcast advertising preference works
The platform policy describes a Podcast Consent Management Tool for listeners in the United States and Canada, excluding Quebec. It says submitted preferences are processed within 48 hours and a confirmation email follows activation. That statement belongs to this tool; it should not be reused as a deadline for unrelated access or deletion requests.
The policy also says the preference applies to the specific publisher or podcast platform where the tool is offered. You can still receive ads, and unrelated properties may not be covered. An ad supported by the podcast’s subject matter can continue without using the same personalized targeting.
The podcast preference page was discoverable but returned a 403 during our browser check. If it loads for you, follow the instructions shown there. If it fails, describe the issue to the privacy contact or use the publisher’s available controls. Do not assume visiting a blocked page recorded an opt-out.
The AdsWizz cookie policy provides another set of controls. Browser cookies, podcast preferences and a direct deletion request are distinct mechanisms. Choose the combination appropriate to your concern rather than treating a cookie banner as proof of database-wide erasure.
Processing time and recurring exposure
AdsWizz’s platform policy describes ordinary retention of pseudonymous data for up to 90 days, followed by deletion or anonymization. This is a description of its retention practice, not a timer you can use to prove the outcome of an individual request. Different processing purposes and legal exceptions can affect a response.
If you follow up, ask for the status of the action you requested and the identifier it covers. A message saying a preference was saved should not be interpreted as confirmation that all historical records and partner copies were erased. Equally, an account with a podcast publisher may retain records outside AdsWizz’s control.
New devices, changed identifiers, separate publishers and renewed consent can change the context of later advertising. Review app permissions and preferences after a device change. Keep any confirmed opt-out details so you can ask a focused question if the same processing appears to recur.
Related advertising-data processes are covered in our Lotame guide, The Trade Desk guide and LiveRamp guide. They concern separate companies and are relevant only when those companies are involved. One audio-ad request does not automatically update those providers.
Frequently asked questions
Will opting out stop all podcast advertisements?
No. The policy says ads may continue with less personalization. A podcast can sell contextual ads or use other advertising systems. The useful question is which personal-data processing was changed, not whether an episode contains any commercial message.
Is the podcast tool available worldwide?
The inspected policy specifies the United States and Canada excluding Quebec for that tool. Other rights and routes can depend on location. Readers elsewhere can contact the privacy team about their situation without claiming eligibility for a tool that names a narrower scope.
Should I close my podcast account first?
Closing an account is a separate decision and can affect access to saved content or subscriptions. The documented AdsWizz email route does not require you to close a publisher account as a universal first step. Ask about the relevant data and identifiers before taking unrelated actions.
Does the 48-hour statement cover deletion requests?
It describes preference processing in the podcast tool. The policy does not establish that every deletion request uses that same deadline. Ask for request-specific timing and keep verification or receipt separate from completion.
How do I check other kinds of exposure?
Browse the opt-out topic hub for specific companies. A free data broker scan can check supported public listings, but it cannot certify deletion of private audio-advertising records. Use each source’s own response to assess its request outcome.
Sources and verification notes
Primary sources checked September 22, 2026: the AdsWizz platform policy, its published privacy contact, cookie-policy link and standalone podcast-preference route. The platform policy is dated August 21, 2025. Browser evidence documents accessible policy text and the blocked tool. No email, form submission, account connection or removal test was performed.
Continue reading
Related privacy guides
Norton vs EasyOptOuts Data Removal: Cost and Request Effort
Compare Norton Privacy Monitor Assistant and EasyOptOuts on annual cost, request effort, supported sites and privacy using current official sources.
Read articleAltair Data Resources Opt Out: Form and Deletion Steps
Use Altair Data Resources’ consumer portal to request an opt-out or deletion. Check required fields, postal options, verification and agent rules.
Read articleAdsquare Opt Out: Device ID, Privacy Form and Deletion
Request an Adsquare opt-out or deletion using its Privacy Center. Learn why a device advertising ID matters and which personal details to avoid.
Read article