Store Key Codes Securely

Why Key Code Security Matters

Key codes and bitting data are essentially the "passwords" to your customers' homes, cars, and businesses. A leaked key code could allow someone to cut a working key without authorization. This is why KeyBolt treats this data with the highest level of care.

How KeyBolt Protects Sensitive Data

Key codes, bitting data, and safe combinations are stored in encrypted fields in the database. Here's what that means in practice:

• Encryption at rest — all sensitive locksmith data is encrypted in the database. Even if someone gained access to the raw database, they couldn't read the key codes.
• Organization-scoped access — only members of your organization (your shop) can view this data. No other KeyBolt customer can see your records.
• No KeyBolt employee access — KeyBolt staff cannot view your customers' key codes, bitting data, or safe combinations. The encryption keys are managed so that only authenticated users in your organization can decrypt this data.
• Row-Level Security (RLS) — every database query is filtered by your organization ID at the database level. This isn't just application logic — it's enforced by the database itself.

Adding Key Codes to a Customer

1. Open a customer's profile from the Customers tab.
2. Scroll to the Key Codes section.
3. Tap "+ Add Key Code".
4. Enter a label (e.g., "Front door Schlage," "2021 Toyota Camry," "Mailbox").
5. Enter the key code. This is displayed in monospace font for easy reading — important when you're reading codes like "S34YK" or "X198" at a glance.
6. Tap Save.

You can add as many key codes as needed per customer. Each code gets its own labeled entry.

Bitting Data vs. Key Codes

These are often confused, but they're distinct concepts in the locksmith trade:

• Key code — a reference number stamped on the lock or key (e.g., "A1234"). Used to look up the correct bitting in a code book or software.
• Bitting — the actual depth cuts on the key (e.g., "3-2-5-4-1-3"). This is the physical specification needed to cut a working key.

KeyBolt has separate fields for both. Store both when you have them — having the bitting on file means you can cut a key without needing to decode on site.