KeyBridge ← Back to KeyBridge

Privacy

Last updated November 9, 2026

In short:

Who I am

KeyBridge is made by AI World by Shachar, a one-person maker of free tools. Questions or requests about your data: aiworldbyshachar@gmail.com. KeyBridge is open source, so everything on this page can be checked in its code.

What KeyBridge does with your keyboard

To notice your shortcuts, a small helper inside KeyBridge watches the keyboard (a keyboard hook on Windows, an event tap on the Mac - the same thing every hotkey app uses).

What stays on your computer

In KeyBridge's data folder (%APPDATA%\KeyBridge on Windows, ~/Library/Application Support/KeyBridge on the Mac):

Your shortcuts, groups and trashshortcuts.json, including how often you used each shortcut. Usage counts never leave the computer.
Settingssettings.json: language, open at login, this computer's name.
Your sign-in and codesecrets.json, a file only your user can read. On Windows it's also sealed with the system's secure storage.
Sync notessync.json: what this computer last agreed with the server, so only changes are sent.
Logkeybridge.log: when KeyBridge started, how many shortcuts were synced, errors. Never what you type, what your shortcuts say, or your email address.

If you export your shortcuts to a file, that file is readable as text - keep it somewhere private.

What's stored in the cloud - only if you sign in

Signing in is optional. When you do, KeyBridge keeps a copy of your shortcuts in a database hosted by Supabase, so your other computers can get them. Before anything is sent, it's locked on your computer with a key made from your code (AES-256-GCM). The code itself never leaves your computers.

Your accountYour email address and when you signed in. The email is used to send you sign-in codes and for nothing else - no newsletters, no marketing. Sign-in emails are sent through Gmail, from aiworldbyshachar@gmail.com.
Your shortcuts, groups and trashLocked with your code - unreadable without it. Stored next to each one: a random id, a revision number, whether it was deleted, which of your computers changed it, and when.
A check valueA short value locked with your code, so KeyBridge can say "wrong code" when one is mistyped.
Your computersFor each one: a random id, its name (locked with your code too), whether it's a Mac or a PC, and when it was last seen - so you can see your computers and sign one out.

Each account can only reach its own rows. As the operator I can see that an account exists, its email address, how many items it holds and when they changed - but not what they say. Supabase, which hosts the database and handles sign-in, keeps the usual technical records of sign-ins and requests (such as times and IP addresses) for security, for a limited time.

How long it's kept, and how to remove it

If you lose your code

Any computer that's still signed in shows it again (Account → Show my code). Nobody else has it, so it can't be reset: if the code and every signed-in computer are lost, the locked copy in the cloud can't be opened by anyone, me included.

This website

This site is hosted on GitHub Pages. It sets no cookies and has no analytics or trackers. GitHub, as the host, may keep standard server logs. The download buttons lead to GitHub, and the Ko-fi links to Ko-fi, each with its own privacy policy.

Changes

If this page changes, the date at the top changes too, and every earlier version is in the project's history.