BCOMPLIANCE WEBAPP
Privacy policy
How we handle your information, and the choices you have when using BCompliance.
Effective 29 October 2026
Who we are
BCompliance WebApp (“BCompliance”, “we”, “our”) is operated by Stelcore Management Services Private Limited. It provides an operations workspace for compliance applications, client and company records, documents, invoices and business communications.
This policy describes information processed through BCompliance, including optional Google sign-in and Gmail connections. Where your organization supplies or manages your information, contact its administrator about its own data practices as well.
Information we handle
- Account information: your name, email address, profile information, account identifiers, role and authentication details.
- Workspace information: information you or your organization enter or upload, such as company and contact details, applications, agreements, documents, invoices and payment records.
- Communications: recipients, subjects, message contents, attachments and sending records for emails prepared or sent through BCompliance.
- Service and security information: login and activity records, session information, technical errors and device/network information used to operate and protect the service. If your organization uses workforce features, those features can also process attendance, work activity and location information associated with attendance.
We use this information to deliver the functions you use, maintain business records, manage access, troubleshoot problems and protect the service. Session cookies and browser storage support sign-in, security and interface preferences.
Google and Gmail data
Google sign-in: with your permission, we receive Google account identity information such as your name, email address, account identifier and profile picture, where provided. We use it to authenticate you and associate your Google identity with your BCompliance account.
Gmail connection: when you choose Connect with Google for Gmail, we request identity permissions and gmail.send. We use your email address and Google account identifier to identify the sender. We store an encrypted refresh token so authorized sending can continue without asking you to reconnect for every email.
We send the recipients, subject, message body and attachments you prepare or authorize in BCompliance to Google for delivery. We may retain the message and its sending status, Gmail message identifier and thread identifier as part of your workspace’s communication history. The Gmail connection does not request inbox-reading, mailbox-modification or email-deletion permissions.
Limited use: BCompliance’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used to provide the user-facing sign-in and email features described here. We do not sell it, use it for advertising, or use it to train generalized artificial intelligence or machine-learning models.
Human access to Google user data is limited to circumstances allowed by that policy, such as your explicit consent to support a specific issue, necessary security investigations or applicable legal requirements.
Storage and security
Information is stored in BCompliance’s application databases and file-storage systems, with access controlled by authentication and workspace permissions. Gmail refresh tokens are encrypted before storage. We use HTTPS for the production service. No method of storage or transmission can guarantee complete security.
Google handles your Google password during OAuth sign-in and connection; BCompliance does not receive that password through the OAuth flow. Any separately configured legacy app-password connection is distinct from Google OAuth.
Retention and deletion
We retain account and workspace information while needed to provide the service, maintain the organization’s business records, address security or disputes, or satisfy applicable obligations. Retention depends on the type of record and the purpose for keeping it; this policy does not promise a fixed automatic deletion period.
Disconnecting Gmail removes the stored sender credential from BCompliance’s active database and attempts to revoke Google access. If revocation fails, BCompliance asks you to remove access in your Google Account. Disconnecting does not delete existing communication history, uploaded files, business records or messages already delivered to recipients.
To request deletion of your account or associated data, email sumit@stelcore.com from your registered email address and describe the information involved. We will verify the request, coordinate with your organization where relevant, and explain any information that must be retained. Backup copies may persist until replaced or removed under the applicable backup lifecycle.
Your choices
You can decline Gmail access, disconnect the integration in Workspace settings → Gmail connection, or revoke access through Google Account connections. Revoking access stops future authorized use of that connection; it does not recall messages already sent.
You may contact us to request access to, correction of or deletion of your information, or to raise a privacy concern. Available rights depend on applicable law and your relationship with the organization managing the workspace.
Contact and updates
For privacy questions, data requests or connection support, contact Stelcore Management Services Private Limited at sumit@stelcore.com.
We will update this page when our practices change and identify the effective date. Material changes to Google data use will be disclosed before that new use begins, with additional consent where required.