Skip to content
Kubali

Use cases

One engine for everyone who films, photographs or messages people. Churches come first. The rules stay the same for the rest: ask for each use separately, record the answer, and make it easy to say no.

Parishes, branches, media and children's teams

Churches and denominations

The service is livestreamed, the camera team films the congregation, and a sign at the door is the only notice. A sign is a notice. It is not consent, and nobody knows who said no.

How Kubali helps

  • Ask each member separately about the livestream, recordings, photos and the WhatsApp group, by SMS, a QR code at the door, or a paper form that you scan in.
  • Give the media team a list of people who said no, so the camera knows where not to point.
  • Send a yearly check, and let anyone reply STOP at any time. A withdrawal opens a task for the media team.
LivestreamRecordingsPhotos on social mediaWhatsApp groupChildren's ministry images

What the person receives

Organisers, venues and production teams

Events and conferences

Hundreds of people walk past a camera. Some agreed, some did not, and the only proof is a line in the ticket terms.

How Kubali helps

  • Put a QR code on the entrance, and others on seats or zones. People scan, confirm their number, and tap Yes or No on each item.
  • See the answers by seat or zone. The camera team gets a do-not-film list for any purpose.
  • Export an evidence pack with the exact wording each person saw.
Event photographyVideo and livestreamTestimonialsMarketing reuse

What the person receives

Programme teams and audio-visual crews

Speakers and panels

A talk is also the speaker's own work. Recording it, streaming it, publishing it and sharing the slides are different permissions, and a speaker may agree to some talks and not others.

How Kubali helps

  • Add each session and its speakers. Every speaker is asked about each item, for each talk, separately.
  • The AV team sees one status per session: Record, Stream only, or Do not record. Anything unanswered counts as no, and Kubali warns when a session is close with answers missing.
  • If a speaker withdraws, a takedown task is opened for anything already recorded or published.
RecordingLivestreamPublishing the recordingSlidesName and photoSpeaker agreement

What the person receives

Brand, communications and customer teams

Companies and marketing teams

A customer's photo or testimonial is reused months later, and nobody can show what they agreed to, or when.

How Kubali helps

  • Ask for each use on its own: the testimonial, the photo, the newsletter. A yes to one is never a yes to another.
  • Check before you publish or send. A single call says whether this person may be used for this purpose.
  • Keep a record that staff cannot edit, with the wording version each person saw.
TestimonialsPhotos and videoMarketing messagesCase studies

What the person receives

Head teachers, communications and clubs

Schools

Photos of pupils end up on the school page, and nobody is sure which parents agreed.

How Kubali helps

  • Mark a pupil as a child and add the guardian's number. Every request goes to the guardian, never to the child.
  • Guardians answer per purpose, and can change their mind by replying.
  • Withdrawals open a task so the photo comes down.
Photos on the school pageSports day videoTrip photosNewsletter features

What the person receives

Church management, event, CRM and messaging software

Developers and software vendors

Every product that stores contacts or sends messages ends up building its own, weaker consent screen.

How Kubali helps

  • Call one endpoint before you send a message or publish media: may I?
  • Embed a hosted consent form on any page with one line of code, or ask through the API.
  • Store consent captured elsewhere, with evidence, and get webhooks when someone changes their mind.
Consent checkEmbedsHosted pagesEvidence

What the person receives

GET /v1/consents/check?phone=+2547…&purpose=marketing_sms
→ {"allowed": false, "state": "refused"}

See it with your own wording.