Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

Have the Government-Sponsored Enterprises Fully Repaid the Treasury?

Federal Reserve Bank of AtlantabyFederal Reserve Bank of Atlanta
March 24, 2014
in Archive
Reading Time: 11 mins read
0
Share on Facebook

Have U.S. taxpayers been fully compensated for their bailout of the government-sponsored enterprises (GSEs) Fannie Mae and Freddie Mac? The Treasury isreported to have argued that “the value of Treasury’s commitment to the GSEs was “incalculably large,'” with the implication that it could never be repaid.Richard Epstein, the Peter and Kirsten Bedford Senior Fellow at the Hoover Institution, responded that “the level of the Treasury commitment was not ‘incalculably large’: it was $188 billion, all of which will shortly be repaid.” The significance of Epstein’s argument is that if Treasury has been fully compensated for its bailout of Fannie and Freddie, a case can be made that the future profits of the two GSEs should go to their private shareholders.

Fannie and Freddie logosAs an accounting matter, one could argue that Epstein is correct; the dividends equal the amount of Treasury funds provided to the GSEs. And as a legal matter, the issue may ultimately be resolved by the federal courts. However, as an economic matter, the value of the government’s contribution clearly exceeds $188 billion once the risk borne by taxpayers is taken into account.

In this Notes from the Vault I examine the value of the taxpayers’ contribution to Fannie and Freddie from an economic perspective. My analysis of these contributions is divided into three parts: (1) the GSEs’ profitability prior to the 2008 conservatorship agreement (bailout), (2) the value of the taxpayer promise at the time of the bailout, and (3) support of new investments since they were placed in conservatorship.

The GSEs prior to conservatorship
The Federal National Mortgage Association (Fannie Mae) and the Federal Home Loan Mortgage Corporation (Freddie Mae) have long been closely linked to the federal government (see W. Scott Frame and Lawrence J. White, 2005). Fannie Mae began as a government corporation chartered during the Great Depression. It was privatized in 1968, but continued to receive a variety of benefits from the federal government. Freddie Mac was chartered in 1970 and converted into a publicly traded company in 1989. It also received a variety of federal benefits. These charter benefits included a line of credit with the Treasury, exemption from state and local taxes, and the ability to issue “government securities” for the purposes of the Securities Exchange Act of 1934. These benefits, combined with prior federal support of distressed GSEs, gave rise to market perceptions of an implied federal guarantee.1 These perceptions increased the value of GSE guarantees and lowered their funding costs.

In effect, Fannie and Freddie were in a partnership with the federal government—with GSE shareholders bearing part of the risk and receiving all of the profits. In return, U.S. taxpayers bore all of the risk of loss in excess of the GSEs’ very low capital requirements and received, at most, a small portion of the profits taxed away through the imposition of minimum lending requirements to low- and moderate-income households (the affordable housing goals).2 Thus, it’s little wonder that in 1999, then Fannie Mae CEO Franklin Raines is reported to have stated “[w]e manage our political risk with the same intensity that we manage our credit and interest rate risks.”3

Embedded losses at time of conservatorship
The decline in housing prices in 2007 and 2008 resulted in increasing levels of financial stress on Fannie and Freddie (see W. Scott Frame, 2009). On September 7, 2008, the Federal Housing Finance Agency placed the two GSEs into conservatorship. Along with this action, the Treasury entered into senior preferred stock agreements with Fannie and Freddie to insure that the value of their liabilities did not exceed the value of their assets. The Treasury initially committed up to $100 billion to each of the GSEs to maintain non-negative net worth. In return, the senior preferred stock accrued dividends at a rate of 10 percent per year, which increased to 12 percent if the dividends were not paid in cash.

That stock agreement with Treasury was subsequently modified three times. The third amendments with Fannie and Freddie in August 2012 effectively removed the limit on Treasury’s promise to maintain positive net worth—that is, the Treasury would now cover the full value of whatever losses were incurred by each GSE. It also replaced the requirement of regular dividend payments with one that starting in 2013, each entity pay “the amount, if any, by which the Net Worth Amount at the end of the immediately preceding quarter exceeds zero.” In other words, essentially all of Fannie and Freddie’s profits are to be paid to Treasury.

Fannie and Freddie suffered $230 billion in losses in their businesses from 2008 to 2011, according to my calculations using the Federal Housing Finance Agency’s first-quarter 2013 Conservator’s Report. These losses far exceeded the two GSEs’ book capital of $78 billion at the time of conservatorship, which would have resulted in a combined negative net worth of $152 billion absent the senior preferred stock purchases by Treasury, according to the Conservator’s Report. In addition, Treasury earned $36 billion in dividends under the agreement effective until the beginning of 2012. In order to cover the losses in excess of capital and dividend payments, the GSEs drew $188 billion from Treasury, the figure cited by Epstein. Starting in 2012, both Fannie and Freddie have had positive earnings, which have been paid to the Treasury under the revised agreement. As asserted by Epstein, the GSEs’ dividend payments from 2008 through the end of the first quarter of 2014 will exceed their respective draws.

