Draft — subject to final review. This document is published for information while it is finalised and may change before it takes effect.
This notice explains how Front End Engineering Consultancy Limited, trading as FEEC (“FEEC”, “we”), uses cookies and similar browser storage on emitledger.com and in the EmitLedger web application. For how we handle personal data generally, see our Privacy Policy.
1. Summary
- The website (emitledger.com) sets no cookies and uses no analytics, advertising or tracking technologies, and no third-party scripts.
- The web application (app.emitledger.com) and our sign-in service (auth.emitledger.com) use only strictly necessary cookies and browser storage to sign you in, keep your session secure and remember basic choices.
- Because we use only strictly necessary technologies, we do not show a cookie consent banner. If that changes, we will ask for your consent first.
2. What we use
2.1 Website: emitledger.com
| Name | Type | Purpose | Duration |
|---|---|---|---|
theme | Local storage (not a cookie) | Remembers your light or dark theme choice, only if you use the theme switch. It never leaves your browser. | Until you clear it |
2.2 Sign-in service: auth.emitledger.com
Our identity service (Keycloak, operated by FEEC) sets cookies needed for secure sign-in, such as:
| Name (examples) | Purpose | Duration |
|---|---|---|
AUTH_SESSION_ID, KC_AUTH_SESSION_HASH, KC_RESTART | Keep track of a sign-in in progress and protect it against tampering | Session or a few minutes |
KEYCLOAK_IDENTITY, KEYCLOAK_SESSION | Keep you signed in across the web application and sign-in pages (single sign-on session) | Until sign-out or session expiry |
KEYCLOAK_LOCALE | Remembers the sign-in page language, if you choose one | Session |
The exact names can change between versions of the identity software. They are all first-party and strictly necessary.
2.3 Web application: app.emitledger.com
| Name | Type | Purpose | Duration |
|---|---|---|---|
Sign-in tokens (oidc.*) | Session storage (not a cookie) | Hold your short-lived access tokens while the browser tab is open | Cleared when you close the tab or sign out |
| Last selected organisation | Local storage (not a cookie) | Opens the organisation (tenant) you used last | Until you clear it or sign out |
2.4 Mobile app
The mobile app does not use cookies. It stores sign-in tokens in your device’s secure keychain or keystore, as described in the Privacy Policy.
3. Third-party cookies
None. Our DNS provider does not handle web traffic to our sites, so it sets no cookies. If we ever route traffic through a content-delivery or security service that sets its own strictly necessary cookies, we will list them here.
4. How to control cookies
You can block or delete cookies and browser storage in your browser settings. Blocking the sign-in cookies or storage will stop you from signing in to the web application. Blocking the website’s theme storage only means your theme choice is not remembered.
5. Contact
Questions: privacy@emitledger.com.