Privacy

Report Privacy

Reports generated by the service are private by default.

Access to analysis results is limited to the context in which the report was created. In most cases this means the report is accessible only to the wallet that initiated the analysis request.

Reports are not publicly indexed or exposed by default. A report may become accessible to others only if one of the following actions occurs:

• the report is explicitly published
• a private share link is generated
• the owner chooses to disclose the report externally

Private reports are intended to remain visible only to the report owner and the systems required to deliver the service.

Wallet Authentication

Certain actions within the platform require wallet authentication.

Wallet authentication is used for functions that involve ownership or account-linked operations. These actions may include:

• accessing report history
• verifying report ownership
• managing report visibility
• interacting with optional onchain receipts

Authentication is performed using cryptographic signatures rather than traditional username and password systems. The service does not store private keys and does not request access to wallet funds.

The wallet address may be associated with generated reports for the purpose of maintaining ownership and history records.

Data Processing

When a contract snippet or verified contract address is submitted for analysis, the system processes the provided input in order to generate the security report.

The service may temporarily process:

• submitted Solidity snippets
• verified contract source code retrieved from public explorers
• metadata necessary to generate the report

This information is used strictly for analysis and report generation.

The platform does not claim ownership over submitted contract code.

Operational Logs and Telemetry

Operational logs and service telemetry may be collected in order to maintain system reliability, performance, and security.

These records may include:

• request metadata
• system errors
• performance metrics
• security monitoring events

Operational logs are used solely to maintain and improve the service. They are not used for advertising or behavioral tracking.

Where possible, logging systems are configured to avoid storing unnecessary user-submitted content.

Security Considerations

Reasonable technical measures are used to protect the integrity and confidentiality of processed data. These measures may include access controls, infrastructure protections, and monitoring systems designed to detect abnormal activity.

However, no internet service can guarantee absolute security. Users should avoid submitting sensitive or confidential proprietary code unless they understand and accept the risks inherent to any online analysis service.

Third-Party Infrastructure

The service may rely on external infrastructure providers in order to operate, such as hosting, networking, or blockchain infrastructure services.

These providers may process limited operational data required for the platform to function. Such processing occurs under the infrastructure provider's own security and privacy standards.

Data Retention

Reports and related metadata may be retained for the purpose of providing history features and maintaining report ownership.

Operational logs and diagnostic information may be retained for a limited period to support system maintenance, debugging, and abuse prevention.

Retention policies may change over time as the service evolves.

Changes to This Policy

This privacy section may be updated as the platform develops new features or modifies how data is processed.

Material changes may be reflected through updates to this page.

Continued use of the service after updates indicates acceptance of the revised privacy terms.