Data Deletion — Church Media Kit

This page explains how to request deletion of your Church Media Kit account and data, what gets deleted and when, and what does not get deleted. If your Church connects a YouTube channel to publish Shorts, the YouTube section below explains that provider boundary. Other external publishing destinations are not yet available; if Hekima later makes one available and Customer uses it, the provider-boundary information below would also apply. It supplements the Privacy Policy and Terms of Service.

How to request deletion

• In-app: Go to Settings in Church Media Kit and use the account deletion option.
• By email: Send a request from your account's registered email to privacy@churchmediakit.com.

Hekima's policy is to acknowledge a verifiable deletion request within 5 business days.

Export before you delete

The Service does not currently provide a portable account-data export. Before deletion, download any supported Studio images and ready Sermon Clips you need, individually or through the available bulk clip-download flow. Keep your own original sermon recording; the Service is not a recording archive. Those downloads are not a complete account export and do not include retained uploads, source or prompt inputs, publication manifests, provider records, credentials, logs, or third-party copies of live posts.

What gets deleted, and when

Hekima's deletion policy commitment, being implemented as a durable, retryable process, is:

• An active-account deletion request is completed within 30 calendar days, subject to a documented legal hold, security investigation, or other lawful exception.
• Deletion removes database records, private Cloudflare R2 source and working objects (such as uploaded sermon recordings and account assets), extracted audio, transcripts and timings, clip metadata, rendered clips and their supporting files, Sermon Outputs, other derived assets, and stored connection credentials. Database-driven deletion jobs identify the R2 objects due for removal and retry failed object deletion.
• Backup copies are expected to expire within an additional 35 days after active deletion completes, absent a documented legal hold or statutory retention requirement.

Original sermon recordings and individual video deletion

Original Sermon Video files become eligible for deletion 14 days after upload completes. The retryable cleanup process defers removal while processing or rendering still needs the source. After removal, original-recording playback and source-dependent retries are unavailable; separately retained clips, transcripts, and Sermon Outputs are not removed merely because the original source expires.

A Team Member with the required Church capability may use the Sermon Upload Workspace's delete action to delete a Sermon Video and its associated transcript, outputs, clips, and registered source and supporting files. Database-driven jobs retry private-file cleanup. Removing a source or a Sermon Video does not remove copies someone has already downloaded or published outside the Service.

What survives deletion

Some records are retained even after your account is deleted, because Hekima is required to keep them or because deleting them would compromise a legitimate integrity, legal, or security purpose:

• Legal holds — material subject to a documented legal hold, subpoena, or investigation is preserved until the hold is lawfully lifted.
• Billing, tax, and legally required records — retained for 6 years, or longer if required by law.
• Security and authentication logs — retained for 90 days; breach and incident records — retained for 24 months.
• Support records — retained for 24 months.
• PostHog measurement records — account identity, product measurement, replay, and essential browser-error records already sent to PostHog are provider-held copies. Hekima does not yet operate an automated provider-deletion workflow for those copies. A verified request stops future account-linked browser measurement after the account is deleted; provider-held records remain subject to PostHog's applicable retention and deletion process.
• YouTube Shorts already published — Shorts published to a connected YouTube channel remain on YouTube; your Church Media Kit deletion request does not delete or unpublish them.
• Potential future provider-held posts — if Hekima later makes another external-publishing destination available and Customer uses it, content sent to a connected destination would not be deleted by your Church Media Kit deletion request.

See the Privacy Policy, Section 10, for the full retention matrix.

YouTube channel connection

This applies if your Church connected a YouTube channel. Disconnecting the channel in Studio Settings → Posting defaults, or Google rejecting the stored authorization at the next upload attempt, marks the connection revoked and Church Media Kit stops using it; the encrypted token and channel details are deleted when the Church or account is deleted. Once the connection is revoked, scheduled Shorts to that channel will not be published; they fail with a notice. Disconnecting in Church Media Kit does not itself revoke Church Media Kit's access in your Google account. Neither disconnecting nor deleting your Church Media Kit account or Church deletes or unpublishes Shorts already published; they remain on YouTube.

To remove a Short that Church Media Kit uploaded, open YouTube Studio, locate the video, and use YouTube's delete or visibility controls. To revoke Church Media Kit's access to your Google account, open https://myaccount.google.com/permissions and remove Church Media Kit.

If external publishing becomes available: Meta-specific instructions

If Hekima later makes external publishing available and Customer uses it, deleting a Church Media Kit account would remove locally stored Meta connection credentials. It would not itself revoke authorization in Meta or delete or unpublish posts already published to Meta.

The current subscription does not include a separate control to connect or disconnect an individual Meta destination.

To remove a post sent through a future external-publishing feature, use Meta's own controls:

1. Open the connected provider's app or page where the post was published.
2. Locate the post.
3. Use Meta's delete, unpublish, or archive option for that post.

Church Media Kit does not currently provide provider post IDs or URLs through a portable export. If the future feature is used, use the connected Meta account's own publication history to locate posts for removal.

Questions

Send a question about deletion, export, or retention to privacy@churchmediakit.com.