Pro Se analysisAnalysed on

YouTube

Good overall compliance, with 4 red flags.

The policy scores 100 out of 100 and is graded C. It describes collecting 9 categories of personal data.

Download Pro Se App

Source policy: www.google.com

Pro Se rating: 100 out of 100, Good

100Good

Pro Se Rating
Privacy grade
Grade C
Overall score
100/100
Data categories
9 collected
Third parties
0 shared
Red flags
4 found

Critical attention required

Red flags identified

Our analysis flagged 4 points of concern in YouTube's privacy policy.

Extensive Data Sharing

Analyze outcome:

4/27

The policy permits broad sharing of data with third parties, often without clear disclosure.

Vague Language and Ambiguity

Analyze outcome:

4/27

Use of broad or unclear terms that provide the service with excessive leeway in data handling.

Personal Data for Unrelated Purposes

Analyze outcome:

4/27

Data used for purposes outside of the service's stated mission without explicit consent.

Lack of Transparency

Analyze outcome:

4/27

Insufficient clarity on what data is collected, its uses, and sharing practices.

What data is collected?

9 of 16
Categories of personal data the policy says are collected.
  • Demographic

    Data such as age, gender, ethnicity, and possibly education level or employment status.

  • User Profile

    Information users provide to create a profile, which might include a username, bio, preferences, etc.

  • Location

    GPS data, IP address-based location, and other geolocation data.

  • Cookies and Tracking Elements

    Information collected through cookies, web beacons, and other tracking technologies used to track user behavior and preferences online.

  • User Online Activities

    Information about how users interact with a website or application, such as browsing history, search queries, and usage patterns.

  • Computer Information

    IP address, browser type and version, operating system, and device identifiers.

  • Personal Identifier

    Data that can be used to identify an individual, such as name, email address, phone number, and government-issued IDs.

  • Contact Information

    Phone numbers, email addresses, and other contact points.

  • Financial

    Encompasses payment information, transaction history, credit card details, and financial account details.

Purpose of data collection

9 of 10
Understand why your data is requested.
  • Transaction Processing

    Personal and payment information is often collected to process transactions and manage billing for services or products.

  • Service Provision

    Data is often collected to provide and improve the services or products that users have requested. This could involve using personal data for account creation, service delivery, or customer support.

  • Marketing and Advertising

    With user consent, data may be used for marketing purposes, such as targeting advertisements or promotions to users who might find them relevant.

  • Personalization

    To enhance user experience, data might be collected to personalize content, recommendations, and features based on individual preferences and behaviors.

  • Communication

    Organizations often collect contact information to communicate with users, such as sending transactional emails, updates, newsletters, or responding to inquiries.

  • Security and Fraud Prevention

    Information might be collected to protect against and detect fraud, unauthorized activities, and other security threats.

  • Legal Compliance

    Organizations may need to collect data to comply with legal obligations, such as maintaining records for regulatory purposes or responding to legal requests.

  • Research and Development

    Data might be used for research and development to innovate and develop new features, technologies, or services.

  • Analytics and Improvement

    Data is used to analyze how users interact with a service or product. This helps in improving user experience, addressing issues, and making informed business decisions.

Data retention periods

4
How long the policy says data is kept.
  • Long-term Retention

    Data retained for several years due to legal, contractual, or business reasons. This might include transaction records, certain legal compliance data, and employee records.

  • Immediate Deletion

    Data that is deleted immediately or as soon as it is no longer needed for processing, such as session data that does not persist beyond a logout.

  • Medium-term Retention

    Data kept for several months to a few years. Examples include marketing data retained until a user unsubscribes or demonstrates inactivity for a certain period.

  • Short-term Retention

    Data retained for a short period, often days to a few months, such as some types of temporary logs or non-essential cookies.

Mobile app permission concerns

Based on the permissions the application requests, beyond what the policy states it collects.
  • No undisclosed data

    The privacy policy discloses every type of data this app's permissions could give it access to.

