Privacy & scope

This preview is operated by Warptech Sdn Bhd. Contact: info@warptech-ai.com.

Public website checks

We inspect public pages in a separate desktop Chromium browser. OpenAI may process your goal, public-page screenshots, headings and control labels to guide a bounded inspection. Do not put passwords, confidential information or private URLs into a public check. Public discovery does not enter credentials or submit forms. Some websites restrict automated browsers. Checks are observations, not a security audit or a guarantee.

Protected test accounts

The separate, opt-in protected-login preview accepts a dedicated account for a website you control or are authorized to test. Credentials are encrypted before storage in Supabase; the encryption key is held separately as a hosting secret. Credentials must be decrypted temporarily to perform the approved login. They are not sent to the AI model or returned through the account-list interface.

The protected runner uses Browserbase with session recording and logging disabled and captures a final-page screenshot after successful login. Inputs, images, the test account email/username and long hexadecimal IDs are masked; other page content may remain visible. Use dedicated accounts without real customer data. It permits one submission to the configured authentication endpoint and checks the configured signed-in page. Browserbase and the target website necessarily process the login traffic. An optional configured email-code step reads fresh matching messages from the website's dedicated AgentMail inbox. This preview does not automate signup, outgoing messages, payments or CAPTCHA.

Stored information

Supabase stores customer email addresses, saved websites, test configurations and linked reports. Public checks can include screenshots and Browserbase session recordings. Protected-login reports contain configured checks, outcomes and masked final-page screenshots. Account data is scoped to its owner; authorized service operators can access operational data. Hosting providers may retain request metadata such as IP addresses and timestamps.

Disabling a test account stops its use; it preserves its stored record. Automated retention and credential rotation are not yet implemented. Contact us for data requests. Never use a personal or administrator password as a test credential.

Sign-in and inboxes

Google sign-in requests basic profile and email information, not Gmail inbox access. Secure session cookies keep you signed in. An open Gmail tab on your computer does not connect that inbox to our cloud runner. The administrator pilot can provision dedicated AgentMail inboxes and check received-message counts. AgentMail processes and stores those test emails; Supabase stores inbox ownership and addresses. The connection does not permit sending or deleting messages. Automated signup and opening confirmation links are not currently enabled.

Preview limitations

Only authorized, low-volume checks are permitted. Other browser engines and all possible website journeys are not covered. No paid subscription or payment collection is active in this preview.