Who we are and what this covers
This policy explains how Sheikh Bilal (“we”, “us”) handles information on shbilal.com and in the private CRM, BMS, CDM and FMS applications operated as part of this portal suite. These applications are for authorised personal and business use. Not every application includes every integration described below.
For privacy questions, data-access requests or deletion requests, email [email protected] and identify the application and account concerned. Do not email passwords or access tokens.
Information handled
The public website does not provide account registration, advertising or an analytics tracker. Hosting and security systems may process technical information such as IP address, request time, browser information and requested URL to deliver the site and protect it from abuse. If you email us, we receive your email address and message.
Private applications may store account and permission information, records you enter or import, documents, contacts, communication history, operational logs and connected-service authorisations. Which information is present depends on your enabled application, permissions and actions.
Google connections: access and use
Google access is requested through Google authorisation only when you choose a connected feature. The consent screen identifies the application and requested permissions. Authorising one portal does not automatically authorise every other portal.
- Google account identity: where requested, your account identity or email associates a connection with the account you selected.
- Google Drive: enabled workflows may list and read authorised files and folder metadata, import selected documents or communication archives, and create or upload files for configured archives, backups or exports. Where a sharing feature is enabled, a specific authorised action may manage file access. Actual access is limited by the granted permissions and configured workflow.
- Google Contacts: BMS supports importing contacts and linking them to local records. An explicitly authorised contact-editing feature may update contacts; read access alone does not permit this.
- Google Calendar: BMS supports reading authorised calendar events for import and organisation. This policy does not describe permission to create or edit calendar events.
CRM primarily uses Google Drive for configured intake, archive and file workflows. CDM does not need a Google connection for ordinary dashboard navigation. FMS connections, if introduced, must disclose their purpose and permissions before authorisation. Features not enabled for your account do not gain access merely because they are mentioned here.
Storage, security and retention
Private application records and imported files are held on the configured application host. Configured cloud workflows may additionally store selected files or backups in an authorised Google Drive destination. Authorisation credentials and tokens are held in protected application or host credential storage, not in this public website.
Records are retained for the configured workflow and until removed under the relevant retention settings or an authorised deletion request, subject to legitimate record-keeping obligations. Logs and backup copies can have separate retention periods; removing a live record does not immediately remove every historical backup. Please contact us for the retention and deletion arrangements applicable to a particular record.
Access controls and secure transport help protect information. No method of storage or transmission is completely secure. Do not assume all stored files or all backups are encrypted.
Sharing and Limited Use
Google user data is used to provide the authorised, user-facing features described above. It is not sold, used for advertising or used to train general-purpose artificial intelligence models. Access is restricted to authorised users and service providers needed to operate the selected workflow. Any transfer must be necessary for that feature, follow your instructions, or satisfy applicable legal or security requirements.
Human access to Google user data is limited to your consent for specific data, security investigations, legal requirements, or permitted internal operations on aggregated and anonymised data. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Cloudflare provides website delivery, routing and security. Google processes information under its own policies when you use its services. Data may be processed outside your country through these providers. Following an external business link takes you to that organisation’s separate website and policies.
Your choices and deletion
You can decline optional Google permissions, disconnect an integration in the application where available, or revoke access through Google Account connections. Revocation prevents future authorised API access but does not automatically delete records already imported or files already uploaded.
To request access, correction or deletion, contact us using the email above. We may need to verify your identity and authority over business records. We will explain any applicable retention obligations and remaining backup retention. This website is not directed to children.
Cookies and policy updates
This static public site does not set application login cookies or use advertising cookies. The hosting/security provider may use necessary security cookies. Private portals use their own essential session and preference storage. Changes to this policy will be published here with an updated effective date. Material changes to an integration’s data use require appropriate notice and, where required, renewed consent.