Privacy explained around the real Connect data journey.

This Privacy Center explains how Connect by JBRH handles information when people visit our website, contact Cira, create or administer an account, connect supported communication services, or when customer organizations use Connect to manage business relationships. Connect is operated by JBRH Digital Solutions (Private Limited).

For website visits, Cira enquiries, account administration, billing, product security and our own service communications, JBRH generally decides why and how the relevant information is handled. For customer-controlled contacts, prospects, mailbox content, Knowledge and business conversations processed to provide Connect, the customer organization generally determines the business purpose and JBRH processes the information to provide the service, subject to applicable law and the agreed service relationship.

When you use the Connect website, standard technical information may be processed, such as browser or device characteristics, requested pages, timestamps, coarse network information and security events. We use this information to operate, secure and understand the service.

Connect’s website analytics are configured to remain off until a visitor makes an affirmative analytics choice through the privacy-preference control. The current preference is stored in the browser so the site can respect that choice. You can revisit your preference from this Privacy Center.

Cira is Connect’s business solutions advisor. If you contact Cira, we process the details you submit—such as business contact information, company or use-case information and the substance of your enquiry—to respond, arrange a demonstration, discuss technical fit, trial interest or quotations, and protect the enquiry workflow. Optional marketing choice is separate from what is needed to respond.

Connect may process name, business email, account identifiers, role, workspace membership, session and security information needed to authenticate users and administer the service. Supported sign-in can include Google identity services.

When Google sign-in is used, Connect requests standard identity information such as OpenID, email and profile information needed to authenticate the user and associate the sign-in with the correct Connect account or workspace.

When an authorized user connects Gmail or Google Workspace features, Connect requests only the Google scopes required for the selected functions. Current source-supported functions include mailbox access using Gmail permissions and a separate read-only Gmail path for the payment-verification workflow. Disconnect and revocation logic exists for supported Gmail connections.

Connect’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide or improve user-facing features that are prominent in the Connect experience, for security, or as otherwise permitted by the Limited Use requirements.

Connect supports selected mailbox connections, including Google and other provider or custom mailbox methods. Authentication tokens, provider credentials or mailbox passwords are handled as sensitive credentials and are not intended for public display. Disconnecting a provider stops future authorized access; already synchronized workspace records can have a separate lifecycle.

If a customer connects a mailbox or communication channel, Connect may process message metadata, message content, threads, contacts, sender or recipient information, timestamps, labels or status and related operational data needed to display, route, search, synchronize, send or manage business communications according to customer instructions.

Connect supports prospect workflows that can include customer-uploaded information and business information gathered from public or otherwise permitted sources. Provenance and research or qualification information may be stored so a customer can understand how a record was sourced and used. Customers remain responsible for lawful outreach, suppression and honoring applicable objections or opt-outs.

Connect includes suppression and do-not-contact controls intended to help prevent further outreach after an applicable opt-out or internal suppression decision. A minimal suppression record may need to be retained longer than ordinary prospect information so that a deletion request does not accidentally cause future re-contact.

Knowledge can contain customer-uploaded files, URLs, raw text, extracted text and derived representations used to make customer-approved business knowledge available to Connect workflows. Depending on the feature, derived material may include chunks, summaries or embeddings.

Connect processes workspace Rules, behavior settings, authority levels, routing preferences and instructions so the service can operate according to customer configuration. These settings can influence when Connect acts automatically and when it stops for human review.

Needs You and related review workflows can contain task context, activity references and business conversation context needed for an authorized human to understand and resolve an escalation.

Connect records selected operational events to provide activity history, diagnose failures, protect accounts, investigate abuse and support reliability. Security and audit information may be retained where necessary to protect the service, establish what occurred, resolve disputes or meet legal obligations.

Connect can process plan, entitlement, usage, invoice, payment-status and payment-verification information. Payment providers may process payment-card or banking information under their own terms; Connect should not be treated as the issuer of those payment instruments.

Connect uses selected infrastructure, identity, communications, payment and processing technologies. The production-evidence table above is generated from the latest successful read-only production audit. A source-code adapter alone is not treated as proof that the provider is currently active. Provider legal-entity, DPA, regional-processing and contractual details may be maintained separately as those commercial records are verified.

Connect can classify, route, draft, extract, summarize, research or otherwise assist with business operations according to enabled features and customer instructions. Consequential workflows can be configured for human review. Connect is not intended to remove the customer’s responsibility for business decisions, lawful communications or appropriate oversight.

Connect does not publish invented one-size-fits-all deletion periods. Different categories can require different lifecycles based on customer instructions, account state, connected-provider behavior, security needs, billing or accounting obligations, suppression requirements, dispute handling and applicable law. We retain information only for as long as reasonably necessary for the relevant purpose or obligation, then delete, anonymize or otherwise restrict it where appropriate and technically practicable.

Disconnecting Google or another connected account is not necessarily the same operation as deleting records already synchronized into a Connect workspace. A customer or authorized user may request deletion of applicable workspace data separately, subject to identity verification, technical dependencies and lawful retention exceptions.

Privacy or account-closure requests can be submitted to JBRHDIGITALSOLUTIONS@Gmail.com. We may need to verify identity and authority before acting. Depending on the request, deletion can involve account or session records, provider tokens, synchronized communication content, contacts, prospect records, Knowledge content or other workspace information. Some records may be retained where necessary for security, fraud prevention, suppression, accounting, dispute resolution or another legal obligation.

Information deleted from active systems may remain temporarily in protected recovery copies until those copies are rotated, expire or are no longer required for resilience or legal reasons. Recovery copies are not intended to be used as ordinary active customer data after a valid deletion has been completed.

Subject to the law that applies to the request and our role for the relevant data, you may ask about Access, Correction, Deletion, withdrawal of consent, marketing preferences, connected-account revocation, or an objection relating to prospect or public-source information. Contact JBRHDIGITALSOLUTIONS@Gmail.com. If JBRH is processing the data only on behalf of a customer organization, we may direct the request to that organization or assist it in responding.

Connect uses authenticated access controls, tenant-aware data boundaries and protected handling for sensitive credentials, together with operational safeguards appropriate to the service. No internet service can guarantee absolute security. Customers should protect administrator accounts, endpoints and connected provider accounts and promptly report suspected compromise.

Technology providers can process information in different countries depending on the service, account configuration and provider infrastructure. Where cross-border processing applies, JBRH and customers should use the contractual and legal mechanisms required for that context. This Privacy Center does not claim a transfer mechanism that has not been verified for a specific provider relationship.

Connect is intended for business and professional use. Account holders should be at least 18 years old. Connect is not intentionally directed to children. Customer-controlled business communications may nevertheless contain information about minors in contexts chosen by the customer; the customer remains responsible for ensuring that use is lawful and appropriate.

Privacy rights differ by location and by the role JBRH has for the relevant information. We will evaluate requests under the law that applies rather than claiming that every regional privacy regime applies to every Connect user. Mandatory rights are not removed by this Privacy Center.

We may update this Privacy Center when Connect features, providers, law or business practices change. The effective date will be updated when a materially revised notice is published. Where required, additional notice or consent will be provided.

JBRH Digital Solutions
Private Limited
Address: 1-57-1, Road Number 10, Banjara Hills, Hyderabad – 500034, Telangana, India
Telangana State, India

Privacy: JBRHDIGITALSOLUTIONS@Gmail.com
Support: Support@ConnectByJBRH.com
Terms: Terms of Service

Effective date: 27 August 2026.
Jurisdiction used in the public Terms: Hyderabad, India.