Cookie Policy
This Cookie Policy explains how Arrows Software Inc. ("Company," "we," "us," and "our") uses cookies and similar technologies to recognize you when you visit our website at
https://arrows.to, including pages we serve on that domain such as the Sales Skills install page at skills.arrows.to (together, the "Website"). It explains what these technologies are and why we use them, as well as your rights to control our use of them.
In some cases we may use cookies to collect personal information, or information that becomes personal information if we combine it with other information.
What are cookies?
Cookies are small data files placed on your computer or mobile device when you visit a website. Cookies are widely used by website owners to make their websites work, work more efficiently, and provide measurement information.
Cookies set by the website owner (in this case, Arrows Software Inc.) are called "first-party cookies." Cookies set by parties other than the website owner are called "third-party cookies." Third-party cookies enable features such as advertising, interactive content, and measurement. The parties that set these cookies may be able to recognize your browser when it visits our Website and when it visits certain other websites.
Why do we use cookies?
We use first- and third-party cookies and similar technologies for several reasons. Some are required for our Website to operate, and we refer to these as "essential" or "strictly necessary." HubSpot's tracking code loads in a cookies-denied state so that HubSpot can report aggregate page-view and session totals. Before you accept Analytics cookies, HubSpot is instructed not to set a cross-session visitor identifier or associate Website activity with a visitor or CRM contact. With your permission, we use HubSpot and Google Analytics cookies to recognize visits across pages and sessions, understand Website activity, and attribute demo bookings and other conversions. We use the Meta Pixel, the LinkedIn Insight Tag, and HubSpot's advertising category with your permission to measure campaign performance and build audiences for relevant Arrows advertising on other platforms. With your permission, we also use Syft, together with its partner RB2B, to identify the company a visitor works for and, for visitors in the United States, the individual visitor, so that our sales team can follow up on interest in Arrows. Syft uses LiveIntent's identity services and IP-address lookup services as part of this matching. Where this policy refers to your permission, that permission is requested before these cookies are used if you visit from the European Economic Area, the United Kingdom, Switzerland, or California. If you visit from anywhere else, Analytics and Marketing cookies are used by default once the notification banner has been on screen for about ten seconds, unless you reject them first, and you can turn them off at any time as described below.
How can I control cookies?
You have the right to decide whether to accept or reject non-essential cookies. You can exercise your choices in the Cookie Consent Manager. It allows you to select which categories of cookies you accept or reject. Essential cookies cannot be rejected because they are strictly necessary to provide the Website and remember your preferences. If you visit from the European Economic Area, the United Kingdom, Switzerland, or California, non-essential cookies are only used after you accept them. If you visit from anywhere else, the notification banner tells you that Analytics and Marketing cookies are used by default. They start about ten seconds after the banner appears unless you reject them first, and you can reject them there or at any time in the Cookie Consent Manager.
The Cookie Consent Manager appears in the notification banner and can be reopened using the "Cookie settings" link in the Website footer. Your choice is stored for the whole arrows.to domain, so it applies on skills.arrows.to as well and you are only asked once. If you reject Analytics cookies, HubSpot is instructed not to set a cross-session visitor identifier or associate Website activity with your browser or a CRM contact, and Google Analytics does not load through our Website. HubSpot may still report aggregate page views and session counts. If you reject Marketing cookies, the Meta Pixel, the LinkedIn Insight Tag, and Syft do not load through our Website, and HubSpot is instructed not to use advertisement cookies. If your browser sends a Global Privacy Control signal, we treat it as a rejection of Analytics and Marketing cookies: those categories are switched off, cannot be enabled in the Cookie Consent Manager while the signal is present, and any earlier Analytics or Marketing consent is withdrawn on your next visit. You may still use the Website, although some optional functionality may be limited. You may also set or amend your browser controls to accept, refuse, or delete cookies.
The tables below describe cookies and browser-storage entries that may be used through our Website. An entry may not appear for every visitor, and third-party providers may change names, purposes, or expiration periods over time.
Essential website cookies:
These cookies are strictly necessary to provide the Website and remember your privacy choices.
| Cookie or storage name | Provider | Service | Purpose | Expiry |
|---|---|---|---|---|
| arrows_cookie_consent | arrows.to | Arrows Cookie Consent Manager | Stores the cookie categories you accepted or rejected and the applicable consent-policy version. | 182 days |
| __cf_bm | wistia.com | CloudFlare | Cloudflare places the cookie on end-user devices that access customer sites protected by Bot Management or Bot Fight Mode. Set by Wistia's content delivery network when the embedded video player is loaded. | 30 minutes |
| __cfruid | hubspot.com | HubSpot CDN | Supports rate limiting for HubSpot's tracking-code delivery. | Session |
| __cfuvid | hubspot.com | HubSpot CDN | Supports rate limiting and distinguishes users that share an IP address. | Session |
| __cf_bm | hubspot.com | HubSpot CDN | Supports bot protection for HubSpot's tracking-code delivery. | 30 minutes |
Analytics and customization cookies:
These cookies collect information that is used either in aggregate form to help us understand how our Website is being used or how effective our marketing campaigns are, or to help us customize our Website for you.
HubSpot's tracking code can use the __hmpl and hublytics_events_53 browser-storage entries listed below to process tracking events. HubSpot states that these entries do not contain personally identifiable information or information that identifies a device. We instruct HubSpot not to use cross-session analytics identifiers unless you accept Analytics cookies. See HubSpot's current cookie documentation for more information.
| Cookie or storage name | Provider | Service | Purpose | Expiry |
|---|---|---|---|---|
| hubspotutk | arrows.to | HubSpot | This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. | 6 months |
| __hstc | arrows.to | HubSpot | Contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | 6 months |
| _ga_<container-id> | analytics.google.com | Google Analytics | Used to persist session state. | 399 days |
| __hssrc | arrows.to | HubSpot | Used to determine if a session is a new session. | Session |
| _gid | analytics.google.com | Google Analytics | ID used to identify users for 24 hours after last activity. | 24 hours |
| _gat[_<customname>] | analytics.google.com | Google Analytics | Used to throttle the request rate. | 1 minute |
| _ga | analytics.google.com | Google Analytics | ID used to identify users | 399 days |
| __hssc | arrows.to | HubSpot | This cookie keeps track of sessions. | 30 minutes |
| __hmpl | arrows.to | HubSpot browser storage | Stores non-identifying metadata about HubSpot tracking events. HubSpot stores it in session or local storage depending on consent status. | No fixed expiry published; removed when site data is cleared |
| hublytics_events_53 | arrows.to | HubSpot browser storage | Temporarily stores HubSpot tracking events until they are sent over the network. HubSpot states that it does not identify the visitor's device. | No fixed expiry published; removed when site data is cleared |
Advertising and campaign measurement cookies:
If you accept Marketing cookies, we enable HubSpot's advertising category, the Meta Pixel, the LinkedIn Insight Tag, and Syft to measure visits and conversions, understand the effectiveness of our campaigns, create advertising audiences, show more relevant Arrows ads, and identify the businesses and, where permitted, the people visiting our Website. Depending on how you arrived at the Website and your settings with those providers, the technologies may receive information such as the page URL, referring URL, browser and device information, IP address, timestamp, and advertising click identifiers. We do not send the contents of demo forms to Meta or LinkedIn through these pixels. If you accept Marketing cookies and register for an Arrows event, our server also tells Meta about the registration directly, using Meta's Conversions API. It sends the event, the page URL, a one-way hashed (SHA-256) copy of your email address, Meta's own browser and click identifiers, and your IP address and browser details, so Meta can measure our ads when its pixel is blocked. If we later assess that a registration is a good fit for Arrows, HubSpot, our CRM, may send Meta a second event for that registration with a hashed copy of your email address. We send nothing to Meta this way if you have not accepted Marketing cookies.
Syft (Syft Data, Inc.) is a visitor identification service. Syft loads only for visitors in the United States. When you accept Marketing cookies, Syft records the pages you view and matches your visit against business and identity data held by Syft and its partners in order to tell us which company you work for. For visitors in the United States, Syft's RB2B add-on may additionally identify you as an individual, including your name, work email address, and LinkedIn profile, drawing on RB2B's identity data. To perform this matching, Syft loads LiveIntent's identity resolution service and IP-address lookup services, which may set the cookies listed below and receive your IP address, browser information, and the page URL. We use the results to contact companies and people who have shown interest in Arrows. If your browser sends a Global Privacy Control signal, Syft does not load.
For more information about these providers' data practices and current cookie details, see HubSpot's cookie documentation, Meta's Privacy Policy, Meta's Cookie Policy, LinkedIn's Privacy Policy, LinkedIn's Cookie Table, Syft's website, RB2B's Privacy Policy, and LiveIntent's Privacy Policy.
| Cookie or storage name | Provider | Service | Purpose | Expiry |
|---|---|---|---|---|
| _fbp | arrows.to | Meta Pixel | Identifies browsers for advertising delivery, campaign measurement, conversion attribution, and retargeting. | Up to 90 days |
| _fbc | arrows.to | Meta Pixel | Stores a Meta advertising click identifier when a visitor arrives through a Meta ad, supporting conversion attribution. | Up to 90 days |
| li_fat_id | arrows.to | LinkedIn Insight Tag | First-party indirect identifier used for LinkedIn conversion tracking, retargeting, and analytics. | 30 days |
| lms_ads | linkedin.com | LinkedIn Insight Tag | Used to identify LinkedIn members outside LinkedIn for advertising. | 30 days |
| lms_analytics | linkedin.com | LinkedIn Insight Tag | Used to identify LinkedIn members outside LinkedIn for analytics and campaign measurement. | 30 days |
| AnalyticsSyncHistory | linkedin.com | LinkedIn Insight Tag | Stores information about when a synchronization with the lms_analytics cookie occurred. | 30 days |
| li_sugr | linkedin.com | LinkedIn Insight Tag | Supports probabilistic matching of a visitor's identity outside designated countries. | 90 days |
| IDE | doubleclick.net | Google Marketing Platform | This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite | 399 days |
| test_cookie | doubleclick.net | Google Marketing Platform | This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies. | 14 minutes |
| UserMatchHistory | linkedin.com | Used for LinkedIn Ads identifier syncing. | 30 days | |
| bcookie | linkedin.com | Browser identifier used by LinkedIn for abuse detection and diagnostic purposes. | 1 year | |
| bscookie | linkedin.com | Used by LinkedIn to remember that a logged-in member has previously completed two-factor authentication. | 1 year | |
| _gcl_au | adsense.google.com | Google AdSense | Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. | 89 days |
| lidc | linkedin.com | Used to facilitate LinkedIn data-center selection. | 24 hours | |
| syft.anonymous_id | arrows.to | Syft | Identifies your browser across visits so Syft can link page views into one visitor record. | 365 days |
| syft.session | arrows.to | Syft | Identifies your current browsing session for Syft. | 365 days |
| syft.source_touch | arrows.to | Syft | Records the campaign or referrer that brought you to the Website for this visit. | 1 day |
| syft.initial_source_touch | arrows.to | Syft | Records the campaign or referrer that first brought you to the Website. | 30 days |
| _reb2buid | arrows.to | RB2B (via Syft) | Identifies your browser for RB2B's visitor identification. | 360 days |
| _reb2butk | arrows.to | RB2B (via Syft) | Identification token used by RB2B to match your visit to a person. | 365 days |
| _reb2bsessionID | arrows.to | RB2B (via Syft) | Identifies your current browsing session for RB2B. | Session |
| _reb2bgeo | arrows.to | RB2B (via Syft) | Stores an approximate location derived from your IP address so RB2B can determine whether identification applies to your visit. | 20 days |
| _lc2_fpi | arrows.to | LiveIntent (via Syft) | First-party identifier used by LiveIntent's identity resolution service. | 400 days |
| _lc2_fpi_js | arrows.to | LiveIntent (via Syft) | Checks that LiveIntent's first-party identifier can be read by its script. | Session |
| _li_dcdm_c | arrows.to | LiveIntent (via Syft) | Records the domain LiveIntent's identifier was set on. | Session |
| YSC | youtube.com | YouTube | Registers a unique ID to keep statistics of what videos from YouTube the user has seen. | Session |
| VISITOR_INFO1_LIVE | youtube.com | YouTube | Tries to estimate the users' bandwidth on pages with integrated YouTube videos. | 179 days |
How can I control cookies on my browser?
As the means by which you can refuse cookies through your web browser controls vary from browser to browser, you should visit your browser's help menu for more information. The following is information about how to manage cookies on the most popular browsers:
In addition, most advertising networks offer you a way to opt out of targeted advertising. If you would like to find out more information, please visit:
- Digital Advertising Alliance
- Digital Advertising Alliance of Canada
- European Interactive Digital Advertising Alliance
Embedded video and audio
Articles on our Website can contain videos hosted by YouTube, podcast episodes hosted by Transistor, and product videos hosted by Tella and by Wistia. None of these load when you open a page. Each one appears as a placeholder with a play button, and the provider is contacted only when you press it. If you do not press play, no request reaches that provider and none of its cookies are set. Pressing play loads the provider's own player, which may then set the cookies described in the tables above. For YouTube we use the privacy-enhanced player at youtube-nocookie.com.
We embed video on our Website using Wistia (Wistia, Inc.). The Wistia player is only loaded if you click to play the video; until then, no request is made to Wistia and no video is loaded. Because the player is loaded only at your request, it is not gated behind a cookie category in our Cookie Consent Manager. Loading the player causes Wistia’s content delivery network to set the Cloudflare __cf_bm cookie listed above.
The player itself does not set cookies. It stores two entries in your browser’s local storage, wistia and wistia-video-progress-<video id>, which remember player preferences and how far through a video you watched, so playback can resume where you left off. You can remove these at any time by clearing your browser’s site data for our Website. For details of how Wistia handles this information, see the Wistia Privacy Policy.
Booking a demo
Our demo booking page uses RevenueHero (Hero Software Labs, Inc.) to show available times and route your request to the right person. RevenueHero loads on that page without waiting for a cookie choice, because booking a meeting is the only function of the page and the scheduler cannot work without it. It is not used for advertising, and it does not run on any other page of our Website. RevenueHero sets its own cookies when it loads; see the RevenueHero Privacy Policy for details.
What about other tracking technologies, like web beacons?
Cookies are not the only way to recognize or track visitors to a website. We may use other, similar technologies from time to time, like web beacons (sometimes called "tracking pixels" or "clear gifs"). These are tiny graphics files that contain a unique identifier that enables us to recognize when someone has visited our Website or opened an email including them. This allows us, for example, to monitor the traffic patterns of users from one page within a website to another, to deliver or communicate with cookies, to understand whether you have come to the website from an online advertisement displayed on a third-party website, to improve site performance, and to measure the success of email marketing campaigns. In many instances, these technologies are reliant on cookies to function properly, and so declining cookies will impair their functioning.
Do you use Flash cookies or Local Shared Objects?
Websites may also use so-called "Flash Cookies" (also known as Local Shared Objects or "LSOs") to, among other things, collect and store information about your use of our services, fraud prevention, and for other site operations.
If you do not want Flash Cookies stored on your computer, you can adjust the settings of your Flash player to block Flash Cookies storage using the tools contained in the Website Storage Settings Panel. You can also control Flash Cookies by going to the Global Storage Settings Panel and following the instructions (which may include instructions that explain, for example, how to delete existing Flash Cookies (referred to "information" on the Macromedia site), how to prevent Flash LSOs from being placed on your computer without your being asked, and (for Flash Player 8 and later) how to block Flash Cookies that are not being delivered by the operator of the page you are on at the time).
Please note that setting the Flash Player to restrict or limit acceptance of Flash Cookies may reduce or impede the functionality of some Flash applications, including, potentially, Flash applications used in connection with our services or online content.
Do you serve targeted advertising?
Third parties may serve cookies on your computer or mobile device to serve advertising through our Website. These companies may use information about your visits to this and other websites in order to provide relevant advertisements about goods and services that you may be interested in. They may also employ technology that is used to measure the effectiveness of advertisements. They can accomplish this by using cookies or web beacons to collect information about your visits to this and other sites in order to provide relevant advertisements about goods and services of potential interest to you. The information collected through this process does not enable us or them to identify your name, contact details, or other details that directly identify you unless you choose to provide these.
How often will you update this Cookie Policy?
We may update this Cookie Policy from time to time in order to reflect, for example, changes to the cookies we use or for other operational, legal, or regulatory reasons. Please therefore revisit this Cookie Policy regularly to stay informed about our use of cookies and related technologies.
The date at the top of this Cookie Policy indicates when it was last updated.
Where can I get further information?
If you have any questions about our use of cookies or other technologies, please contact us at help@arrows.to.