Your data. A clear next step.

How we handle your request

1. We review your email and clarify the account and requested scope when necessary.
2. If needed, we ask for a way to confirm control of the relevant account without requesting a password, code or token. We request only the information needed for that check.
3. We identify relevant connections, stored credentials, local and remote account metadata, content and project records. We distinguish information we control from posts or drafts held by a social platform.
4. After confirming the request, we use a reviewed, scoped manual procedure to handle the applicable local and remote stores and address connection removal. Stored-credential removal and platform authorization revocation are checked separately.
5. We reply with the actions completed, any limits or unresolved items, and the scope and reason for information retained. We explain any further step you need to take through the platform’s own controls.

This is a manual procedure. We do not guarantee a fixed response or completion time. If we cannot verify the relevant account or complete part of the request, we explain that limitation rather than report it as deleted.

What may be retained

Content-rights evidence, approvals and records of completed actions may still be needed to explain editorial work or request handling. We review personal links in those records and minimize unnecessary identifying information. We explain retained scope and reasons in our response.

Backups are not all erased immediately or automatically. If a backup is restored, we reapply previously completed deletions or minimization before the restored data returns to active use. See the retention table in our privacy policy.

Current connections and platform content

The earlier owner-authorized desktop YouTube connection used read-only access and local macOS Keychain storage. A separate web connection was verified with read-only and upload permissions and remote encrypted storage. Current token validity is not guaranteed by those earlier checks. Handling a request must distinguish Google authorization, any remaining Keychain credentials, the remote store’s current and earlier encrypted records, and related copies or backups. This update does not establish an enabled general deletion or provider-revocation service or a completed deletion outcome. Changing the active record alone does not erase earlier versions. We report each requested action separately and explain unresolved retention or deletion limits. The existing Meta web connection has real owner-authorized account grants and protected remote credential records. A deletion or access-removal request must identify the relevant local and server records and platform authorization separately. No completed deletion, secure erasure or provider revocation is claimed by this update.

Editorial content prepared or published through platform interfaces is separate. Removing an app’s authorization does not by itself delete local or remote project records or platform posts and drafts. Platform-hosted material may need to be managed through the platform’s own controls.

These are instructions, not a technical callback

This static page describes how to contact Storycraft K-Drop for manual handling. It does not accept a platform deletion callback, verify a signed request, run an automatic deletion job or issue an automated confirmation code or status URL.

The published instructions were adopted on 13 September 2026. This update reflects the factual corrections published on 29 September 2026. For other privacy questions, contact storycraft.hive@gmail.com.