The Integration Group (“Integration” or “we”) is committed to protecting the privacy and data of its professionals, clients, suppliers, partners and other entities with which it works. For this reason, Integration assumes a transparent approach in relation to the practices it uses for data collection and storage. Integration’s Cookie Policy (the “Cookie Policy”) describes which cookies and other storage technologies are used, as well as their purposes. Please note that the Cookie Policy does not include the full navigation or use of this website or the other Integration websites. It should be read together with the Terms of Use and the Privacy Policy.
Your acceptance of the Cookie Policy
We ask you to read the Cookie Policy carefully. By accepting the use of cookies on our website, you indicate your full agreement with the Cookie Policy.
What are cookies?
Cookies are text files stored in the browser or on the computer’s hard drive (or other similar devices, including mobile devices) as a result of the websites accessed. In general, cookies are normally used to provide some important information to the website owner about visitors or to allow the websites to run more efficiently. Similar technologies operate in a similar manner, storing information on the device to enable the collection of data regarding how Integration’s website is being used.
Why does Integration use cookies and similar technologies?
Cookies can help you navigate more efficiently on Integration’s website pages, improving your experience. Cookies identify visitors, “understand” their interests, “remember” their preferences and help ensure that the ads and content shown are more relevant to the user. They also show Integration how the site is being used, allow access control to certain content and help to process requests made online.
Integration may also use cookies and similar technologies through marketing automation and lead management platforms to understand interactions with website content, downloads, forms and communications, improve user experience and measure the effectiveness of campaigns.
What types of cookies does Integration use and why?
The cookies on our pages may be first-party cookies (developed by Integration) or third-party cookies. The list of cookies used is presented in the table below.
| COOKIES |
| Type | Name | Duration | Purpose |
| Strictly necessary cookies | cookieyes-consent | 1 year | Stores the user’s cookie consent preferences |
| Strictly necessary cookies | wordpress_logged_in*, wordpress_sec* | Session / up to 14 days | WordPress authentication for logged-in administrators only; not set for regular visitors |
| Strictly necessary cookies | wp-settings-*, wp-settings-time-* | 1 year | Stores WordPress admin interface preferences for logged-in administrators only |
| Functionality cookies | _wpfuuid | Up to 13 months | Set by WPForms on pages with contact forms; used to prevent spam and duplicate submissions |
| Analytics cookies | _ga | Up to 2 years | Google Analytics 4: distinguishes unique visitors to generate anonymous usage statistics |
| Analytics cookies | _ga_EJZYKYZJ9F | Up to 2 years | Google Analytics 4: maintains session state for the site’s analytics property |
| Marketing cookies | rdtrk | 1 year | RD Station: identifies the visitor so that website visits can be associated with a contact who submits a form |
| Marketing cookies | __trf.src | 1 year | RD Station: records the traffic source through which the visitor arrived at the site |
| Marketing cookies | bcookie | 1 year | Browser identifier used by LinkedIn to recognize the device, prevent abuse and attribute site visits to LinkedIn advertising campaigns |
| Marketing cookies | bscookie | 1 year | Secure browser identifier used by LinkedIn for security purposes and to remember the user’s LinkedIn session state |
| Marketing cookies | li_sugr | 90 days | Browser identifier used by LinkedIn for probabilistic matching of visitors for advertising measurement and audience targeting |
| Marketing cookies | UserMatchHistory | 30 days | Used by LinkedIn Ads to synchronize advertising identifiers and track visitors across websites for ad targeting and measurement |
| Marketing cookies | AnalyticsSyncHistory | 30 days | Stores the date of the last synchronization of LinkedIn analytics data |
| Marketing cookies | lidc | 1 day | Used by LinkedIn to route requests to the appropriate data center |
| Third-party cookies (embedded videos) | VISITOR_INFO1_LIVE | 180 days | Used by YouTube to estimate the user’s bandwidth, remember player preferences and personalize recommendations and ads |
| Third-party cookies (embedded videos) | VISITOR_PRIVACY_METADATA | 180 days | Stores the user’s cookie consent and privacy state for YouTube |
| Third-party cookies (embedded videos) | YSC | Session | Used by YouTube to store a unique session ID to track video views and interactions with embedded videos |
| Third-party cookies (embedded videos) | __Secure-YNID | 180 days | Google/YouTube identifier used for security, fraud prevention and to maintain user preferences |
| Third-party cookies (embedded videos) | __Secure-ROLLOUT_TOKEN | 180 days | Used by YouTube to manage the gradual rollout of player features |
| Third-party cookies (embedded videos) | vuid | Up to 13 months | Vimeo: collects analytics on embedded video playback |
| Third-party cookies | __cf_bm | 30 minutes | Set by Cloudflare on behalf of LinkedIn and Vimeo to distinguish humans from bots; does not track users for marketing |
| Similar technologies (local storage) | ic_dl_registered | 180 days | Remembers that the visitor has already completed the registration form to access downloadable content |
| Similar technologies (local storage) | ic_dl_pending | 1 hour | Temporarily stores the requested material between the download click and form completion |
| Similar technologies (local storage) | ata_lead | 2 hours | Pre-fills the assessment questionnaire with information the visitor has already provided |
| Similar technologies (session storage) | rdtracker:token | Session | RD Station: tracking token for the current browsing session |
| Similar technologies (local storage) | li_adsId | Persistent | LinkedIn Ads identifier stored in the browser to attribute conversions to advertising campaigns |
How to refuse the use of cookies?
If you do not want to store cookies on your device, you can click “Decline” in the pop-up that appeared when you started browsing Integration’s website. You can also adjust your internet browser settings to prevent cookies from being stored on your device.
If you do not want to store cookies on your device, you can remove existing cookies and block future cookies with adjustments to your internet browser settings. Please note that the option “do not track” is not recognized by our website.
Remember that deleting, refusing or blocking cookies will impact your user experience, as some features will not be available.
Questions, suggestions or complaints about cookies
If you have any questions, suggestions or complaints regarding use of cookies or similar technologies by Integration, please contact us at:
Privacy Department
Jorge Jamil – Data Protection Officer (DPO)
Rua Jerônimo da Veiga, 45, offices 153/154, Itaim Bibi, São Paulo/SP, Brazil, CEP (Zip Code) 04536-000
Email: privacy@integrationconsulting.com