Deployna is a personal, non-commercial project run in the Netherlands by Abdulhalim Alhossini. It is not a company or separate legal entity.
Code security
Code and file security
Last updated: 28 July 2026
The intake flow is designed to keep your files separate from the running website and minimise access and retention.
When you submit
The brief is stored in the protected application database. An optional ZIP is limited to 15MB, checked for type and structure, and stored outside the public web directory with restricted permissions, without automatic extraction or execution.
ZIP deletion is scheduled after 7 days, with retries and an operational failure if deletion does not succeed. After 90 days, personal request fields and the associated email-delivery record are erased, including expired intake requests inside SQLite backups.
Private repositories and secrets
Never send a password, token or SSH key. If a private repository must be reviewed, we will explain a temporary, limited and revocable access method. Revoke access when it is no longer needed.
Security limits and your responsibility
No system is perfectly secure. Use a project copy with secrets and sensitive data removed, and keep an independent backup before applying any suggestion.
We do not run requester code on the shared server. Deeper execution or testing requires a separate environment and agreed boundaries.
Report a security issue
If you find a security issue in Deployna, email a concise report to hello@deployna.com. Do not publish details or access another person's data. We will acknowledge and assess the report as quickly as its severity requires.