Best for banking, healthcare, identity, insurance and payment workflows.
Generate a custom rto-lock.json policy
Create a ready-to-upload lock file in your browser, without hand-writing JSON. Use it to block Remote Tab Opener completely, or allow public pages while protecting sensitive areas.
🔒 Built locally in your browser. Nothing is sent to remote-tab-opener.com.
rto-lock.json
4. Upload it to your website
Why use RTO Lock?
A simple way to publish your automation policy
RTO Lock lets a website clearly say what is allowed and what is blocked. Sensitive services should usually deny everything. Public websites can allow safe pages while blocking login, account, payment or administration paths.
Good for documentation, help pages and public product content.
You get a ready-to-upload JSON file and an optional text summary.
RTO Lock
Visible policy, clear boundaries
The goal is not to hide anything. The goal is to make a website’s policy explicit, readable and easy to deploy.
- Use
/.well-known/rto-lock.jsonas the preferred location. - Use
/rto-lock.jsonas a simple fallback if needed. - Run the audit tool after upload to confirm the file is reachable.
Policy builder
Choose what your site allows
Core capabilities
Scope and path rules
Generated output
Download generated files
Review the live JSON below, then download the final files.
Live generated rto-lock.json
Show the text summary file
Upload checklist
What to upload
- Download rto-lock.json.
- Upload it to
/.well-known/rto-lock.json. - Use
/rto-lock.jsonas fallback if needed. - Serve it publicly over HTTPS.
Next step
Validate after upload
Once your file is on the server, use the audit tool to confirm that RTO can find and validate it.
Run RTO Lock auditInstallation notes
Your settings stay local
The generator does not send your settings to remote-tab-opener.com. The policy file is built in your browser, downloaded locally, and installed by you on your own website. The preview exists only to help you verify the generated content before upload.