Back to home

Privacy Policy

Effective date / Last updated: June 24, 2026

1. Introduction — Who We Are

ClearHost ("ClearHost," "we," "us," or "our") provides a cloud-based hospitality Property Management System (PMS) and related services that help hotels, hostels, guesthouses, and other accommodation providers manage properties, bookings, guests, billing, and marketing. Our services are available at https://clearhost.in and associated subdomains and applications (collectively, the "Service").

This Privacy Policy explains what personal data we collect, how and why we use it, who we share it with, how long we keep it, and the rights and choices available to you under India's Digital Personal Data Protection Act, 2023 (the "DPDP Act"). It also describes how the Service interacts with third-party platforms, including Google and Meta (Facebook and Instagram).

ClearHost is the Data Fiduciary (controller) for personal data we collect about our account holders, prospective customers, and website visitors. For most personal data relating to hotel guests and bookings, our customers (the accommodation providers using the Service) are the Data Fiduciaries and ClearHost acts as a Data Processor on their behalf. See Section 2 ("Scope") for details.

If you have any questions, contact us at support@clearhost.in.

2. Scope

This Policy applies to:

  • Platform users / staff — owners, managers, and staff of accommodation businesses who hold ClearHost accounts.
  • Organizations and properties — the businesses and properties managed through the Service.
  • Hotel guests and customers — individuals whose data is entered into, or synchronized into, the Service by our customers (for example, through manual entry, the direct booking engine, or channel-manager / OTA synchronization).
  • Website visitors and prospects — visitors to https://clearhost.in.

Fiduciary vs. processor. When ClearHost decides why and how personal data is processed (e.g., your ClearHost login, billing for your subscription, our website), ClearHost is the Data Fiduciary. When our customers use the Service to manage their guests and bookings, the customer is the Data Fiduciary and ClearHost processes that data on their instructions. If you are a hotel guest and wish to exercise rights over your data, please contact the accommodation provider you interacted with; we will assist them as their processor. You may also contact us at support@clearhost.in and we will route your request appropriately.

This Policy does not apply to third-party websites, products, or services that we do not control, even if we link to them (see Section 16, "Third-Party Links").

3. Information We Collect

We collect the following categories of personal data. Not every category applies to every individual.

3.1 Account and profile data (platform users / staff)

  • Name, first name, last name
  • Email address (used as your unique login identifier)
  • Phone number
  • Profile image
  • Role and permissions, email-verification status
  • Account credentials — passwords are managed and hashed by our authentication provider (better-auth); we do not store your password in plain text. If you sign in with Google, we receive your Google account email and basic profile (see Section 7.1(a)).

3.2 Organization and property data

  • Organization name, slug, and GST number
  • Staff memberships, roles, permissions, and last-active timestamps
  • Staff invitations (invitee email, assigned role, property assignments, expiry)
  • Per-property contact details: contact email, phone number, address, and city

3.3 Guest and booking data (entered or synchronized by our customers)

