JB CAST · LEGAL & TRUSTJB CAST Data Deletion, Disconnect & Revocation
JB CAST gives users control over connected provider access and provider-derived data stored by the application. This page explains how to disconnect a provider, revoke access, request deletion, and understand what is and is not deleted.
1. Disconnecting a Provider
In the production version, a connected provider is designed to be disconnectable through:
Settings → Workspace & Connections → [Provider] → Disconnect
In the production version, the Disconnect flow is designed to:
- stop JB CAST from using the provider connection;
- make the local credential unusable;
- remove the local credential material;
- attempt provider-side token revocation where supported;
- stop pending provider-bound work from automatically executing;
- begin removal or de-identification of covered provider-derived data held by JB CAST.
2. What Disconnect Does Not Delete
Disconnecting a provider from JB CAST does not automatically delete content already stored by that provider.
For example, Disconnect does not by itself delete:
- an existing YouTube video;
- a Facebook post or Reel;
- a TikTok post.
To remove provider-hosted content, use that provider’s own tools or an explicitly supported authorized deletion feature.
3. Provider-Derived Data
Depending on the provider and features used, provider-derived data may include:
- channel/Page/profile identity;
- provider account display information;
- provider publication IDs;
- provider publication URLs;
- provider publishing evidence;
- provider-native analytics;
- provider capability information;
- OAuth credential material.
When a qualifying deletion request or revocation occurs, JB CAST will delete or irreversibly de-identify covered provider-derived data according to applicable provider requirements.
4. YouTube / Google Revocation
In the production version, YouTube access is designed to be disconnectable through JB CAST where supported.
Users may also revoke JB CAST access through Google’s account security permissions.
The production flow is designed to support revocation and covered-data deletion within the deadlines required by the applicable YouTube API Services policy, including the 7-calendar-day requirement where applicable.
The production deletion workflow is designed to meet this deadline where applicable.
5. Facebook / Meta Deletion
Users may request deletion of Meta Platform Data associated with JB CAST.
JB CAST provides a publicly accessible deletion-request path and handles covered Meta Platform Data in accordance with applicable Meta data-use requirements.
6. TikTok Data Deletion
In the production version, TikTok access is designed to be disconnectable through JB CAST where supported, and users may also use applicable TikTok account controls.
TikTok-related data held by JB CAST will be removed or de-identified according to the applicable provider and JB CAST retention rules.
JB CAST maintains valid public Privacy and Terms URLs and transparent data practices for applicable TikTok App Review requirements.
7. Analytics Data
Provider-derived analytics associated with a deleted or revoked provider authorization are subject to the applicable provider deletion rules.
JB CAST’s production deletion workflow is designed so that covered analytics can be removed without deleting unrelated local workspace data.
8. Publishing Ledger Data
JB CAST may retain minimum local business history where lawful and necessary.
However, provider-derived identifiers or evidence that must be deleted under a provider requirement will be deleted or irreversibly de-identified.
JB CAST does not retain provider-derived data merely by relabeling it as an internal business record.
9. Original Source Media
Disconnecting a provider or deleting provider-derived data does not delete original source media stored on the user’s computer.
JB CAST will not delete source files merely because a provider connection is disconnected.
10. Local Backups and Exported Files
Copies that a user has manually created outside JB CAST-managed storage remain under the user’s control.
Examples include:
- copied database backups;
- exported diagnostic files;
- manually duplicated application folders.
JB CAST cannot remotely delete files that exist only on the user’s own device outside the managed application data location.
11. Request Data Deletion
Users may request deletion by contacting:
privacy@jalshabangla.com.bd
Suggested subject:
JB CAST Data Deletion Request
Please include only the minimum information necessary to identify the relevant JB CAST connection, such as:
- your name or organization;
- provider involved;
- JB CAST workspace/installation identifier if available;
- whether the request relates to a specific provider or all Jalsha Bangla-managed JB CAST data.
12. Do Not Send Sensitive Credentials
Never include:
- password;
- OTP;
- access token;
- refresh token;
- API secret;
- provider app secret.
Jalsha Bangla does not require these items to process a deletion request.
13. Verification
We may request limited non-secret information to confirm that a deletion request is authorized.
This protects users against unauthorized destructive requests.
We will not ask you to send your provider password or raw OAuth token as identity verification.
14. Deletion Time
Covered deletion requests will be processed without unnecessary delay.
Where YouTube policy applies to Authorized Data, deletion will be completed as soon as possible and no later than 7 calendar days after the applicable revocation or deletion request, as required by the applicable YouTube API Services policy.
Where another provider requires a shorter period, the shorter applicable requirement will control.
15. Legal Retention Exceptions
Certain minimum information may be retained where retention is required by applicable law or a binding legal obligation.
Any retained information must be limited to what is legally required.
Provider data that must be deleted under applicable provider rules will not be retained merely for convenience.
16. Completion
Where a deletion request is submitted through a Jalsha Bangla-managed support channel, we will provide a status or completion response where reasonably possible.
17. Contact
JB CAST / Jalsha Bangla
Operator: Jalsha Bangla Address: House 5/A, Road 1/C, Block B, Nobodoy Housing, Adabor, Dhaka 1207, Bangladesh Country: Bangladesh
Data deletion requests: privacy@jalshabangla.com.bd General support: contact@jalshabangla.com.bd
CONTACT
JB CAST / Jalsha Bangla
House 5/A, Road 1/C, Block B, Nobodoy Housing, Adabor, Dhaka 1207, Bangladesh