Church Media Kit Privacy Policy

1. Scope, operator, and accountability

This Privacy Policy explains how Hekima Solutions Inc. ("Hekima," "we," "us," or "our") collects, uses, discloses, and retains personal information in connection with the Church Media Kit service (the "Service") at https://churchmediakit.com. Hekima's mailing address is 7915 152A Ave NW, Edmonton, Alberta T5C 3A1, Canada.

Hekima has designated a Privacy Officer role accountable for this Policy. Privacy inquiries, requests, and complaints should be directed to privacy@churchmediakit.com.

This Policy covers personal information Hekima collects through the Service, whether from Customer and the people in Customer's Church or from a visitor who uses a public part of the Service without an account, such as requesting a Backgrounds Free Sample, taking the Church Media Check (Section 15) or requesting a Free Resource (Section 16). Where this Policy refers to "Customer," it also applies to such a visitor for the information the visitor gives Hekima and for the rights described in Section 12. It does not cover a customer organization's own website, ministry activities, or communications made outside the Service, and it does not cover third-party services Customer connects except as described in Section 7.

2. Information collected directly from you

• Account and organization information — name, email, phone, avatar, organization/church profile, and role.
• Preferences and settings — language, timezone, posting defaults, and notification preferences.
• Sermon source information — the YouTube video URL, channel lookup or search input, or recording Customer submits, recording metadata, and any ownership/rights attestation described in the Terms of Service.
• Uploaded media — logos, brand assets, sermon or service recordings, and other files Customer uploads.
• Generation inputs — prompts, instructions, and settings Customer provides for a generation request.
• Generated content — drafts, edited content, kit metadata, and design data Customer creates or edits in Studio, plus extracted audio, transcripts and word timings, detected Sermon Ranges, clip selections, captions, rendered clips, and Sermon Outputs produced from recordings.
• Support communications — messages Customer sends to support@churchmediakit.com or privacy@churchmediakit.com.
• Free Sample request — the email address a visitor enters on Backgrounds to receive a Free Sample download link. No account is needed, no marketing consent is requested or recorded, and the address is used only to send that one link (Section 14).
• Church Media Check report request — the email address a visitor enters to receive their full Church Media Check report by email, an optional church name, the separate optional tips-and-product-news consent choice, the PDF reports the visitor chose, and the visitor's check answers, which are saved with the request (Section 15). The answers of a visitor who does not request the emailed report stay on the visitor's device.
• Free Resource request — the email address a visitor enters to receive a Free Resource (a free printable PDF), an optional church name where the form offers one, the separate optional new-free-resources, tips and offers consent choice, which resource and which page or blog article the request came from, and the visitor's optional self-check answers, which are saved with the request (Section 16). The answers of a visitor who does not request the emailed code stay on the visitor's device.
• Connected-destination choices — if a Church Owner or Admin connects a YouTube channel, the channel chosen and, for each Short a person in Customer's Church publishes or schedules to it, the title, description, visibility and audience setting, and any scheduled time. If Hekima later makes another external-publishing destination available and Customer uses it, the social destinations Customer connects and selects.

3. Information collected automatically