So have Treasury and taxpayers been fully compensated for the value of their contribution to the GSEs? There are three issues to consider when answering whether $188 billion is sufficient repayment.

First, the use of the $188 billion in senior preferred stock purchases as the measure of Treasury’s support deprives Treasury of any return on its investment from 2012 through 2014. The dividends paid to Treasury during 2008−11 were paid for by increasing the draw (Treasury buying more senior preferred stock) and, hence, included in the $188 billion “repaid” to the Treasury. However, the calculations cited by Epstein effectively apply 100 percent of the GSEs’ payments in 2012 through 2014 to reducing the balance of Treasury’s senior preferred holdings. If instead we assume that Treasury should have continued to earn a 10 percent dividend on its total holdings, then the GSEs would have owed substantially more dividends. Although a calculation of exactly how much more dividends is beyond the scope of this commentary, back-of-the-envelope calculations show the amount that should have been recorded exceeds $18 billion in 2012 alone.4 Further dividends would also have been due to the Treasury in 2013 and 2014.

Second, the calculations only compensate Treasury and the taxpayers for the losses that they bore and include no payments for the implicit capital they provided to the GSEs. That is, Treasury not only supplied funds to the GSEs but promised to bear any future losses, ultimately agreeing to provide unlimited funds to cover whatever losses were incurred in the future. Fannie and Freddie and their supporters certainly should recognize that committing to cover losses is valuable even if the losses do not arise—one of the GSEs’ primary business activities involves the provision of just such a guarantee on the mortgage-backed securities they issue.

The value of the Treasury contribution in promising to cover any additional losses on the GSEs’ pre-conservatorship loans could be measured as the fees demanded to cover such risks (as with Agency MBS or credit default swaps), or it could be measured as the expected return on the implicit capital that Treasury provided to the GSEs. Ideally, one would want to consider several different approaches to estimating the value and then take some sort of average, a task far beyond the scope of this post. A simpler task would be to get some sense of the perceived extent of the commitment during the crisis, for instance, by looking at the Treasury’s estimates of its exposure at that time. The U.S. government’s 2009Financial Report (pages 81−82) notes that the Treasury had purchased $95.6 billion as of September 30, 2009. However, the Treasury estimated that its remaining liability under the senior preferred stock agreement ranged from a “best case” scenario of $76.9 billion to an “extreme case” of $206.7 billion, noting that “no value within the range is a better estimate than any other amount.” Thus, the Treasury estimated that a reasonable upper bound on its total preferred stock purchases was about $300 billion.

A possible counterargument to the above analysis is that Treasury imposed an excessively high dividend rate of 10 percent for the senior preferred stock. In order to provide a rough approximation of what might be reasonable, I looked at economic data from the St. Louis Fed on the yield on high-risk bonds as proxied by the Bank of America Merrill Lynch U.S. High Yield CCC or Below Effective Yield (see chart). According to Standard & Poor’s, a rating of CCC indicates the bond is still paying interest but is “currently vulnerable and dependent on favorable business, financial and economic conditions to meet financial commitments.” That seems like a generous description of the condition of Fannie and Freddie at the time they were put into conservatorship.

chart

What we can observe in the chart is that the 10 percent rate set in the senior preferred stock agreement is rather favorable to the GSEs over this period. The bond rate was over 15 percent at the time the GSEs were being put into conservatorship and the rate was being set on the senior preferred stock. The rate subsequently spiked at around 40 percent, and dropped below 10 percent only for brief periods prior to the latter part of 2013.

Thus, looking at the value of Treasury’s contribution relative to the GSEs’ pre-conservatorship business, we find that Treasury’s $188 billion senior preferred stock holdings understate the value of its contribution by attributing no dividends to Treasury in 2012−14, by ignoring the value of Treasury’s promise to absorb all of the GSEs’ losses, and by using a senior preferred stock dividend rate that likely provided inadequate compensation for the risk Treasury bore as a creditor.

Postcrisis: government bore all of the risk of the new businesses
As we have seen, Fannie Mae’s and Freddie Mac’s pre-conservatorship portfolios generated major losses. Yet the GSEs have recently been able to generate large profits that allowed them to pay dividends equal to a substantial part of their draws from the Treasury. How did they do this? The primary reason is that a large fraction of their current portfolios consists of profitable business generated since the beginning of 2009. Indeed, Fannie Mae (page 2) reports that 77 percent of its book of single-family mortgage guarantees has been acquired since the start of 2009.

