Privacy Policy • LinkedScope

Who we are

We are LINKUPERS DIGITAL BUSINESS LTDA, registered under Brazilian CNPJ 50.667.466/0001-13, and the operator of LinkedScope, a platform for the intelligent management, analysis, and optimization of advertising campaigns across LinkedIn Ads, Google Ads, and Meta Ads. Our website is: https://linkedscope.com.

For more information about the terms of use of our platform, please access our Terms of Use.

Data Collection

Data Provided by the User

During the use of the LinkedScope platform, we collect data that you provide directly or authorize us to process, including:

Registration information, such as name, email address, and company information.
Profile settings, account configuration, advertising preferences, target companies, target job titles, and campaign preferences.
Contact information managed in LinkedScope, including names, email addresses, telephone numbers, company information, job titles, and other fields provided by you or your organization.
Lead form submissions and information collected through forms configured by you or your organization.
Website attribution and technical information submitted through forms, including campaign parameters and advertising identifiers.

We store this information as necessary to authenticate users, operate LinkedScope, manage contact and lead records, generate reports and insights, synchronize advertising audiences, send conversion events, and provide other features requested by the user.

Data Collected from LinkedIn Ads

When you connect a LinkedIn Ads account, LinkedScope accesses data made available through the LinkedIn API, including the selected advertising account, campaign groups, campaigns, ads, performance metrics, account configuration, lead-generation form submissions, and identifiers required to attribute leads and conversion events.

LinkedIn lead submissions may include names, email addresses, telephone numbers, company information, job titles, form answers, campaign references, and submission identifiers. New lead submissions received from LinkedIn may be stored in LinkedScope as lead records so that users can manage, qualify, report on, and send conversion events for those leads.

When you synchronize a contact audience with LinkedIn, LinkedScope creates an upload file containing the available contact fields required by LinkedIn, including SHA-256 hashed email addresses and available first name, last name, job title, company, country, and related account identifiers. The upload file and derived hashes are generated for the synchronization process and are not retained solely for audience-upload purposes. LinkedScope stores the resulting LinkedIn audience identifier, synchronization status, timestamps, and safe operational errors.

Campaign and performance data retrieved from LinkedIn may be processed temporarily for reports, dashboards, analytics, and optimization features. User-requested reports, lead records, synchronization status, and other operational results may be retained when required to provide the requested service.

Data Collected from Google Ads

When you connect a Google Ads account, LinkedScope accesses Google data made available through the Google Ads API and Google Data Manager API, including:

The selected Google Ads customer account, account identifiers, account currency, timezone, and account configuration.
Campaigns, campaign groups, ads, ad groups, performance information, conversion actions, and advertising metrics.
Google lead form submissions, including submission identifiers, timestamps, campaign and ad references, standard form fields, custom form fields, and click identifiers such as gclid, gbraid, and wbraid when provided by Google.
Contact information selected by the user for Customer Match audiences, such as email addresses and telephone numbers.

LinkedScope uses Google data to connect and manage the selected Google Ads customer, display advertising reports and insights, import Google lead form submissions, create or manage Google Ads conversion actions, send user-requested conversion events, and create or replace Customer Match audiences from contact lists selected by the user.

Google lead submissions may include names, email addresses, telephone numbers, company information, job titles, form answers, campaign references, click identifiers, and submission timestamps. New lead submissions received from Google may be stored in LinkedScope as lead records so that users can manage, qualify, report on, and send conversion events for those leads.

For Google Customer Match, email addresses and telephone numbers are normalized and converted to SHA-256 hashes in memory before being uploaded through the Google Data Manager API. The derived hashes are not retained solely for audience-upload purposes. LinkedScope stores the resulting Google user-list identifier, synchronization status, timestamps, and safe operational errors.

Google campaign, performance, and account data may be processed temporarily for reports, dashboards, analytics, audience operations, and conversion features. Lead records, conversion status, selected account metadata, synchronization status, and user-requested reports may be retained when required to provide the service.

Data Collected from Meta Ads

When you connect a Meta Ads account, LinkedScope accesses data made available through the Meta Graph API and Conversions API, including:

The selected Meta advertising account, Pixel, Facebook Page, and related account identifiers.
Campaign, ad set, ad, performance, and Custom Audience information required for advertising management and reporting.
Lead Ads form submissions received through Page webhooks or synchronized from Meta, including lead identifiers, form fields, campaign references, and attribution information.
Contact information selected by the user for Custom Audience synchronization, including email addresses, telephone numbers, first names, and last names.
Conversion and attribution parameters used by the Meta Conversions API, including event identifiers, event source URLs, browser attribution values such as fbc and fbp when available, IP address, user agent, and other supported lead fields.

LinkedScope uses Meta data to manage advertising accounts and Custom Audiences, receive and import native Meta Lead Ads submissions, report campaign activity, and send user-requested Lead and QualifiedLead conversion events through the Meta Conversions API.

Meta lead submissions may include names, email addresses, telephone numbers, company information, form answers, campaign references, Page and form identifiers, and submission timestamps. New lead submissions received from Meta may be stored in LinkedScope as lead records so that users can manage, qualify, report on, and send conversion events for those leads.

For Meta Custom Audiences, email addresses, telephone numbers, first names, and last names are normalized and converted to SHA-256 hashes in memory before being uploaded when required by Meta. The derived hashes are not retained solely for audience-upload purposes. LinkedScope stores the resulting Meta Custom Audience identifier, synchronization status, timestamps, and safe operational errors.

