Client control
Client accounts should belong to the client wherever practical. WeekFound designs for portability, documented handover and an understandable manual fallback. Retention should come from useful service, not technical lock-in.
Access
Connections receive the least permission required to perform the agreed workflow. Administrator access is avoided where a narrower role is available. Access is reviewed when a project changes or ends.
Human approval
Sensitive communications, financial actions and decisions affecting people retain meaningful human approval. Automation handles preparation and routing before it is trusted with broader execution.
Testing and launch
Automations are tested with representative historical examples, expected exceptions and failure scenarios. Acceptance criteria are agreed before launch, and material changes return to testing.
Monitoring and recovery
Production workflows have a named owner, visible failure alerts and a documented manual fallback. Monitoring requirements and support response times are set out in the project or managed-service agreement.
Data and AI services
The data used, the purpose of processing, retention and third-party services are documented for each engagement. Confidential or personal data is not placed into an AI service simply because doing so is convenient.
Responsible limits
WeekFound does not begin with safety-critical, medical, credit, hiring, disciplinary, payment-authorisation or other high-impact automated decision-making. Specialist legal, security or compliance advice is brought in where the risk requires it.
Questions or incidents
Before public launch, this section will contain the monitored security contact address and incident-reporting process.