Relab plugins send data to unknown amazon server. Here's how you opt out.

[bmanic]

A bit of a scummy move form the company. That's no good. You can opt out by going into the hamburger menu, choose "About" then click the EULA button and scroll with mouse wheel the EULA text, a LONG TIME, all the way to the bottom. Then tick the "Opt out" box and hit OK.

They really should make this whole process a lot more clear and don't try to actively hide it.

/public service announcement

EDIT: Less hostile post and removed the video as I don't want to support that youtuber either.

[Funkybot's Evil Twin]

I mean, it does say on the About link, something like, 'to opt out of data collection read the EULA", so it's not the most hidden thing in the world, but I'd prefer they hadn't put it in the About menu.

[kraster]

I mean, it does say on the About link, something like, 'to opt out of data collection read the EULA", so it's not the most hidden thing in the world, but I'd prefer they hadn't put it in the About menu.

I'm a big fan of Relab's plugins but I'm firmly of the opinion that these kinds of things should always be an opt in situation.

[Funkybot's Evil Twin]

Don't get me wrong. I would prefer it were opt in too.

[db3]

Sonsig Ace has this, but I don't see same menu in Sonsig Rev A, so assume it's a newer development. This sort of underhand practice puts me off supporting companies.

[sl1200mk2]

There's a reply in another forum in the 'Relab 176' thread where the official Relab account summarizes exactly what data they collect and why, if anyone is interested.

Hey all,

I wanted to give a clearer picture of why we collect anonymous usage data and what we’re doing with it.

The short version: it’s been one of the biggest reasons our plugins have kept improving - especially recent plugins like the Relab 176 and Color Drive.

Things like which parameters and features people actually use, where the CPU load spikes, or which setups cause crashes. That’s helped us tighten performance, refine our product decisions, and even make tooltips and UI controls more helpful.

I’ve posted exactly what we collect at the end of this post.

Right now, we fully agree: it’s a bit too much - things like Start/Stop are in there and are completely useless.

At the moment, every single control change can generate an event. That’s overkill, and it’ll be revised in the future so the plugins send far less.

We’ve also noticed that our EULA in the installer doesn’t match the one inside the plugin.

The wording around data analytics should be identical everywhere, and it isn’t right now. We’ll be updating both so they’re fully aligned and crystal clear.

That’s simply a documentation mistake, we’ll fix it so everything lines up.

We want it to be extremely clear that we don’t collect any identifiable information, and we don’t use the data for anything other than improving our products.

Bottom line:
The data is completely anonymous and technical.
We’re reducing what’s collected.
We’re simplifying or removing what we don’t need.
And we’re keeping what actually helps us make the tools better.
Hopefully you’ve noticed the results in the 176 and Color Drive from what we’ve learned.

We’ll keep refining both the plugins and how we communicate about them.

Appreciate everyone here for pushing us to be clearer.

Here as always to answer any questions, and if I can't - I'll get to someone who can. Thanks!!

----------------

Here’s the exact code used by our platform Amplitude for what’s being collected (and NOT being collected):

"_time": 1761592436877,
"$insert_id": "b115d0a17f0f4db294fc2090a322a586",
"$schema": 13,
"amplitude_attribution_ids": null,
"amplitude_id": 942390506733,
"app": 652927,
"city": null,
"client_event_time": "2025-10-27 19:13:56.877000",
"client_upload_time": "2025-10-27 19:13:57.905000",
"country": null,
"data": {
"group_first_event": {},
"group_ids": {},
"path": "/2/httpapi"
},
"device_carrier": null,
"device_family": null,
"device_id": null,
"device_type": null,
"display_name": "preset_changed",
"dma": null,
"event_id": 18229532,
"event_properties": {
"associated_packs": "Drum & Rhythm Color",
"associated_tags": "Drum Bus,Odd-Harmonics,Tape,Parallel,Weight",
"build_number": "42",
"event_version": 1,
"full_parameter_state.autoGain": "0.0",
"full_parameter_state.autoTrim": "1.788139343261719e-7",
"full_parameter_state.bypass": "0.0",
"full_parameter_state.calibration": "40.0",
"full_parameter_state.drive": "100.0",
"full_parameter_state.hpEnabled": "0.0",
"full_parameter_state.hpFreq": "0.0",
"full_parameter_state.input": "1.788139343261719e-7",
"full_parameter_state.interstage": "1.0",
"full_parameter_state.mix": "50.0",
"full_parameter_state.offlineOversampling": 0,
"full_parameter_state.output": "1.788139343261719e-7",
"full_parameter_state.polarity": "0.0",
"full_parameter_state.realtimeOversampling": 0,
"full_parameter_state.tiltFreq": "0.2668508291244507",
"full_parameter_state.tiltGain": "10.0",
"full_parameter_state.tiltMode": "0.0",
"full_parameter_state.xovrType": 1,
"is_factory_preset": true,
"plugin_instance_id": "0586b7edd0ed4f3b881f54924f2bd27e",
"plugin_name": "Relab Color Drive",
"plugin_version": "0.8.3",
"preset_id": "6cab7a7f8dc346c6a2cb5e3ef66562a3",
"preset_name": "Oxide Drum Crush",
"wrapper_type": "AU"
},
"group_properties": {},
"groups": {},
"ip_address": null,
"language": "English",
"library": "http/2.0",
"location_lat": null,
"location_lng": null,
"os": "Mac OSX 14.8.1",
"os_name": "Mac OSX",
"os_version": "14.8.1",
"partner_id": null,
"paying": null,
"plan": {},
"platform": null,
"processed_time": "2025-10-27 19:13:58.876000",
"sample_rate": null,
"server_received_time": "2025-10-27 19:13:57.905000",
"server_upload_time": "2025-10-27 19:13:57.907000",
"session_id": -1,
"source_id": null,
"start_version": null,
"timeline_hidden": false,
"user_id": null,
"user_properties": {
"cpu_architecture": "Apple M2 Pro",
"daw": "Studio One",
"ram_size": "16384"
},
"uuid": "bbc61b36-cbf5-4748-9d87-31d9af0f2d82",
"version_name": null

[ffx]

Well, to fullfil EU law, I think they have to change it to OPT-IN! Just like Native Instruments or Arturia do, AFAIK. A first time popup asking "DO YOU WANNA HELP US?"...

[legendCNCD]

I'll opt-out of buying them

[xmstkvr]

OMG OMG call everyone because a company in 2025 is collecting data from you! Where did you hear this? Oh, YouTube bizarro told me? Where? There...Oh, wait, what?

A plugin developer and course seller who is angry at the competition. Listen, if he can’t even recognize the quality of compression in this plugin, no wonder he resorts to underhanded tactics by badmouthing competitors. Now I see why he is angry and why his course sales aren’t going well. If he thinks this plugin only produces thumps, he shouldn't be surprised that people aren’t buying your courses and that you’re angry at the whole world.

By the way, I agree regarding data collection, but there is an opt-out option. The fact that no one bothers to read the EULA is not the company's problem.

And the real META absurdity of bmanic and everyone else is that you claim you discovered some so-called “evil force,” yet the person who "reported" this is collecting metrics on YouTube's own videos on you while you watched that video hahahaha, and that no one can actually turn off or opt out. Hahahahaha. Btw did anyone actually bother to read what is being collected through the plugin? Of course not! Bikeshedding experts.

And all this happened on a platform that collects x1000 more than the mentioned company.

What a joke!!!!!!!!!!!

Internet knights with stinky legs.

[bmanic]

A plugin developer and course seller who is angry at the competition. Listen, if he can’t even recognize the quality of compression in this plugin, no wonder he resorts to underhanded tactics by badmouthing competitors. Now I see why he is angry and why his course sales aren’t going well. If he thinks this plugin only produces thumps, he shouldn't be surprised that people aren’t buying your courses and that you’re angry at the whole world.

I agree that the Youtuber that the information comes from is a complete douche. It's why I didn't post the link.

However, that doesn't mean an idiot isn't right some times (see my signature. it's there for a reason). And only sheep and people with a weak mind refuse to see wisdom no matter from where it comes from. In this case that certain youtuber, who 99% of the time produces absolute trash, is right. I don't give a shit about his motives.

By the way, I agree regarding data collection, but there is an opt-out option. The fact that no one bothers to read the EULA is not the company's problem.

The opt-out option is purposefully hidden and buried within a thing that isn't obviously a menu. It is deception, 100% on purpose. If you fail to see this fact then you are a gullible fool. Like you said, nobody bothers to read EULAs. This is precisely why we have laws that prevent sneaky bullshit like the exact law of data collection that EU made.

And the real META absurdity of bmanic and everyone else is that you claim you discovered some so-called “evil force,” yet the person who "reported" this is collecting metrics on YouTube's own videos on you while you watched that video hahahaha, and that no one can actually turn off or opt out. Hahahahaha. Btw did anyone actually bother to read what is being collected through the plugin? Of course not! Bikeshedding experts.

There's nothing meta about this at all. The only absurdity is your very strange obsession with this one weird youtuber. You somebody who he hurt with his dumb videos?

And you can opt-out from a lot of google metrics just fine.. but in your case, obviously you jump into whataboutism. Weak tactic of a weak mind.

Internet knights with stinky legs.

.. says the internet tough guy who wants to defend unlawful and unethical practices of a company just because you "like the sound". Actually come to think of it, YOU are the one white knighting in this situation. Pimping for Relab it seems. Sock puppet?

[Nantho]

I just want to chime in to tell that bmanic is one of the most trustworthy person I've ever "met" online. Here at KVR or on other forums , he is and has always been nothing but helpful.

Thank you for everything Mister bmanic

[Kai Enaki]

Regardless of our opinions about data collection, a user has the right to be informed about its existance on first contact (e.g. when accessing a web page or installing software). They also have the right to restrict or object to their data being processed before any data processing starts. These rights have been enforceable within the EU, where Relab Development reside, since 2018 and has come at the cost of billions for those who have been deemed to breach them.

That said. As mush as I dislike companies trying to play hide and seek with data collection, I dislike the "everything is a scam" creator for thinking it's okay to crack Relab's products. There are no excuses for prompting your community into piracy regardless of what you might think of your competition.

[Teksonik]

Hey Relab, here's a radical idea...why don't you improve your products before you sell them to us instead of making us essentially beta test them for you...for free?

First you want to infect my system with ilok to protect your intellectual property then you want to use my bandwidth and CPU cycles to improve your plugins? Anything else I can do for you?

I own hundreds of great plugins from developers who don't require data mining (or iLok) to make them great so maybe you should just learn how to write better code instead of using your paying customers as a crutch.

The fact that data mining goes on with our OS etc is irrelevant to the subject at hand which is developers who think they have a right to do anything they wish to the critical DAW systems of their paying customers.

When we're on Facebook or Google or whatever we have some expectation of data mining but when we just sit down in our studios and fire up our DAWs we should have some expectation of privacy while we work on our intellectual property. Capice?

Imagine a project that uses dozens of plugins and all of them are sending data willy nilly at the same time. At some point there is going to be some degradation of system performance which we all know is critical when working with audio and CPU hungry plugins.

Data mining our DAW systems is not a defensible position, period, no matter what weak argument is presented to the contrary. ReLab is not the only developer guilty of this infraction so to all of those developers who are guilty, GFY.

*Rant Over*....for now.

[enCiphered]

Somewhere in Denmark, a Relab dev just sipped coffee and whispered, "Mission accomplished".

[writheuk]

The same applies to Relapse QuantX...