Legal & Privacy

Last Updated: April 2026

Plexevent is committed to protecting the security, integrity, and availability of the platform and the data entrusted to it.

This document outlines the security practices, principles, and limitations associated with the Plexevent Service.

1. Security Approach

Plexevent is designed with security considerations as part of its development and operational processes.

We aim to implement practical and industry-aligned safeguards to reduce the risk of:

• unauthorized access
• data loss
• system disruption
• misuse of the platform

However, no system can be completely secure, and users acknowledge the inherent risks of internet-based services.

2. Infrastructure Security

Plexevent relies on established infrastructure providers to host and operate the platform.

These include:

• Amazon Web Services (AWS) – cloud infrastructure
• Hostinger – hosting and email infrastructure

Primary infrastructure region:

European Union (Frankfurt)

These providers maintain their own security frameworks, certifications, and operational safeguards.

 Plexevent is not responsible for failures or incidents originating from third-party infrastructure providers.

Plexevent does not guarantee:

• prevention of all security incidents
• continuous availability
• complete data integrity

Users accept that use of the Service involves inherent cybersecurity risks.

3. Encryption

Plexevent uses encryption to protect data in transit.

This includes:

• HTTPS connections
• TLS encryption between client and server

These measures help reduce the risk of unauthorized interception of data.

4. Account Security

User accounts are protected through standard authentication mechanisms.

Security practices include:

• password hashing
• secure login sessions

 Users are responsible for:

• maintaining password confidentiality
• securing their own devices
• preventing unauthorized access to their accounts

Plexevent is not responsible for account compromise resulting from user negligence.

5. Access Control

Access to systems and data is restricted based on necessity.

Controls may include:

• role-based access permissions
• restricted administrative access
• controlled access to production environments

Access to customer data is only granted where required for:

• system operation
• support
• maintenance
• security purposes

6. Data Protection Measures

Plexevent applies technical and organizational safeguards, including:

• secure infrastructure
• controlled system access
• monitoring systems
• database protection mechanisms
• backup processes

These measures aim to protect against:

• unauthorized access
• accidental loss
• alteration
• disclosure

7. Monitoring and Logging

Plexevent systems may be monitored to detect:

• unusual activity
• system errors
• performance issues
• potential security incidents

Monitoring helps improve platform reliability and security.

8. Data Backups

Data backups may be performed to support recovery in case of:

• system failures
• infrastructure issues
• accidental data loss

Backup processes are designed to improve system resilience but do not guarantee full recovery in all scenarios.

9. Security Responsibilities of Users

Users are responsible for:

• securing their own accounts
• ensuring lawful and secure use of the platform
• protecting devices used to access Plexevent
• managing access within their organization

 Plexevent is not responsible for security issues caused by user behavior, misconfiguration, or misuse of the platform.

10. Third-Party Services

Plexevent relies on third-party services including:

• Stripe (payments)
• AWS
• Hostinger
• Google Analytics
• Meta Pixel
• Hotjar / Microsoft Clarity

These services operate independently.

 Plexevent does not control and is not responsible for their security practices or incidents.

11. Incident Handling

If a security issue is identified, Plexevent may take actions such as:

• investigating the issue
• applying fixes or updates
• restricting access where necessary

Where applicable, notifications may be provided in accordance with legal requirements.

12. Responsible Disclosure

If you believe you have discovered a vulnerability, please report it to:

service@plexevent.com

We encourage responsible disclosure to improve platform security.

13. Security Limitations

Users acknowledge that:

• no online system is completely secure
• service interruptions may occur
• third-party failures may impact availability
• security incidents may occur despite safeguards

Plexevent provides the Service on an "as is" and "as available" basis and does not guarantee absolute security or uninterrupted operation.

14. Updates

This Security Overview may be updated periodically.

The latest version will be available with the updated "Last Updated" date.