Prayer Basket Carried by the Prayer Council

A confidential house of prayer

Some burdens were never meant to be carried alone.

Send your prayer request here — your name, and the thing you are actually walking through. Named intercessors will carry it before God, daily. It will not be published, posted, broadcast, or shared on any media. And when God answers, you can come back and mark it answered, so the whole house can give thanks with you.

No account needed. No public profile. No follower count. Nothing to perform.

“Bear ye one another's burdens, and so fulfil the law of Christ.”

Galatians 6:2

“Confess your faults one to another, and pray one for another, that ye may be healed. The effectual fervent prayer of a righteous man availeth much.”

James 5:16
☉
Prayed over by nameReal, vetted intercessors — not an algorithm, not a bot, not a crowd.
🔒
Never on mediaNo pulpit, no podcast, no screenshot, no WhatsApp group, no social post. Ever.
☰
Sealed by covenantEvery intercessor signs a written confidentiality covenant before seeing a single request.
✓
You can mark it answeredReturn with your reference code and record how God answered — privately, or as a testimony if you choose.

Start where you are

What are you carrying today?

Choose what fits. It only sets the starting point of your request — you can say more, or less, in your own words.

How the Basket works

Five steps, and then we keep going.

You send it

Your name and your burden, in your own words. Anonymous if you prefer.

We seal it

Your request is encrypted and sealed. You receive a private reference code — only you hold the copy.

The Council is assigned

A small, fixed number of intercessors is assigned. Not a mailing list. Not a group chat.

It is prayed over

Daily, in the watch. Officers log the prayer privately — with no detail that could identify you if that is what you asked for.

You mark the answer

Come back with your code and record the answer — or tell us to keep standing. Nothing is published unless you say so.

The ground we stand on

Scriptures that built this house

Every design decision on this platform — the basket, the council, the secrecy, the record of answers — is anchored in a text. These are not decoration.

I. Why there is a council at all

II. Why it is secret, and stays secret

III. Why we keep a record of answers

The promise in plain English

“What I send here will not end up on a screen.”

Not on a projector. Not on a livestream. Not read aloud from a pulpit. Not forwarded. Not screenshotted. Not sold, traded, mined, or handed to any advertiser, ministry partner, or “prayer network”. This is the one thing we promise above everything else — because a person only tells the truth when they are safe.


This alignment demo makes no network calls. Everything you type on this page stays inside your own browser. There is no server, no analytics, no font CDN, no tracking pixel, no cookie. That is deliberate — it is a working demonstration of the “sealed” promise, not a marketing claim. The production build adds an encrypted vault and reader console behind the same design. Until then, please do not submit a real, sensitive request here — use it to align on the concept.

Send a prayer request

Tell us your name, and what you are going through.

Be as specific or as guarded as you need. Nothing here is read by a crowd. Before you begin, the three things that are true of every request in this basket:

Confidential by covenant. Read only by the named intercessors assigned to it.
Never published. Not on media, not in church, not to your family, not to anyone.
You stay in control. You can update it, or ask for it to be erased, at any time.

Your name helps us pray for a person, not a case. If you would rather not be named at all, switch on anonymous mode below and we will still pray.

Only used if you ask for a reply, or to return a gentle check-in. Leave it blank and we will simply pray, with no way to contact you.

What are you walking through?

Choose one or more. This only routes your request to the right watch.

