Privacy policy

Prepared October 12, 2026 · Current controlled-test desktop application

locks.biz is a desktop application for organizing locksmith records. This policy explains how the application handles information when you use its local workspace, import records, or connect a Google Sheets workbook. For privacy questions, contact Philip Christiansen at philip@christiansen.zone.

Information the application handles

The application processes the records you enter, import, or select in a connected workbook. These may include locations, openings, key systems, cylinders, access relationships, physical key copies, holder details, notes, and record history. Imports process the CSV or Excel files you choose and retain source-row and batch information with imported records.

A Google connection also uses authorization credentials and the selected workbook’s identifier and metadata. The application uses these to access and synchronize that workbook.

Google access and use

Connecting Google is optional. The application requests the drive.file permission to access files you select for use with locks.biz, rather than broad access to your entire Google Drive. It reads workbook structure and records and writes changes you authorize, including setup, imports, edits, and history.

Google data is used to provide the workspace and its synchronization features. It is not sold, used for advertising, or used to train generalized artificial-intelligence or machine-learning models. Use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Storage and protection

Your selected Google workbook is the authoritative shared record store. After it has loaded successfully, locks.biz keeps a local SQLite snapshot and pending changes on your computer so supported work can continue offline.

Local cached records and pending changes use operating-system secure storage for encryption when a meaningful protected backend is available. Protection depends on your operating system and configuration; the application shows its protection status and warns when storage is unprotected. Google refresh credentials are saved encrypted only when meaningful OS-backed secure storage is available; otherwise authorization remains in memory for the session.

Sharing and service providers

The desktop application communicates directly with Google to authorize access and synchronize your selected workbook. The current application does not upload workbook records to a locks.biz-operated server and does not include advertising or analytics tracking. Workbook sharing permissions remain under your control in Google.

If you email support, the information you include is handled through email to respond to your request. Do not send key records, passwords, authorization tokens, or your application profile. This website itself has no analytics scripts, advertising, or forms. A website hosting provider may process ordinary request data, such as IP addresses and browser information, to deliver and protect the site.

Retention and deletion

Records remain in your Google workbook until you or someone with access changes or deletes them. Archiving a record retains its information and history; archiving is not deletion.

Disconnecting a workbook removes its synchronized local cache and saved application OAuth session after confirmation. Disconnect is blocked while pending or conflicted work remains, to protect unsynchronized changes. Resolve that work before disconnecting.

Uninstalling the application is designed to retain the local profile, including pending work. It does not delete your Google workbook. Local profile removal and Google workbook deletion are separate actions. Support correspondence remains in the support mailbox unless removed; contact us to request deletion of correspondence we hold.

Your choices

You may use the sample workspace without connecting Google. You control which workbook you select and its Google sharing settings. You can remove the application’s account access in Google Account connections. Disconnecting locally does not itself revoke the Google-side grant. Revoking access stops future authorized Google access but does not automatically erase existing local records.

Keep customer-controlled workbook backups. Unsynchronized changes exist locally until successfully written to Google; copying an encrypted local profile alone is not a portable backup.

Changes and contact

This policy describes the current controlled-test application. We will update this page when the application’s data practices change. For access, deletion, or other privacy questions about information held by the project, email philip@christiansen.zone. For records in your own workbook, you or your organization controls their management.