COMMON
QUESTIONS.
Practical answers about starting a project, what the inquiry form does, and how CodeDev handles the information you submit.
What kinds of projects can I ask about?
Web applications, desktop tools, Android applications, Linux/system utilities, networking workflows, integrations, automation, and other software work that fits CodeDev’s current capabilities.
Do I need a complete specification before contacting you?
No. Explain the problem, who uses the system, the current workflow, important constraints, and what a useful first release must accomplish. Requirements can be refined after the initial review.
Does sending the form mean the project is accepted?
No. The form starts a conversation only. Scope, price, schedule, ownership, support, and acceptance terms should be agreed separately before work becomes a binding engagement.
Where does my inquiry go?
The inquiry is saved first in the private CodeDev database. If owner notifications are enabled, a copy is also sent through Resend to the configured owner mailbox. A notification failure does not delete the database record.
How long is an inquiry kept?
Open inquiries are retained while they are needed. After an inquiry is marked closed, the live record is retained for up to 730 days before it becomes eligible for permanent retention-policy deletion. See the Privacy Notice for details.
Can I ask CodeDev to correct or delete my information?
Yes. Submit a “Privacy Request” using the email address associated with the original inquiry when practical. Identity may need to be verified before information is disclosed or permanently deleted.
Is an account required to contact CodeDev?
No public account is required. The private account and MFA controls are for authorized CodeDev administrators.
Can I attach files to the project inquiry form?
Not currently. Avoid sending secrets, credentials, production database exports, or other sensitive material in the message. If a project needs files later, an appropriate transfer method can be agreed separately.
Will I receive source code?
That depends on the specific project agreement, third-party licenses, and the type of deliverable. Source-code ownership and repository access should be stated explicitly in the project scope.
How is the site protected?
The production design uses HTTPS, CSRF protection, rate limiting, private admin routes, role-based authorization, scrypt password hashing, TOTP MFA, step-up checks for sensitive actions, and security-focused response headers. Security is an ongoing process rather than a guarantee that incidents are impossible.
Start with the problem.
Use the inquiry form and choose General, Feedback, Project, Collaboration, or Privacy Request.
Contact CodeDev →