Nonprofit Website Builder That Makes the Work Clear

No. Describe the organization, audience, approved facts, programs, visual direction, and actions in plain language. Playcode AI builds the first version and helps revise it. A named person should still review mission claims, dates, privacy language, accessibility, provider setup, and every public path before publication.

Playcode can build a checkout or donation handoff when the chosen payment provider exposes the required API or hosted path and the organization supplies its approved account, server-side credentials, and requirements. The provider remains responsible for payment processing and its records; there is no native one-click donation service implied.

No automatic tax-receipting, tax-deductibility, charity-status, or compliance claim should be made. Receipt behavior depends on the organization, jurisdiction, provider, transaction, and reviewed policy. Confirm current legal and tax requirements with qualified advisers, then configure and test the provider’s exact receipt path before promising it publicly.

Yes, but start by defining the record, required fields, consent version, initial pending state, authorized reviewers, retention, deletion, and fallback. Validate on the server and save the request before sending notifications. Screening, background checks, safeguarding, acceptance, and scheduling remain separate processes unless their exact paths are built and reviewed.

Record the source, reporting period, definition, exclusions, approver, and next review date for each figure. Do not ask AI to fill gaps or turn a projection into a result. Explain enough context for a visitor to interpret the number, and remove it when the team can no longer verify it.

No website builder should substitute a blanket compliance claim for review. Build semantic headings, labels, keyboard paths, visible focus, contrast, descriptive alternatives, clear errors, and responsive layouts, then test with current automated and manual checks. Include people with relevant access needs in review when the organization can.

Avoid collecting sensitive or regulated information merely because it may be useful later. Ask only for fields needed for the current action, keep secrets and private details out of URLs and routine logs, define who can access the record, and obtain separate legal, security, privacy, and safeguarding review where the use case requires it.

Yes. Publish with HTTPS and connect a custom domain according to the current plan and DNS setup. Keep changing the same project by chat or supported visual editing, assign content owners, and test each change. The project uses real code that can be exported, while live data export remains a separate contract.