Pro Se analysisAnalysed on

Chrome Beta

Good overall compliance, with 7 red flags.

The policy scores 100 out of 100 and is graded D. It describes collecting 12 categories of personal data and sharing it with 1 third party.

Download Pro Se App

Source policy: policies.google.com

Pro Se rating: 100 out of 100, Good

100Good

Pro Se Rating
Privacy grade
Grade D
Overall score
100/100
Data categories
12 collected
Third parties
1 shared
Red flags
7 found

Critical attention required

Red flags identified

Our analysis flagged 7 points of concern in Chrome Beta's privacy policy.

Tracking Across Sites

Analyze outcome:

7/27

The service tracks users' activities on third-party websites, indicating extensive data collection.

Vague Language and Ambiguity

Analyze outcome:

7/27

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

No Data Access or Correction Rights

Analyze outcome:

7/27

Users lack the ability to view or correct their personal data.

Reading Private Messages

Analyze outcome:

7/27

The service has the ability to access and read your private communications.

Undefined Retention Timeframes

Analyze outcome:

7/27

Absence of specified periods for data retention or reasons for keeping data.

Extensive Data Sharing

Analyze outcome:

7/27

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

Identity Used in Ads

Analyze outcome:

7/27

Users' identities or likenesses are used in advertisements shown to others.

What data is collected?

12 of 16
Categories of personal data the policy says are collected.
  • Computer Information

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

  • Demographic

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

  • Social Media Information

    Data obtained from users' social media profiles or activity, if integrated with the service.

  • Personal Identifier

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

  • Purchase and Order History

    Specific financial information detailing items bought or services contracted.

  • Financial

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

  • Health Information

    Information related to health or medical conditions, if applicable.

  • Contact Information

    Phone numbers, email addresses, and other contact points.

  • User Online Activities

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

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

  • Communications

    Content of user communications through messaging services or support channels.

Data shared with third parties

1
Organisations the policy says data is shared with.
  • Lumen

Purpose of data collection

9 of 10
Understand why your data is requested.
  • 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.

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

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

  • Security and Fraud Prevention

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

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

  • 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

5
How long the policy says data is kept.
  • User-Controlled Retention

    Information that users have control over in terms of when or if it is deleted, such as data stored in user accounts that can be deleted by user action.

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

  • Permanent Retention

    Information that is retained indefinitely, often until the user requests deletion or the service is terminated. This might apply to essential account information for active users.

  • Regulatory Compliance

    Data retained specifically to meet regulatory requirements, where laws dictate specific timeframes, such as tax records or data related to legal disputes.

  • 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

2
Based on the permissions the application requests, beyond what the policy states it collects.
  • User Profile

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

  • Biometric Data

    Fingerprints, facial recognition data, or other biometric identifiers.

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

9 of 11
Technical and organisational safeguards the policy describes for protecting your data.
  • 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.

  • Privacy Audits and Reviews

    Regular internal or external audits and reviews that check how personal data is handled and protected.

  • Generic Security Assurances

    The policy states that data is protected but does not describe the specific measures used.

  • Incident Response

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

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

  • Secure User Authentication

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

  • Encryption

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

When will users be notified about privacy policy changes

3 of 8
Circumstances that trigger user notification regarding updates to data handling practices.
  • Privacy-Relevant Changes

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

  • Minor Updates and Clarifications

    Editorial changes, such as corrected wording or clarifications, that do not change how data is handled.

  • Consent Requirements

    Changes that require users to give, renew or withdraw their consent.

How will users be notified about privacy policy changes

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

  • Website Announcement

    A notice is posted on the service's website, such as a banner or a news page.

  • Email Notification

    Users are told about the change by email, at the address linked to their account.

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

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

  • Vital Interests

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

  • Legal Obligation

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

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

  • 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

  • Consent

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

Contact information

Reach out to the data controller for questions, requests, or concerns about your personal data.
Website
privacy.google.com
Address
1600 Amphitheatre Parkway, Mountain View, California 94043, USA
Company name
Google LLC

About this application

Platform
Android
Application id
com.chrome.beta
Category
Productivity
Store listing
Store page