Project Atlas 3.5

Effective Date: 04/10/2026

Welcome to Project Atlas, a master key system generation tool provided by Williams Lock Service. By accessing or using this application, you agree to the following terms and conditions.

1. Acceptance of Terms

By selecting "Accept" below, you acknowledge that you have read, understood, and agree to be bound by this User Agreement. If you do not agree, you must select "Decline" and discontinue use of the application.

2. Intended Use

Project Atlas is designed to assist locksmiths and security professionals in generating master key systems for planning and reference purposes.

• Use only for lawful purposes
• Only for systems you are authorized to design or service
• Must comply with applicable laws and standards

3. No Guarantee of Accuracy (IMPORTANT)

This tool is provided as a reference aid, not a substitute for professional judgment.

• All generated systems and bittings must be independently reviewed
• You are solely responsible for system functionality and security
• Unexpected or invalid results may occur, especially with edge-case parameters

4. Beta Software Disclaimer & Data Responsibility

Project Atlas is currently in a beta stage.

• Features may change or break without notice
• Bugs or calculation errors may occur
• Not all configurations are fully tested

Additionally:

• Users are strongly encouraged to download and retain copies of all generated systems
• System viewer conflicts or display issues may occur
• Never rely solely on a system token to retrieve system data

5. Data Storage & Privacy Model (IMPORTANT)

This application is designed to minimize data retention.

• Generated systems and exported project content are NOT stored on Project Atlas servers or in the Project Atlas authentication database
• Systems are recalled using system tokens and user parameters or locally saved json files
• Account sign-in and sign-up are processed through Supabase authentication services used by Project Atlas
• When you create an account, Project Atlas sends your email address, password, optional organization name, and related account metadata such as beta-access and professional-use flags to that authentication service
• Account and authentication records may remain with that authentication provider until deleted or otherwise removed from the account system
• Project Atlas may store application files and related resources in your browser cache, service worker storage, and local browser storage to support offline use, app installation, performance, and session persistence
• Project Atlas may also store authentication tokens, session timing data, offline authorization state, and basic signed-in UI state in local browser storage or session storage on your device
• This local browser storage occurs on your device, not on Williams Lock Service servers
• Exported json files, spreadsheets, and pinning sheets saved by the user remain local files on that device unless the user moves or shares them elsewhere
• Acceptance of this agreement is stored locally in your browser so the application can remember that choice on later visits
• If email confirmation is required, authentication callback parameters may briefly appear in the browser address bar until the app clears them after processing
• Clearing browser data, site data, or installed app data may remove cached files, offline functionality, saved local preferences, and agreement state
• Requests to correct or delete account information must be directed to Williams Lock Service using the contact information below and may depend on capabilities available in the authentication provider
• Loss of system token and/or downloaded files can result in permanent data loss for pinout sheets. The safest practice is to export the full project zip whenever you finish editing and replace your locally stored project folder with the updated extracted folder. In the event of file loss, json files can be recovered in the generator by loading the system token on your spreadsheet at the bottom of the generator page.

Security Best Practices:

• Use blind codes or internal client numbers instead of real names
• Maintain your own secure mapping of those codes
• This prevents system data from being tied to real clients
• Only enter organization information you are comfortable associating with your Project Atlas account
• Sign out of the app on shared devices when finished, but remember that sign-out does not protect files already saved locally on the operating system
• Protect exported project folders the same way you would protect any other sensitive files stored on the device

6. Limitation of Liability

Williams Lock Service shall not be held liable for:

• Errors in generated key systems
• System failures or key conflicts
• Security vulnerabilities
• Loss of access due to missing system tokens or files
• Any damages resulting from use of this tool

7. User Responsibility

• Verify all outputs before use
• Ensure compatibility with hardware and keyways
• Maintain proper security practices
• Safeguard system tokens and downloaded data

8. Modifications to Agreement

This agreement may be updated at any time. Continued use constitutes acceptance of changes.

Your use of Project Atlas authentication features is also subject to the availability and processing practices of the third-party authentication provider used by the service.

9. Contact

Williams Lock Service
Mark Williams
mark@williamslockservice.com

By clicking "Accept", you acknowledge that this tool is in beta, that generated system data is not stored by the service, that account and authentication data may be processed for access control, and that all generated systems must be verified before use.