Review building entry and visitor privacy

Identify the system and who manages its data

ButterflyMX's policy describes property owners and managers as business customers and the company as a processor of tenant and visitor data. Its California rights section says tenants or visitors may need to send requests to the property owner or manager. Ask who handles the relevant records and the applicable request route; rights and procedures can differ by jurisdiction. ButterflyMX: property data, optional contacts and processor role

Ask what an event means and who can see it

The technical guide distinguishes access attempts, unlocks and call attempts, with different permission scopes. Ask which events are logged at the property, which account or credential they name, and who can review them. A log label should be interpreted alongside the method and result. ButterflyMX: access attempts, calls and permission scope

The administrator guide describes filters and emailed PDF reports. Useful questions include the retention period for each event and image type, permitted recipients, export handling and how errors are corrected. The availability of a reporting feature does not itself explain the property's actual policy. ButterflyMX: administrator call and door-release records

Review directory visibility and the loss of panel calls

The focused directory help says a resident can have their name hidden while retaining app access. Visitors then cannot call that resident from the entry panel. It directs users to Support for that request. Confirm the intended effect with the property before changing a directory entry used by visitors or deliveries. ButterflyMX: directory visibility and call consequences

Review existing visitor and delivery passes

The visitor-pass help says door access, active times and expiry are part of the pass, and property management controls availability. Review an existing pass's purpose, recipient and intended duration. Deleting a pass is an access decision, separate from a request about retained event records. ButterflyMX: visitor-pass scope and photo availability

1. In the Delivery Pass help, Visitor Access > Active/Expired shows created delivery and visitor passes. It documents Edit to remove a pass that is no longer needed, with confirmation for an unused delivery pass. Check the specific feature's current label and the pass being changed. ButterflyMX: reviewing and removing existing passes
2. The same help describes single-use delivery passes and a maximum validity of 30 days if unused. That is a pass-validity description, not a promise that its history or photos are deleted after 30 days. ButterflyMX: reviewing and removing existing passes

Review vehicle access through the property's allowed role

The vehicle help says residents can edit their own vehicle details only where the property permits resident management. Otherwise an administrator handles changes. It expressly says removing or editing the vehicle does not change past plate history. Read those effects before requesting a vehicle-access change. ButterflyMX: vehicle access and retained history

Review optional phone contact access separately

The policy describes phone-contact syncing as optional and permission based. Review that app permission if the feature is unused. It is a separate choice from records generated by the building's intercom or access system. ButterflyMX: property data, optional contacts and processor role