When you sign in with Google, we request access to the following Google user data:

Google user data is used exclusively for the following purposes:

• Authentication: Your Google email and name are used to identify you when you sign in, display your profile, and associate your property listings or bids with your account.
• Property Listings: Sellers can upload supporting documents (title deeds, RAJUK certificates, floor plans) from their Google Drive to their property listing. We access only files you explicitly choose.
• Marketplace Data: Google Sheets is used as our backend database to store and retrieve property listings, buyer bids, and seller contact information in real time.
• Bid Submission: When a buyer places a bid, the bid details are written to a Google Sheet owned by the platform administrator.

We take your privacy seriously. Here is exactly how your data is — and is not — shared:

• No selling of data: We do not sell, rent, lease, or trade your Google user data to any third party under any circumstance.
• No advertising networks: Your data is never shared with advertising platforms, data brokers, or marketing companies.
• Platform administrator only: The backend spreadsheet data (listings, bids) is accessible only to the platform administrator (allinfo.realestatebd@gmail.com) for operational purposes.
• Firebase Authentication: Sign-in is handled by Google Firebase. Firebase processes authentication tokens securely and does not store or share your data beyond the authentication flow.
• Legal compliance: We may disclose data if required by law, court order, or government authority — only to the extent legally required.

We are committed to protecting your data with industry-standard security practices:

• No server-side storage: We do not maintain our own database of user data. All data resides within your own Google account (Drive, Sheets) and Firebase Authentication infrastructure.
• Authentication tokens: OAuth access tokens are handled exclusively by Firebase Authentication and are never logged, stored on our servers, or transmitted to third parties.
• HTTPS encryption: All data transmission between your browser and our platform is encrypted via HTTPS/TLS.
• Minimal data footprint: We request only the OAuth scopes strictly necessary for the features you use. We do not request broad access to your Google account.
• Google-managed security: Data stored in Google Drive and Google Sheets is protected by Google's own enterprise-grade security infrastructure.

We retain only what is necessary and provide clear options to delete your data:

In compliance with Google's requirements, we explain why each scope is necessary:

• drive.file — Allows sellers to upload property documents (title deeds, approval certificates) directly from their Google Drive to their listing. We access only files the user explicitly selects. This is the most restrictive Drive scope available and does not allow access to other files.
• spreadsheets — Our entire platform backend is powered by Google Sheets as a real-time database. This scope is required to read property listings for buyers, write new bids, and allow sellers to submit listings. No alternative scope provides this specific read/write capability.
• openid / profile / email — Required for Google Sign-In to identify users, display their name and profile photo, and associate actions (bids, listings) with their account.

You have full control over your data and Google account access:

• Revoke access anytime: Visit myaccount.google.com/permissions to remove our app's access to your Google account at any time.
• Request your data: Email allinfo.realestatebd@gmail.com to receive a copy of all data associated with your account on our platform.
• Request deletion: Email allinfo.realestatebd@gmail.com with "Data Deletion Request" and we will delete all your data within 7 business days.
• Opt out of non-essential features: You can use the browse/search features of our platform without signing in with Google.
• File a complaint: If you believe your data rights have been violated, you may contact your local data protection authority.