Skip to main content

Security & Compliance

The practices we follow to protect client code, data and intellectual property.

Last updated: 15 November 2026 (draft)

Draft for legal review. This document was drafted as a starting point and has not yet been reviewed by a qualified lawyer. Items marked [CONFIRM] must be verified before this page is relied on.

Our approach

Clients share source code, product plans and sometimes user data with us, so protecting that information is part of how we work. This page describes the practices we follow. It is a description of practices, not a certification or a guarantee. [CONFIRM: every statement on this page is accurate for current operations before publishing.]

Confidentiality and IP

  • We sign a mutual NDA before reviewing proprietary material on request.
  • Unless your agreement says otherwise, ownership of code and deliverables built for you transfers to you on payment.
  • Client material is accessed only by team members working on the engagement.

Secure development

  • Secure coding practices aligned with widely used guidance such as the OWASP Top 10.
  • Code review, dependency updates and automated testing as part of delivery.
  • Secrets (API keys, passwords) kept in environment configuration, not in source code.
  • Separate environments for development, staging and production where the project calls for it.

We do not currently claim ISO 27001, SOC 2 or similar certification. [CONFIRM: update if any certification is obtained.]

Access and infrastructure

  • Least-privilege access to repositories, cloud accounts and project tools, removed when an engagement ends.
  • Encryption in transit (HTTPS/TLS) for this Site and for client-facing systems we host.
  • Use of reputable cloud and hosting providers. [CONFIRM: providers and regions.]

AI features and your data

Our Site chat assistant sends conversation text to third-party model providers to produce replies (see the Privacy Policy). When we build AI features for clients, we agree with the client which providers and settings are used, and we can configure deployments so that client data is not used to train shared models. Whether that is possible depends on the provider chosen and is confirmed per project.

Data protection compliance

We design with the requirements of laws such as India’s DPDP Act 2023, the EU/UK GDPR, the CCPA/CPRA, Australia’s Privacy Act and the UAE PDPL in mind, and can sign a data processing agreement where a project requires one. [CONFIRM: DPA template available.]

Incidents and vulnerability reports

If we become aware of a security incident affecting client data, we will notify the affected client without undue delay and as required by the agreement and applicable law.

To report a vulnerability in this Site, email support@appfeeders.com with the subject “Security”. Please give us reasonable time to respond before disclosing publicly. [CONFIRM: preferred security contact, e.g. security@appfeeders.com.]