Security
A pilot build means I work inside your accounts for a few weeks. That only works if you know exactly what I am asking for, how I hold it, and what happens to it when the work is done. This page is that list.
The short version: least access, in your name, held in a password manager, removed at handoff. Nothing of yours runs on infrastructure you cannot see.
What I ask for
- Only the accounts the one workflow touches. If the workflow reads your calendar and sends texts, I ask for the calendar and the texting tool, not your bank or your email password.
- A user invite in your account, or a scoped API key, wherever the tool offers one. I only ask for a shared login when a tool has no other option, and I say so on the scope page.
- The specific permissions needed, not admin. If a tool only offers admin, that goes on the scope page too, so you decide.
How I hold it
- Every credential lives in a password manager. None are pasted into documents, emails, chats or AI prompts.
- I do not store your data on my own systems beyond the working copies I need to build and test, and those are deleted at handoff.
- Two factor authentication stays on your accounts. I never ask you to turn it off.
What runs where
- The workflow runs in your accounts: your calendar, your CRM, your spreadsheet, your texting or invoicing tool.
- Any AI model it uses runs on an API account set up in your name, so you can see what is sent, what it costs, and shut it off in one click.
- Where the scope calls for a human review step, the workflow waits for one. Nothing goes out to a customer, a carrier, or a bank without the approval the scope page says it needs.
- Every action the workflow takes is logged inside the tools it runs on, so you can see what it did and when.
What I hand back
- At handoff I remove my user, revoke any key issued to me, and tell you it is done. If you want me to keep access for support, that is your call and it goes in writing.
- You get a one page record of every account the workflow touches, what it can do there, and how to turn it off.
- The workflow keeps running whether or not you ever call me again. There is no license and no kill switch on my side.
Texting and email compliance
If a workflow texts or emails your customers, it sends from your number or address, on your account, to people who gave you permission. Every texting workflow I build honors STOP and HELP replies. You stay the sender of record.
This website
Served over HTTPS with standard security headers, no analytics and no ad trackers. The details of what the site collects are in the privacy policy.
Questions
If your industry has rules I need to follow (HIPAA, insurance carrier requirements, PCI), tell me on the call and it goes on the scope page before any work starts. Email JahFeelAutomation@gmail.com or book a 30 minute call.