Information handled
Depending on how you use the service, we may handle account identifiers, credential hashes rather than plaintext credentials, request and usage metadata, payment transaction metadata, and operational or security logs.
Request processing
Requested target URLs may be processed as necessary to perform a request, apply safety checks, and account for usage. Database records contain accounting and request metadata. The current architecture does not claim that fetched page HTML is stored as a product record.
Credentials and payments
Credentials are designed to be stored as hashes where persistence is required. Payment processing may involve transaction metadata needed for reconciliation and support. Payment secrets are configuration credentials, not customer-visible account data.
Service providers and security
Generic infrastructure and service providers may process data as needed to operate the service. We use operational controls intended to reduce credential exposure and request-secret leakage, but no online service can guarantee absolute security.
Public-site analytics
With your permission, Google Analytics measures visits and conversion events on public marketing, documentation, and legal routes. Analytics is not loaded on Console, administration, account-loading, or API routes. We do not send credentials, account identifiers, target URLs, payment identifiers or amounts, or wallet addresses to analytics. You can decline analytics when prompted.
Questions
For privacy questions, use the support contact configured for the service environment.