For Meta Conversions API events, supported identifiers and form fields are normalized and hashed as required by Meta. A normalized IP address may be stored in LinkedScope as encrypted data and decrypted only in memory when a raw IP address is required by Meta. The user agent and available browser attribution parameters may be stored with the lead or processed temporarily for conversion attribution and delivery.

Temporary Processing and Stored Operational Data

Data retrieved from advertising APIs and data submitted to advertising APIs may be processed temporarily while LinkedScope performs an API request, imports a lead, prepares an audience upload, generates a report, or sends a conversion event.

LinkedScope may store the operational information required to provide these features, including contact records, imported lead records, selected account and asset identifiers, audience identifiers and synchronization status, conversion-action identifiers, conversion event status and timestamps, safe provider responses or errors, user-requested reports, and account configuration. Raw API responses and upload payloads are not retained when they are not necessary for the applicable feature.

Browsing Data and Cookies

We use cookies and similar browser technologies to operate and improve LinkedScope, including:

Session and security cookies used to keep users authenticated and protect requests.
Preference cookies used to remember display settings and user preferences.
First-party attribution identifiers used to associate website form submissions with advertising campaigns when available and permitted by applicable consent settings.

Technical information such as IP address and user agent may be collected when a lead is submitted through a website form. IP addresses used for security or conversion purposes are stored in encrypted form where applicable. These technical values are distinct from browser cookies and may be sent to an advertising platform only when required for a feature explicitly enabled by the user.

Cookies and similar technologies may have limited durations and can be controlled through browser settings and applicable consent mechanisms. Disabling required cookies may prevent some platform features from functioning correctly.

Embedded Media

LinkedScope may display embedded content from other platforms, such as videos, images, or advertising-related interfaces. Embedded content from other websites behaves as if you were visiting those websites directly, and those platforms may apply their own privacy policies and terms.

Data Sharing

LinkedScope does not sell or rent users’ personal data. We share data only in the limited circumstances described below, when necessary to provide a feature requested by the user, comply with legal obligations, protect the security of the platform, or operate the service through trusted providers acting on our behalf.

When the user enables an integration, relevant data is exchanged with LinkedIn, Google, or Meta through their official APIs to provide the selected advertising, audience, lead, reporting, and conversion features.
When the user synchronizes a contact audience, the selected contact identifiers are sent to the applicable advertising platform only after the user initiates or authorizes the synchronization and accepts the applicable audience terms.
When the user enables conversion tracking, relevant lead, attribution, and technical data may be sent to the selected advertising platform to report a Lead or QualifiedLead conversion.
We may use infrastructure, hosting, database, monitoring, security, communication, and support providers that process data under contractual confidentiality and data-protection obligations.
In the case of password-reset requests, the IP address may be included in the reset email for security purposes.

We do not transfer Google, LinkedIn, or Meta data for sale, data brokerage, creditworthiness or lending decisions, targeted or personalized advertising unrelated to the user’s account, or generalized artificial-intelligence or machine-learning model training. Automated tools may process advertising data only to provide a user-requested report, analysis, recommendation, or other user-facing feature.

How Long We Keep Your Data

We retain account, configuration, contact, lead, audience synchronization, conversion, and integration data for as long as necessary to provide the requested services, maintain security, comply with legal obligations, resolve disputes, and enforce our agreements.

OAuth credentials and integration tokens are protected using appropriate security controls. Disconnecting an integration stops future access to the provider account but does not by itself delete data already stored in LinkedScope. Data already transmitted to LinkedIn, Google, or Meta may remain subject to the respective platform’s systems, terms, and deletion controls.

Closing a LinkedScope account starts the account-deletion process. We delete or anonymize data from our systems when the closure process is completed, except for information that must be retained for legal, security, fraud-prevention, billing, audit, or dispute-resolution purposes. A request to revoke an integration and a request to delete stored data are separate actions.

Your Rights Regarding Your Data

As a platform user, you have the right to:

Request access to and a copy of the personal data we hold about you.
Request correction or updating of inaccurate or incomplete data.
Request deletion of personal data, subject to legal and operational retention requirements.
Request information about how your data is accessed, used, stored, and shared.
Disconnect an advertising integration and revoke LinkedScope’s future access through the relevant provider.
Submit a separate request for deletion of data stored in LinkedScope.
Withdraw consent or object to processing where applicable under the relevant law.

Disconnecting or revoking an integration stops future access but does not automatically delete data previously stored in LinkedScope or data already transmitted to the provider. To exercise these rights, please contact us through this contact form.

Data Security

We apply appropriate technical and organizational security measures to protect data against unauthorized access, alteration, disclosure, loss, or destruction. These measures may include access controls, encrypted connections, protected credentials, encryption of sensitive stored information, monitoring, logging controls, and least-privilege access.

For audience synchronization, email addresses, telephone numbers, and available names are normalized and converted to SHA-256 hashes in memory before being sent to Google or Meta where required. LinkedIn audience uploads use SHA-256 hashed email addresses together with the available contact fields required by LinkedIn. These audience-upload hashes are not retained solely for upload purposes.

For lead conversion processing, IP addresses stored by LinkedScope are encrypted at rest where applicable, and raw IP values are decrypted only in memory when required by Meta’s Conversions API. Conversion diagnostics stored by LinkedScope exclude the complete live customer-information payload whenever possible. However, no system is completely secure, and we cannot guarantee absolute security.

Changes to This Privacy Policy

We may update this Privacy Policy periodically to reflect changes in our services, integrations, data practices, or legal requirements. We will notify users of significant changes through the platform, by email, or by publishing an updated version on this page.

Contact

If you have any questions or concerns about this Privacy Policy or our data practices, please contact us through this contact form.