This is the most sensitive category of data processed through the Service. Depending on how the accommodation provider uses ClearHost, it may include:

  • Guest identity: name, surname, email, phone, postal address (address, city, ZIP/postal code, country)
  • Date of birth
  • Company name and GSTIN
  • Government-issued identity documents: document type (passport, national ID, driver's license, Aadhaar, PAN, voter ID), document number, uploaded copies/images of the document, and verification status
  • Guest preferences, staff notes about a guest, tags, and blacklist status and reason
  • Booking and stay records: arrival and departure dates, occupancy details (adults, children, infants, ages), folio charges, special requests, payment method and status
  • Service requests (e.g., guest name, room number, message)
  • For reservations synchronized from online travel agencies (OTAs) via our channel-manager integration, a card "guarantee" block (cardholder name, card type, card number, expiration date, and security code) may be received from the OTA to honor the reservation (see the note below and Section 12)
  • Ad-click attribution identifiers associated with a booking (e.g., gclid, wbraid, gbraid, fbc, fbp, and the landing URL)

Note on sensitive personal data. Government identity documents and similar information are treated as sensitive. Accommodation providers are responsible for collecting such data lawfully and for entering it into the Service only where permitted. Card guarantee data received from OTAs is described further in Section 3.5 and Section 12 (Security).

3.4 Direct booking-engine data (public bookers)

When a guest books directly through a property's ClearHost booking engine, we collect: first name, last name, email, phone, special requests, and ad attribution identifiers.

3.5 Payment and billing data

  • Subscription billing. ClearHost subscriptions and booking payments are processed by our payment processor, Razorpay. For these payments we store Razorpay order, payment, subscription, and customer identifiers and signatures, along with billing metadata (e.g., customer name, amounts, GSTIN, payment method/reference). We do not store raw card numbers for SaaS subscription billing; card data is handled by Razorpay.
  • Property-connected Razorpay credentials. A property may connect its own Razorpay account to collect booking payments through its booking engine. In that case we store the property's Razorpay key ID and a Razorpay key secret; the key secret is encrypted at rest using AES-256-GCM (see Sections 7.3 and 12).
  • OTA card guarantees. As noted in Section 3.3, card guarantee details received from OTA channels are stored only to fulfill those reservations; see Section 12 for how this data is treated.

3.6 Usage, log, and device data

  • Activity and audit logs: the acting user's name, role, and user ID; IP address; device/user-agent string; and session timestamps
  • Notification records and preferences (in-app and email; an optional per-user Slack webhook URL if you choose to enable Slack notifications)
  • Standard technical information generated when you use the Service (e.g., request metadata)

3.7 Cookies and local storage

We and our service providers use cookies and similar technologies. ClearHost uses authentication/session cookies to keep you signed in (in production, these are scoped to the .clearhost.in domain so they work across our subdomains). The web application also uses browser localStorage for client-side application state and to capture ad-attribution parameters from your visit. See Section 14 ("Cookies and Similar Technologies").

We do not embed third-party web-analytics or session-replay SDKs in the web application.

3.8 Data from connected integrations

If you (or your organization) connect a third-party account — for example Google Sign-In, a Google Ads account, a Meta Ads account, or a property-level Razorpay account — we receive or store data from those platforms as described in Section 7 ("Third-Party Services, Connected Integrations, and Sub-Processors"). This includes OAuth tokens or API credentials, account and campaign identifiers, billing/spend information, and advertising metrics.

4. How We Use Information

We use personal data to:

  • Provide and operate the Service — create and manage accounts and organizations; authenticate users; manage properties, guests, bookings, billing, and notifications.
  • Process transactions — handle subscription billing and booking payments through Razorpay.
  • Communicate with you — send transactional and account emails (e.g., email verification, password reset, welcome, and operational notifications) via our email provider (Brevo).
  • Provide marketing and advertising tools to our customers — through the optional "Promote Property" feature, help accommodation providers create and manage their own advertising campaigns on Google Ads and Meta, read campaign metrics and billing/spend from those platforms, and (where the provider configures it) upload hashed conversion data to measure ad performance (see Sections 7.1(b) and 7.2).
  • Support property onboarding and location features — provide address autocomplete and map display using Google Places and Google Maps (see Section 7.1(c)).
  • Maintain security and integrity — detect, investigate, and prevent fraud, abuse, and security incidents; maintain audit logs.
  • Comply with legal obligations — including tax, accounting, and lawful requests from authorities.
  • Improve the Service — diagnose problems and improve features that are visible to users.

We do not sell personal data, and we do not use Google user data or Meta Platform Data to train generalized or general-purpose artificial intelligence models. Where the Service uses a third-party AI provider (OpenAI) to help generate advertising copy and creative suggestions, it processes only the marketing inputs the user provides for that feature; it is not used to read your Google or Meta user data for AI training.

5. Consent and Legal Grounds for Processing (DPDP Act, 2023)

Under India's Digital Personal Data Protection Act, 2023, we process your personal data on the following grounds:

  • Your consent. We ask for your consent — for example, when you create an account, connect an optional integration (Google Sign-In, Google Ads, Meta Ads), or enable certain features. Your consent is free, specific, informed, unconditional, and unambiguous, and is limited to the personal data necessary for the stated purpose. You may withdraw your consent at any time and as easily as you gave it (see Section 11). Withdrawal does not affect the lawfulness of processing carried out before the withdrawal.
  • Certain legitimate uses recognised by the DPDP Act — such as where you voluntarily provide your personal data for a specified purpose, to comply with a legal obligation or order, and for other purposes permitted under the Act.

Where ClearHost acts as a Data Processor on behalf of a customer who is the Data Fiduciary (e.g., guest and booking data), that customer is responsible for obtaining the necessary consent and establishing a valid ground for processing.

6. Disclosure and Sharing of Information

We share personal data only as described below. We do not sell personal data.

  • With your organization. Data you submit is accessible to authorized members of your organization according to their roles and permissions.
  • With service providers and sub-processors. We use the third parties listed in Section 7 to operate the Service. They process data only on our instructions or as needed to provide their service.
  • With connected ad platforms at your direction. When you use the "Promote Property" feature, campaign and (optionally) hashed conversion data are sent to Google Ads and/or Meta to run and measure your campaigns. Campaigns are created on the advertising account you connect.
  • For legal reasons. We may disclose data to comply with applicable law, regulation, legal process, or enforceable governmental request, or to protect the rights, property, or safety of ClearHost, our users, or others.
  • In a business transfer. If ClearHost is involved in a merger, acquisition, financing, reorganization, or sale of assets, personal data may be transferred as part of that transaction. Where required, we will provide notice and obtain consent before Google user data or Meta Platform Data is transferred.

7. Third-Party Services, Connected Integrations, and Sub-Processors

We rely on the following third parties. Each processes only the data needed for its function.

Provider Purpose
better-auth Authentication, session management, and password hashing
Google (Identity / Sign-In) Optional social login (see 7.1(a))
Google Ads Optional advertising via "Promote Property" (see 7.1(b))
Google Maps / Places Address autocomplete and map display (see 7.1(c))
Meta (Facebook / Instagram) Ads Optional advertising via "Promote Property" (see 7.2)
Razorpay Subscription and booking payments; optional property-connected accounts (see 7.3)
Brevo Transactional email delivery
Cloudinary Media and document (including guest ID document) hosting
Channex Channel-manager / OTA synchronization (source of OTA booking and card-guarantee data)
OpenAI AI-assisted advertising copy/creative suggestions
Slack Optional per-user notification webhooks (only if you enable it)
MongoDB Atlas Primary managed database
DigitalOcean (App Platform) and Cloudflare Application hosting and content delivery / security

We may update this list as our providers change. The current list is maintained in this Policy.

7.1 Google API Services / OAuth, Sign-In, Ads, and Maps

ClearHost's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The following describes, for each Google integration, the Google user data we access, and how we use, store, share, retain, and delete it.

(a) Google Sign-In (Google Identity)

  • What we access. If you choose "Sign in with Google," we use Google's default sign-in scopes (openid, email, and profile). We read your Google account email and basic profile, from which we derive your first and last name.
  • How we use it. Solely to create and authenticate your ClearHost account and to populate your profile. This is a user-facing login feature.
  • How we store it. Your email and name are stored in your ClearHost user profile. Sign-in sessions are managed by our authentication provider using signed session cookies.
  • How we share it. We do not share this Google profile data with third parties except the infrastructure providers needed to run the Service (Section 7), and never for advertising or sale.
  • Retention and deletion. Retained for the life of your account; deleted or anonymized when your account is deleted, subject to Section 10. You can disconnect Google Sign-In or delete your account by contacting support@clearhost.in (see Section 7.1(e) for our Google data-deletion path).

(b) Google Ads API ("Promote Property")

  • What we access. Through a separate, explicit OAuth consent flow, we request a single scope: https://www.googleapis.com/auth/adwords. We use access_type=offline and prompt=consent to obtain a long-lived refresh token. We use a Google Ads developer token and, optionally, a manager (MCC) account.
    • We read: the Google Ads customer/account IDs you can access and their descriptive account names; campaign metrics and cost/spend; and geo-target constants used for targeting.
    • We write (only on the advertising account you connect, and only at your direction): campaign budgets, campaigns, ad groups, geo-targeting criteria, phrase-match keywords, and Responsive Search Ad headlines, descriptions, and final URLs.
  • Why we need it. To let you create, manage, pause, and report on your own search-advertising campaigns from within ClearHost.
  • How we store it. Your Google Ads refresh token is encrypted at rest using AES-256-GCM and stored as an encrypted credential in our database. It is decrypted only in memory for the duration of an API call and is not cached in plain text.
  • How we share it. Campaign data and instructions are sent to the Google Ads API to operate your campaigns. We do not sell this data or share it with data brokers.
  • Retention and deletion. The encrypted token is retained while your Google Ads connection is active. When you disconnect, we make a best-effort call to Google's token-revocation endpoint and delete the stored token. See Section 7.1(e) to request deletion.

(c) Google Maps Platform — Maps and Places

  • What we access. During property onboarding, we use the Google Places API (New) for address autocomplete and place details, and the Google Maps Embed API to display a map. When you select a place, we may receive and store the following place details to populate your property record: place ID, display name, formatted address, phone number(s), website URL, Google Maps URL, rating and user-rating count, price level, opening hours, business status, latitude/longitude, and Plus Code.
  • Why we need it. To make property setup faster and more accurate and to display location on the property page.
  • Caching. We store the place ID as a stable identifier (the place ID is exempt from Google's caching restrictions). We do not pre-fetch, cache, or store other Places content beyond Google's allowed limits.
  • Attribution and Google's policy. ClearHost's use of Google Maps Platform is subject to the Google Privacy Policy, which is incorporated here by reference. Maps and Places features display the required "powered by Google" attribution.
  • Retention and deletion. Place details stored on a property record are retained for as long as the property exists in your account and are deleted when the property or account is deleted.

(d) Limited Use affirmation (all Google APIs)

ClearHost's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. These requirements apply to the raw data obtained from the scopes and to data aggregated, anonymized, or derived from them.

In particular, ClearHost: (1) limits its use of Google user data to providing or improving user-facing features that are prominent in the Service; (2) does not transfer Google user data except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger or acquisition with prior user notice and consent; (3) does not allow humans to read Google user data unless we obtain your affirmative agreement, it is necessary for security or to comply with law, or the data is aggregated and used for internal operations; and (4) does not sell Google user data, transfer it to data brokers or information resellers, use it to serve advertisements, use it for credit or eligibility decisions, or use it to train generalized AI models. The Google integrations ClearHost currently uses are Google Sign-In, the Google Ads API, and the Google Maps Platform (Maps and Places), each described above. If we ever wish to access a type of Google data not disclosed here, we will first update this Policy and prompt you to re-consent.

(e) Requesting deletion of your Google data

You can disconnect a Google integration at any time within ClearHost, or delete your account. To request modification or deletion of any Google-derived data ClearHost holds about you (your Google Sign-In profile data or a connected Google Ads credential), email us at support@clearhost.in with the subject line "Google Data Deletion Request" and the email or account associated with the connection. We will verify your request, delete the relevant data (including making a best-effort revocation call to Google for any stored Google Ads token), and confirm completion.

You can also revoke ClearHost's access to your Google account at any time from your Google Account security settings at https://myaccount.google.com/permissions (Third-party apps & services); revoking there immediately invalidates the tokens ClearHost holds.

7.2 Meta (Facebook & Instagram) Platform

ClearHost's Meta integration is exclusively an advertising integration within the optional "Promote Property" feature. It lets an accommodation owner connect their own Facebook/Meta advertising account so ClearHost can create and manage ad campaigns on their behalf, read billing/spend, and surface metrics. ClearHost does not publish organic content to your Facebook Pages or Instagram, and does not use any Instagram content-publishing or Page-posting capability. (Any Instagram link shown in a property's booking-engine page is simply a URL you enter manually; it does not use the Meta API.)

(a) Permissions we request

When you connect Meta, we request these permissions: ads_management, ads_read, business_management, and pages_read_engagement. The auth_type=rerequest option is used so that previously declined permissions can be re-requested.

(b) What Meta data we access and store

  • Your Meta/Facebook user ID (from GET /me), used transiently during connection.
  • A long-lived (~60-day) user access token, obtained by exchanging the authorization code; it is stored encrypted at rest with AES-256-GCM, together with its expiry timestamp. We do not silently refresh it — when it expires you are prompted to reconnect.
  • Your ad account list (account ID such as act_XXXX, name, account ID, status, and currency), discovered via GET /me/adaccounts, and the selected ad account.
  • Your Facebook Page list (Page ID and name), discovered via GET /me/accounts, and the Page you select (a Page is required as the source for ad creatives).
  • Billing/account standing: account status and funding-source display string (e.g., a prepaid balance), and lifetime ad spend (from account-level insights).
  • Created ad objects (campaign, ad set, and ad IDs) and daily campaign metrics (spend, clicks, and conversions/purchase actions).
  • Optionally, a Meta pixel/dataset ID to support sending purchase events via Meta's Conversions API.

All Meta data is collected from the connecting app owner / property owner. No Meta data is collected from booking-side guests.

(c) How we use Meta data

To create, manage, and report on your advertising campaigns; to show you account status, funding, and spend; and (where you configure it) to send conversion events that measure ad performance. Where conversion events are sent, guest email and phone used for matching are hashed with SHA-256 before transmission.

(d) Sharing and retention

Meta-derived data is processed only to provide the advertising features described above and is shared only with Meta (to operate your campaigns) and the infrastructure providers in Section 7. We only process Meta Platform Data as described in this Policy, and we do not sell, license, or purchase Platform Data. We retain the encrypted token and connection data while your Meta connection is active and delete it when no longer necessary for a legitimate business purpose, when you disconnect, when you ask us to, when we stop operating the feature, or if Meta requests it.

(e) How to request deletion of your Meta data

You can disconnect your Meta account at any time within ClearHost. When you disconnect, ClearHost makes a best-effort call to DELETE /me/permissions to revoke the app's access on Meta's side and then removes the stored Meta credentials and connection details (encrypted access token, external account ID, token expiry, Page ID, account/page option lists, pixel ID, and funding details) from our systems.

To request modification or deletion of any Meta-derived data ClearHost holds about you, email us at support@clearhost.in with the subject line "Meta Data Deletion Request" and the email or account associated with the connection. We will verify your request, delete the relevant data, and confirm completion. This contact is provided as our data-deletion contact for Meta-related data in accordance with Meta's Platform Terms and Developer Policies.

7.3 Property-connected Razorpay accounts

In addition to ClearHost's own subscription billing through Razorpay, a property may connect its own Razorpay account so that booking payments are collected directly by that property. Where a property does this, we store the property's Razorpay key ID and a Razorpay key secret; the key secret is encrypted at rest using AES-256-GCM. These credentials are used only to initiate and verify payments for that property's bookings, are accessible only to authorized members of the controlling organization and the infrastructure providers in Section 7, and are removed when the property disconnects its Razorpay account or the property/account is deleted.

8. Data Sharing & Disclosure Summary

To summarize Section 6 and Section 7: we share personal data with (i) members of your organization per their permissions, (ii) the sub-processors listed in Section 7, (iii) Google and Meta when you use connected advertising/login features, (iv) authorities when legally required, and (v) an acquirer in a business transfer. We do not sell your personal data.

9. Cross-Border Data Transfers

ClearHost is operated from India. Some of our service providers and infrastructure (including MongoDB Atlas, DigitalOcean, Cloudflare, Razorpay, Brevo, Cloudinary, Google, Meta, and OpenAI) may store or process data on servers located outside India. The DPDP Act permits the transfer of personal data outside India, except to any country or territory specifically restricted by the Central Government. We transfer and process personal data only in accordance with these requirements, and we require our service providers to maintain appropriate safeguards. You may request more information at support@clearhost.in.

10. Data Retention

We retain personal data for as long as needed to provide the Service, comply with our legal obligations, resolve disputes, and enforce our agreements:

  • Account and organization data — for the life of the account; deleted or anonymized after account closure, subject to legal retention requirements.
  • Guest and booking data — retained per the controlling customer's configuration and instructions, and our legal obligations; ClearHost deletes it on the customer's instruction or when no longer required.
  • Connected-integration tokens and credentials (Google Ads, Meta, property Razorpay) — retained while the connection is active; deleted on disconnect or request.
  • Payment records — retained as required for tax, accounting, and audit purposes.
  • Logs and audit records — retained for a limited period for security and operational purposes.

For data obtained from Meta, we delete Platform Data when it is no longer necessary for a legitimate business purpose, when we cease operations, or upon request, consistent with Meta's Platform Terms.

11. Your Rights Under the DPDP Act, 2023

Subject to applicable law and to verification of your identity, you (as a Data Principal) have the following rights in relation to your personal data. To exercise any of them, contact support@clearhost.in (see Section 17). If you are a hotel guest, we may need to refer your request to the accommodation provider (the Data Fiduciary) that controls your data.

  • Right to access information — to obtain a summary of the personal data we process about you and a summary of our processing activities.
  • Right to correction and erasure — to have inaccurate or incomplete personal data corrected, completed, or updated, and to have your personal data erased where it is no longer necessary for the purpose it was collected.
  • Right to grievance redressal — to a readily available means of registering a grievance with us (see Section 18, Grievance Officer).
  • Right to nominate — to nominate another individual to exercise your rights on your behalf in the event of your death or incapacity.
  • Right to withdraw consent — to withdraw your consent at any time, as easily as you gave it.

We do not sell your personal data to any third party.

12. Security

We take reasonable and appropriate technical and organizational measures to protect personal data, including:

  • Encryption of integration credentials at rest — Google Ads refresh tokens, Meta long-lived access tokens, and property-connected Razorpay key secrets are encrypted using AES-256-GCM and decrypted only in memory when needed.
  • Authentication controls — sessions are signed and managed by our authentication provider; email verification is required before login; passwords are hashed.
  • Access controls — role- and permission-based access within organizations, and audit logging of sensitive actions (including IP address and device information).
  • Encrypted transport — data is transmitted over HTTPS/TLS.
  • Restricted infrastructure — data is stored in a managed MongoDB Atlas database, with hosting on DigitalOcean and protection via Cloudflare.

Card data. ClearHost does not store raw card numbers for its own subscription billing; those payments are handled by Razorpay, and property-connected Razorpay payments are likewise processed by Razorpay. In the limited case where card "guarantee" details are received from an OTA channel-manager feed to honor a reservation, ClearHost is the recipient of data the OTA transmits; we minimize our handling of this data, restrict access to authorized users of the controlling organization, and are working to further reduce and protect it. Accommodation providers are responsible for handling such data in compliance with applicable payment-card (e.g., PCI-DSS) and privacy requirements, including not retaining it longer than necessary to honor the reservation.

No method of transmission or storage is completely secure. If we become aware of a personal-data breach, we will notify affected individuals and the Data Protection Board of India, and take other steps, as required by the DPDP Act, 2023 and the rules issued under it.

13. Children's Privacy

The Service is intended for businesses and their authorized staff and is not directed to individuals under 18, consistent with the DPDP Act, 2023, which treats anyone under 18 as a child. We do not knowingly create accounts for, or collect personal data directly from, children. Accommodation providers are responsible for any guest information they enter, including information about minors traveling with guests, and ClearHost relies on the accommodation provider's lawful ground (including verifiable consent of a parent or lawful guardian where required under the DPDP Act, 2023) for any minor guest data entered into the Service. We do not undertake tracking, behavioral monitoring, or targeted advertising directed at children. If you believe a child has provided us personal data, contact support@clearhost.in and we will take appropriate steps to delete it.

14. Cookies and Similar Technologies

We use the following:

  • Strictly necessary / authentication cookies — to keep you signed in and secure your session. In production these are scoped to the .clearhost.in domain to support our subdomains.
  • Local storage — for client-side application state and to capture advertising-attribution parameters from your visit.

We do not use third-party advertising or analytics cookies/SDKs within the application. You can control cookies through your browser settings; disabling necessary cookies may prevent you from signing in or using parts of the Service.

15. Automated Decision-Making

We do not use your personal data for solely automated decision-making that produces legal or similarly significant effects about you.

16. Third-Party Links

The Service may contain links to third-party websites and services (for example, a property's social media links, or Google's and Meta's platforms). We are not responsible for the privacy practices of those third parties. We encourage you to review their privacy policies, including the Google Privacy Policy and Meta's Privacy Policy.

17. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date above and, where changes are material, provide additional notice (for example, by email or in-product notice). If we intend to access a new type of Google user data or Meta Platform Data not covered here, we will update this Policy and obtain your renewed consent before doing so. Your continued use of the Service after an update takes effect constitutes acceptance of the revised Policy, to the extent permitted by law.

18. How to Contact Us & Exercise Your Rights

For any privacy question, to exercise your rights, or to request access, correction, or deletion of your data (including Google- or Meta-derived data), contact us:

  • Email: support@clearhost.in
  • Data Fiduciary: ClearHost
  • Registered address: 304, A1 Prospera, Baghmugaliya, Bhopal, Madhya Pradesh 462043, India

We will respond within the timeframes required by applicable law. We may need to verify your identity before acting on a request.

Grievance Officer (India — DPDP Act, 2023)

In accordance with Section 13 of the Digital Personal Data Protection Act, 2023, you may contact the office responsible for grievance redressal regarding the processing of your personal data:

  • Attention: Grievance Officer, ClearHost Privacy Office
  • Email: support@clearhost.in
  • Address: 304, A1 Prospera, Baghmugaliya, Bhopal, Madhya Pradesh 462043, India.

We will acknowledge and respond to grievances within the timeframes prescribed by applicable law. If your grievance is not resolved, you may have the right to approach the Data Protection Board of India.