How Connect is operated, billed, secured and answered for.

If you believe your information has been handled wrongly, or you are unhappy with how a request was answered, raise it with the Grievance Officer.

Grievance Officer: the Owner of JBRH Digital Solutions.
Email: grievance@connectbyjbrh.com

Write from the email address associated with your Connect account where possible, and describe what happened, when, and what you would like done. We acknowledge grievances and respond on the timelines described in Data rights. If a grievance concerns Maya by JBRH or Agent TOBO by JBRH rather than Connect, say so and it will be routed to the right product.

This is a named role with a monitored address, not a generic contact form. It is the escalation path when the ordinary support route has not resolved something.

You can ask to access what Connect holds about you, correct anything inaccurate, delete your account and its contents, export your data, or object to or restrict a particular use.

How: email grievance@connectbyjbrh.com from your account address. Requests from an unrelated address are verified before anything is actioned, because acting on an unverified deletion request is itself a data breach.

Timeline: acknowledged within 7 days; substantively answered within 30 days. If a request is complex enough to need longer, we say so and give a date rather than going quiet.

Two roles. For your own account, sign-in and billing information, JBRH Digital Solutions decides how it is handled. For contacts, prospects and message content inside a customer's workspace, the customer organisation decides — JBRH processes it to provide Connect. If you are a prospect contacted through a Connect customer, we will route your request to that customer and tell you we have done so.

Deletion is real. Account deletion removes the workspace and its contents. Records we are required to keep — payment and billing history in particular — are retained as described in Retention, and are not used for anything else afterwards.

Different data exists for different reasons, so it is kept for different periods. One blanket figure would either destroy records the business must keep or hold personal content far longer than promised.

Removal runs in bounded batches, is scoped per workspace, records every run, and never touches a workspace on a paid plan by age alone. Nothing in the financial, account or security categories is deleted merely because time has passed.

Strictly necessary. Connect sets a session cookie when you sign in. It is what keeps you signed in; the application cannot work without it. It is marked secure and is not used for advertising.

Analytics. Where analytics is enabled it measures aggregate site usage. Your consent choice is recorded in your browser, and declining does not reduce what the product does.

Not used. Connect does not sell personal information, does not run advertising networks, and does not build cross-site advertising profiles.

You can clear cookies at any time in your browser; clearing the session cookie signs you out.

Connect sends email on your behalf from shared and dedicated sending infrastructure. What one customer does affects whether everyone else's mail is delivered, so these are enforced rather than aspirational.

You must not use Connect to send unsolicited bulk mail to purchased or scraped lists; contact anyone who has opted out or is on a suppression list; misrepresent who you are or who the mail is from; send unlawful, harassing, deceptive or infringing content; or attempt to bypass sending limits, verification, or another workspace's boundary.

You must have a lawful basis for contacting the people you upload, honour opt-outs promptly, and keep your account credentials secure.

What Connect enforces automatically. Daily sending limits per workspace; suppression checks before every send, which fail closed if suppression status cannot be determined; automatic slowing or stopping when bounce or complaint rates degrade; deterministic checks that hold a message rather than send it when it makes unverified claims about price, guarantees, service levels or meeting times.

Serious or repeated breach can result in sending being suspended or the account being closed. Where we suspend, we say why.

These are practices actually implemented in the running system. They are described plainly rather than as guarantees, because no operator can promise a system will never be breached.

• Transport. HTTPS is enforced; plain HTTP is redirected. Strict-Transport-Security, a content security policy, clickjacking protection and MIME-sniffing protection are set on responses.
• Sign-in. Google sign-in uses state, nonce and PKCE with a verified identity token. The Owner password is stored using Argon2id. Session tokens are stored only as SHA-256 digests, never in readable form.
• Stored credentials. Connected mailbox credentials are encrypted at rest with a key held separately from the database.
• Separation between customers. A signed-in customer reaches an explicit list of permitted endpoints; anything not on that list is refused. Endpoints do not accept a workspace identifier from the request body.
• Machine access. Server-to-server credentials are scoped to one workspace and an explicit set of permissions, stored only as digests, compared in constant time, revocable, and rate limited.
• Against manipulated input. Incoming mail is screened for instructions aimed at the automation before any model processes it, and such messages are routed to a person.
• Dependencies. Every dependency is pinned to an exact version with a cryptographic hash, and scanned for known vulnerabilities.
• Backups. Consistent database snapshots with a rehearsed restore, verified by comparing schema and row counts rather than assumed.

What we do not claim. Connect holds no ISO, SOC 2 or comparable certification, and this page does not assert compliance with any framework. If you need a certification for procurement, ask before purchasing rather than after.

