Privacy & Cookies Policy

Introduction

inspect (inspect.wwwavy.com) is operated by WANGLONG (WANGLONG TECHNOLOGIES SDN. BHD., 1347287-M), based in Penang, Malaysia.

WANGLONG respects your personal privacy and code confidentiality. This policy outlines what information we collect when you visit inspect, create an account, or submit target URLs, code repositories, or archive packages for quality audits, and how that information is handled.

Information We Collect & Audit Processing

When you create an account or sign in to inspect, we collect your email address and authentication credentials. When you execute an audit:

• Public URLs: Audited in isolated, sandboxed headless Chromium instances to inspect DOM hierarchy, color contrasts, layout bounding boxes, and typography definitions.
• Git Repositories & ZIP Archives: Shallow-cloned or extracted into secure, temporary sandbox directories with path-traversal safeguards. All sandbox files are immediately purged after AST and CSS token analysis is complete.

We use this information solely to deliver automated frontend reports and manage your credit balance. We never sell, rent, or distribute your personal contact information or private source code to third parties.

Cookies & Session Management

Cookies are small text files sent to your browser to maintain session state and provide security.

• Strictly Necessary Cookies: We utilize secure HTTP-only cookies (wwwavy_session) solely to authenticate user accounts, enforce session expiration, and secure API requests.
• Analytics & Performance: Minimal, privacy-focused traffic telemetry to monitor application performance and ensure platform reliability.

You can manage or disable cookies through your browser settings, though disabling session cookies will prevent signing in to your account.

Data Security & Cryptography

We implement industry-standard technical and operational safeguards:

• User passwords are protected with cryptographic PBKDF2/scrypt one-way password hashing.
• All data in transit is encrypted using HTTPS and TLS protocols.
• Worker task dispatches and status webhooks are authenticated with HMAC-SHA256 request signatures.
• Isolated compute environments scale down and wipe working directories immediately after each job.