COMVIST · TRUST & PRIVACY
Privacy Policy
How Comvist handles information for residents, guards, management, and people visiting their communities.
Effective and last updated:
- App & developer
- Comvist — Bhaskar Vepa
Android package: in.comvist.app - Privacy contact
- saibhaskar.as400@gmail.com
Initial launch: India
About this policy
Comvist is one app for residents, guards, and management. This policy covers the Android app, related web application, and marketing website. Your community may maintain its own records and have separate responsibilities for information it adds to Comvist. Contact us for help identifying the appropriate community contact.
Comvist’s resident, guard, and management accounts are intended for adults aged 18 or older. This statement does not mean that an automated age-verification system is in place. Visitor records may concern people under 18. Only provide visitor information that is necessary for community access and that you are authorised to provide. A parent or guardian can contact us about a child’s information.
Information we collect and why
- Accounts and community assignments: names, email addresses, phone numbers, roles, memberships, and unit assignments identify accounts, control access, and route relevant community information.
- Bills and payment proofs: bill details and uploaded proof files, including payment details visible in them, support billing, reconciliation, and management review. Avoid uploading unrelated personal or financial information.
- Visitors and gate activity: visitor names and contact details, entry/exit records, vehicle numbers, and optional visitor photos support visitor approval, identification, and gate operations. Residents or authorised staff may supply this information, not only the visitor.
- Contacts you select: the contact picker uses the name and phone number of the contact you choose to help fill visitor details. It does not upload your entire address book.
- Communications and notifications: community communications, poll responses where used, support messages, and notification tokens or subscriptions support community updates and relevant notifications.
- Technical information: hosting requests, authentication events, and operational error information support service operation, access security, and troubleshooting.
Access within a community
Access depends on the user’s role and community or unit assignment. Residents access relevant account, unit, billing, and visitor information. Guards use visitor and gate-operation information required for their duties. Authorised management users handle community administration and relevant billing and visitor records. A guard role does not by itself grant billing access.
Comvist platform support may access information as needed to investigate issues, administer the service, and handle privacy requests. Shared community records may remain relevant to other authorised users after one person leaves, subject to the retention and deletion rules below. Community removal alone does not delete the global Comvist account.
Service providers and processing
- Supabase: authentication, application database, and storage of uploaded files.
- Expo and Firebase Cloud Messaging: Android push-notification delivery using notification tokens. Web notifications, when enabled, use the push service associated with the user’s browser.
- OpenAI: Comvist’s production backend is configured to process uploaded payment-proof files using OpenAI to extract details such as amount, date, and payment reference. This can transmit the proof image or PDF itself, including personal and financial information visible in it, not just extracted text. Processing happens on the server, not on the phone. Extraction may fail; a failed result does not establish that the file was never transmitted. Extracted results assist reconciliation and may require management review.
- Vercel: website hosting and delivery of website requests and assets.
When you choose to send a website enquiry through WhatsApp, WhatsApp processes that message under its own terms. Service-provider processing may take place outside India; India-only availability does not establish India-only processing. Provider handling and any copies retained by those providers are subject to their applicable service arrangements and retention practices. We do not promise zero provider retention.
Information may also need to be disclosed in response to a valid legal requirement. Such a disclosure is separate from routine community-role access.
Device permissions and your controls
- Contacts: for user-selected contact picking. You can enter visitor details manually instead.
- Camera: for QR scanning and optional live visitor-photo capture. Visitor-photo capture does not require microphone recording.
- File or photo selection: you choose payment-proof files to upload. Do not include unrelated records.
- Notifications: for relevant updates. You can change permission in device settings; denying it prevents push delivery, not the existence of in-app information.
Permissions can be changed in device settings. Refusing permission may limit the feature using it. Only provide another person’s details or photo when authorised to do so, and tell them how the information will be used.
Security practices
Comvist uses authenticated requests, role-based access checks, and private storage buckets for payment proofs and visitor photos. These controls help limit access; no system eliminates every security risk. Keep credentials private and report suspected unauthorised access to our privacy contact.
We do not claim end-to-end encryption, a security certification, or an independent security audit.
Retention and deletion
Our approved retention schedule is set out below. A retention period is not a promise of instant deletion at an exact minute. Account deletion and requests concerning particular records are handled by Comvist support.
- Visitor photos 30 days
- Access expires after 30 days. A scheduled backend worker attempts to remove expired photo files and metadata and retries failures. Temporary cleanup failures can delay physical removal. Visitor entry/exit history is a separate category.
- Visitor entry/exit history 90 days from record creation
- This is the normal retention limit for gate-history records. Longer retention is limited to a documented unresolved dispute or a specific legal obligation.
- Bills and payment proofs 24 months after the associated bill closes
- These records support reconciliation and dispute review. A bill closes when settled and any related dispute is resolved; unresolved bills remain subject to review. Longer retention is limited to a documented unresolved dispute or a specific legal obligation, not a blanket exception.
- Account information and other operational records
- Account and assignment information supports the active account. Upon a verified deletion request, Comvist support handles removal of the account, memberships, personal profile information, notification tokens, subscriptions, and associated personal data, subject to the limited exceptions described here. Support correspondence and technical logs are reviewed for operational need; this policy does not promise a fixed expiry for those categories.
- Backups and service-provider copies
- A fixed backup-expiry period has not been verified, and we do not promise 30-day backup deletion or immediate removal of every provider-held copy. Support will explain any known retained copies and applicable restrictions when handling a deletion request and seek deletion from relevant service providers where applicable.
Current implementation: automatic cleanup of visitor entry/exit history and bills/payment proofs is not implemented. The periods above are the approved retention rules, not a claim that automated expiry is running. Contact support to request review and removal of records that exceed these periods.
Account deletion does not restart an existing retention period. Any retained record must be limited to necessary information, restricted to the relevant purpose, and deleted when that purpose and any applicable retention requirement end. Where an exception applies, support will explain the record category, reason, and applicable period or condition for deletion.
Access, corrections, and account deletion
For questions, corrections, or access requests, email saibhaskar.as400@gmail.com. To request deletion of your account and associated data, follow the Account Deletion instructions. No login or app reinstallation is needed to contact us.
Requests are handled manually by Comvist support, led by Bhaskar Vepa. Support verifies account ownership before disclosing or removing information and confirms the outcome. Community management may help verify membership but cannot substitute community removal for global account deletion. No instant or automated account-deletion service is promised.
Marketing website and enquiries
The contact form prepares a WhatsApp message in your browser using the details you enter. It does not submit an enquiry to a website form database. Opening WhatsApp does not send it automatically; you choose whether to send it. Avoid passwords, access codes, resident lists, or sensitive payment information.
The light/dark choice is saved in this browser’s local storage. Clear this site’s browser data to remove it. Website requests are handled by Vercel; see Vercel’s privacy policy.
Contact and updates
Developer and privacy contact: Bhaskar Vepa, saibhaskar.as400@gmail.com.
We will update this page when our practices change and identify the updated date. Where required, material changes will be communicated before changed practices take effect.