E-Künye keeps the details you keep typing into forms, such as addresses, IBANs, ID numbers and emergency contacts, in one clean list. Tap a line to copy it, hold it to edit.
Available in Turkish and English.
Features
- Tap to copy, hold to edit. On desktop, right-click or press E to edit. The first copy mentions holding once. Prefer visible controls? Switch the list style to With buttons under Settings to get copy and edit buttons on every row.
- Ready-made fields in groups: my details (including SWIFT/BIC), ID and documents (ID card serial and expiry, passport, driving licence, tax number and office), family, spouse, special dates, home and bills, car (including the chassis number), and health and emergency. Each field comes with a matching emoji, input hint and keyboard type.
- Field types: text, long text, phone, email, number, IBAN, national ID, date and blood type. Each type opens the right keyboard and tidies the value on save (IBAN in groups of four, phone numbers, dates as DD.MM.YYYY). It also warns about likely typos, such as a wrong IBAN check digit or an invalid Turkish ID number, without blocking the save. Blood type is picked from a list.
- Fully editable: rename, delete or re-emoji any field, or add your own. Reorder mode moves rows up and down.
- Search: results drop down while you type; picking one copies it. Matching ignores case and Turkish accents, and starter fields not in your list yet are offered as quick adds.
- App lock: an optional 6-digit PIN, with Face ID or fingerprint where the device supports it, asked at launch and after more than a minute in the background.
- Light and dark themes: follows the system, or pick one under Settings.
- Hide in list: sensitive values such as IBANs, ID numbers and Wi-Fi passwords show as dots but still copy on tap.
- Optional sync: sign in with Google to see the same list on your phone and computer. Entries are encrypted on the device with a sync password before upload.
- Backup and restore: export the whole list as a JSON file (through the share sheet where the browser supports it) and restore it on any device.
- Recommend to a friend: opens the phone's share sheet with a short message and the link; where there is no share sheet, the message is copied instead. Shared links show a preview image (Open Graph).
- Turkish and English: picks the browser language on first launch and can be switched under Settings. Built-in field names follow the language; fields you renamed stay as they are.
- Installable and offline: add it to the home screen on Android or iOS. It works without a connection after the first visit.
- Phone first: opened on a computer, it shows a QR code to continue on your phone. Settings has an About section with home screen steps, why and how to use it, and who made it.
Privacy
By default your data never leaves the device. It lives in the browser's localStorage on that device, with no account needed.
Sync is opt-in. When you turn it on, each entry is encrypted in the browser with AES-256-GCM, using a key derived from your sync password (PBKDF2-SHA256, 600,000 iterations), before it is written to Firestore. The server only stores ciphertext. Each record is bound to its account and entry id, so it cannot be moved elsewhere and still decrypt. Nobody, including the project owner, can read the synced entries without the password. If the password is forgotten, the cloud copy is wiped and uploaded again from a device that still has the list.
The app lock keeps the list from whoever picks up an unlocked phone. It is a screen lock, not encryption: the PIN is stored as a salted PBKDF2 hash, wrong PINs are throttled, and Face ID / fingerprint unlock uses a device passkey (WebAuthn) checked on the device. A forgotten PIN can only be cleared by erasing the data on that device; the saved sync key goes too, so the sync password is needed to restore a synced list.
Without sync, clearing browser data or switching phones will lose the list unless you have a backup. Installing to the home screen makes storage more durable, especially on iOS. Backup files are plain JSON and are not encrypted, so keep them somewhere safe.
Project structure
| File | Purpose |
|---|
index.html | Page markup; text is filled in from the language files |
css/style.css | Styles |
js/boot.js | Runs before the first paint: applies the saved theme and hides the list while the app lock is on |
js/lock.js | App lock: PIN screen, throttling, Face ID / fingerprint through WebAuthn |
js/fields.js | Field types: keyboard, formatting and validation per type |
js/app.js | App logic: list, search, editor, backup, install hint, language and theme switch, sync UI |
js/sync.js | Optional sync: Google sign-in and Firestore (loaded only when sync is used) |
js/sync-core.js | Encryption and the merge between local and cloud entries, with no Firebase dependency |
firestore.rules | Firestore security rules: each user can only reach their own encrypted records |
lang/tr.js, lang/en.js | All interface text, preset field names and hints, one file per language |
manifest.webmanifest | PWA manifest (name, colors, icons) |
sw.js | Service worker: caches the app shell and Google Fonts for offline use |
icons/ | App icons (192, 512 and maskable, plus the Apple touch icon) the QR code shown on desktop, and og-image.png, the 1200×630 link preview |
There are no dependencies and no build step.
Adding a language
- Copy
lang/en.js to lang/xx.js, change .en to .xx on the first line and translate the values. Keep every key.
- Add
<script src="lang/xx.js"></script> to index.html before js/app.js.
- Add
"./lang/xx.js" to ASSETS in sw.js and bump CACHE.
The new language then shows up in the Settings switch automatically.
Running locally
Serve the folder over localhost, because service workers only run on HTTPS or localhost:
python -m http.server 8000
Then open http://localhost:8000. Opening index.html straight from disk also works, but without offline support.
Deploying
Any static host works, for example GitHub Pages serving the main branch from the root folder.
When you change any cached file (anything listed in ASSETS), bump CACHE in sw.js (for example e-kunye-v6 to e-kunye-v7) so installed apps pick up the update.
Sync setup
Sync uses a Firebase project (Authentication with Google, and Cloud Firestore). The web config in js/sync.js is public by design; access is enforced by sign-in and firestore.rules. To use your own project:
- Create a Firebase project and a web app, and put its config in
js/sync.js.
- Enable Authentication → Google, and add your domain under Authorized domains.
- Create a Firestore database and publish
firestore.rules under Rules.
Firestore layout:
| Path | Fields |
|---|
users/{uid} | v, salt, iter, check: key parameters and an encrypted value to verify the password |
users/{uid}/items/{id} | iv, ct, updatedAt, deleted: one encrypted entry; deletions are kept as markers so they reach other devices |
Entries merge one by one, and the most recent change to an entry wins.
Data format
Each entry is stored as:
{ "id": "…", "emoji": "🏠", "title": "Ev adresi", "value": "…", "hidden": false, "type": "longText", "updatedAt": 1727250000000 }
Every record loaded from storage or a backup passes through normalizeItem, so older data keeps loading safely. When extending the format, only add fields with defaults; never rename a field or make one required.
