Mihro is a residential operations platform designed for residential complexes, property managers, administrators, staff members, and residents.

This Privacy Policy explains what information may be collected, how it is used, who may access it, and how Mihro helps protect personal data inside the platform.

Mihro is provided to residential complexes, property management companies, and building administrations. These organizations may act as the data controller for resident-related data. Mihro may act as a service provider or data processor where applicable.

Different users may access different parts of the platform depending on their role, permissions, and the modules enabled by the complex administration. These users may include residents, household members, staff members, complex administrators, and platform administrators.

Mihro may collect and process the following categories of information:

Account Data This may include name, email address, phone number, role, account status, language preference, authentication information, and session-related data.

Residential Data This may include complex, building, apartment, floor, household role, verification status, access level, and related resident profile information.

Vehicle and Parking Data If parking features are enabled, this may include vehicle plate numbers, vehicle details, assigned parking spots, parking zones, parking notifications, and parking-related activity.

Requests and Communications This may include fix reports, complaints, incidents, feedback, chat messages, administrator responses, status updates, timelines, and timestamps.

Packages and Reservations This may include package records, pickup status, facility reservations, event RSVPs, visitor passes, and related resident actions.

Access-Related Logs If access modules are enabled, Mihro may process gate access logs, entrance or intercom activity, guest pass usage, camera access sessions, and related audit records.

Device and Session Data This may include IP address, browser or device information, authentication events, access token metadata, security logs, and technical information needed to operate and protect the service.

Mihro may use cookies, local storage, and session storage for essential functions such as authentication, session persistence, language preference, PWA behavior, and user interface preferences.

Non-essential analytics or marketing cookies are only used if configured and disclosed.

Mihro uses data to:

- operate and secure the platform; - authenticate users; - enforce tenant isolation and role-based permissions; - display resident, admin, and staff modules; - manage building operations; - process requests, complaints, incidents, packages, reservations, and access actions; - send notifications and status updates; - maintain audit and activity logs; - improve reliability, security, and user experience.

Sensitive modules such as gate access, intercom access, guest passes, and camera viewing are controlled by backend permissions, tenant configuration, and administrator settings.

Resident data may be visible to authorized complex administrators, authorized staff members, and platform operators when required to provide and support the service.

Mihro may use trusted third-party service providers for hosting, database infrastructure, storage, email delivery, monitoring, and operational support.

Mihro does not sell resident personal data.

Data retention periods may depend on the residential complex, customer agreement, legal requirements, operational needs, and enabled modules.

Certain records, such as audit logs, access logs, billing-related records, and security events, may be retained for administrative, legal, or security purposes.

Customers may request export or deletion workflows where supported and legally permitted.

Mihro uses tenant-scoped data access, role-based permissions, protected APIs, audit and activity logging, and encrypted transport in production environments.

Access to sensitive features is controlled by permissions and administrator configuration. Gate, intercom, camera, and guest access actions are processed through the backend and are not exposed directly to residents.

No software system can be guaranteed to be completely secure. Customers should carefully manage administrator accounts, integrations, access permissions, and resident approvals.

Depending on your jurisdiction, you may have rights to access, correct, delete, export, restrict, or object to certain processing of personal data.

Residents should generally contact their residential complex or management company first, because they may be responsible for managing resident data inside the platform.

For platform privacy questions, contact:

[Contact Email]