• Strictly necessary session cookies issued by Supabase Auth to keep Customer signed in.
• Strictly necessary Free Sample cookie that lets a visitor download the Backgrounds Free Sample they requested (Section 13).
• Request and security metadata (such as IP address, device/browser information, and request logs) processed by Cloudflare and Supabase as part of operating and securing the Service.
• Free Sample request records — when a visitor requests a Backgrounds Free Sample, Cloudflare Turnstile checks the form submission, including the requesting IP address, for automated abuse. With the email address, Hekima stores a keyed hash of the requesting IP address (the IP address itself is not stored in this record), a hash of the download link (Hekima's database does not store the link itself), the request time, the time the link was first used, and the number of downloads counted against it. Hekima uses these records to limit repeated requests per network connection and per email address and to count downloads against the link's allowance.
• Church Media Check report request records — Cloudflare Turnstile checks the full-report form submission, including the requesting IP address, for automated abuse. With the request, Hekima stores a keyed hash of the requesting IP address (the IP address itself is not stored), the request time, the number of submissions from the same address that day, the advertisement angle of the page, bounded first-touch campaign tokens (an allow-listed UTM source, medium and campaign and a referrer category; never the full page address or referrer), and the send state of the follow-up email (Section 15).
• Free Resource request records — Cloudflare Turnstile checks the request form submission, including the requesting IP address, for automated abuse. With the request, Hekima stores a keyed hash of the requesting IP address (the IP address itself is not stored), the request time, the number of submissions from the same address that day, bounded first-touch campaign tokens (an allow-listed UTM source, medium and campaign and a referrer category; never the full page address or referrer), the code state, and the send state of the follow-up email (Section 16).
• Backgrounds download history — when a person in Customer's Church downloads a Backgrounds file or category pack, or is refused because of a fair-use or trial limit, Hekima records the Church, that person's account ID, the file kind and resolution or pack, the design or category, the outcome, and the time. People in the Church can see their Church's history. Free Sample downloads are not recorded here; they only increase the link's download count.
• Download history — when a person in Customer's Church downloads a Sermon Clip or a clip archive, a slide deck export, a Studio design export or a motion export, Hekima records the Church, that person's account ID, what was downloaded, its file format and the time. Hekima uses this history to run and support the Service, for example to answer a support request about a file. It is kept in Hekima's database only and is not sent to the analytics or advertising tools described in this Section; the product measurement described below may still count that a download happened, without saying what was downloaded.
• Staff access records — each time an authorised Hekima staff member opens a Customer file or a person's content in Hekima's internal console (Section 9), Hekima records which staff member opened it, what was opened, which Church, the account ID of the person whose content it was, and the time.
• Application events, errors, and logs generated by using the Service. Essential server and background Supabase failure telemetry is sent to PostHog even when optional browser tracking is declined. Sermon Video pipeline failures also use only closed stage and reason categories. This telemetry contains only fixed component, subsystem-area, request-method, runtime, HTTP-status, status-class, and applicable pipeline stage and reason categories under a static anonymous service identity, with geo-IP enrichment disabled; it excludes Customer Material, account identifiers, request or response bodies, error messages, URLs, paths, queries, headers, keys, and SQL. When an authenticated Customer declines optional browser measurement, a bounded browser application-error event may still identify that Customer in PostHog using the Customer's Supabase account ID, email address, and display name so Hekima can diagnose the failure. It excludes error content and is never sent to Google Tag Manager.
• Site analytics and advertising — Google Tag Manager loads across public and Studio pages by default unless you decline tracking or a supported browser privacy signal is present. Loading the container sends Google technical request information such as your IP address and browser information. Configured tags, including Meta Pixel, can collect page information and advertising identifiers to measure visits and advertising performance.
• Site and Studio product measurement and replay — when PostHog is configured and tracking is enabled, bounded page categories, named Studio features, workflow actions and outcomes, and an in-memory session pseudonym. For an authenticated Customer, PostHog also receives the Customer's stable Supabase account ID, email address, and display name so product events and replays can be associated with that Customer. Product events exclude Customer Material, church identifiers, raw URLs, query strings, referrers, error messages, filenames, and page text. Session replays may show rendered page and Studio design content to help diagnose failures; they mask every input value, block file and hidden inputs, strip URL queries and fragments from replay URLs and serialized URL attributes, and exclude console logs, network headers and bodies, and canvas capture.
• Payment status received from Stripe (see Section 4) and stored to reflect subscription state.
• External-publication attempts and provider identifiers — if Customer publishes to a connected YouTube channel, or if Hekima later makes another external-publishing destination available and Customer uses it, status, timestamps, and identifiers returned when content is sent to a connected destination.

The analytics and advertising described above runs by default before an undecided visitor chooses. You can select Essential only or turn it off in Cookie preferences. A saved decline stops optional browser analytics, advertising, product events, and replay; it does not stop the bounded authenticated browser application-error event described above. Global Privacy Control and Do Not Track stop browser measurement, including that event. Necessary storage remains active for essential service and authentication. Both runtimes cover public and Studio pages; PostHog requires its own configuration. This measurement does not authorize reuse of Customer Material for model training, evaluation, product-improvement datasets, or marketing content.

4. Information received from third parties

• Stripe — subscription and payment status (such as active, past-due, or canceled) and transaction records. Stripe collects payment card details directly; Hekima does not receive or store full card numbers.
• TranscriptAPI and YouTube — publicly available video metadata (title, description, thumbnail) and caption/transcript data for a URL Customer submits.
• Pexels — metadata about a photo Customer selects from stock-photo search (such as photographer credit and source URL).
• Google / YouTube (channel connection) — if a Church Owner or Admin connects a YouTube channel for publishing, the channel ID, channel name, and avatar URL of the channel Customer chooses, an OAuth refresh token for that channel (stored encrypted), and the ID and link of each Short published through the connection.
• Meta — if Hekima later makes an external-publishing feature available and Customer uses a Meta destination, account/destination identifiers, display names, avatar URLs, and publication status.

5. Purposes for processing

Hekima processes personal information to: create and administer Customer's account; deliver the Service, including recording processing and transcription, AI-assisted text and clip generation, Studio editing, playback while the source is retained, and export; process billing through Stripe; provide support; secure the Service and prevent fraud or abuse; comply with legal obligations; and send transactional communications necessary to operate the account. Authorised Hekima staff may view Customer Material, such as uploaded recordings, generated clips, posts, designs, slide decks and their exports, only to answer a support request, fix an error, check the quality of what the Service produced, or improve the Service (Section 9). For Backgrounds, Hekima also processes a visitor's email address to send the Free Sample link they request, Free Sample request records to limit repeated requests and count downloads, and Church download history to apply fair-use and trial limits, show the Church its own download history, and review abuse. For the Church Media Check, Hekima processes a visitor's email address and chosen PDF reports to send the confirmation code and the one report email they request, the optional church name stored with the request, request records to limit repeated requests, and the separate consent record to send tips and product news only where the visitor asked for them (Section 15). For a Free Resource, Hekima processes a visitor's email address to send the confirmation code and the one resource email they request, the resource, the page or article it was requested from and the optional self-check answers to understand which resources and articles help, request records to limit repeated requests, and the separate consent record to send tips and product news only where the visitor asked for them (Section 16). If Customer connects a YouTube channel, Hekima also processes the information needed to upload the Shorts Customer publishes or schedules to that channel. If Hekima later makes another external-publishing destination (such as Meta) available and Customer uses it, Hekima would also process the information needed for that feature. Hekima also sends onboarding and getting-started tips to account holders during the account relationship, which Customer can turn off in Notifications or from any such email (Section 14). Optional product news is a separate purpose that requires Customer's express consent.

6. AI and recording-processing data flows

For drafting, sermon detection, clip selection, or caption correction, Hekima sends OpenAI the relevant sermon context, transcript text or excerpts, prompts, and settings, using OpenAI's Responses API configured with store: false. This configuration is intended to limit OpenAI-side persistence of the request. It is not a claim of zero data retention or that OpenAI performs no abuse-monitoring review of the request; those are OpenAI's own policies and are not eliminated by this configuration. Hekima does not use Customer Material sent to OpenAI, or received back from OpenAI, to train Hekima's own models, and does not authorize OpenAI to use it for training without OpenAI's own applicable no-training default and Hekima's separate contractual controls. Hekima does not use Customer Material for model training, evaluation, or product-improvement datasets without Customer's separate, explicit, revocable consent (see the Terms of Service, Section 4).

Uploaded recordings are processed on Cloudflare infrastructure to extract audio and render clips. Extracted audio and bounded transcription context, such as the church or speaker name and Scripture-related vocabulary, are sent to Cloudflare Workers AI using its Cloudflare-hosted Deepgram Nova-3 speech-to-text model. The Service stores the resulting transcript and word timings for clip processing and requested Sermon Outputs. This transcription path uses Cloudflare's hosted model rather than a direct Deepgram API integration. Provider-side handling remains subject to Cloudflare's applicable terms and controls; private R2 storage does not mean that processing is confined to Canada or that provider retention is zero.

7. Subprocessors

Hekima uses the following subprocessors to operate the Service:

Hekima's policy is to give at least 30 days' notice of a change to this subprocessor list, subject to an urgent security replacement.

8. International processing

Hekima uses Cloudflare R2's Eastern North America location hint for application files. That hint is a best-effort placement preference, not a Canadian data-residency guarantee. Hekima and the subprocessors listed in Section 7 may process personal information outside Canada, including in the United States, as necessary to provide the Service. Cross-border processing may make information subject to access requests under the laws of the country where a provider operates. If Customer has a question about cross-border processing, contact privacy@churchmediakit.com.

9. Storage and security

By design, all files created or retained by the Service, including source uploads, account assets, generated media, and publication assets, are stored in private Cloudflare R2 buckets. Development and production use separate buckets. Direct browser uploads and provider reads use short-lived signed access; the signed URL is a temporary bearer credential and is not stored as the file record. Hekima stores an immutable object key and provider-neutral metadata in its database. Connected-destination OAuth credentials are stored encrypted. Hekima applies least-privilege access controls for staff and systems that can access Customer content. Only authorised Hekima staff may view Customer Material, and only to answer a support request, fix an error, check the quality of what the Service produced, or improve the Service. Staff open files and a person's content through an internal console that records each view: which staff member, what was opened, which Church, the account ID of the person whose content it was, and the time (Section 3). Viewing for these purposes does not permit use of Customer Material for model training, product-improvement datasets or marketing (Terms of Service, Section 4). No storage or transmission method is completely risk-free, and this Policy does not claim absolute security, a specific certification, or a specific compliance badge.

10. Retention matrix

Retention may be extended for material subject to a documented legal hold, security investigation, or statutory retention rule.

11. Deletion and provider boundaries

Customer may request deletion in-app (Settings) or by emailing privacy@churchmediakit.com; see Data Deletion for instructions. Hekima's deletion policy commitment, being implemented as a durable, retryable process, is to complete an active-account deletion request within 30 calendar days (subject to a documented legal hold, security investigation, or other lawful exception) and to expire backup copies within an additional 35 days, removing database records, private R2 source and working objects, derived assets, credentials. Hekima does not yet operate an automated provider-deletion workflow for account-linked measurement records already sent to PostHog; those provider-held copies remain subject to PostHog's applicable retention and deletion process.

YouTube. 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 Google; Customer can revoke that access at any time at https://myaccount.google.com/permissions. Deleting content, the Church, or the Church Media Kit account does not delete or unpublish Shorts already published; YouTube Shorts already published remain on YouTube, and Customer manages them in YouTube Studio. See Data Deletion for step-by-step instructions.

Potential future provider-held content. The current subscription does not include external publishing to Meta. If Hekima later makes that feature available and Customer uses it, deleting a Church Media Kit account would remove locally stored Meta connection credentials but would not itself revoke authorization in Meta or delete or unpublish posts already published to Meta. Customer would need to use Meta's own controls. See Data Deletion for step-by-step instructions.

12. Access, correction, withdrawal, and complaints

Customer may request access to, correction of, or deletion of its personal information, or withdraw a consent it has given, by emailing privacy@churchmediakit.com. Hekima's policy is to acknowledge a verifiable request within 5 business days and complete it within 30 calendar days, subject to a documented legal hold or other lawful exception. Withdrawing a consent may limit or end the corresponding functionality; it does not affect processing that already occurred lawfully before withdrawal. A visitor who requested a Backgrounds Free Sample, a Church Media Check report or a Free Resource without an account may make the same requests, at the same address, about the email address and request record Hekima holds for them.

If Customer is not satisfied with Hekima's response, Customer may escalate to the applicable privacy regulator, including the Office of the Information and Privacy Commissioner of Alberta (oipc.ab.ca) or the Office of the Privacy Commissioner of Canada (priv.gc.ca), depending on which law applies to the request.

13. Cookies

Church Media Kit uses strictly necessary session cookies and similar storage, including Supabase Auth session cookies, to keep Customer signed in and provide essential service functions. When a visitor opens a Backgrounds Free Sample link, the Service moves the link into a strictly necessary bg_sample cookie, limited to Backgrounds pages, not readable by page scripts, and expiring after 7 days, so the downloads the visitor asked for work without the link staying in the page address; it is not used for analytics or advertising and does not depend on the analytics and advertising choice. Optional analytics and advertising through Google Tag Manager and PostHog runs by default until you decline. The banner remains visible until you make a choice; a default setting is not recorded as your express acceptance. Saved declines and unavailable preference storage keep optional tracking off. Global Privacy Control and Do Not Track also stop the bounded authenticated browser application-error event.

The app stores your allow or decline preference in browser local storage and honors existing declines. PostHog stores its SDK preference marker and, for authenticated Customers, receives the Customer's stable Supabase account ID, email address, and display name. Cookies, identifiers, and collection by Google Tag Manager tags depend on the configured tags, including Meta Pixel. Google analytics storage, advertising storage, advertising user data, and advertising personalization are enabled while tracking is allowed and denied when it is declined. The app does not explicitly send Customer Material or account details into the tag data layer.

You can turn analytics and advertising off from the public footer or Studio Settings. Withdrawal reloads the current page to stop loaded tags and also applies in other open tabs. Withdrawal does not undo information already sent. Changes to measurement practices require updated disclosures and applicable privacy review.

14. Communications

Hekima sends three kinds of email. Transactional messages are necessary to operate the account, such as sign-up confirmation, password reset, billing, security and team notices; they cannot be turned off. The one email that sends a Backgrounds Free Sample download link to the address a visitor enters is also transactional; it is not marketing and does not add the address to any mailing list. The same is true of the one Church Media Check report email (Section 15) and the one Free Resource email (Section 16). Some service notices about Customer's own content, such as finished Sermon Kits and publishing failures, can be turned off in Notifications. Onboarding and getting-started tips help Customer use the Service during the account relationship; each one identifies Hekima, includes Hekima's mailing address and a one-click unsubscribe, and can also be turned off in Notifications. Product news and other marketing email is sent only with Customer's separate, express consent, recorded with its version, date and source, and every such message includes an unsubscribe. Hekima records unsubscribe requests and processes them within 10 business days, consistent with Canada's Anti-Spam Legislation (CASL).

15. Church Media Check

The Church Media Check at https://churchmediakit.com/church-media-check is free and needs no account. Your answers are processed on your own device to build the on-page result and the PDF reports, and, apart from the analytics described below, they stay on your device unless you ask for the emailed full report. So that a page refresh does not lose your place, a copy of your answers and the optional church and preparer names you type is kept in that browser tab's session storage, together with where you are in the full-report pop-up and whether you confirmed your code. While the code step is open, the same storage also keeps the email address you gave, the id of your report request and your product-news choice, so a refresh can still confirm the code or send a new one; those three are removed when the code step ends. All of it is cleared when the tab closes, and it is not a cookie. Session storage itself is not sent to Hekima; the email address, request id and choice reach Hekima only in the requests you make by sending the form or the code. The share button sends only the page address; the Share report button hands the PDF to your device's own share sheet.

If optional analytics is allowed (Section 13), the check sends PostHog bounded events with closed values only: your role, the top gap and workload level shown on the result, the step numbers you complete, which report you downloaded or shared, the advertisement angle of the page, and the bounded first-touch campaign tokens described in Section 3. This analytics never includes your answers, your church name, or any free text, and it is not sent to Google Tag Manager. When you confirm your address with the emailed code, and optional analytics and advertising is allowed, the check also sends one content-free lead event (no answers, email or church name) to Google Tag Manager, where configured advertising tags such as the Meta Pixel can count it (Section 3).

To receive your full report by email, you give an email address (required). You may also give a church name (optional) and tick a separate, unticked box to receive occasional tips and product news; that consent takes effect only when you confirm your address with the emailed code, and it is recorded with the wording version you agreed to and the time you confirmed. When you send that request, Hekima also receives and stores your check answers with it. They are closed multiple-choice answers: your role, church size band, services, campuses, which weekly media jobs you do, how the sermon is recorded and where it is posted, team shape, who approves posts, your hours, and your struggles, plus the top gap and workload level shown on your result. The church and preparer names you typed are not stored as answers. Church Media Kit operators view these answers in an internal console to understand the media problems churches face; Hekima contacts you about them only if you gave and confirmed the separate tips-and-product-news consent. Apart from that analytics, answers from people who do not request the emailed report are never sent to Hekima. Hekima stores the email address, the optional church name, the consent choice, the check answers, the request records described in Section 3, and the PDF reports you chose, which contain the result built from your answers and the names you typed. Hekima uses the PDFs only to attach them to the report email and does not read or analyse them; each one is held in a private Cloudflare R2 bucket and deleted once the email is sent or has finally failed, when the code expires without being confirmed, and in any case within 7 days (Section 10). Rate limits use a keyed hash of your network address, not the address itself.

Hekima first emails you a short six-digit code, valid for 30 minutes, to confirm the address is yours; your reports download on your device only after you type the code into the pop-up, and Hekima emails the reports only after you do the same. Once you confirm, Hekima sends you one service email with the reports attached and links to retake the check and to start free. It is transactional and does not add you to any mailing list. Tips and product news are sent only if you ticked the separate box and confirmed the address; every such message will identify Hekima, include Hekima's mailing address, and include an unsubscribe, and you can withdraw that consent at any time by emailing privacy@churchmediakit.com. The church name is stored with your request and is not used to contact your church. Your saved answers are kept with the request record and deleted with it, as described in Section 10.

16. Free Resources

Free Resources are free printable PDFs, such as checklists, templates and planners, offered at https://churchmediakit.com/free-resources and in blog articles. They need no account. Each has an optional self-check of multiple-choice questions, and your answers decide which gap lines the PDF prints and which Church Media Kit app the PDF and your email suggest you try next. Those answers stay on your device unless you send the email request described below. So that a page refresh does not lose your place, the form keeps your self-check answers (closed multiple-choice ids), and, while the code step is open, the email address you gave, the id of your request and your product-news choice, in that browser tab's session storage; it is cleared when the tab closes, is not a cookie, and is not sent to Hekima except in the requests you make by sending the form or the code.

If optional analytics is allowed (Section 13), the Free Resource pages and forms send PostHog bounded events with closed values only: which resource, which kind of page it was offered on, which step you reached (card seen, form opened, self-check answered, email submitted, code confirmed, PDF downloaded, start free clicked), and the bounded first-touch campaign tokens described in Section 3. This analytics never includes your email address, your church name, your answers or the article you came from, and it is not sent to Google Tag Manager. When you confirm your address with the emailed code, and optional analytics and advertising is allowed, the form also sends one content-free lead event (no answers, email or church name) to Google Tag Manager, where configured advertising tags such as the Meta Pixel can count it (Section 3).

To receive a Free Resource, you give an email address (required) and complete the Cloudflare Turnstile check. You may also give a church name where the form offers one, and tick a separate, unticked box to receive new free resources and occasional tips and offers from Church Media Kit; that consent takes effect only when you confirm your address with the emailed code, and it is recorded with the wording version you agreed to and the time you confirmed. Hekima stores the email address, the optional church name, the consent choice, the resource, whether it was requested from the hub, the resource page or a blog article (and which article), your optional self-check answers as closed multiple-choice ids, and the request records described in Section 3. Church Media Kit operators view these requests in an internal console to see which resources and articles help; Hekima contacts you about them only if you gave and confirmed that separate consent. Rate limits use a keyed hash of your network address, not the address itself.

Hekima first emails you a short six-digit code, valid for 30 minutes, to confirm the address is yours; the PDF downloads on your device only after you type the code into the pop-up, and Hekima emails the PDF only after you do the same. Once you confirm, Hekima sends you one service email with the PDF attached, a short personal note and a link back to the resource page. Only if you gave and confirmed the separate consent, or your request came from the United States, does that email also include a link to all free resources and a short suggestion, based on your answers, of which Church Media Kit app to try, with a link to start free, an unsubscribe link and Hekima's mailing address, and the PDF attached to that email then carries the same suggestion with a QR code. Without either, the email and its attached PDF carry no product promotion, no link to all free resources and no link to start free (the PDF that downloads on your device in the pop-up still includes the suggestion). To decide which email rules apply, Hekima stores the two-letter country derived from the network address of your request, and no other location data. The email is transactional and does not add you to any mailing list. After you confirm, the pop-up on the website shows the same kind of suggestion, whether or not you ticked the box. The PDF is made on demand from the resource and your answers, in your browser and again on our server for the email, and no PDF file is kept or stored. If you gave a church name, it is printed on the PDF and is not used to contact your church. New free resources, tips and offers are sent only if you ticked the separate box and confirmed the address; every such message will identify Hekima, include Hekima's mailing address, and include an unsubscribe, and you can withdraw that consent at any time by emailing privacy@churchmediakit.com or with the unsubscribe link in the message, which withdraws it for every request from your address. If your request came from the United States and you did not tick the box, the same unsubscribe link stops the suggestion in any later Free Resource email to your address. When you unsubscribe, Hekima keeps your email address and the time you unsubscribed, with no end date, so that we do not send you suggestions again; that record is removed only when you give and confirm a new consent. Your request record is deleted 12 months after the request, as described in Section 10; where you gave and confirmed that consent, only the address, the resource and the consent record are kept after that.

17. Eligibility

The Service is offered globally to organization/church accounts whose accepting owner is at least 18 years old and authorized to act for the organization, subject to applicable law and location-specific payment or feature availability. See the Terms of Service, Section 2. Church Media Kit is not directed to children, and Customer is responsible for ensuring any personal information about a minor that appears in Customer Material is included only as necessary and with appropriate authority.

18. Business transfers and legal disclosures

Hekima may disclose personal information where required by law, subpoena, or valid legal process; to protect the rights, property, or safety of Hekima, its customers, or others; or in connection with a corporate transaction such as a merger, acquisition, financing, or sale of assets, subject to appropriate safeguards and, where lawful, notice.

19. Customer and Hekima roles

For Customer Material Customer submits to the Service (such as uploaded recordings, sermon content, transcripts, clips, and generated drafts), Hekima acts as a service processor on Customer's instructions, under the licence terms in the Terms of Service. For account administration, billing, security and fraud prevention, Backgrounds Free Sample requests, Church Media Check report requests, Free Resource requests, fair-use limits, download history, staff access records, and legal compliance, Hekima determines its own purposes and means of processing. Where a customer-specific Data Processing Addendum or Security Addendum is required, it is addressed separately from this Policy.

20. Geographic scope

Church Media Kit permits account creation globally, subject to applicable law and location-specific payment or feature availability (Section 17). Rights described in this Policy may vary depending on which province, state, or country's law applies to Customer's account.

21. Policy changes

Hekima may update this Policy. Hekima maintains a version archive and will state the current version and Last Updated date at the top of this document. A material change to the purposes or risks of processing will be accompanied by notice and, where the change requires it, an opportunity for Customer to provide renewed consent before the change applies, consistent with the Terms of Service, Section 13.