Lysty Logo

Security

Last updated: February 2026

At lysty.co, we take the security of your data seriously. This page explains how we protect your information and what responsibilities users have when using the platform.

1. Infrastructure Security

lysty.co is built using Firebase (Google Cloud Platform), which provides secure, industry-standard infrastructure.

  • Data is stored in secure Google Cloud environments
  • Access is restricted using authentication and database security rules
  • All communication is encrypted using HTTPS

2. Authentication and Access Control

  • User authentication is handled securely through Firebase Authentication
  • Each user can only access their own private data
  • Passwords are encrypted and never visible to lysty.co administrators

3. Data Protection

  • Your documents and lists are stored under your unique user account
  • Private content is not publicly accessible unless you explicitly share it
  • We do not sell or share your data for advertising purposes

4. Shared Links and Access Codes

lysty.co allows users to share documents and lists via links or access codes.

  • Anyone with access to a shared link or code may view the content
  • You are responsible for managing who you share access with
  • We recommend not sharing sensitive or confidential information through public links

5. User Responsibilities

  • Keep your account credentials secure
  • Do not share your password with others
  • Use strong and unique passwords
  • Log out from shared or public devices

6. Limitations of Security

While we take reasonable measures to protect your data, no system is completely secure.

We cannot guarantee absolute security of information transmitted over the internet or stored electronically.

7. Reporting Security Issues

If you discover a security vulnerability or have concerns about the platform, please contact us immediately:

📧 operaciones.lysty@gmail.com

We appreciate responsible disclosure and will investigate all reports promptly.

8. Updates to This Security Policy

We may update this page as our security practices evolve.

Updates will be reflected with a revised date at the top of this page.

Back to Home