Moreover, the government’s role in supporting the GSEs is not like debtor-in-possession financing of inventory for a manufacturer where the manufacturer’s value-added comes from processing raw materials into final goods. The primary value-added of the GSEs is their promise of timely payment of principal and interest on the mortgage securities that they guarantee; and the sole reason that this promise has value in the post-conservatorship world is the implicit capital provided by the Treasury. As Alex J. Pollock states:

“Fannie and Freddie’s most important business is guaranteeing mortgage-backed securities (MBS). Even with the government’s $187 billion investment in them, their net worth has been zero, without it, hugely negative. What is the value of a guaranty from a guarantor with hugely negative capital? Zero. It is solely the fact that the government guarantees Fannie and Freddie’s obligations that gives this business any revenue or profit at all.”

Thus, as an economic matter, the post-conservatorship dividends paid to the Treasury did not arise from risks being borne by private shareholders. Rather, as pointed out by Felix Salmon, the payments came from—and can reasonably be considered a return on—the risks being borne solely by the Treasury (and taxpayers).

Concluding thoughts
The claim that the taxpayers and Treasury have been fully repaid for their support of Fannie Mae and Freddie Mac is based on an accounting calculation that does not withstand economic analysis. The claim that Treasury’s commitment has been fully repaid attributes no dividend payments to Treasury starting in 2012, attributes no value to the government guarantee to absorb whatever losses arose in the pre-conservatorship book of business, and arguably reflects Treasury setting too low of a dividend rate on its senior preferred stock. Moreover, the profits that are being used to pay the dividends did not arise from the contributions of private shareholders but rather entirely reflect risks borne by the Treasury and taxpayers. Thus, the Treasury claim that the value of the aid was “incalculable” is an exaggeration; the value surely can be fixed within reasonable bounds. However, the implication of this claim, that the GSEs cannot repay the economic value on behalf of their common shareholders, is nevertheless accurate.

What should happen next to Fannie Mae, Freddie Mac, and government involvement in residential real estate finance is the subject of an ongoing debate, with a new bill introduced in the Senate earlier this month. I have considerable sympathy for the argument that Fannie and Freddie should not be kept in their current status. On the other hand, W. Scott Frame, Lawrence J. White, and Isurveyed the major “reform” proposals and concluded that these proposals will result in taxpayers again being subject to very large risks in a future residential real estate downturn.

Larry D. Wall is the executive director of the Center for Financial Innovation and Stability at the Atlanta Fed. The author thanks Kris Gerardi, Scott Frame, Paula Tkac, and Larry White for helpful comments and Brian Robertson for research assistance. The views expressed here are the author’s and not necessarily those of the Federal Reserve Bank of Atlanta or the Federal Reserve System. If you wish to comment on this post, please e-mail atl.nftv.mailbox@atl.frb.org.

_______________________________________

1 For instance, the bailout of the Farm Credit System (see Julie Andersen Hill).

2 The GSEs returned part of the subsidy in the form of lower interest rates to mortgage borrowers. However, economic theory predicts that part of an input subsidy will be used to lower price and increase quantity demanded by a profit-maximizing firm, as I have previously explained. Thus, evidence that the GSEs lowered mortgage rates is not proof that they sacrificed profits to do so.

3 Nevertheless, whenever the topic of an implicit guarantee was raised in public policy debates, the two GSEs adamantly denied the existence of any such subsidy. Indeed, W. Scott Frame and I were treated to a lecture by a high-level Fannie Mae officer who asserted that no such subsidy existed and demanded that we rewrite a draft of our 2002 paper to take out any claims of a subsidy.

4 First, assume that all of the GSEs’ 2012 payments could have gone to repurchasing Treasury’s senior preferred stock at the start of the year, reducing the balance to $168 billion. At a dividend rate of 10 percent, the GSEs would then have owed $16.8 billion in dividends to Treasury. But this leaves only $2.2 billion of the $19 billion payment available to repurchase senior preferred shares. Thus, we can safely conclude that the balance could not have been reduced below $185.8 billion and hence that at a 10 percent rate, the required dividend would have exceed $18 billion.

Reference
W. Scott Frame and Lawrence J. White, 2005. “Fussing and Fuming over Fannie and Freddie: How Much Smoke, How Much Fire?” Journal of Economic Perspectives19, 2 (Spring): 159−184.

 

Previous Post

GoBank Opens Online Store Selling Bank-Branded Swag

Next Post

VIDEO: Square Reaches Out to Spanish-Speaking Market

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

VIDEO: Square Reaches Out to Spanish-Speaking Market

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo