Product support
Questions about Nibleaf Cloud, publishing, workspaces, imports, billing during beta, or self-hosted deployment.
Email product supportChoose the address that matches your request. Clear routing helps us keep product questions separate from privacy, security, and abuse reports.
Questions about Nibleaf Cloud, publishing, workspaces, imports, billing during beta, or self-hosted deployment.
Email product supportQuestions about personal data, retention, subprocessors, account access, or a deletion request.
Email the privacy teamPotential vulnerabilities, exposed credentials, authentication problems, or other security-sensitive reports.
Email the security teamPhishing, unlawful content, impersonation, malware, or another misuse of a site published through Nibleaf.
Email the abuse teamFor a product problem, include the affected public URL or workspace name, the action you attempted, what you expected, what happened, and the browser or device you used. A short sequence of reproducible steps is more useful than a screenshot alone.
Do not email passwords, session cookies, API keys, recovery codes, or full database exports. If a report involves sensitive account or security information, use the privacy or security address above and share only what is necessary to investigate it.
We welcome corrections to product claims, comparisons, technical guidance, and translations. Send the article URL, quote the sentence that needs attention, and link to a primary source when one is available. We review factual corrections separately from sales or partnership requests.
Messages can be written in English or Arabic. If a correction changes a published claim, we update the article and its modification date so readers can see that the page was reviewed again.
Send an article correctionThe codebase is AGPL-licensed with a public source repository and container release. Review the deployment guide before planning an installation, migration, backup policy, or DNS change.
View self-hosting guide