Aya security audit terms
Revision: 2026-11-11.2. Published: 2026-11-11.
The operator is sole proprietor Nikita Andreevich Olenev, OGRNIP 324527500121240. These terms describe authorization for automated public website checks, each level’s scope and the parties’ responsibilities. Contact: https://t.me/nekitocka.
Scope by level
01 / Read onlyScope v. 1.1
Basic
- Duration
- Up to 1 minute
- HTML
- Up to 2 MiB
Public page: TLS, HTTPS, headers, cookies, CSP, static HTML and forms. One root GET and up to five redirects within the same protocol, host and port. No sign-in, cookie forwarding, Nuclei or exploitation. Up to one minute; HTML up to 2 MiB. Publicly available.
02 / Stack-based checksScope v. 1.1
Medium
- Duration
- Up to 10 minutes
- Traffic limit
- Up to 128 MiB
Basic checks, technology detection and matching read checks from the pinned HTTP catalog: exposed configuration, source, logs, backups and service files. Up to 10 minutes and 128 MiB gateway traffic.
03 / Active probesScope v. 1.1
Maximum
- Duration
- Up to 30 minutes
- Traffic limit
- Up to 512 MiB
Medium checks, CORS and active HTTP/CVE probes for the detected stack, including bypass, injection and execution markers. Requests may change website state, create records and disrupt service. Up to 30 minutes and 512 MiB gateway traffic.
04 / Full HTTP catalogScope v. 1.1
Cyber-hacker
- Duration
- Up to 2 hours
- Traffic limit
- Up to 2 GiB
The entire compatible HTTP catalog without stack filtering, including active probes, plus attempted creation, reading and deletion of a random canary file. Up to two hours and 2 GiB gateway traffic. Data changes, load and disruption are possible; cleanup of all effects is not guaranteed.
Redirects and access
At every level, the public page may be retrieved through up to five redirects within the original origin. Other domains, protocols or ports are not followed. During this navigation, no cookies or credentials are forwarded; no sign-in or form submission is performed. Ownership proof and catalog checks remain tied to the original origin. Private areas are not considered tested.
Authority and target
By accepting and submitting a URL for each run, you confirm ownership or a current owner authorization covering the selected level. Check the rules of your hosting, CDN and other affected providers. An administrator role and an ownership-proof exemption do not replace legal authorization. Do not test third-party infrastructure without the necessary authority.
Risks and preparation
Choose the level in view of its effects; prepare backups, monitoring, recovery access and a maintenance window where needed. Active requests may cause WAF blocks, data changes, resource charges or downtime. Isolation and load limits apply; DoS, mass brute force, external callback categories and unsupported protocols are excluded. These measures do not guarantee the absence of side effects.
Stopping and cleanup
Stop new actions with /cancel or withdraw through /audit_terms. Stopping does not undo earlier requests. Limited cleanup of Aya’s own canary file may continue after stopping; an unconfirmed cleanup path appears in the report. Review and remediate other effects with the website owner.
Reports and data
Reports contain observed signatures, recorded coverage and limitations, not a security guarantee. False positives and omissions are possible. Authorization, private business logic and browser flows are not comprehensively tested. AI receives the address and normalized finding categories for a short summary, not raw responses, cookies or discovered secrets. HTML uses stored facts. Reports are retained for up to 30 days; personal data is handled under the Studio privacy policy.
Responsibilities
You are responsible for your authority, target and lawful instructions. The operator remains responsible for its own conduct under applicable law. These terms do not exclude liability that cannot legally be excluded, mandatory consumer rights or third-party rights.
One-time acceptance and updates
Initial acceptance records the Telegram user, revision, time, language and button message. It covers later voluntary runs within this scope. Signature catalogs and technical explanations may change without another prompt if authorized effects, duties and risks are not materially expanded; the current revision is announced before the next run. Initial acceptance and update notices are recorded separately, without inventing another acceptance. Material expansions require a new acceptance. Updates do not retroactively change completed checks.
Declining and contact
Declining prevents a check and does not disable other Aya features. Audit authorization is separate from promotional mailings. Withdraw, request acceptance details or request deletion through /audit_terms or https://t.me/nekitocka. Acceptance records are retained while needed for feature access and lawful evidence of authorized actions.