Link Messenger

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.

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.

Biometric Data

Fingerprints, facial recognition data, or other biometric identifiers.

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.

Communications

Content of user communications through messaging services or support channels.

Google Cloud Platform

Amazon Web Services

Google Play

Apple

Google

App Store

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.

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.

Security and Fraud Prevention

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

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.

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.

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.

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.

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.

Demographic

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

Data Access Limitation

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

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.

Privacy-Relevant Changes

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

Business Changes

Changes to the organization itself, such as a merger, acquisition or sale of assets, that may affect how data is handled.

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.

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.

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.

No

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.

16 years