The legal set
HCC Status Feed License
The free license any directory, map, guide or app uses to show HCC status: the same terms for everyone, status shown in HCC's exact words, every record linked, and nothing ranked by status.
Version 0.1 (draft), October 15, 2026. HCC publishes the version that applies on this page before it licenses the feed to any directory.
This license is between Halal Community Council, a South Carolina nonprofit in formation ("HCC"), and the operator of a directory, map, guide or app that shows food businesses (the "Licensee"). HCC offers it to any directory on these same published terms. Schedules A and B are part of the published terms. Schedule C is internal and is not published.
In plain words
- Any directory can show HCC status, for free, on these terms. The terms are the same for everyone.
- Show status exactly as HCC publishes it, and link to the HCC record every time.
- Keep it current: changes show within one hour, and if your copy goes stale for 24 hours, hide HCC status until it is fresh.
- If your directory shares ownership or control with HCC, say so in a visible line next to HCC status.
- Never rank or boost a place because of HCC status, unless the user chooses an HCC filter.
- Never sell food from places HCC checks, and never take commissions on it.
- HCC takes no share of your revenue, and you pay HCC nothing.
1. Who may license the feed
1.1 Any operator of a directory, map, guide or app that lists food businesses may apply, using the form in Schedule B. HCC accepts every applicant that agrees to these terms and can meet section 9 (no food sales or commissions).
1.2 The license is non-exclusive and non-transferable. HCC may license the feed to any number of directories, including competitors of the Licensee. The Licensee may not sublicense the feed, except to its own service providers who host or run its directory for it.
1.3 HCC may decline or end a license only for a reason in these terms, applied the same way to every Licensee.
2. What the Licensee may show
2.1 For each place in the feed, the Licensee may show these fields, and only these:
- the place's name and city, as on the HCC record;
- the HCC status, in the exact status string the HCC Standard publishes (Standard 10.1). For example: "HCC Verified: Pillar (Halal Community Council)", or "Not currently verified since date: renewal not completed (Halal Community Council)";
- the record number;
- the date checked and the good-through date;
- the record's one-line scope summary (what the check covers);
- the link to the HCC record; and
- the live seal image served by HCC for that record.
2.2 The Licensee does not show individual facts from a record, past statuses or a status history. The "since date" in a Not currently verified status is part of the status string, so the Licensee shows it with the status, exactly as published. The full record lives on HCC's site, where every fact keeps its basis and context.
2.3 The feed holds only public record data. It holds no evidence, no case files and nothing private.
3. Price: free
3.1 The license is free. HCC charges no fee for the feed.
3.2 If the cost of running the feed ever requires a fee, HCC will publish one cost-based fee, the same for every Licensee, at least 90 days before it applies. Any Licensee may then end this license without penalty.
3.3 HCC pays Licensees nothing, and receives nothing of value from them.
4. Show status exactly as published
4.1 The Licensee shows HCC status in HCC's exact words: the status string in the HCC Standard, section 10.1, with HCC's capitalization, and with the level name, date and reason exactly as published. Every status it shows includes the full name "Halal Community Council", as that string does. It does not shorten, reword, summarize, translate or add to it.
4.2 In particular, the Licensee never:
- shows "Not verified", "Failed", "Removed", "Revoked", "Suspended" or any other word in place of "Not currently verified" and its published reason;
- adds a rating, score, star, adjective or comment to HCC status;
- uses the word "certified", which HCC never allows with its name or its status, or puts HCC's name or status in Arabic characters;
- shows HCC status for a place that is not in the feed, or carries one location's status to another location, a chain or a parent company;
- implies that HCC checked anything beyond the published scope.
4.3 The Licensee may choose not to show HCC status at all for any place. If it shows HCC status for a place, it shows the current status, whatever it is, or nothing.
4.4 For the seal, the Licensee uses only the live seal image HCC serves for that record. It never stores, copies, redraws, recolors or crops a seal, and never caches the image longer than HCC's cache headers allow, so every copy changes when the status changes.
4.5 For French or Spanish pages, the Licensee uses only HCC's published translations, when HCC publishes them.
5. Link the record
Every display of HCC status links to that place's HCC record (the short link, for example halalcommunitycouncil.com/r/HCC-0001), as a visible link on the same screen. On a listing page, the link and the scope summary appear together with the status.
6. Keep it current
6.1 Change signals. HCC sends a signed change signal to the Licensee's HTTPS endpoint within about one minute of any status change, and retries until the Licensee confirms receipt (Schedule A). The Licensee verifies the signature before acting on it.
6.2 One hour. The Licensee shows every change within one hour of HCC sending the change signal. A Licensee that does not take change signals instead polls HCC's changes endpoint at least every 15 minutes, and shows every change within one hour of it appearing there.
6.3 Daily full sync. The Licensee runs a full sync at least once every 24 hours.
6.4 Fail closed. If the Licensee has not completed a successful sync in the past 24 hours, it hides all HCC status and seal images until a sync succeeds.
6.5 No archive. The Licensee does not keep or republish HCC status beyond what it needs to show current status. On a status change, the old status is replaced, not kept for display.
7. The common-ownership line
7.1 Who must show it. A Licensee under common ownership or control with HCC must show the common-ownership line. A Licensee is under common ownership or control with HCC if HCC's member, or any person or trust that owns or controls HCC's member, owns any interest in the Licensee or controls it, directly or indirectly.
7.2 The line. The Licensee shows this line, filling in only its own directory name:
HCC status is set by the Halal Community Council, which shares common ownership with directory name. Paying for a listing never affects HCC status.
The line names no person. The Licensee may not reword it except as HCC approves in writing for every Licensee.
7.3 Where it goes. The line sits next to HCC status, in visible text at least as large and as legible as the status itself:
- on every listing page that shows HCC status;
- on every list, search result and map screen that shows HCC status, placed beside or above the first HCC status on screen and visible whenever any HCC status is on screen; and
- in any email, newsletter or social post that shows HCC status.
It never sits only in a tooltip, a hover, a footer, a link, an "about" page or behind a click.
7.4 Never "independent". A Licensee under common ownership or control never describes HCC as independent of it, of its owners or of any company they control.
7.5 Telling HCC. Each Licensee states in Schedule B whether it is under common ownership or control with HCC, confirms it every year, and tells HCC within 10 days of any change.
8. No ranking boost, and no pay-for-status
8.1 The Licensee never ranks, orders, boosts, features, highlights or pins a place by default because of its HCC status or level.
8.2 A user may choose a filter or sort for HCC status. That filter or sort is off by default, is labeled with HCC's full name (for example, "HCC Verified (Halal Community Council)"), and is never renamed as the Licensee's own badge or program.
8.3 The Licensee never prices a listing, placement or ad by HCC status or level, never offers HCC status as part of an ad product, and never shows HCC status in an ad unit or sponsored placement in any way different from how it shows status on an ordinary listing.
8.4 The Licensee never says or implies that buying a listing, placement or ad affects HCC status, and never sells or bundles an HCC check, membership, service or seal with anything it sells. HCC's fairness rule applies: "HCC status is never sold with, bundled with or discounted for anything else a business buys, from anyone."
9. No food sales and no commissions
9.1 "Checked food" means food or food service offered by a business that holds a current HCC Verified status or an HCC event record.
9.2 The Licensee, and any business it controls, never:
- sells checked food;
- takes orders, catering bookings or reservations with food deposits for checked food; or
- takes a commission, per-order fee, delivery fee or share of revenue on checked food.
9.3 Listing fees, placement fees and advertising fees that do not depend on food sales are allowed, subject to section 8.
10. HCC takes nothing from the Licensee's revenue
HCC takes no share of placement, listing, advertising or any other revenue of any Licensee, and receives no payment, discount or service from any Licensee for the feed or for anything tied to it.
11. The Licensee's own labels
11.1 A Licensee may show its own labels and the claims businesses make to it. Those stay visibly separate from HCC status, in a different style, and are never placed so that a reader would think HCC confirmed them.
11.2 A Licensee's own labels never use HCC's name, "HCC", the level names, the seal's look, or the word "Verified" in a way that could be read as HCC status.
11.3 A label that a place is certified names the outside certifier, as that certifier's statement.
12. Marks, and no endorsement
12.1 The Licensee may use the names "Halal Community Council", "HCC", "HCC Verified", "Cornerstone", "Pillar" and "Keystone" only to show status from the feed, as these terms allow. It gets no other right in HCC's names, seal or marks.
12.2 HCC does not endorse any Licensee or its directory. The Licensee never says or implies that HCC endorses, recommends or partners with it, and never calls itself an official or approved HCC directory.
13. Data and security
13.1 The Licensee uses the API key HCC issues, keeps it secret, and tells HCC at once if it may be exposed.
13.2 The Licensee does not scrape HCC's website, does not try to reach any non-public HCC data, and does not combine HCC data with other data to infer anything HCC has not published.
13.3 HCC may set fair, published rate limits that apply to every Licensee.
14. Errors, concerns and business requests
14.1 If the Licensee believes HCC data is wrong, it tells HCC. It never corrects HCC data itself.
14.2 If a business asks the Licensee to change its HCC status, the Licensee refers it to HCC.
14.3 If a user raises a concern about a place's halal practice, the Licensee may point the user to HCC's private concern form.
15. Checks on compliance
15.1 HCC may check any Licensee's display, by automated checks and by looking, and may ask for screenshots.
15.2 After HCC's notice, the Licensee fixes:
- a wrong or stale status, or a missing or altered common-ownership line, within 24 hours; and
- anything else within 10 business days.
16. Suspension and ending
16.1 Suspension at once. HCC may suspend the Licensee's API key at once if the Licensee shows a wrong or stale status for more than 24 hours after notice, omits or alters the common-ownership line, breaks section 8 or 9, or misuses HCC's marks.
16.2 Ending for breach. HCC may end this license for any other breach not fixed within 10 business days after notice.
16.3 Ending on notice. Either side may end this license on 30 days' written notice.
16.4 After suspension or ending. The Licensee removes all HCC status, seal images and the common-ownership line within 24 hours, and deletes all cached feed data within 7 days. A suspended Licensee may resume after HCC confirms the problem is fixed.
17. Responsibility
17.1 HCC provides the feed with reasonable care and is responsible for its own records. HCC does not promise the feed will be uninterrupted.
17.2 The Licensee is responsible for how it displays HCC data. It will defend and hold HCC harmless from claims arising from its display, from stale or altered data on its pages, from its own labels, and from a missing common-ownership line.
17.3 HCC's total liability under this license is limited to $100.
18. Changes to these terms
HCC changes these terms only by publishing new terms at least 30 days before they apply, for every Licensee at once. A change the law requires may apply sooner. A Licensee that does not accept a change may end the license under section 16.3.
19. General
19.1 South Carolina law governs this license.
19.2 Notices to HCC go to Halal Community Council, PO Box 2, Darlington, SC 29540 or the feed contact address in Schedule A. Notices to the Licensee go to the contacts in its Schedule B.
19.3 The Licensee may not assign this license without HCC's written consent.
19.4 This license, with Schedules A and B, is the whole agreement about the feed.
Schedule A. Technical terms (published)
These are the planned endpoints for the HCC build. HCC will publish final paths and limits before the first license starts.
| What | How |
|---|---|
| Places list | GET /wp-json/hcc/v1/places?state=verified&updated_since=<date> |
| One place | GET /wp-json/hcc/v1/places/HCC-0001 (level, scope, dates, record link) |
| Live seal | GET /seal/HCC-0001.svg, purged on any change |
| Record short link | /r/HCC-0001 (also the QR target) |
| Change signal | A signed POST from HCC to the Licensee's HTTPS endpoint within about one minute of any change, retried until confirmed |
| Full sync | The places list for every status (verified and not currently verified), without updated_since, at least once every 24 hours |
Fields in the feed: record number, place name, city and state, status, level, reason (when not current), date checked, good-through date, scope summary, record URL, seal URL, last-changed time.
Timing the Licensee must meet: changes shown within one hour (section 6.2); polling at least every 15 minutes if not taking signals; full sync at least every 24 hours; hide all HCC status after 24 hours without a successful sync (section 6.4).
Schedule B. Licensee application and yearly confirmation (published)
- Licensee legal name: ______________________
- Directory, map, guide or app name(s) and web addresses: ______________________
- Business contact (role, email): ______________________
- Technical contact (role, email): ______________________
- HTTPS endpoint for change signals, or "polling": ______________________
- Is the Licensee under common ownership or control with HCC, as defined in section 7.1? Yes / No
- If yes, the directory name to use in the common-ownership line: ______________________
- The Licensee and every business it controls do not sell checked food, take orders or bookings for it, or take commissions or per-order fees on it (section 9). Confirmed: Yes
- The Licensee accepts these terms without changes. Confirmed: Yes
Signed by (role): ______________________ Date: __________
The Licensee repeats items 6 to 8 every year on the license anniversary.
Read with this license
- The HCC Standard, Version 1: section 10.1 sets the exact status strings a licensee must show, and section 10.3 the live seal.
- The Register: the records the feed carries, each with its own link.
- How we stay fair: why a directory under common ownership with HCC must say so, and the never-seal rule.
- Seal Use Rules: the words and forms a business may use, which a directory follows for the seal image.
- Terms of use: the terms for this website, including bulk collection of records.
To ask for the license, write to [email protected]. It is free, and the terms are the same for every directory.
Show HCC status, exactly as HCC publishes it.
Free, the same terms for everyone, and every status links back to the record it came from.