Your rights

7 of 7 granted
What the policy says about your data protection rights.
  • Right to access your dataYes
  • Right to erasureYes
  • Right to correct your dataYes
  • Right to data portabilityYes
  • Right to object to processingYes
  • Right to restrict processingYes
  • Right to withdraw consentYes

Security measures applied to protect the data

8 of 11
Technical and organisational safeguards the policy describes for protecting your data.
  • Encryption

    Data is encoded so that only authorized parties can read it, in storage, in transit, or both.

  • Secure User Authentication

    Accounts are protected by measures such as strong passwords, two-factor authentication or secure session handling.

  • Secure Data Transfer

    Data is protected while it moves between devices and servers, typically over encrypted connections.

  • Privacy and Security Program

    A formal program of policies, roles and controls the organization maintains to protect personal data.

  • Incident Response

    A defined process for detecting, containing and reporting security breaches, including notifying affected users where required.

  • Data Access Limitation

    Access to personal data is restricted to the staff and systems that need it, for example through role-based permissions.

  • Secure Data Storage

    Personal data is kept in protected systems, such as secured data centers or encrypted databases.

  • Regular Training and Awareness

    Staff receive ongoing training on data protection and security practices.

When will users be notified about privacy policy changes

4 of 8
Circumstances that trigger user notification regarding updates to data handling practices.
  • Introduction of New Services

    New products or features that collect or use personal data in new ways.

  • Legal Compliance Updates

    Changes made to comply with new or amended laws and regulations.

  • Changes in Data Processing

    Changes to how, where or by whom personal data is processed, such as new service providers or storage locations.

  • Privacy-Relevant Changes

    Changes that affect what personal data is collected, how it is used, or who it is shared with.

How will users be notified about privacy policy changes

1 of 8
The channels and methods used to communicate privacy policy updates to users.
  • Update in Privacy Policy Document

    The revised policy is published, usually with a new "last updated" date, and users are expected to check it themselves.

6 of 6The lawful grounds under which your personal data is collected and processed.
  • Legal Obligation

    Processing is needed to comply with a law the organization is subject to.

  • Consent

    The user has agreed to the processing of their personal data for one or more specific purposes.

  • Public Task

    Processing is needed to carry out a task in the public interest or an official function set out in law.

  • Legitimate Interests

    Processing is needed for the legitimate interests of the organization or a third party, unless the user's rights and interests override them.

  • Vital Interests

    Processing is needed to protect someone's life or physical safety.

  • Contractual Necessity

    Processing is needed to perform a contract with the user, or to take steps the user asked for before entering into one.

Children's data

What the policy says about collecting data from children.
  • Addresses data from children

    Whether the policy specifically covers how data from children and minors is handled.

    Yes

  • Collects data from children

    Whether the policy says the service collects personal data from children.

    Yes

  • Minimum age

    The age below which the policy says personal data is not collected.

    13 years

  • Age for consent

    The age the policy gives for obtaining consent to process a child's data.

    13 years

Legal basis for children's data

  • Legal Obligation

    Processing is needed to comply with a law the organization is subject to.

  • Consent

    The user has agreed to the processing of their personal data for one or more specific purposes.

  • Public Task

    Processing is needed to carry out a task in the public interest or an official function set out in law.

  • Legitimate Interests

    Processing is needed for the legitimate interests of the organization or a third party, unless the user's rights and interests override them.

  • Vital Interests

    Processing is needed to protect someone's life or physical safety.

  • Contractual Necessity

    Processing is needed to perform a contract with the user, or to take steps the user asked for before entering into one.

Contact information

Reach out to the data controller for questions, requests, or concerns about your personal data.
Email
https://support.google.com/policies/contact/general_privacy_form
Phone number
N/A
Website
https://policies.google.com/privacy
Address
N/A
Company name
Google

About this application

Platform
Android
Application id
com.google.android.youtube
Store listing
Store page