Code of Ethics · Version 1.0 · November 2026

How we govern AI, automation and data before a project even starts.

TechMucho builds websites, custom software, data integrations and AI workflows for companies and professionals. Our technical decisions affect clients, teams and end users: this code puts in writing what we do, what we refuse and who takes responsibility.

Operational charter · Public commitmentsv1.0

Useful, verifiable technology with humans in control

Client data ownershipUsed strictly for the agreed task, never for unauthorized training
Human oversightNo critical AI output or automated decision without human review
Clear transparencyVerified facts, technical hypotheses and proposals always kept distinct

Guiding principles

Eight concrete rules for every digital and AI engagement

This code applies to management, collaborators and partners acting on behalf of TechMucho across client systems, data and workflows.

1. Competence before sales

We never propose work we cannot deliver or do not believe is useful. If a requested feature does not help the client, we say so openly — even if that reduces revenue.

2. Data belongs to who produces it

Client and end-user data remain client property. We work under least-privilege access, keep un-anonymized client data out of test environments and revoke access at handoff.

3. Transparency on AI usage

Every AI-assisted deliverable sent to a client undergoes human verification. We never delegate hiring, scoring, disciplinary or access-to-service decisions about people to AI.

4. No deceptive automation

We do not build dark patterns, hidden charges or bots designed to pretend to be human. Whenever an automated system responds, it clearly identifies itself.

5. Honesty on limits and outcomes

We do not promise results controlled by third-party platforms or authorities without stating the dependency. We separate verified facts, hypotheses and proposals.

6. Disclosure of conflicts of interest

Whenever we have a commercial interest, commission or partnership tied to a vendor or tool we recommend, we disclose it before the client decides.

7. Respect for the people we work with

Sustainable workloads, clear terms and zero unpaid work or implicit pressure: internal fairness prevents errors that would otherwise hit clients.

8. Mutual confidentiality

Client architectures, quotes, operational gaps and business records never become conversation material or public case studies without explicit approval.

Red lines and reporting

When we stop work and how we enforce this code

An ethics charter only matters in hard situations: when saying no protects the client and when an issue is raised.

Red lines · Written refusal

5 cases where we stop

Stopping work protects the relationship by proposing the right alternative.

We pause or decline delivery in writing whenever a request crosses these operational boundaries:

  • Collecting or processing personal data without a valid legal basis
  • Automating decisions affecting individual rights, employment, credit or essential access
  • Presenting AI-generated text or media as real customer testimonials
  • Confirming unrealistic delivery dates or technical outcomes as guaranteed
  • Using personal credentials or system access outside authorized scope

Privacy, GDPR & EU AI Act

Data protection and security

Every credential has an owner, a purpose and an expiry.

Our engineering practices align with GDPR principles and EU AI Act transparency and literacy standards (Regulation EU 2024/1689):

  • Passwords, API keys and tokens stored in encrypted vaults, never in chats or documents
  • Staging and testing workflows isolated from real customer records
  • Periodic access audits and immediate revocation at project closure
  • Cooperation with the client’s lawyer or DPO whenever formal legal review is needed

Reporting & Accountability

Reporting channel

Reviewed and answered within 10 working days.

Clients, team members and partners can report any practice that conflicts with this charter safely:

  • Direct confidential channel: info@techmucho.com (attention: Dr. Ing. Ilyass Mouchafi)
  • Formal review within 10 working days of receipt
  • Zero retaliation for good-faith reports, even if unconfirmed
  • Immediate suspension from client work if a violation is confirmed

How we work

How this code operates across all four project phases

01

Proposal stage

Every quote states clearly what is included, what is out of scope and what data or access the client must provide.

02

Build stage

Decisions touching personal data, automated actions or AI outputs undergo technical review and explicit human sign-off.

03

Operations & support

We log errors and exceptions traceably and keep operational documentation updated for client teams.

04

Project closure

At closeout we return or delete working data, hand over assets and revoke all temporary access rights.

Frequently asked questions

Clarity before we begin

Because software, automation and AI directly impact business operations and customer data. Putting clear boundaries in writing protects clients and keeps accountability explicit before edge cases happen.

Next step

Report or ask for clarification

A few details are enough to start understanding your goals, priorities and the most suitable solution.

We reply within 72 business hours to the address you provide. No newsletter, no spam.