What is the fe_typo_user cookie?
fe_typo_user is the session cookie TYPO3 sets when a visitor logs in on the public-facing (front-end) side of a site built with this CMS – for example, to access restricted content, gated forms, or member areas.
The cookie appears as soon as a visitor logs in through TYPO3's front-end login extension (such as felogin or an equivalent) and is normally removed when the browser session ends or the user logs out.
What data it stores
The cookie's value is a session identifier generated by TYPO3, used to link subsequent HTTP requests to the user's authenticated session on the server. The exact value format can vary depending on the TYPO3 version and site configuration, so it should not be manually interpreted or altered.
The data is sent only to the domain (or subdomain) of the site that set the cookie, to the same server running TYPO3 – not to any third-party service.
What it is used for
The cookie's purpose is purely functional: it lets the TYPO3 server recognize a logged-in front-end user throughout a browsing session, without requiring credentials again on every page.
For the site owner, this cookie is essential for any feature that requires visitor login, such as protected content areas, client portals, or personalized forms.
Does it require consent?
- CookieFix category: necessary (strictly necessary).
- Under Article 5(3) of the ePrivacy Directive (transposed in Romania via Law 506/2004) and guidance from ANSPDCP, cookies that are strictly necessary to provide a service explicitly requested by the user, such as login, do not require prior consent.
- The site owner must still disclose this cookie in the cookie policy, including its purpose, duration (session), and correct category.
- It does not need to be offered as an opt-out choice in the consent banner, but transparency about its existence remains mandatory.
How to block or delete fe_typo_user
A visitor can delete or block this cookie from browser settings (Chrome, Firefox, Edge, Safari – per-site cookie management), but doing so will automatically log them out of their TYPO3 front-end account.
For site owners, because this cookie is strictly necessary, it should not be blocked by a CMP prior to consent – blocking should only apply to statistics, marketing, and preferences categories. A platform like CookieFix can automatically block scripts in those categories until consent is given, leaving strictly necessary cookies like fe_typo_user unaffected.
Frequently asked questions
It's a session cookie used by TYPO3 to keep track of a visitor's login state on the public front end of the website.
No, since it is strictly necessary for user-requested authentication to function, it does not require prior consent under ePrivacy, but it must be disclosed in the cookie policy.
It is a session cookie, so it is automatically deleted when the browser is closed or the user logs out.
You will be logged out of the TYPO3 site's front-end account and will need to log in again to access restricted areas.