Please don't include other people's confidential details (for example, a third party's medical record or an unproven allegation). Pray for them by first name only.

How urgent is this?
How would you like it prayed?
Who may see your details?

I have read and accept the Terms of Reference for this platform.
I accept the Confidentiality Covenant: that my request, my name and my details will never be published, broadcast, read aloud, forwarded, screenshotted or shared on any media or in any group.
I understand the one limit on confidentiality: if the team learns of imminent danger to life, abuse of a child or vulnerable person, or a serious crime in progress, they must refer it for help rather than stay silent. This is a limit we cannot remove — and would not want to.
I am 18 or over, or I am sending this with a parent or guardian's knowledge. (required for under-18s)

You will receive a private reference code immediately. Keep it — it is the only key to your request, and the only way to record an answer later.

If you are in danger right now, do not wait for this form. Contact emergency services or a trusted person immediately. Prayer Basket is not a crisis line, and it is not monitored minute by minute. In Zambia: Police 999/112; Lifeline Zambia 933. Elsewhere, use your local emergency number.

The Prayer Council

A small, sworn, constant watch.

The Prayer Council is not a crowd and it is not a following. It is a deliberately small, fixed, vetted body of intercessors who have each signed a written covenant before being given access to any request. They are the ones who keep the basket.

Shape

Small on purpose

A request is assigned to a fixed, minimal number of intercessors — never a distribution list. The fewer people who hold a secret, the more likely it stays one.

Watch

A rota, not a mood

The Council is divided into watches across the day and week, so that urgent requests are picked up within the hour and standing requests are carried every day without fail.

Accountability

Two-witness rule

No intercessor acts alone on a request that names a third party or an allegation. Any pastoral follow-up is done by two, and logged.

The instrument that binds us

The Intercessor's Covenant

Every person granted access to the basket signs this. It is the same instrument you will find in the Covenant & Privacy tab, in full. In summary:

  1. I will not disclose. I will not share, discuss, hint at, forward, screenshot, photograph, record, publish, broadcast, preach, teach from, or post any request, name or detail — in any medium, at any time, including after I leave the Council.
  2. I will not perform. I will never pray a request aloud where anyone outside the assigned watch can hear it, unless the sender has expressly asked for it.
  3. I will not profit. No request may be used for fundraising, testimonies, content, media, engagement, or any personal or organisational gain.
  4. I will not keep a private copy. No personal notes, no exported lists, no phone gallery screenshots, no saving to personal drives or cloud accounts.
  5. I will keep the log honest and thin. I will record only what is needed to show the request was carried — never more detail than necessary.
  6. I will not counsel beyond my office. I am not a doctor, lawyer, psychologist or financial adviser, and I will not pretend to be.
  7. I will refer, not conceal. Imminent danger to life, abuse of a child or vulnerable person, or a serious crime in progress will be escalated to the Safeguarding Lead — with the sender informed wherever it is safe to do so.
  8. I will submit to access control. I accept that every look at a request is logged, that my access can be withdrawn at any moment, and that misuse is a breach of this covenant.
  9. I will bear, not judge. I will not respond with shame, condemnation, or advice nobody asked for. I will pray.
  10. I will release it. When my term ends, or I step away, my access dies with it — and so does everything I saw.

Behind the promise

How a request is actually handled

  1. Received & sealedThe request is encrypted the moment it arrives. It is never stored in a plain-text list, a spreadsheet, or an inbox.
  2. Triaged by one personA single duty officer reads it, to set urgency and redaction — not a room, not a committee, not a group chat.
  3. Assigned to a closed watchThe minimum number of intercessors required. Each one signs the covenant before their first request.
  4. Carried in the watchPrayed over on the rota. The log records that it was carried — and deliberately little else.
  5. Answer recorded, if you say soYou mark it answered with your reference code. It becomes public only if you explicitly release it — otherwise it stays sealed forever.
  6. Erased on requestAsk and it is destroyed, with written confirmation. No “archive”, no backup copy kept out of reach.
Nobody gains from your private pain. There is no plan on this platform for the request to become content — no testimonies pipeline, no podcast clip, no “powerful story” segment. If your story is ever told, it is because you chose to tell it, in your own words, having seen exactly what would be said.
Reader console — demonstration

What an intercessor sees

This is a live illustration of the reader view, not real data. The passcode for this demo is 2468.

Serving

Apply to serve on the Council

We would rather have five people who keep their word than five hundred who do not. If you carry a call to intercession, tell us who you are — and expect to be asked questions.

Answered prayers

Did God answer? Come and say so.

A prayer that is never revisited is a prayer that quietly disappears. Here you can look up the request you sent, record what happened, keep standing, or ask for it to be erased.

Enter your reference code

Your code was shown when you sent your request, in the form PB-XXXX-XXXX. It is the only key. We cannot look it up for you — that is the point.

If you have lost your code, you will need to send a fresh request. We deliberately keep no searchable index that could be used to find your request — or to prove it exists.

Nothing you record here is published automatically. Marking a request “answered” is private bookkeeping between you and God. It appears on the Testimonies wall only if you separately, explicitly release it — and even then, you choose the words, and choose whether your name appears at all.
Sample content. The testimonies below are fictional illustrations of the format a released answer takes. On the live platform every card here would exist only because a sender explicitly chose to release it, in their own words, with their own name or anonymity choice. No request is ever published by us.

When the answer has not come yet

A basket that only records the easy answers is not honest. Some prayers are carried for years. That is not failure — it is the shape of a real walk with God, and it is honoured here.

“Keep standing” is a real answer

Use your reference code to set a request back to Still standing. Nothing changes for the worse: the Council keeps carrying it, and you are not asked to explain yourself.

You are not being graded

There is no “faith score”, no public tally of who got answered and who did not. Your record lives with you alone, behind your code.

“And he spake a parable unto them to this end, that men ought always to pray, and not to faint.”

Luke 18:1

Persistent prayer is commanded, not embarrassing. Waiting is part of the instruction.

Governance

Terms of Reference, Confidentiality Covenant & Privacy Notice

This is the document that makes the promise enforceable. It is written to be read by an ordinary person, not only by a lawyer.

A · Terms of Reference

What this platform is. Prayer Basket is a confidential, invitation-free facility for submitting personal prayer requests to a closed body of intercessors (“the Prayer Council”), for the purpose of intercessory prayer, and for the sender to record the outcome privately.

What this platform is not. It is not a crisis or emergency service, a medical or psychological service, a legal or financial advisory service, a counselling practice, or a substitute for your local church, your doctor, your lawyer, or the emergency services.

Purpose and scope

  1. To receive personal prayer requests, with or without identifying details.
  2. To assign each request to a minimal, closed, covenant-bound group of intercessors.
  3. To carry those requests in prayer according to the sender's stated preference.
  4. To allow the sender to record, privately, whether and how the request was answered.
  5. To do all of the above without ever publishing, broadcasting or otherwise disclosing a request against the sender's wishes.

Roles

  • The Steward — accountable for the platform, the covenant, and compliance.
  • The Safeguarding Lead — the named person to whom any risk to life or safety is escalated.
  • The Duty Officer — the single person who triages incoming requests.
  • Intercessors — members of the Prayer Council who have signed the Covenant.
  • The Sender — you. You retain ownership of your request and your story.

Conditions of use

  1. You must be 18 or over, or submit with a parent or guardian's knowledge and consent.
  2. Do not submit another person's confidential information without lawful authority. Pray for them by first name only.
  3. Do not submit material that is unlawful, or that makes an allegation against a named person, or that identifies a child.
  4. Do not use this platform to advertise, fundraise, recruit, or promote any cause.
  5. Requests that breach these conditions may be declined or removed. Where possible you will be told why.

B · Confidentiality Covenant

This is the operative “non-disclosure” instrument. It applies in two directions: to every intercessor who receives a request, and to the platform itself.

B1 · The promise made to the sender

  1. The platform and every member of the Prayer Council shall treat each request as confidential information belonging to the sender.
  2. A request shall not be published, posted, broadcast, livestreamed, projected, read aloud, preached from, taught from, screenshotted, photographed, recorded, forwarded, printed, filed publicly, shared in any group (including private messaging groups), or disclosed to any third party — including a spouse, family member, church officer, ministry partner, or “prayer network”.
  3. A request shall not be used for content, media, engagement, testimonies, fundraising, promotion, or any personal or organisational advantage, at any time.
  4. A request shall not be sold, licensed, traded, bartered, or disclosed to any advertiser, data broker, analytics provider, or artificial-intelligence training pipeline.
  5. The obligation in this clause survives the end of the sender's involvement, the end of an intercessor's term, and the closure of the platform. It has no expiry.

B2 · The intercessor's undertakings

  1. To sign this Covenant before being granted access to any request.
  2. To keep no private copy: no personal notebooks, no exported lists, no screenshots, no saving to personal devices, drives, or cloud accounts.
  3. To record only the minimum necessary in the prayer log, and never to enrich it with identifying detail the sender asked to withhold.
  4. To disclose a conflict of interest immediately — for example, if the request names someone known personally to the intercessor — and to recuse from it.
  5. To submit to access logging, and to accept that access may be withdrawn at any time without reason.
  6. To refer (not conceal) any matter falling within clause E (Limits & safeguarding).
  7. To keep the Covenant after stepping down, retiring, resigning, or being removed.

B3 · Reporting a breach

Any suspected breach of this Covenant must be reported to the Steward immediately. The Steward will (a) contain it, (b) determine which senders are affected, (c) inform those senders without delay, and (d) record the outcome. A confirmed deliberate breach is grounds for immediate removal and, where the law allows, referral.

C · Privacy Notice

Who holds your information. The Steward of Prayer Basket acts as the data controller for the requests submitted here. Contact details are published in the footer.

What is collected

  • The name you give, or your choice to remain anonymous.
  • Contact details — only if you choose to supply them.
  • The content of your request, and the categories and urgency you selected.
  • The visibility level you chose, and your consents.
  • A private reference code, and a minimal prayer log (that the request was carried — and no more than that).
  • Technical data strictly necessary to deliver and protect the service (for example, minimal security logging and anti-abuse signals). No advertising identifiers.

Sensitive information

Requests frequently contain what the law calls sensitive personal data — information about health, sexuality, religious belief, family circumstances, or allegations of wrongdoing. Prayer Basket treats every request as sensitive by default, without needing to classify it. It is processed on the basis of your explicit consent, which you give when you tick the consents on the submission form, and which you may withdraw at any time.

Why it is processed

  1. To pray for you, as you asked.
  2. To show you the status of your own request.
  3. To keep the service safe, and to meet legal duties where they apply.

Nothing else. Prayer requests are not used for marketing, not profiled, not scored, not used to train any model, and not shared with any commercial partner.

Alignment

This Notice is designed to align with the Zambian Data Protection Act No. 3 of 2021 and its principles of lawfulness, purpose limitation, data minimisation, storage limitation, integrity and confidentiality, and accountability. Where a sender is in the European Union or the United Kingdom, the platform is additionally intended to align with the GDPR and the UK GDPR. See clause G — this is an alignment statement for consideration by counsel, not a legal opinion or certification.

D · Security model

The promise of confidentiality is only as strong as the controls behind it. The production build is intended to operate as follows.

D1 · Designed-in controls

  • Encryption in transit — TLS on every connection; no plain HTTP endpoint.
  • Encryption at rest — each request sealed with its own key (envelope encryption, AES-256-GCM). A stolen database on its own yields ciphertext, not confessions.
  • Least privilege — only the intercessors assigned to a request can open it. There is no “read all” account that any single person holds by default.
  • Access logging — every opening of a request is recorded: who, when, and why. Logs are append-only and reviewed.
  • No third parties — no advertising pixels, no third-party analytics, no social plugins, no external font or script CDNs. The page you are reading now makes zero external network requests.
  • No indexing — the platform is marked noindex, nofollow and is never submitted to search engines. Requests are not addressable by a guessable URL.
  • Anti-abuse — rate limiting and a human-verification challenge on submission, without invasive fingerprinting.
  • Strong authentication — multi-factor authentication is mandatory for every intercessor account. No shared logins.
  • Deletion that means deletion — erasure removes the record and its key material, with written confirmation to you.

D2 · Honest limitations

No system is invulnerable, and this platform does not claim to be. Confidentiality can be defeated by a determined insider, by a compromised device, by legal compulsion, or by your own act of forwarding your reference code. We therefore promise procedural and technical rigour — covenant, access control, logging, and minimal retention — not mathematical impossibility. Where a risk remains that we cannot remove, it is stated openly in clause E.

E · Limits & safeguarding

Confidentiality has one hard limit, and it protects the vulnerable. It cannot be a hiding place for harm.

Confidentiality will be set aside — to the minimum extent necessary, and with the sender informed wherever it is safe to do so — where the team learns of:

  1. an imminent risk to life, including suicidal intent or serious self-harm;
  2. abuse, neglect, or exploitation of a child or a vulnerable adult;
  3. a serious crime in progress, or an ongoing threat of serious violence to an identifiable person;
  4. a clear and present risk to public safety; or
  5. a lawful and binding order of a court or competent authority.

If you are in danger now, contact the emergency services before you contact us. Zambia: Police 999 / 112; Lifeline Zambia 933. Elsewhere: your local emergency number.

Third-party allegations. Where a request names a person and alleges wrongdoing, the platform will not investigate, adjudicate, or circulate it. The sender will be directed to the proper civil or church authority. No allegation will ever be published here.

Minors. Requests from under-18s are accepted only with a parent or guardian's knowledge. Requests concerning a child protect the child's identity above all else, and the child's name is never recorded.

F · Your rights

  • To know — what is held about you, and why.
  • To correct — anything inaccurate. You may update your request at any time using your reference code.
  • To erase — to have your request destroyed, along with its key material, with written confirmation. There is no retained shadow copy.
  • To withdraw consent — at any time, without needing to give a reason, and without penalty. Withdrawal ends the prayer; it does not retroactively legalise anything done before it.
  • To complain — to the Steward first; and to the relevant data protection authority if unresolved.

Because the platform holds no searchable index of requests, and because a request may be anonymous, we may need your reference code to act on any of the above. This is a deliberate trade-off: what cannot be searched for cannot be leaked or compelled.

G · Status of this document

This document is written to state the platform's genuine intentions in plain, enforceable language. It is not legal advice and has not been reviewed by counsel. Before the platform receives real requests from the public, the following must be completed:

  1. Review and adaptation by a qualified lawyer in the operating jurisdiction, including the position under the Zambian Data Protection Act No. 3 of 2021 (and GDPR/UK GDPR if any senders are in those regions).
  2. Registration, where required, as a data controller with the relevant data protection authority.
  3. Adoption of a written child and vulnerable-adult safeguarding policy, with a named Safeguarding Lead and a documented escalation path.
  4. A written retention schedule, and a tested deletion procedure.
  5. A signed covenant on file for every intercessor, before access is granted.
  6. A named, insured legal entity to act as controller — the Steward cannot hold this personally.

Demonstration data appearing on this site is fictional. This build stores nothing on a server: everything you type remains in your own browser.