VOLTENWORKS LOOKUP

Privacy policy

Effective September 9, 2026.

This page describes how Voltenworks Lookup handles account information, payments and website lookup requests. It covers Lookup specifically.

Account information

Clerk handles signup, sign-in and session management. Lookup stores your Clerk account identifier to associate API keys, credits and requests with your account. Clerk processes the identity information you provide during signup. Lookup does not store your account password.

API keys and request records

We store a hash of each API key, its identifying prefix, its name and whether it has been revoked. The complete key is shown when it is created. Keep it private.

For lookup requests, we store an account identifier, your request identifier, a hash of the input URL, processing status, timestamps, credit movements and the completed result. A result can contain the scanned URL and public evidence URLs. These records support usage history, billing and replaying a completed request without charging twice.

Public website scans

Lookup fetches the public page you request and reads its HTML to identify software signals. It does not execute page JavaScript or sign in to the scanned website. A destination website can observe a request from the scanning service.

Raw HTML, inline script contents and cookie values are not returned in the API result or stored in the request-result table. Query strings and credentials are removed from returned resource evidence URLs. The scanned page URL can still appear in a result. Do not submit URLs containing personal information, secret tokens or confidential information.

Payments

Stripe processes payments and subscriptions. Lookup stores Stripe customer and subscription identifiers, credit balances and a credit ledger. Payment card numbers are handled by Stripe and are not stored by Lookup.

Service providers and storage

Authentication information is processed by Clerk, and payment information by Stripe. Vercel hosts the application. Neon stores account, request and credit records in a PostgreSQL database in AWS Northern Virginia, United States. Clerk, Stripe and Vercel may process information in other locations under their own service and privacy terms.

Retention and requests

Account, request and credit records are retained until deletion is requested; there is no automatic expiration schedule for these records. Contact support to request access, correction or deletion. We may retain records needed to resolve disputes, prevent abuse or meet financial and other legal obligations. Authentication and payment providers apply their own retention policies to information they process.

Tracking

Lookup uses Clerk session functionality for authentication. We use self-hosted Umami on the public landing and documentation pages to count visits, referral sources, campaign links and signup-button clicks. Umami does not use tracking cookies, and our tracker respects Do Not Track. It receives page paths, browser and device information and approximate location derived from the request. We do not send account identifiers, API keys, lookup inputs or customer dashboard activity to Umami. We do not use an advertising tracker. External authentication and payment pages may use their own cookies and storage.

A first-party cookie lasting up to 30 days across Voltenworks product subdomains stores limited campaign and product categories. It contains no account ID or unique visitor token. Browser session storage helps distinguish visits. When products share a verified sign-in system, internal aggregate reports can count customers using or buying multiple products; separate accounts are not matched by email. Journey attribution and Umami tracking honor Do Not Track and Global Privacy Control. See the Voltenworks privacy policy for details.

Contact

For privacy requests, billing questions or support, email support@voltenworks.com.