Information Conduit does not collect
Conduit does not store full credit card numbers, card security codes, bank account credentials, or raw payment-card details. Payment-card entry and processing are handled by Stripe, and Conduit receives only the billing records needed to operate subscriptions, receipts, invoices, refunds, chargebacks, and support.
Conduit does not upload or store your local project files, scene files, scripts, rendered outputs, production notes, shot data, or creative work in the website account system by default.
Conduit does not ask for passwords, private keys, seed phrases, full payment-card numbers, government identification numbers, medical information, or unrelated personal data through normal support channels. Do not send that kind of information unless support specifically provides a safer process for a necessary request.
Conduit does not sell personal information and does not currently operate the website as an advertising-tracking platform.
Data map
Conduit handles the following categories of account and service data to operate subscriptions, license access, desktop activations, billing support, and account support.
| Category | Examples | Purpose | Provider or location | Retention |
|---|---|---|---|---|
| Website usage | Page path, referrer, approximate screen size, timezone, browser user agent, and a site visitor ID cookie | Understand whether the public site is working, find broken customer paths, and improve the website | Conduit website records | Kept while useful for site operations, troubleshooting, launch measurement, security, or aggregated review |
| Account access requests | Name, email address, role, project stage, plan interest, team size, project title, message, user agent, and hashed IP-related metadata | Review account requests, prioritize onboarding, respond to interested customers, and reduce spam or abuse | Conduit website records | Kept while needed for account follow-up, support, launch planning, abuse prevention, or deletion requests |
| Account and authentication | Email address, Supabase user ID, sign-in state, and account role where applicable | Sign-in, account access, dashboard access, and support lookup | Supabase and Conduit website records | Kept while needed for the account, access control, support, security, or dispute resolution |
| Billing and subscription | Stripe customer ID, checkout session ID, subscription ID, plan, status, receipt or invoice references, webhook events | Checkout, subscription status, plan changes, cancellation status, refunds, receipts, and billing support | Stripe and Conduit subscription records | Kept while needed for billing, accounting, tax, fraud prevention, chargebacks, support, or legal obligations |
| License and device activation | License records, activation records, device association records, last-seen timestamps, account/subscription status used for access checks | License issuance, desktop access decisions, device management, abuse prevention, and account support | Conduit website records and local desktop app records where applicable | Kept while needed to operate license access, resolve device issues, investigate abuse, or support the account |
| Support communications | Messages sent to support, account email, Stripe receipt references, issue descriptions, security reports | Customer support, billing review, privacy requests, security reports, and account recovery | Support email provider and Conduit support records | Kept while needed to answer the request, maintain a support history, handle disputes, or satisfy legal/accounting needs |
Local project and production files
Conduit is designed so desktop production work stays local unless a future feature clearly says otherwise. Local project files, scene files, scripts, rendered outputs, production notes, and shot data are not uploaded to the website account system by default.
If a future feature syncs, uploads, backs up, or shares project data, that feature should explain what changes before it is enabled.
How information is used
Account and billing information is used to provide access, issue license keys, manage desktop activations, process subscriptions, display account status, and provide support.
The desktop app may send minimal account activity events, such as whether a signed-in user opened a starter sample project or completed a first Core workflow, so Conduit can improve onboarding. These events do not include project files, scripts, scene content, rendered output, shot notes, or private creative material.
Support information is used to answer requests, investigate billing or access issues, respond to privacy requests, and handle security reports.
Service providers
Conduit uses Supabase for authentication and account data, Stripe for billing, GitHub Actions for deployment checks, and a self-hosted website server for the production website.
These providers may process information needed to deliver their services, such as login events, billing records, webhook events, and support-related metadata.
Conduit does not store full card numbers. Payment-card handling is provided by Stripe.
Cookies and similar technologies
The website may use cookies or similar browser mechanisms for authentication, session handling, routing, security, account access, and privacy-conscious site measurement.
The current site measurement uses a first-party visitor ID cookie and basic pageview metadata. It is used to understand whether the website is working and where the customer path needs improvement.
Conduit does not currently describe the website as an advertising-tracking platform. If that changes, this policy should be updated before that feature is used.
Privacy requests
You can contact support to ask for access to account information, correction of inaccurate account details, deletion of account information, or clarification about the information connected to your account.
Some requests may require identity confirmation. Some records may need to be retained for billing, tax, security, fraud prevention, chargebacks, dispute resolution, or legal reasons.
For privacy requests, include the account email and say whether you are asking for access, correction, deletion, or another account-data change.
Retention and deletion
Conduit aims to keep only the account, billing, license, activation, and support records needed to operate the service and protect users, billing, and infrastructure.
Records may be deleted, anonymized, aggregated, or retained depending on the type of record, the status of the account, and whether the record is needed for billing, tax, fraud prevention, security, support, dispute resolution, or legal reasons.
Security and limits
Conduit uses reasonable operational safeguards for account, billing, license, activation, and support data, but no website, account system, or internet-connected service can be promised to be completely secure.
If you believe account data or service security may be affected, contact support and avoid sending passwords, private keys, full card numbers, or unrelated personal data.
International use
If you use Conduit from outside the United States, account, billing, support, and operational information may be processed in the United States or in locations where Conduit service providers operate.
Contact
Questions can be sent to support@conduitstudioapp.com.