Human approval where it matters
Important work waits for a person to review it. A specific action runs automatically only when the business has clearly approved it. That choice is written down and tested before the work goes live.
Trust & safety
How access actually works.
Automation is only worth having if you can describe, out loud, what it is permitted to do. This page is that description. It is written to be checked, not to be reassuring.
The default operating boundary
Builder helps with work your business has approved. A person decides what happens next unless the business has clearly approved a specific action to run automatically.
Least access that works
Each connection gets the narrowest permission that does the job. If a business process only needs to read your inbox and create drafts, that is all it is authorized to do — not full account access because it was simpler to set up.
Each Engine belongs to one business
Each Builder + Engine client receives a separate Engine with its own account access, settings, and backups. One client does not share an Engine with another.
Tested before the work goes live
Agreed business processes are exercised with representative or sanitized inputs before production use. Expected results, approval points, and known failure paths are reviewed during stabilization.
Retries and duplicate actions are limited
Where an action can be retried, the business process uses defined retry limits and duplicate-action protection when the connected system supports it. Exceptions are routed to a person instead of repeating indefinitely.
Credentials are handled separately
Passwords and access codes are not collected through the public contact form or ordinary email. Account access is entered directly or shared through an approved secure method after the work is agreed.
OriginsLynk Engines monitor supported conditions
Automated health checks and failure alerts are configured for supported conditions. OriginsLynk investigates detected failures during the business-hours support periods defined in the service agreement.
Configuration backups are checked
The Engine configuration and process state described in your agreement are backed up and checked. These backups do not replace the backup responsibilities of every outside account connected to the system.
Revocation is yours, not ours
Access is granted from your own accounts, which means you can withdraw it from your own accounts, immediately, without asking us and without waiting for a business day.
I check whether your tools are a good fit
I learn what your business already uses and decide whether OriginsLynk can work with it. If the fit is poor or the risk is too high, I will say so before you buy.
The part most vendors leave out
What we do not claim.
OriginsLynk Engines store authorized connections
The Engine needs permission to use the business accounts involved in its approved work. That access is stored on the client's dedicated Engine and can be taken away.
If you are not comfortable with that — and it is reasonable not to be — OriginsLynk Builder does not include an always-on Engine.
We hold no compliance certifications
We are not SOC 2 certified, not HIPAA compliant, and not ISO 27001 audited. We are a small operation that follows sound practice, and we would rather say that plainly than imply a certification we do not have. If your work requires one, you need a vendor who has been audited for it.
AI gets things wrong
AI-generated content and decisions may be incomplete or incorrect. Clients remain responsible for reviewing outputs and approving consequential business actions unless a written authorization establishes a different review process. Training includes how to check important claims before acting on them.
Availability and compatibility have limits
OriginsLynk does not guarantee uninterrupted service, error-free output, or compatibility with every third-party platform. Results depend on the client's business process, source data, integrations, account access, and third-party services.
Sensitive and regulated work is excluded by default
Automated work involving regulated information or decisions with legal consequences is not included unless it is separately reviewed and designed. We would rather turn down that work than build it casually.
Questions about any of this?
Ask them before you buy something, not after. If something here does not fit how you need to work, that is worth finding out in the first conversation.