{% extends 'shared/base.html' %} {% load static %} {% block title %} Cookies Policy {% endblock %} {% block head %} {% endblock %} {% block body %}

Cookies Policy

Please read these terms and conditions carefully before using our service.

1. Introduction

This Cookie Policy explains how sWarden uses cookies and similar technologies on its web-based platform.

sWarden is a fully anonymous, open-source password and secret manager that prioritizes your privacy and security. Our use of cookies is minimal, strictly limited to those necessary for the platform to function securely and effectively.

We do not use cookies for analytics, advertising, or behavioral tracking. No personal data is stored or collected through cookies.

2. Our Use of Cookies

sWarden only uses first-party, strictly necessary cookies. These are required to:

  • Maintain secure login sessions
  • Prevent cross-site request forgery (CSRF)
  • Validate CAPTCHA submissions (to prevent abuse)

We do not use:

  • Tracking cookies
  • Third-party cookies
  • Analytics tools
  • Fingerprinting scripts
  • Social media plugins

Every cookie in use is essential for the operation and security of the platform.

4. No Third-Party Cookies

sWarden does not use:

  • Google Analytics
  • Facebook Pixel
  • Advertising or remarketing trackers
  • Embedded third-party content that sets cookies

Your activity is never tracked across other websites. We don’t collect, share, or sell any cookie data but the ones listed above.

5. Your Cookie Controls

You can control or delete cookies at any time using your browser settings. However, since sWarden relies only on essential cookies, disabling them may result in:

  • Inability to log in
  • Loss of session functionality
  • CAPTCHA challenges not working

For full functionality and protection, we recommend allowing sWarden's cookies without removing them. Check out the source code for more in-code details at GitHub (footer).

7. Contact

Due to our anonymous-first model, we do not offer email-based support.

For questions, bug reports, or contributions, please refer to:

{% endblock %}