Terms of Use

Last updated: January 6, 2026

License

ShieldAuth is free and open source software released under the MIT License. You are free to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software.

MIT License

Copyright © 2026 ShieldAuth

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Disclaimer

ShieldAuth is provided "as is" without warranty of any kind. While we strive to ensure the software is secure and reliable, you use it at your own risk. We are not responsible for:

  • Loss of access to accounts due to lost or corrupted data
  • Unauthorized access resulting from device compromise
  • Any damages arising from the use or inability to use the software

Your responsibilities

When using ShieldAuth, you are responsible for:

  • Maintaining the security of your device
  • Keeping backup codes for your accounts
  • Regularly backing up your device
  • Using strong passwords and enabling device encryption

Security recommendations

For optimal security when using ShieldAuth:

  • Enable FileVault disk encryption on your Mac
  • Use a strong login password
  • Enable Touch ID if available
  • Keep macOS and ShieldAuth updated
  • Store backup codes in a secure, separate location

Changes to terms

We may update these terms from time to time. Changes will be reflected on this page with an updated revision date. Continued use of ShieldAuth after changes constitutes acceptance of the new terms.

Contact

For questions about these terms, please open an issue on our GitHub repository.