Built to improve your processes without making a mess of your data.
Automation means connecting tools. We keep access scoped, documented, and tied to the work we have agreed to do.
Trust starts with clear boundaries.
The aim is to solve a practical operational problem without creating confusion around access, ownership, or handover.
Client control
You remain in control of your business data, tools, and access decisions throughout the project.
Scoped access
DejaDo uses only the access needed to deliver the agreed automation and avoids broad access where a narrower option will do.
No plaintext passwords
OAuth is preferred where supported. Where it is not available, access should be handled through a secure vault rather than shared in plain text.
PII-safe logging
Build and support notes should avoid unnecessary personal data and focus on the operational issue being solved.
UK/EU-first where supported
UK/EU data hosting is prioritised where the chosen client tools and project requirements support it.
Clear handover and support
The handover explains what was built, what access is in use, and what support arrangement has been agreed.
You should not need to send passwords through a form.
Access is agreed as part of the project scope. The safest route depends on the tools involved and what the automation needs to do.
- OAuth is used where the client tool supports it.
- Secure vault access is used where OAuth is not available.
- Access should be least-privilege for the agreed project scope.
- Access can be revoked when it is no longer needed.
- Passwords, API keys, and sensitive customer data should not be sent through public forms.
Some projects involve trusted external platforms.
The tools involved depend on the client systems and selected automation. A fuller list can be supplied or published later when approved.
Automation platforms selected for the agreed project
Productivity tools already used by the client
CRM or accounting systems involved in the automation
Cloud infrastructure needed to host or support the build
Want to know how your tools would be handled?
Tell us what systems you already use. We'll explain what access would be needed before anything is built.