Delhi45Lite
⋮
Settings / सेटिंग्स✎ Write a post+ Add listing

News-feed notifications

Privacy policy

Updated 3 November 2026 · Website, Delhi45 Lite and Android.

View sections / विषय सूची

Information you provide

We use your name, email address, Firebase account ID and any verified phone number to operate your account. We also store the posts, comments, reviews, business details, uploads and support requests you submit. Passwords are handled by Firebase Authentication and are not sent to the Delhi45 PHP API.

Public information

Published posts, comments, reviews, business descriptions and listing contact details are public. Anonymous posts hide your name publicly; the service still retains the submitting account for moderation. Do not post sensitive information about yourself or others.

Location and uploads

With your permission, listing and community-update forms use your current device location to fill an address, city and matching neighbourhood. On the website, coordinates and your network IP are sent directly to BigDataCloud for locality lookup under its privacy policy (https://www.bigdatacloud.com/privacy). The mobile app uses the device geocoding service. GPS coordinates are not stored in your Delhi45 account; the address you confirm is saved with your submission. You can deny permission and enter the address manually. Photos you upload may contain metadata; avoid uploading material that reveals information you do not want to share.

Service providers and device storage

Firebase provides email, Google and phone authentication. Phone verification is subject to Google’s authentication and anti-abuse practices. Hosting and database providers process the records needed to operate the service. Your browser stores sign-in state through the Firebase SDK and may cache public assets and pages for offline use; authenticated API responses and account pages are not cached by the service worker.

Optional analytics and advertising

Where the consent platform confirms consent is not required, analytics and advertising default to enabled. A saved choice to disable them is preserved. Where consent is required or the region is unresolved, optional tracking remains disabled until the applicable choices permit it. You can change these settings at any time. With your choice, public website and Lite PWA pages use Google Analytics to measure visits and Google AdSense to support the service with ads. These providers process network/device information and may use cookies. Analytics page views omit URL query strings, form values, account pages, email, phone and precise addresses. Personalised ads are an optional choice. They are enabled only when supported by the applicable Google consent signals; without valid signals the site does not grant ad personalisation. You can choose Analytics and Ads separately, reject both, or change your choice at any time using Cookie & privacy choices in the footer. Essential sign-in, security and offline storage continue without optional tracking. Google privacy policy: https://policies.google.com/privacy; advertising choices: https://myadcenter.google.com/.

Radio and favorites

Delhi45 Radio stores station metadata and your account favorites. Guest favorites and recent stations stay in device storage. Audio connects directly to the station or its authorized provider, which receives your network/device information under its own privacy policy. Delhi45 does not proxy, record or offer downloads of radio audio. Playback counters are aggregate attempts, not individual listener profiles. Use Report station for stream, metadata or rights concerns. You may remove favorites at any time.

Optional mobile analytics and ads

The Android app uses Firebase Analytics for generic screen-visit events and Meta App Events for app opens, installs and advertising-campaign measurement when enabled in privacy settings. Meta may receive device and network information; advertising-identifier collection is enabled only when analytics and eligible personalised-ad choices allow it. Meta events do not include your name, email, phone, private messages or form contents. Meta privacy policy: https://www.facebook.com/privacy/policy/. Where Google UMP confirms consent is not required, analytics and advertising default to enabled unless you previously disabled them. It does not attach your account ID, name, email, phone, search text or private message contents to those events. AdMob and participating mediation partners, including Meta Audience Network, supply optional banner ads, with a separate choice for personalised advertising and Google consent controls on content screens and may process device, network and advertising identifiers for ad delivery, measurement and fraud prevention. Google consent messages apply where required. You can turn Analytics and Ads on or off separately in the app menu under Analytics & ads privacy. Login, posting forms and private inbox screens do not show ads. Google privacy policy: https://policies.google.com/privacy.

Advertising choices, GDPR and IAB

Analytics, ads and personalised ads are separate optional choices. On Android, Google User Messaging Platform (UMP) requests applicable consent and provides privacy options where required. On the website, Google’s certified consent message must be published in the publisher account before it can collect IAB TCF choices. Optional local switches do not replace that message or create a TCF consent string. Where applicable, non-essential consent is requested before use; rejecting or withdrawing it does not remove access to normal community features. Personalisation may use Google advertising/device identifiers and permitted interest signals; it is not guaranteed for every request.

Changing or withdrawing permission

Open Analytics & ads privacy in the Android menu or Cookie & privacy choices on the website/Lite PWA. You may decline optional measurement and advertising, or change previous choices. A change applies to future collection; data already lawfully processed may remain with providers according to their retention policies. Device permissions and push notifications can also be changed in system settings.

Bank directory and provider-backed widgets

Bank branch names, IFSC, addresses and contact details are public reference data imported from the attributed Razorpay dataset. A branch lookup may refresh that public record through Razorpay; stored data remains visible if the provider fails. Missing fields are not filled with invented details. Weather city searches may be sent to WeatherAPI or OpenStreetMap/Nominatim and approximate forecast coordinates to MET Norway. Device location is requested only when you choose the location option; coordinates are rounded to two decimal places before the widget request. Stock ticker preferences stay on the device/browser; selected symbols are sent to the quote provider through the Delhi45 server. NewsAPI headline metadata is used only when a production-eligible account is configured. Provider keys remain private on the server.

YouTube and external information sources

YouTube players and external links are provided by third parties and may receive IP address, device information and the page/referral information needed to serve their content. Gold API metal quotes and Frankfurter/ECB currency reference data are fetched by the Delhi45 server and cached; your account information is not sent with that request. Weather forecasts are fetched server-side for fixed Delhi/Palam coordinates from MET Norway; no user GPS or account details are sent. Stock, weather and hallmark source links open the source’s own site, where its privacy practices apply.

Your access, correction and deletion requests

You can edit your profile and owned listing, choose profile visibility, request account or selected-data deletion, or contact bluedotcom@gmail.com for access and correction help. We may ask for enough information to confirm ownership. We do not publish private account email/phone on public profiles; business contacts you intentionally put in a listing are public. Copies shared by other users, search engines or external sites may take time to disappear or require a separate request.

International processing and retention

Google and hosting providers may process information outside your country under their applicable terms and safeguards. Delhi45 keeps account and submitted content while needed to operate the service, process your requests and investigate abuse. Public offline copies may remain on a device until refreshed or cleared. We do not claim a fixed deletion time for provider backups or records retained for a lawful obligation.

Use and protection

Information is used to provide the service, connect neighbours, prevent abuse, handle requests and moderate content. We restrict private actions to the authenticated account, use encrypted network transport on the live service and limit repeated requests.

Push notifications

Notifications are optional. When you enable them, Firebase Cloud Messaging issues a device/browser token. Delhi45 stores the token, platform and a random installation identifier to deliver local updates. Tokens are not tied to an account. Disable notifications from the same device or browser settings. Google handles push delivery.

Views and app security

Opening a community update sends its post ID and a locally stored visitor identifier to count views. The server stores a daily hash of that identifier with the post rather than the original identifier. Firebase Authentication processes network and device information for authentication and abuse prevention. Android app security verification uses Firebase App Check and Google Play Integrity to process app and device attestation information.

Reporting and blocking

Content includes opaque author identifiers so the app can remember authors you block on that device. Anonymous updates use a separate identifier from named content. Reports sent to the team include the reported content reference and your signed-in account for review.

Retention and your choices

Request account or selected-data deletion using the deletion page. Requests are reviewed by support. Records needed to investigate abuse, meet legal requirements or maintain security may be retained as required. Contact the team if you cannot access your account.

Children and policy changes

Do not submit children’s personal information or private information about another person without appropriate permission. Changes to service practices will be reflected in this policy.

Community content and complaint handling

  1. Public posts, replies, reviews and rental contacts can be read without login, shared by others and indexed by search engines. Profile privacy does not make previously published public content confidential.
  2. A report or moderation appeal is handled as a support record linked to the reporting account where authentication is required. Provide only the details needed to investigate; avoid sending OTPs, passwords or unnecessary identity documents.
  3. The reported author is not publicly given your private contact information as part of the reporting interface. Limited information may be used for review, abuse prevention, legitimate investigation or a lawful disclosure.
  4. Relevant content and records may be retained where needed for applicable legal obligations or an investigation. Requests for access, correction or deletion can be sent through Contact & support or the account deletion page.

Rental search, dates and public owner details

  1. Room/PG searches use the locality, budget, selected facilities, floor and move-in date you choose. Searching does not publish your contact details or make a rental enquiry automatically.
  2. A property owner must agree before publishing the rental phone, address and photos. These deliberately public listing contacts are separate from private account email/phone and may be copied by other people.
  3. Do not upload tenancy agreements, financial records, identity documents or photographs that reveal another person’s private information without permission. Confirm your consent before publishing.
  4. Availability and facility selections are owner-provided. A change or removal on Delhi45 may not immediately remove copies stored by other users, external sites or search engines.

Event registrations and saved login

  1. Event registration records associate your account with the event, ticket type, attendance choice and a reference so that you can view or cancel your own RSVP. Public ticket availability shows aggregate counts, not an attendee directory.
  2. You may choose to open external maps, calendars or organiser contact links; the destination’s own privacy practices apply. A shared event link is public and does not include your private registration reference.
  3. Firebase maintains saved sign-in and refreshes short-lived credentials. Delhi45 applies a maximum sign-in age of 180 days; logout, cleared storage, revoked access or account security changes can require earlier sign-in.
  4. On a shared device, sign out when finished. Optional advertising/analytics choices do not replace login security and are not a condition for reporting abuse or reading public content.

Report / Contact the Delhi45 team →

Delhi45 menu

Shop complaint

Delhi45 on your Home Screen

Full installation guide
Repair / Refresh Delhi45