Security at EazePro

EazePro uses layered safeguards across application access, tenant authorization, managed infrastructure, software delivery, and operational response. This page describes current practices and is not a certification or guarantee that incidents cannot occur.

• Authenticated access with role- and permission-aware application controls.
• Tenant-scoped data access designed to keep organization workspaces separate.
• Administrative, financial, and driver workflows expose only the functions intended for the user’s role.
• Session and credential controls are provided through the application’s authentication system.

• TLS encryption protects data in transit to supported production services.
• Production application and database workloads run on managed cloud infrastructure.
• Payment card data is handled by Stripe; EazePro does not store complete card numbers.
• Backups, logging, dependency maintenance, and production access are managed according to operational need.

Customers must protect credentials, use appropriate roles, remove departed users, keep devices secure, validate connected services, and notify us promptly of suspicious activity. Do not place unnecessary sensitive information in free-text fields.

Please report a suspected vulnerability privately to info@codepaper.com. Include the affected URL or feature, reproduction steps, and potential impact. Do not access another person’s data, disrupt the service, use social engineering, or publicly disclose an unresolved issue. We will acknowledge, investigate, and coordinate remediation in good faith.

If we confirm an incident affecting customer data, we will investigate, contain, remediate, and notify affected customers or authorities where required by applicable law.