This page describes practical security measures AffordaDev applies to the public website and to software development work. It does not claim certifications, audit results, or compliance standards that AffordaDev does not possess.
1. Security approach
Security is treated as part of building and operating useful software: protect access, validate input, limit unnecessary exposure, and keep systems maintainable.
2. Website security
For this marketing website, AffordaDev aims to:
- Serve pages over HTTPS
- Keep the production site static where possible to reduce attack surface
- Validate and sanitize contact form submissions before processing
- Avoid collecting more visitor information than needed for project inquiries
- Keep deployment credentials out of the public repository
3. Development practices for client systems
When building client software, AffordaDev typically designs around practical controls such as:
- Authentication and authorization appropriate to the system
- Input validation and output encoding
- Role-based access where user permissions differ
- Secure deployment practices for the agreed hosting environment
- Backups and recovery planning where hosting and scope include them
- Dependency updates as part of ongoing maintenance when engaged to do so
Exact controls depend on the project scope, hosting environment, and written agreement with the client.
4. Limitations
No system can be guaranteed completely secure. AffordaDev does not claim immunity from vulnerabilities, third-party service failures, or misuse of credentials by authorized users.
If you believe you have found a security issue related to this website, please report it privately by email rather than posting details publicly.
5. Contact
Security questions or vulnerability reports related to this website can be sent to [email protected].