BlueCave

Privacy & data

Published 7 November 2026 · Initial pilot

BlueCave helps apartment and PG communities manage everyday operations. This notice describes the current app’s data handling. Your property’s own management practices and records are separate.

Account and property records

We store account identity, verified email, securely hashed passwords for email accounts, sessions, property memberships, invitations, announcements, complaints, bookings, dues and payment records. Google sign-in uses basic account identity; BlueCave does not request access to Gmail or Google Drive. Passwords and Google client secrets are not exposed to property managers.

Who can see what

Property access is limited by role and membership. Authorized managers handle operational records for their property; guards see the records needed for gate operations. Payment receipts contain payer, property and confirmation details. BlueCave operators can review property applications and operate the underlying service.

Guardian sharing

Guardian links require an invitation and acceptance. Students choose whether to share dues/receipts, relevant announcements, presence and serious-incident notices. Either party can revoke a link. Revocation removes further access through BlueCave, but cannot recall copies previously downloaded or notifications already delivered.

Complaints and serious concerns

Anonymous complaints hide the reporter’s identity from property managers and guardians. BlueCave retains an internal account association for private replies, duplicate prevention and resolution confirmation. Routine complaints stay within the property. With incident-sharing consent, serious-incident notices follow the configured automatic rules. A notice describes a reported concern, not an independently verified fact, and does not share the private complaint thread.

Location and gate history

Location is requested only when a student chooses a check-in and grants browser permission. Raw coordinates are used to calculate proximity to the PG and are not stored. We store the proximity result, accuracy and timestamp. Guard-recorded entry/exit events are stored separately. Presence records are pruned after 30 days; old or uncertain location readings show Unknown. There is no continuous background location tracking.

Providers and notifications

Cloudflare hosts the app and database; Google supplies optional sign-in; Resend delivers verification and recovery emails. Optional web push uses the browser’s push service and stores a subscription endpoint and keys. Push notifications use generic text; sign in to read the update. Hosting and authentication providers may process request and security metadata.

Storage and retention

Authentication uses cookies. The app stores your last dashboard selection on your device; the offline cache contains only a public icon and fallback page. Private API responses are not cached by the app. Property, payment and audit records are retained for community operations until an appropriate retention or deletion action is agreed. They are not automatically removed when a guardian link ends. Backups and downloaded receipts may retain historical records.

Your choices and contact

You can decline location and push, end guardian sharing, and sign out. Contact your property manager about operational corrections and the BlueCave operator about account access, data requests or this notice. Do not include sensitive identity document numbers in a request. This initial pilot supports adult accounts; minor-specific onboarding is not enabled.