Consent Before Testing
No target website is ever scanned or probed by surprise. Every engagement starts with Step 1 outreach and waits for explicit written approval.
Automated bots and AI scanners probe websites nonstop for forgotten developer mistakes and outdated components. Mirown.com protects business owners strictly by prior written permission, governed by international cybersecurity standards and clear legal boundaries.
contact@mirown.com
Many business owners hire outside developers or agencies and never realize a small coding error or outdated dependency was left behind. Mirown.com eliminates the fear of silent automated exploitation by offering structured, transparent, permission-only vulnerability audits.
No target website is ever scanned or probed by surprise. Every engagement starts with Step 1 outreach and waits for explicit written approval.
Before any audit runs, a written Permission Agreement defines exact URLs in scope, excluded paths, safe testing limits, and legal hold-harmless terms.
Once vulnerabilities are documented and submitted privately to the website owner, Mirown's responsibilities finish cleanly—no lingering access or ongoing fees.
Every Mirown.com engagement follows four documented phases so website owners maintain complete control and legal clarity from first message to final handoff.
Mirown contacts the website owner (or receives an inquiry via this website) to request permission before any security check occurs.
Both parties execute a written agreement (.docx / .pdf) defining authorized domains, exclusions, safe limits, and confidentiality terms.
Within signed boundaries, we perform a non-destructive external check—with AI handling most technical analysis—without touching source code.
We send the vulnerability report privately to the owner's authorized email. Once delivered, Mirown's responsibilities finish cleanly.
Professional security work requires crystal-clear legal boundaries protecting both the website owner and the ethical researcher.
Mirown.com sends vulnerability reports strictly and privately to the Website Owner's designated email address. Once delivered, the Website Owner holds sole responsibility for safeguarding the report internally. Mirown.com is not liable if a delivered report or vulnerability detail is forwarded, misconfigured, or leaked by the client's own employees, external developers, contractors, or internal systems.
Testing conducted in good faith within a signed Permission Agreement is authorized by the Website Owner, protecting the researcher from civil or criminal claims for agreed non-destructive checks.
Audits assess publicly reachable security posture at a specific time. Mirown.com provides reports "as-is" without warranty against future zero-days or third-party breaches, and excludes consequential damages.
Clients confirm legal authority over every submitted domain and agree to hold Mirown.com harmless against third-party claims resulting from unauthorized domain submissions or client-side leaks.
At Mirown.com, we openly disclose that AI powers most of our technical discovery and triage, while humans retain strict control over permission, safety rules, and private delivery.
Submit your domain to request a written Permission Agreement, or send your reply regarding an outreach email or delivered report from contact@mirown.com.
Your request/response packet has been prepared with a unique reference ID.
Because Mirown.com handles security reports and written permissions—and because most technical audit work is handled by AI—our data handling commitments are strict and transparent.
Most technical reconnaissance correlation, pattern analysis, triage, and draft report formatting is performed by AI systems under human oversight. Client findings are never sold or used to train public AI models.
We collect only information you voluntarily provide (name, email, domain scope) and non-destructive technical observations after a Step 2 Permission Agreement is signed.
After Step 4 report delivery, Mirown deletes temporary audit artifacts. The Website Owner is solely responsible for protecting delivered reports internally against leaks by their own team or vendors.
| Workflow Step | Information Used | AI Involvement | Retention & Legal Boundary |
|---|---|---|---|
| Step 1: Ask Permission | Public business contact email & domain name | Minimal / Human-initiated outreach | Opt-out / decline honored permanently |
| Step 2: Permission Agreement | Owner name, email, authorized URLs, signed scope | Human-reviewed written authorization | Retained solely as proof of authorization & safe harbor |
| Step 3: Safe Audit | Authorized public endpoints & HTTP responses | Primary: Most technical analysis & triage | Zero mass user-data scraping; zero destructive tests |
| Step 4: Submit Report & Finish | Vulnerability report sent privately to web owner | AI-assisted report drafting, human verified | Duties finish; artifacts purged; client secures internal copy |
No. Step 1 (asking permission) and Step 2 (confirming a signed written permission agreement) always occur before Step 3 (auditing). Zero active testing is performed without authorization.
Most of the technical vulnerability discovery, pattern checking, triage, and draft report structuring is handled by AI under strict non-destructive rules and human oversight.
Once the vulnerability report is delivered privately to the Website Owner's designated email, custody transfers to the client. As stated in our Terms & Safe Harbor and Written Agreement, Mirown.com is not responsible or liable for internal forwarding, misconfiguration, or leaks caused by the client's staff, freelancers, or third-party systems.