Your space.
Your information.

What is saved

The installed extension uses Chromium’s local extension storage for your name and settings, shortcuts, daily priorities, tasks and notes. The browser preview uses localStorage instead; preview and installed workspaces are separate.

This data stays in that browser profile. It is not sent to an Idam server. Uninstalling the extension or losing the profile can remove the data, including any local recovery copy. Export a backup before uninstalling or moving profiles.

When Idam makes network requests

Displaying your shortcuts can automatically make network requests for website icons, even without opening a shortcut. Icon loading tries these sources in order, falling through when an image fails or times out:

1. The saved website’s origin plus /favicon.ico.
2. Google’s favicon service, using the website’s origin, followed by Favicon.im, using its hostname.
3. Chromium’s local favicon endpoint, available in the installed extension.
4. The shortcut’s initials if every image source fails.

The external services receive an origin or hostname, not the saved path, query string or fragment. Icon images use a no-referrer policy. Like other network destinations, the contacted services can receive ordinary connection information such as your IP address.

IP addresses, single-label hostnames and common local or reserved suffixes skip public favicon providers. This is a check of the name, not a DNS lookup: a private site with a public-looking hostname can still be sent to a favicon provider. Direct icon requests to saved sites may still occur.

Successful icon lookups are reused in memory for an hour, and failed lookups for one minute; browser caching also applies. Icon requests do not send your tasks, notes or priorities. Idam does not scrape authenticated pages or run scripts from saved websites.

Search terms go to your selected search provider only when you activate a web search. Shortcut links open their saved destinations when activated. Those destinations apply their own privacy practices.

Backup & restore

Export creates a readable, unencrypted JSON file on your device. It includes saved settings, shortcuts, tasks, notes and daily priorities. It excludes unsaved drafts, favicon images and recovery copies. Export does not upload the file.

Restore reads the file you select locally, validates it, and shows a preview. Your workspace is replaced only after you acknowledge replacement and confirm. Before replacement, Idam keeps one local recovery copy; a later restore replaces that recovery copy. You can export it from backup & restore.

Keep exported files private. Store a separate copy somewhere you control if you need protection against profile loss. Local recovery is not protection against disk failure.

Extension permissions

Idam requests storage to save the workspace and favicon to use Chromium’s local favicon endpoint. It replaces the new-tab page. It does not request access to all websites. It uses no remote scripts, remote fonts or background worker.

This website

The landing page contains no analytics, cookies, forms or client-side scripts. Fonts come from your device. Images and styles are served with the page. Following a GitHub link or another external link takes you to that service.

This website is hosted on GitHub Pages. GitHub may process request information, including your IP address, to deliver and secure the site. See GitHub’s Privacy Statement for its handling of that information. Idam does not add visitor analytics.

Questions or something unexpected?

Open an issue on GitHub with your browser version and what you noticed. Public issues are visible to others: do not attach private notes, full backup files or sensitive shortcut URLs.

You can also read Idam’s source to inspect how it works.