Give access without giving up control.
LayerAssist needs access to fix things for you. Here is exactly how that access is protected — in plain words.
What you share
The same kind of login you’d give a developer: a hosting account, a server or an FTP account. You choose which ones, one at a time.
How it’s stored
Passwords and keys are encrypted before they’re saved, each with its own key. A copy of our database alone can’t reveal them — not even to our team.
When it’s used
Only while a task needs it, and only by the part of LayerAssist that connects to your system. Passwords you send in the chat are hidden as soon as they arrive and kept encrypted; the AI works with the saved access, not the password itself.
What it can and can’t do
It works only on what you’ve connected. Deleting something needs your explicit approval of that exact item, and dangerous or open-ended commands are blocked, no matter who asks or how.
How you stop it
Switch off a website or server in your account and work on it stops. Every action it took stays on record.
Your account, protected too
Turn on two-step sign-in, so a stolen password alone isn’t enough to get into your account.
Details for your IT-savvy friend
- AES-256-GCM encryption with a separate key for every saved credential
- Keys derived with PBKDF2 and HKDF; the vault key is never stored in the database
- Credentials never reach the AI model, logs or audit records
- Server-side policy engine; forbidden operations can’t be unlocked
- Two-step sign-in with authenticator apps (TOTP)
- Durable audit trail for every action and result
From $9 a month · 14 days to change your mind
Next time something breaks, you’ll know who to ask.
Add your website and ask your first question today. Not for you? Cancel within 14 days to get your first payment back, minus only the AI work you used.
Free for 7 days · No credit card needed · No technical knowledge needed.