To report a vulnerability, email grievance@connectbyjbrh.com with enough detail to reproduce it. Please do not test against other customers' data.

Free Forever — ₹0. The account does not expire. It includes five qualified prospects per calendar month and twenty successful emails per day, and adds a Powered by Connect by JBRH signature to outgoing mail. Your workspace and data are preserved for as long as the account exists.

Growth Pass. A prepaid pass in three capacities — 50, 100 or 250 qualified prospects — running for 30 days. It removes the Connect signature, raises the daily sending allowance, and includes priority support.

Prices are set by the server and shown to you before you pay. The amount displayed at checkout is the amount to pay; nothing is added afterwards.

There is no auto-renew and no saved card. Connect stores no card and no mandate. Nothing is ever charged automatically. Buying again is always a deliberate act.

Payment is by UPI. There is no payment gateway and no card handling, so Connect never receives or stores card details.

How a payment is recognised. Checkout generates a unique payment reference and shows an exact amount. You pay that exact amount, quoting that exact reference. A payment-notification email arriving at a dedicated mailbox is then matched against the expected reference, amount, currency and workspace.

What is not enough on its own. A transaction number alone does not activate anything. Neither does anything your browser reports — the browser is never trusted as evidence of payment. The notification must come from a sender on an explicit trusted list and pass sender-authentication checks. A forwarded, mismatched, unauthenticated or unexpected notice is held for human review rather than activated.

Exactly once. A verified payment activates a pass exactly once. Replaying the same reference does not create a second pass or extend anything.

If something does not match, it is held for review and a person looks at it. You are not activated on a guess, and you are not silently ignored. Payment queries go to grievance@connectbyjbrh.com.

Cancelling is doing nothing. There is no auto-renew, so there is nothing to cancel. If you do not buy again, the pass simply ends.

Renewing early does not waste the time you already paid for. If you buy another pass while one is still running, the new 30 days are added to your current expiry rather than replacing it. Renewing on day 20 of a 30-day pass leaves you with 40 days, not 30.

Renewing after expiry starts a fresh 30 days from the moment the new payment is verified.

At expiry the account returns to Free Forever. It is not suspended, locked or deleted. The workspace, contacts, conversations, knowledge, usage history and payment history all remain. Free quotas and the Connect signature return. You can carry on using Connect on the free plan indefinitely, or buy another pass whenever you choose.

A Growth Pass is a prepaid 30-day pass, activated as soon as payment is verified, and is generally not refundable once active — the capacity it unlocks becomes available immediately.

We will refund where the fault is ours: a duplicate payment; a payment verified but the pass not activated; an amount taken that does not match the amount quoted at checkout; or a pass that could not be used because of a failure on our side.

How to request one. Email grievance@connectbyjbrh.com with the payment reference and what happened. We acknowledge within 7 days and decide within 30. Approved refunds are returned to the originating UPI account.

If a refund is declined, you get the reason in writing and can escalate it through Grievance. Nothing here removes rights you have under applicable consumer law.

Free Forever includes support by email on a best-effort basis. Growth Pass includes priority support for the duration of the pass.

Contact grievance@connectbyjbrh.com and describe what you expected, what happened, and roughly when. Support covers Connect's own behaviour. It does not include writing your sales content, supplying prospect lists, or guaranteeing the commercial results of outreach.

Response targets are goals, not contractual service levels. Connect does not currently publish an uptime SLA, and this page does not imply one.

Product: Connect by JBRH — connectbyjbrh.com
Operator: JBRH Digital Solutions
Grievance, privacy, billing and support: grievance@connectbyjbrh.com

For Maya by JBRH, see mayabyjbrh.com. For Agent TOBO by JBRH, see agenttobo.com. Each product handles its own enquiries.

Connect by JBRH is built and operated by JBRH Digital Solutions. When you buy a Growth Pass you are contracting with JBRH Digital Solutions.

JBRH Digital Solutions operates three products:

These are products of one operator, not separate companies. Buying one does not include the others, and capabilities described for one product should not be assumed for another.

Indexing. Legal and trust pages are currently served with noindex while their wording is finalised. They remain publicly reachable by direct link and are canonicalised to connectbyjbrh.com. This is a deliberate publication decision, recorded here so it is not mistaken for an oversight.

When something here changes materially, the effective date at the top changes with it, and the change is announced to account holders before it takes effect where the change reduces what you get or increases what you pay.

An existing Growth Pass is not changed retrospectively: the terms and price you bought under apply for the pass you already hold.

Effective: 28 August 2026  ·  Last updated: 28 August 2026