Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct email for Vungle not listed anywhere publicly #1475

Open
baltpeter opened this issue Oct 18, 2021 · 4 comments
Open

Correct email for Vungle not listed anywhere publicly #1475

baltpeter opened this issue Oct 18, 2021 · 4 comments
Labels
discussion record Issue related to the JSON records

Comments

@baltpeter
Copy link
Member

When you contact privacy@vungle.com (the email listed in their privacy policy), they tell you that it isn't monitored for inbound mail and you should contact GDPR@vungle.com instead.

Usually, I would just update the record accordingly but the problem is that GDPR@vungle.com doesn't seem to be listed anywhere publicly. As our plan is to automatically validate the contact details in the records soon, this is a problem. I also really don't like to list contact details that aren't easily verifiable.

How do we want to deal with this?

One option might be to publicly host their auto-response somewhere and list that as the source. The problem with this is that we would then never notice if this ever changes in the future. The checking tool would always find GDPR@vungle.com listed in our "own" source and assume it's correct.

Hello Benjamin,

Thank you for your email. Note: this inbox is not actively monitored for inbound mail - if you require further assistance, please make sure to follow the instructions below. If your question is not answered below please see the instructions at the end of this email for further information:

I don’t want to see ads

Advertising revenue is a significant factor allowing you to use so many mobile apps and games for free. Although ad networks (like Vungle) help developers of these free apps monetize through advertising, the decisions on whether, when, and how often to show ads are made solely by the developers.

In other words, Vungle has no control over whether the apps you use have decided to monetize through advertising, but we work hard to make the ads you see as interesting, relevant, and engaging to you as possible.

For more information about how we use and manage data in our service, please see our Privacy Policy. (https://vungle.com/privacy/)

I don’t want you to use my data to serve more relevant ads

As stated in our Privacy Policy(https://vungle.com/privacy/), we do not collect information that directly identifies you as an individual (such as your name, email address or physical address). Vungle uses data about your device (such as your Advertising ID, IP address, screen size and orientation, sound settings, make and model, etc.) combined with information about your interaction with our ads to better predict which ads will be of interest to you.

All consumers have the ability to limit what information ad networks (like Vungle) can use to better customize the ads you see by resetting or limiting the use of their Advertising ID. Turning off your Advertising ID will have the following effects:

Vungle will use a generic identifier for your device (i.e. our system will use all zeros), and will not use your device data to build a profile of your device based on the ads we send to you or your interactions with those ads going forward.
You will still see ads, but they will not be customized to you. Turning off the Advertising ID prevents us from learning which types of apps and games that you prefer, so your ad experience may feel more repetitive and less relevant.

Here are simple instructions to reset or turn off the Advertising ID in the settings on your device.(http://vungle.com/opt-out)

As noted above, the decision to show ads is made by the developer of the app you are using, who depends on advertising revenue to support their work and to keep the apps and games you enjoy free to use.

Once you have turned off your Advertising ID, we have no way of associating your device with previous interactions with our service, and all future interactions will be combined with those of every other device with this setting enabled. If you turn on your Advertising ID in the future or reset it now, Vungle will then be able to collect information about your device (including your Advertising ID) for all future interactions. However, it will be a new unique ID and we cannot re-associate your new Advertising ID with any past interactions.
I am an EU resident and want to exercise my data subject rights

If you are a resident of the European Union, you also have the right to request access to or to have us delete any personal information we have collected about you and your device. We have a legal obligation to confirm your identity before responding to your request. If you would like to pursue this option please email us at GDPR@vungle.com.

I am a California resident and want to exercise my data subject rights

If you are a California resident, you also have the right to request access to or to have us delete any personal information we have collected about you and your device. We have a legal obligation to confirm your identity before responding to your request. If you would like to pursue this option please email us at CCPA@vungle.com.

I have a different issue

If you have a question that is not addressed above please send us a detailed description to privacy_inquiries@vungle.com.

We hope that this information was useful to you.

Best regards,

The Vungle Privacy Team

@baltpeter baltpeter added record Issue related to the JSON records discussion labels Oct 18, 2021
@baltpeter

This comment has been minimized.

@baltpeter baltpeter reopened this Oct 18, 2021
@HoffmannP
Copy link

Isn't their webpage a valid source for the E-Mail address? https://vungle.com/blog/gdpr-what-it-is-and-why-it-matters-to-you-part-1-of-3/

@baltpeter
Copy link
Member Author

I'm working on automatic verification of our records that basically goes through all the listed sources and checks whether the email (and other contact details) are (still) listed, with the idea being to detect when a company changes their contact details.

That's why I've disregarded this source. Should they ever change their email, I'd say it's fairly unlikely that they'd update this page since that seems to me like a random one-off blog post that they've probably already forgot about.

But I'm not set on that opinion. I'd be interested what you and other people think about this tradeoff. Should we use the better email that we (likely) can't verify automatically in the future or should we use the email that requires an extra step but can be verified automatically?

@HoffmannP
Copy link

Okey, thanks, now I better understand the issue. I'd propose to add a flag if the address is verifiable as I assume this is not the only case, it's not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion record Issue related to the JSON records
Development

No branches or pull requests

2 participants