Privacy Policy
How Webtunel handles account data, billing data, operational telemetry, task metadata, logs, and support messages.
Last updated: June 15, 2026
Who this policy covers
The controller or responsible business for webtunel-gpu account and payment workflows is Inform Technologies LLC, 30 N Gould St Ste R, Sheridan, WY 82801, US.
This policy covers visitors to webtunel.com, account users, dashboard users, API users, support contacts, and customers who buy prepaid GPU credit.
For privacy requests, contact privacy@webtunel.com or use /contact. Billing privacy questions can also be sent to billing@webtunel.com.
Data we process
We process account identifiers, email addresses, profile and invoice fields, billing references, Stripe checkout references, task metadata, runtime events, logs, artifacts metadata, IP/security telemetry, and support messages.
Task payloads may contain user-provided data. Users should avoid submitting secrets unless the task design requires them and they are properly scoped.
Why we process data
Account and billing data is used to authenticate users, manage credit balances, issue invoices, and provide support.
Runtime data is used to enqueue tasks, enforce credit, lease work to workers, show progress, debug failures, audit platform usage, prevent abuse, and secure the platform.
Where applicable, processing is based on contract performance, legitimate interests in platform security and operations, consent, legal obligations, or the user's request before entering a contract.
Payments and processors
Supabase is used for authentication, sessions, and database-backed account records. Stripe is used for payment checkout, fraud prevention, receipts, invoice references, and payment records.
Stripe may process payment and customer data under its own privacy practices and as a service provider or processor for Webtunel payment workflows.
Third-party GPU infrastructure providers may execute worker images and receive the task data required by the workload. Users control what payload data they submit.
Security and retention
The platform uses owner-scoped records, short-lived stream keys, scoped API keys, and password reset flows through Supabase Auth.
Retention depends on account, billing, tax, operational, dispute, abuse-prevention, and security needs. Some billing and security records may be retained after account closure where required or reasonably necessary.
Users can contact support for access, correction, export, objection, restriction, deletion, or other privacy requests. We may need to verify account ownership before acting.
International transfers and rights
The platform may use infrastructure and processors in multiple countries. Where transfer rules apply, we rely on appropriate contractual, technical, and organizational safeguards from the relevant providers.
Depending on location, users may have rights to access, correct, delete, restrict, object, port data, withdraw consent, or complain to a supervisory authority.