Scope
This policy applies to the Resident Club app, Resident Staff app, Resident.club website, and the community-management services that support them. Resident.club operates and maintains the platform, while a participating residential community may also act as the organisation responsible for resident, visitor, workforce and access records.
Information We Collect
Demo Enquiries
- Contact name, email, phone, role and preferred contact method or time
- Society name, size, city and optional address or map link
- Features of interest, current setup, hosting preference, timeline and other details you choose to share
- Contact consent, enquiry status and follow-up records used by the Resident.club team to respond to your request
Account and Community
- Name, mobile number and email address
- Community, home, household and role relationships
- Guard assignment, employer, shift and gate context
- Vehicle and emergency-contact information when provided
Community Activity
- Visitor invitations, approvals and entry or exit records
- Amenity bookings, helpdesk requests, notices, posts and reactions
- Documents uploaded to private community storage
- Maintenance invoices, payment status and receipt records; Resident.club does not store full card details
Camera, Biometric and Location
- Photos you choose to capture for face enrollment or guard attendance
- Encrypted face templates created only after explicit consent
- Temporary camera frames used for QR or identity checks
- Precise guard location when attendance or patrol verification is requested
Device and Diagnostics
- Device and app identifiers, push-notification tokens and operating-system information
- App interactions and notification-delivery status
- Crash reports, diagnostics, performance and security logs
- IP address and request metadata used to operate and secure the service
How We Use Information
- Authenticate users and maintain secure sessions
- Provide resident, visitor, access, amenity, helpdesk, workforce, document and billing features
- Deliver notifications and service messages
- Verify guard attendance and patrol activity where enabled
- Provide consent-based biometric enrollment and matching where enabled
- Prevent fraud, investigate security incidents, diagnose failures and improve service reliability
- Meet legal, safety, accounting and community-governance obligations
Storage and Service Providers
Core community records may be hosted on infrastructure operated for Resident.club or a participating community. Biometric templates and private documents are kept in their dedicated Resident.club services and are not placed in analytics systems.
The mobile apps use Google Firebase Cloud Messaging for push delivery, Firebase Analytics for product interaction data and Firebase Crashlytics for crash diagnostics. Map features use Google Maps. Transactional messages may be delivered through the email or SMS provider configured for the participating community. These providers process only the information needed for their service under their own security and privacy terms.
Sharing and Access
- Authorised community administrators, guards and staff according to their assigned role and location scope
- Service providers acting on our instructions for hosting, notification delivery, diagnostics and security
- Authorities or other parties when disclosure is required by law or necessary to protect people, property or the service
- A successor organisation in a corporate transaction, subject to appropriate confidentiality and notice obligations
Permissions and Sensitive Features
Camera
Used for QR scanning, optional face enrollment, identity assistance and guard attendance photos. The app asks before access.
Location
Used by Resident Staff when attendance or patrol verification requires it. Location is not collected continuously in the background.
Notifications
Used for visitor, security, helpdesk, community and service updates. Device settings can disable notifications.
Biometrics
Enrollment is optional, consent-based and isolated from ordinary profile data. Consent can be withdrawn from Resident app settings or by contacting us.
Retention and Deletion
We retain information only while needed to provide the service, maintain security and audit trails, resolve disputes, and comply with legal or accounting obligations. Retention periods vary by record type and community policy.
Resident Club users can start an account-deletion request from Profile, or use the Account Deletion page on this website. Resident Staff accounts are provisioned by an employer or community administrator; staff can request access removal through that administrator or contact us.
Your Choices and Rights
The Privacy Choices page explains how to exercise these options and how to contact us when a control is not available directly in an app.
- Access or correct your account information
- Withdraw optional biometric consent
- Control camera, location and notification permissions in device settings
- Request a copy of eligible personal information
- Request account and associated-data deletion
- Raise a privacy concern or complaint
Security and Children
We use access controls, scoped permissions, encryption and audit records designed to protect personal information. No system is completely secure, so users should protect their devices and report suspected misuse promptly.
Resident.club services are intended for participating communities and authorised personnel. A child should not create an account independently. Household information about minors must be provided and managed by an authorised adult or community process.
Contact Information
If you have any questions about this Privacy Policy or wish to exercise your rights, please contact us:
privacy@resident.club+91 080 4210 3876Brigade Cornerstone Utopia, Bangalore, IndiaResident.club Support Team