SECURITY
How we keep your site safe.
Letting an AI change your software is a real decision. Here is exactly what it can and cannot touch.
- 01
A key for one site, for one hour
Your site's code connects to Rent a Vibe Team through a GitHub App that you install and limit to the repositories you choose. For each request we create a fresh access key that works for that one repository only and expires within an hour.
- 02
The AI helper works on a copy, never the live site
Each request is worked on in a separate copy of your site's code. The helper can only write inside that copy. It cannot push to your live branch or deploy anything itself.
- 03
Our credentials stay out of the AI's reach
The worker that runs requests holds the keys needed to publish. Those keys are removed from the helper's environment before it starts, so the AI never sees your hosting token or our GitHub App key. Your payment, domain and database logins are never shared with Rent a Vibe Team at all.
- 04
Publishing is a separate, recorded step
Every change is saved as its own Git commit on its own branch. Publishing is done by the worker, not the AI. By default you review a preview and approve it first; sites can choose to let their own admins publish directly. Either way, we wait for your hosting provider to build the new version, and if that build fails a person is alerted and your live site keeps the previous version.
- 05
Admins only, each one separately
The support button appears only for admins inside your own dashboard. Your site signs each hand-off with a secret that only it and we hold, and a signature is accepted only within five minutes. Each admin gets their own identity, so requests are always attributable.
- 06
Everything is on the record
Every request, reply and change is kept: what was asked, what changed, when it went live, and who handled it. You can see your full history in the app and in your monthly care report, and any change can be rolled back by restoring the previous version.
- 07
When something goes wrong, a person knows
If the helper can't finish, or a change fails to upload or build, the request goes to your team immediately — they're alerted by email and message — and you're told plainly that a person is picking it up. Short network hiccups are retried automatically first.
What we don't claim
We have not been through a formal third-party security audit such as SOC 2. If your business needs one, or you have questions this page doesn't answer, email info@thelazizagroup.com and we'll answer in writing.