Pro Se analysisAnalysed on

Opera: Private Web Browser

Good overall compliance, with 6 red flags.

The policy scores 82 out of 100 and is graded E. It describes collecting 12 categories of personal data and sharing it with 43 third parties. 3 topics a privacy policy is expected to cover are not addressed.

Download Pro Se App

Source policy: www.opera.com

Pro Se rating: 82 out of 100, Good

82Good

Pro Se Rating
Privacy grade
Grade E
Overall score
82/100
Data categories
12 collected
Third parties
43 shared
Red flags
6 found

Critical attention required

Red flags identified

Our analysis flagged 6 points of concern in Opera: Private Web Browser's privacy policy.

Tracking Across Sites

Analyze outcome:

6/27

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

Vague Language and Ambiguity

Analyze outcome:

6/27

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

Data Collection from Children

Analyze outcome:

6/27

Collecting children's data without necessary parental consent.

Weak Security Measures

Analyze outcome:

6/27

Insufficient information on security protocols to protect user data.

Undefined Retention Timeframes

Analyze outcome:

6/27

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

Extensive Data Sharing

Analyze outcome:

6/27

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

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.

  • User Profile

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

  • Financial

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

  • Communications

    Content of user communications through messaging services or support channels.

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

  • Cookies and Tracking Elements

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

  • Location

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

Data shared with third parties

43
Organisations the policy says data is shared with.
  • Xenforo

  • NexWay SAS

  • PayU

  • Facebook SDK

  • Xsolla

  • Polygon

  • Shopify Inc.

  • Paypal

  • Zendesk

  • MobVista SDK

  • Google Billing Services

  • Amazon Assistant

  • Infura

  • Rapyd

  • Cypix

  • OpenBorder, Inc.

  • Brevo

  • Google AdMob

  • Sendinblue

  • Google Geolocation API

  • Google Ads

  • Mixpanel

  • Solana

  • Freshdesk

  • ML Kit barcode scanner

  • CodeFuel Ltd.

  • Firebase Cloud Messaging

  • Outbrain

  • Fulfilio Sp.z o.o.

  • Stripe

  • Gateway

  • Pangle Ad SDK

  • Opera Group

  • Google Safe Browsing

  • OpenAI

  • AppsFlyer

  • Ronin

  • Mobpower Ad SDK

  • Google

  • Firebase Crashlytics

  • Blueboard Limited

  • Firebase Analytics

  • Near

Purpose of data collection

6 of 10
Understand why your data is requested.
  • Personalization

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

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

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

  • 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

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

  • Archived Data

    Data that is archived for historical or research purposes but is no longer actively used. This might be subject to different security measures and access controls.

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

  • 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

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

4 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 portabilityNot stated
  • Right to object to processingNot stated
  • Right to restrict processingNot stated
  • Right to withdraw consentYes

What the policy does not address

3
Topics a privacy policy is expected to cover that this one leaves out.
  • Right to data portability
  • Right to object to processing
  • Right to restrict processing

Security measures applied to protect the data

5 of 11
Technical and organisational safeguards the policy describes for protecting your data.
  • Secure Data Storage

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

  • Generic Security Assurances

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

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

  • 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

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

How will users be notified about privacy policy changes

3 of 8
The channels and methods used to communicate privacy policy updates to users.
  • In-App Notification

    A message is shown inside the app or service, for example the next time users sign in.

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

4 of 6The lawful grounds under which your personal data is collected and processed.
  • Contractual Necessity

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

  • Consent

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

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

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.

    0 years

  • Age for consent

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

    0 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.
Email
datacontroller@yoyogames.com
Website
opera.com
Address
P.O. Box 4214, Nydalen 0401, Oslo, Norway
Company name
Opera Norway AS

About this application

Platform
Android
Application id
com.opera.browser
Store listing
Store page