Project Atlas Privacy Policy

This Privacy Policy describes what information Project Atlas collects, where that information is stored, and how it is used. Project Atlas is provided by Williams Lock Service.

1. Information We Process

• Email address submitted during sign-up, sign-in, email confirmation, and account access workflows.
• Password submitted to the authentication provider during sign-up and sign-in.
• Optional organization name entered during account creation.
• Account metadata written during sign-up, including organization-declared status, organization-recorded timestamp, professional-use declaration, beta cohort, beta-access flag, and beta-joined timestamp.
• Authentication session data stored in the browser, including access tokens, refresh tokens, session-expiration timing, remember-me preference, offline authorization state, and signed-in UI state.
• Agreement acceptance state and cached application resources stored locally in the browser to support offline use and app installation.

2. Information We Do Not Store on the Service

• Generated master key systems, exported json files, spreadsheets, pinning sheets, and project zip contents are not stored on Project Atlas servers as part of the current application flow.
• Those files remain on your device unless you export, move, sync, back up, or share them elsewhere.

3. How Information Is Used

• To create and authenticate user accounts.
• To control access to protected Project Atlas tools.
• To remember signed-in state, remember-me choice, and limited offline authorization windows on the current device.
• To identify beta users and maintain professional-use and organization recordkeeping connected to the account.
• To support email confirmation and account recovery flows when enabled.

4. Third-Party Processing

Project Atlas uses Supabase authentication services for account creation, sign-in, token refresh, and related authentication workflows. Information submitted for those workflows is transmitted to Supabase for processing.

Availability of login, account confirmation, password recovery, and related authentication functions depends in part on that third-party provider.

5. Local Device Storage

• Project Atlas stores app resources in browser cache and service-worker storage to support installed and offline use.
• Project Atlas stores session and offline-access data in local storage or session storage on the device you are using.
• If email confirmation is used, callback parameters may briefly appear in the URL until the application clears them after processing.
• Clearing browser/site data may remove sign-in state, agreement acceptance, cached resources, and offline availability.

6. Retention

• Browser-stored session data remains until it expires, you sign out, or browser/site data is cleared.
• Remembered sessions currently target up to 14 days on the device. Non-remembered sessions currently target about 6 hours on the device.
• Account profile and authentication records stored with the authentication provider remain until deleted or otherwise removed from that service.

7. Your Choices

• You may choose whether to provide an organization name during sign-up.
• You may sign out when finished, especially on shared devices.
• You may clear browser/site data to remove local cached content and locally stored session state.
• You should avoid placing real client names or sensitive identifying information into generated system content or exported files.
• You may request correction or deletion of account information by contacting Williams Lock Service, subject to what can be accessed and removed through the authentication provider.

8. Security Notes

• No browser-based application can guarantee perfect security.
• Exported project files and downloaded data should be protected like any other sensitive files on the device.
• Signing out does not remove project files you already exported or stored locally outside the browser.

9. Policy Changes

This Privacy Policy may be updated as Project Atlas features or account workflows change. Continued use after an update means the revised policy will apply going forward.

10. Contact

Williams Lock Service
Mark Williams
mark@williamslockservice.com