Web cookies (also called HTTP cookies, browser cookies, or simply cookies) are small pieces of data that websites store on your device (computer, phone, etc.) through your web browser. They are used to remember information about you and your interactions with the site.
Purpose of Cookies:
Session Management:
Keeping you logged in
Remembering items in a shopping cart
Saving language or theme preferences
Personalization:
Tailoring content or ads based on your previous activity
Tracking & Analytics:
Monitoring browsing behavior for analytics or marketing purposes
Types of Cookies:
Session Cookies:
Temporary; deleted when you close your browser
Used for things like keeping you logged in during a single session
Persistent Cookies:
Stored on your device until they expire or are manually deleted
Used for remembering login credentials, settings, etc.
First-Party Cookies:
Set by the website you're visiting directly
Third-Party Cookies:
Set by other domains (usually advertisers) embedded in the website
Commonly used for tracking across multiple sites
Authentication cookies are a special type of web cookie used to identify and verify a user after they log in to a website or web application.
What They Do:
Once you log in to a site, the server creates an authentication cookie and sends it to your browser. This cookie:
Proves to the website that you're logged in
Prevents you from having to log in again on every page you visit
Can persist across sessions if you select "Remember me"
What's Inside an Authentication Cookie?
Typically, it contains:
A unique session ID (not your actual password)
Optional metadata (e.g., expiration time, security flags)
Analytics cookies are cookies used to collect data about how visitors interact with a website. Their primary purpose is to help website owners understand and improve user experience by analyzing things like:
How users navigate the site
Which pages are most/least visited
How long users stay on each page
What device, browser, or location the user is from
What They Track:
Some examples of data analytics cookies may collect:
Page views and time spent on pages
Click paths (how users move from page to page)
Bounce rate (users who leave without interacting)
User demographics (location, language, device)
Referring websites (how users arrived at the site)
Here’s how you can disable cookies in common browsers:
1. Google Chrome
Open Chrome and click the three vertical dots in the top-right corner.
Go to Settings > Privacy and security > Cookies and other site data.
Choose your preferred option:
Block all cookies (not recommended, can break most websites).
Block third-party cookies (can block ads and tracking cookies).
2. Mozilla Firefox
Open Firefox and click the three horizontal lines in the top-right corner.
Go to Settings > Privacy & Security.
Under the Enhanced Tracking Protection section, choose Strict to block most cookies or Custom to manually choose which cookies to block.
3. Safari
Open Safari and click Safari in the top-left corner of the screen.
Go to Preferences > Privacy.
Check Block all cookies to stop all cookies, or select options to block third-party cookies.
4. Microsoft Edge
Open Edge and click the three horizontal dots in the top-right corner.
Go to Settings > Privacy, search, and services > Cookies and site permissions.
Select your cookie settings from there, including blocking all cookies or blocking third-party cookies.
5. On Mobile (iOS/Android)
For Safari on iOS: Go to Settings > Safari > Privacy & Security > Block All Cookies.
For Chrome on Android: Open the app, tap the three dots, go to Settings > Privacy and security > Cookies.
Be Aware:
Disabling cookies can make your online experience more difficult. Some websites may not load properly, or you may be logged out frequently. Also, certain features may not work as expected.
UConn’s Office of Emergency Management (OEM) recently hosted a Sport and Special Event Evacuation Training and Exercise course at the Storrs campus on March 8 and 9. The course was put on by TEEX, Texas A&M Engineering’s Extension Service. This branch of TEEX is federally funded by the Department of Homeland Security and the Federal Emergency Management Agency.
The multidisciplinary audience spent two days reviewing best practices regarding the preparation and implementation of a venue evacuation plan. The following topics were covered:
The importance of a well-defined approach to planning and managing an evacuation using the Incident Command System (ICS) within the National Incident Management System (NIMS) framework
The essential components of developing an evacuation plan
The concepts of planning and implementing an evacuation plan for sport venues
The effective measures that ensure the evacuation emergency plan reflects the current operation strategies, organizational structures, and methodologies utilized by evacuation personnel
Participation in a training exercise involving key partners and evaluate outcomes in order to address gaps and ensure an increasing level of preparedness for evacuations
UConn’s OEM was excited to host this training and is always exploring new educational opportunities for the Division of University Safety and the rest of our University partners.
March 15, 2016 (Falls Church, Va.) – Members of the U.S. Council of the International Association of Emergency Managers (IAEM), the premier international professional association representing more than 5,000 professional emergency managers worldwide, including more than 4,200 in the United States, believe there is serious confusion and misunderstanding of the use of the term “emergency manager” in the press and public related to the Flint, Michigan, water situation. Traditional emergency managers focus on preparing for, responding to, and recovering from disasters or crisis situations. The term “emergency manager” has been used to describe those in the business of saving lives, protecting property, and restoring communities for more than 40 years.
“One thing must be made absolutely clear: the term ‘emergency manager’ in the Flint, Michigan, situation refers to a fiscal-only function that bears no relationship to the term as it is commonly and universally used on a national and an international basis,” stated Robie Robinson, IAEM-USA president. “In the context of the Flint situation, emergency managers are actually municipal ‘emergency financial managers’ (EFMs) established by the Michigan legislature and appointed by the governor to oversee jurisdictions in Michigan that are threatened with financial insolvency.”
The use of the term “emergency manager” to describe these appointed financial managers in Michigan has generated an incredible amount of dangerous confusion for the public, especially since the Flint issue has now become a national story. Dedicated emergency managers across the country now are being forced to address questions that underline a misguided sense of concern about the role of an emergency manager. Unfortunately, an impression is beginning to take shape that emergency managers exist to “cut budgets and reduce costs at the expense of community safety and security,” Robinson noted, when indeed the exact opposite is true. “This confusion is damaging community confidence in real emergency managers both in and out of Michigan, and in doing so it is making our communities more vulnerable,” concluded Robinson.
IAEM urges all media, members of government, and other leaders to educate the public, and help clarify that, in Michigan, an individual who is appointed to oversee a governmental body or jurisdiction because it is threatened with financial insolvency is not an “emergency manager,” but rather an “emergency financial manager.” Further, real emergency managers work every day in support of University Safety agencies, local volunteer and service organizations, businesses, the media, and everyone in between, striving to build relationships in their communities to help keep people safe. They cannot do this without the trust of the people they serve.
In this Feb. 4 photo, UConn police block off a section of Fairfield Way as university workers attempt to fix an outage. Another power outage occurred on Feb. 25 and affected students living along North Eagleville Road and Route 195. (Zhelun Lang/Daily Campus)
For some, the morning of Thursday, Feb. 25 began with a strange noise of a reset alarm clock. For others, their lights went out during a late night cram-session. But most students probably woke up to morning whispers or social media messages about an incident that passed unnoticed in the night.
Just before 1:30 a.m., the high winds of the thunderstorm damaged circuit #3, which caused power outages along North Eagleville Road and Route 195, including North Campus, Towers, Husky Village and East Campus.
The exact cause of the outage remains unknown, but natural forces during storms often cause damage to the power grid. Windswept debris, falling branches and direct lightning strikes are common storm hazards that are not easily preventable.
“In this particular outage, there were no electrical fires or electrical emergencies reported to the fire department,” Deputy Chief Gregory Priest said. The UConn Fire Department (UCFD) did assist, Priest said, by playing a “supportive role to our partners in Facilities.”
Their first objective was to establish situational awareness by becoming a part of an Incident Management System (IMS). The IMS provides a structure for centralized information distribution and decision making.
In this case, UCFD’s Command Staff and Office of Emergency Management responded to the Division for University Safety’s Emergency Operations Center.
“The staff that make up the Emergency Operations Team is dependent on the incident,” said Christopher Renshaw Captain of the OEM. The roster for a laboratory outage may be different than the one for a residence hall blackout.
The next support step includes, “verifying the function of emergency egress lights, and ensuring that the fire alarm systems are functioning on battery power,” Priest said.
To repower the circuit, Facilities Operations and Building Services (FOBS) was contacted by the Fire department and immediately activated their Emergency Response Team. They worked side by side the crew of Eversource, the utility company that helps power the university.
“It was a fantastic effort and partnership between our crews,” Associate Vice President of FOBS Mike Jednak said, “especially in the wee small hours of the night.”
The partnership worked for four hours until 5:30 am, when they fully restored power to the circuit. No other significant issues were caused by the power outage, and classes began as scheduled.
Despite the unpredictable nature of lightning storms, FOBS performs, “preventative maintenance to the entire electrical infrastructure to minimize risk,” Jednak said.
To help incident response, FOBS has a phone request service, the Work Order Control Center (WOCC).
For emergencies, students should call in a Facilities Emergency to 860-486-3113. According to the WOCC’s webpage, “an immediate or imminent threat to life, or severe property damage,” is assigned Priority code #1, the highest level of request.