Hive24 legal information

Privacy Notice

Product: Hive24 mobile application and related services
Operator: NexLabs Technologies LLP
Registered address: To be supplied before publication
Privacy/grievance contact: support@hive24.app (monitoring and designated contact must be confirmed before publication)
Effective date/version: To be completed after approval

1. Scope and roles

This notice describes personal information processed through Hive24. NexLabs Technologies LLP operates the software. An apartment association, owner, or administrator may decide why resident, staff, and visitor information is collected for that community. The parties' roles depend on the feature and applicable law and must be confirmed before launch.

2. Information Hive24 may process

Account, authentication, verification, and account-status details, such as phone number, name, and email address if supplied.
Apartment, flat, membership, resident/staff role, and permission details.
Visitor details such as name, phone number, photo, vehicle, visit purpose, approvals, and entry/exit times.
Community content, including notices, complaints, maintenance requests, amenities, dues, expenses, and payment status where those features are used.
Location when a user invokes location-dependent features and grants device permission.
Device and service data such as notification tokens, app/device details, diagnostics, and request metadata used to provide and secure the service.
Images and documents intentionally uploaded by users, residents, staff, or administrators.

Avoid entering sensitive information in free-text fields unless it is necessary for the community workflow and the community is authorized to collect it.

3. Sources and purposes

Information may come from the account holder, apartment administrators, community members, visitors through a resident or staff member, a user's device, or service providers supporting authentication, storage, notifications, and OTP delivery. Hive24 uses it to secure accounts, manage community membership and visitor workflows, deliver requested notifications, store uploaded media, provide community features, prevent abuse, investigate incidents, provide support, and meet legal obligations.

4. Permissions and notifications

Hive24 requests device permissions when a feature needs them, such as selecting or taking a photo, apartment discovery, or notifications. Users can manage permissions in device settings. Declining an optional permission may make the associated feature unavailable.

5. Sharing and service providers

Information may be available to authorized members of the same apartment community according to their roles and the feature. Visitor details may, for example, be available to the resident responsible for the visit and authorized security staff. Administrators manage membership and role assignments.

Supabase: database, authentication, and object storage. The configured project is in Mumbai, India; backup and support locations still require confirmation.
Cloudflare: proxy for API traffic at api.hive24.app. Its products, logs, caching, data locations, and transfer safeguards must be verified before publication.
Google Firebase Cloud Messaging: push notifications and installation tokens.
MSG91: one-time-password delivery and verification.

Provider roles, subprocessors, contracts, and current privacy information must be confirmed for the final notice. Processing may occur in other locations through provider operations, support, backups, or security work.

6. Security and international processing

Hive24 uses access controls intended to limit personal information and photos to authorized users, but no online service can guarantee absolute security. Keep credentials private and report suspected compromise or data exposure to the monitored privacy contact and apartment administrator. The primary Supabase project is configured in Mumbai, India; API traffic also passes through Cloudflare, and other providers may process data elsewhere. Locations, logging, caching, and transfer safeguards remain to be verified.

7. Retention and deletion

Account information may be retained while needed to provide the service, meet legal obligations, resolve disputes, and protect security. Account deletion is available through the in-app flow or public deletion page, subject to ownership transfer and active-admin requirements. Some community, financial, security, or audit records may be retained or pseudonymized for documented legal, operational, or incident-response reasons.

Visitor records without an exit may be marked exited after 24 hours. Closed visitor records are scheduled for deletion after 90 days from the recorded exit time. Unvisited invitations are scheduled for deletion based on their last update. Legal obligations or authorized incident holds may extend retention. Provider backups and logs may have different periods. Production schedules and backup behavior must be confirmed before publication.

8. Requests and rights

Depending on applicable law, a person may have rights to request access, correction, erasure, portability, objection, restriction, or withdrawal of consent. Requests may be sent to support@hive24.app after the inbox and identity-verification process are confirmed. Requests about apartment records may also need to go to the relevant association or administrator. Response timelines and escalation routes must be completed before launch.

9. Children

Hive24 is designed for apartment residents, staff, administrators, and security personnel, not for children to create independent accounts. The minimum age and handling of information about minors must be confirmed before publication.

10. Changes and contact

Material changes should be published with a version and effective date. Where required by law or product policy, renewed acceptance or consent may be requested. The registered address, designated grievance contact, response process, and escalation mechanism must be completed before this draft becomes the final notice.