Security
What leaves your computer? Not your files.
Backups go to a place you own. You don’t need an account to make one.
Six promises about your data.
Your files stay yours
Nothing goes to Genie9. No account needed.
AES-256 per job
With a password only you hold.
Sealed credentials
Never written into a job file.
No open port
Only your Windows account, and the PC’s administrators, can reach the agent.
No telemetry
No usage statistics, no crash reports. Only what is listed below.
Support bundles
A zip you read before you send it.
What is sent, and when.
Backing up, restoring and Find never talk to Genie9.
- Backups, restores, Find
- Nothing to Genie9. A backup goes only to the destination you chose: a disk, a NAS, your own bucket, or your own server or cloud account.
- AI assistants
- Nothing to Genie9: GBM AI’s tools run on this PC, through no network port. What an assistant reads, names, sizes and dates, never what is inside a file, goes to that assistant, as anything you show it does.
- Ask Genie
- When you press Ask: your prompt, your drives, top-level folder names on internal drives, and your jobs with their settings and recent results. Passed to OpenAI to write the job. Never your user name (paths in your user folder go as {UserProfile}), PC name, file contents or passwords. The exact list
- Sign-in and licence
- Your e-mail, this device’s id, the app version, Windows and its processor type, and the app’s language and time difference from UTC, so Genie9’s e-mails come in your language, in your daytime. Activating a licence also sends its key and this PC’s name.
- Update checks
- App version, channel, platform, device id, edition, and when your updates end. Whether this PC runs Free, the trial or an edition, and, while it holds an offer from Genie9, whether its card or notification showed and which button you pressed.
- Alert e-mails from Genie9
- A purchased licence, signed in: this PC’s name, the job and its result, when it ran, the destination and set, the file and verification counts, and the first 50 skipped files with their reasons. The run log only if you tick “Attach the run log”. To your sign-in address only. From 10.0.56 that box starts unticked.
- Your own mail server
- The same e-mail, through your SMTP server. It never touches Genie9.
Encryption · Home
AES-256. A password nobody can recover.
Every file is encrypted and carries a SHA-256 checksum, checked at restore.
- A wrong password writes nothing
- A lost password is final, by design
- Restore needs only the files and the password, in any edition
- It covers file contents: names and dates stay readable, so Find and Restore can list them
Credentials
Saved once. Sealed on this PC.
Share passwords, S3 keys and server accounts are sealed with Windows data protection, never written into a job.
- Exports and support bundles carry no secret
- Switching on the service hands them over sealed for this PC
File servers · Pro
Your password never goes to an impostor.
GBM AI shows an SFTP server’s key first and signs in only once you trust it. A server with another key gets nothing.
- 1
The first test
Shows the server’s key. No password is sent.
- 2
You check it
With the server, and tick that you trust it.
- 3
Every backup
Checks the key before anything goes.
AI assistants · Every edition
Your AI can’t delete your backups.
Assistants see names, sizes and dates. Anything that changes your files waits for your OK in GBM AI’s window.
No assistant can
- Delete a backup, or keep fewer versions
- Change where backups go, or a job’s encryption
- See or enter a password
- Add commands to a job
- Change GBM AI’s settings, or approve its own request
Those tools do not exist, and the agent refuses them if one tries. Three switches in AI assistants decide the rest.
The ransomware guard · Pro
Ransomware stops at the backup.
Every save of a continuous job is checked first. When files change like ransomware, nothing is saved.
Put the files back as they were, from the card. It guards the backups, not the PC: keep your antivirus on. For a copy no PC can delete, lock it in your S3 bucket.
When it asks for administrator rights.
Say no, and nothing breaks: open files are skipped and listed in the report.
- 1
Installing
Setup, updates and uninstalling. Not to use it.
- 2
The Windows service
Once, to switch it on or off.
- 3
Open-file snapshots
At run time, unless the service is on.
- 4
A folder you can’t reach
Only if you choose to restart elevated.
- 5
The change journal
Once per drive, if you turn it on for continuous protection.
The details.
- Encryption
- AES-256 per job, with a per-file SHA-256 check at restore.
- Credentials
- Windows data protection (DPAPI) for your account; for the PC in service mode.
- Local connection
- A named pipe, never a network port. Only your Windows account, and the PC’s administrators, can reach the agent; with the service on, other accounts on the PC are told it is managed by another account.
- AI assistants
- Through gbm mcp on this PC. Reading changes nothing; running a job and a checkpoint only add backups; restores, rewinds and new jobs are requests only GBM AI’s window approves. Every run an assistant starts says so in Activity.
- Telemetry
- None. No usage statistics and no crash reports: a crash is written to a file on this PC only, and support details leave only when you press Send. The licence and update checks carry only what “What is sent” lists.
- Updates
- Signed by Genie9 Ltd. Installed only if checksum and signature match.
- Ransomware guard
- Continuous jobs, Pro and Server. Every save is checked before it is kept; a hold keeps the last good backup from thinning and retention.
- Locked backups
- S3 Object Lock, Pro: governance by default (an account allowed to bypass it can still remove a set), compliance per job (nobody can, until the date). GBM AI never sends the header that bypasses a lock.
Your disk. Your copy. Your password.
Check every one of these in the app.