Name	Expiry	Provider	Type	Purpose
.ASPXANONYMOUS	69 days, 10 hours, and 40 minutes	plantanapp.com	HTTP	This cookie is used by sites using the .NET technology platform from Microsoft. It enables the site to maintain an anonymous user-id to track unique users within a session without them logging in or otherwise identifying themselves.
.DOTNETNUKE	session	plantanapp.com	HTTP	Issued by DNN, necessary for site functionality, including forms authentication, created when a user logs in.
__RequestVerificationToken	session	plantanapp.com	HTTP	Anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery. It holds no information about the user and is destroyed on closing the browser.
ASP.Net_SessionId	session	plantanapp.com	HTTP	A cookie which is used to identify the users session on the server. The session being an area on the server which can be used to store data in between http requests.
language	session	plantanapp.com	HTTP	A DNN cookie is created called "language" to store the current language - in a monolingual install this is simply the browser default language, but if the site supports multiple languages then this may be different based on the language selected by clicking in the languages skin object.
_ga	2 years	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
_gid	session	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
_gat_gtag_UA_352364_3	1 minute	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
_gat_UA_352364_3	1 minute	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
cookieconsent	1 year	plantanapp.com	HTTP	Stores the user's cookie consent state for the current domain.
InfoBoxUserId	session	plantanapp.com	HTTP	In case Plant an App tutorial it is used cookie will make the tutorial continue when you change pages. This helps for reporting and track the tutorials

Name	Expiry	Provider	Type	Purpose
_ga	2 years	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.
_gid	session	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.
_gat	session	plantanapp.com	HTTP	Used by Google Analytics to throttle request rate.
_fap	3 months	plantanapp.com	HTTP	Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.
_fbp	3 months	plantanapp.com	HTTP	Used by Facebook to store and track visits across websites.
__stid	1 year	plantanapp.com	HTTP	Used by ShareThis to track link shares or similiar, and other activities.
__stidv	1 year	plantanapp.com	HTTP	Used by ShareThis to track link shares or similiar, and other activities.
__hstc	13 months	plantanapp.com	HTTP	It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
hubspotutk	13 months	plantanapp.com	HTTP	This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
__hssc	30 minutes	plantanapp.com	HTTP	This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
__hssrc	session	plantanapp.com	HTTP	Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.

Chief Financial Officers benefitting from Low-Code

Chief Financial Officers (CFOs) face a number of challenges in their role, a list that appears to be forever growing. Todays piece has a high level look at the common challenges they face, with a suggestion on how Low-Code can help.

Managing and controlling costs: CFOs are responsible for ensuring that their organization's financial resources are used efficiently and effectively.
Maintaining financial stability and liquidity: CFOs must ensure that their organization has enough cash on hand to meet its short-term obligations and that it is financially stable over the long term.
Compliance with laws and regulations: CFOs must ensure that their organization is in compliance with all relevant laws and regulations, including financial reporting requirements and tax laws.
Managing risk: CFOs must identify, assess, and manage the various risks facing their organization, including financial, operational, and reputational risks.
Providing strategic financial advice: CFOs must work closely with their organization's senior management team to provide strategic financial advice and support decision-making.
Keeping up to date with the ever-changing market conditions and technology advancements.
Managing relationships with stakeholders including investors, lenders, and rating agencies.
Ensuring effective communication of financial information to all stakeholders.
Continuously improving the financial processes, systems, and data analytics.

How Low-Code can help:

A low-code platform like Plant an App can help CFOs and their teams address some of the key challenges they face by providing them with tools to automate, streamline, and optimize their financial processes and workflows. Here's how:

Managing and controlling costs: Low-code platforms can enable CFOs to create custom financial applications that help them better track and manage costs, such as budgeting, forecasting, and expense management tools.

Maintaining financial stability and liquidity: Low-code platforms can help CFOs create applications that provide real-time visibility into the organization's financial position, such as cash flow forecasting and financial performance management tools.

Compliance with laws and regulations: Low-code platforms can help CFOs automate compliance-related tasks, such as financial reporting, tax compliance, and audit management.

Managing risk: Low-code platforms can help CFOs identify and mitigate risks by creating applications that enable them to track and manage key risk indicators, such as credit risk, market risk, and operational risk.

Providing strategic financial advice: Low-code platforms can help CFOs and their teams create financial models and perform scenario analysis, which can be used to provide strategic financial advice and support decision-making.

Keeping up to date with the ever-changing market conditions and technology advancements: Low-code platforms are designed to be flexible and adaptable, which means that CFOs can quickly create and deploy new applications as market conditions and technology advancements change.

Managing relationships with stakeholders including investors, lenders, and rating agencies: Low-code platforms can help CFOs create applications that provide stakeholders with real-time access to financial information, such as financial statements and performance metrics.

Ensuring effective communication of financial information to all stakeholders: Low-code platforms can help CFOs create dashboards and reports that make it easy for stakeholders to understand and analyze financial information.

Continuously improving the financial processes, systems, and data analytics: Low-code platforms can enable CFOs to create applications that provide them with real-time insights into their financial processes, systems, and data analytics, which can help them identify areas for improvement and make data-driven decisions.