Cookie Statement
Cookies are small text files a website stores in your browser. Browsers also offer similar storage, such as localStorage. This statement covers both, and applies to amfelt.com, to the Amfelt platform at app.amfelt.com and to its demo at demo.amfelt.com. All three are operated by Amfelt Labs B.V.. See the
Privacy Statement
for who we are and how we handle personal data.
In Short
- We do not use advertising cookies.
- We do not track you across other websites.
- We count page views on our server, not in your browser, so no analytics cookie is set.
The cookies the platform sets are needed to sign you in and to remember where you were working. The demo’s cookies only run the demo. No third-party service sets cookies on our sites, and none of these cookies is used for tracking, so we do not ask for consent. Cloudflare, our network edge for app.amfelt.com and demo.amfelt.com, may set a strictly necessary cf_clearance cookie when it has to check that a visitor is not a bot; it is not used for tracking.
amfelt.com
The marketing site sets no cookies of its own.
- Theme preference. Your browser remembers whether you chose light or dark mode, in
localStorageunder the keytheme. It stays until you clear your browser storage. It never leaves your device. - Visitor statistics. We count page views on the server: when a page is served, our host reports the visit to Pirsch. This sets no cookie and reads nothing stored in your browser. The Privacy Statement explains what the report contains.
- Forms. The contact and waitlist forms use a hidden spam-trap field instead of a captcha, so no captcha service sets cookies.
app.amfelt.com
The platform only works when you are signed in. The cookies below are strictly necessary: the platform cannot sign you in or keep your place without them, so they do not need your consent. All of them are first-party. We clear them when you sign out, except the two one-time message cookies, which expire on their own after a minute.
| Name | Purpose | Expires |
|---|---|---|
hanko | Your sign-in session. It is set for .amfelt.com, so one sign-in covers every signed-in Amfelt service. | When the session ends |
amfelt_current_tenant | The organization you are working in | 30 days |
amfelt_current_project | The project you are working in | 30 days |
amfelt_current_environment | The environment you are working in | 30 days |
amfelt_session_fp | A random value that keeps the browser’s cached menus apart per organization, project and environment | 30 days |
amfelt_return_to | The page to return to after you sign in | 10 minutes |
amfelt_source_save_toast | Shows a one-time confirmation after you save a change | 1 minute |
amfelt_project_created_toast | Shows a one-time message about a project you just created | 1 minute |
The interactive demo at demo.amfelt.com sets amfelt_demo_session. It gives each visitor their own copy of the demo data and expires after 12 hours. The demo also sets amfelt_current_tenant, amfelt_current_project and amfelt_session_fp from the table above, so it opens on its sample organization and project. As you use the demo, it can also set other cookies from the table, such as amfelt_current_environment when you choose an environment. On a screen at least 1024 pixels wide, the demo embedded on our home page loads when it comes into view, without a click. It then sets the four cookies named here and stores its interface settings in your browser’s localStorage.
The platform also uses localStorage to remember display preferences. These are:
- the list or card view
- line numbers in the code viewer
- how file differences are shown
- the light or dark theme
- whether the sidebars are collapsed
It also keeps a cache of your organization, project and environment names so menus load quickly. The amfelt: entries are removed when you sign out. The demo has no sign-out, so its entries are kept until you clear your browser’s storage.
Managing Cookies
Each browser offers its own way to block and delete cookies. Blocking the platform’s cookies will stop you from signing in. These guides explain the settings for the major browsers:
For any other browser, see its official support documentation.
Changes
If we add a cookie or a service that sets one, we update this page before it goes live. If a new cookie needs your consent, we ask for it first.