Packet + receipt
The submissions page saves a browser packet and, when online, requests a server-side live receipt from BHFF. Exports remain available as a local fallback.
Black History Film Festival
Trust center for the current public launch.
Clear boundaries for submissions, sponsor interest, privacy, accessibility, public claims, and payment readiness while BHFF operates with local packet tools plus server-side live receipt storage.
Submission Terms
What filmmakers should know before using the current submission packet builder.
Rights and permissions
Filmmakers are responsible for rights, screening permissions, music permissions, publicity permissions, and accurate contact information before any official submission process opens.
No acceptance claim
A saved packet, export, or printed record is not an acceptance, selection, finalist status, award, screening guarantee, or contract with BHFF.
Final process pending
Official submission deadlines, fees, categories, eligibility rules, judge process, and paid submission terms must be published before final intake or paid entry goes live.
Privacy
How data behaves on this public launch.
What stays local
- Browser packetsSubmission, sponsor, press, judging, city, and packet tools keep local browser copies so visitors can edit, print, or export their own packet.
- ExportsJSON, CSV, and print packets are created on the visitor's device and are not automatically uploaded.
- ClearingClear buttons remove the relevant local browser records for that tool.
What BHFF may store
- Live receiptsOnline form saves can create server-side receipt records with the submitted fields, page context, receipt ID, and timestamp.
- Request hashesThe intake endpoint stores hashed IP and user-agent values for abuse review without publishing the raw values in public exports.
- Delivery switchesEmail notification and webhook forwarding are supported but only run when server-side config is set; operator export remains available for follow-up.
- Current noticeThis public no-charge intake launch stores review receipts, keeps exports local to the visitor, and does not process payments or final acceptance decisions.
Accessibility
Current accessibility commitments and known next steps.
Current standard
Pages use semantic headings, visible focus states, responsive layouts, text labels, and keyboard-accessible links and form controls.
Next audit
Before full public intake, BHFF should run a formal accessibility pass for color contrast, screen reader flow, keyboard order, error messaging, and mobile form usability.
Sponsor + Payment Terms
Current state for sponsor interest, package estimates, and money-spine displays.
No online charge
The current public site does not process payments, create invoices, charge cards, or issue tax receipts.
Package values
Sponsor values shown in local tools are planning estimates and do not create a sponsorship agreement, placement guarantee, or public sponsor claim.
Refunds and cancellation
Refund, cancellation, substitution, and force majeure terms must be finalized before any paid sponsorship or submission fee goes live.
Approval before placement
Logo placement, sponsor mentions, partner naming, recap materials, and public claims require approval and fulfillment tracking before publication.
Public Claims
Guardrails for dates, venues, judges, sponsors, winners, and partners.
- DatesDo not treat festival dates, deadlines, or city schedules as final until they are source-confirmed.
- VenuesVenue names, host partners, and city-specific programming require approval before public promotion.
- AwardsWinner, finalist, judge, and student showcase claims require verified award data and permission to publish.
- SponsorsSponsor names and logos require signed approval, deliverable tracking, and placement permission.