Privacy Policy

We collect Information about you and your use of the Service in three distinct ways. Because we strictly prioritize data minimization, we do not collect or store standard account passwords.

(i) Information Provided by You

To access the compute features of the Service, you are required to register for an account. When managing your workspace profile, you may choose to provide personal information such as your name, organizational identifiers, or contact preferences. As an interactive data science environment, we also store and process the code, projects, custom data configurations, and environment variables that you directly write, execute, or upload to your active workspaces.

(ii) Information Obtained from Third Parties (Federated Identity)

While signing up or logging into the Service, you may choose to share information with us by delegating authentication to third-party identity management providers. We collect public profile metrics permitted under the scopes you authorize via these channels:

• Google OAuth
• GitHub Auth
• GitLab Auth
• BitBucket Auth

(iii) Information Obtained Automatically While You Use the Service

We automatically collect diagnostic telemetry and technical metadata concerning how you interact with our network perimeter to guarantee stability, manage load capacities, and enforce system security. This includes:

• Data related to your direct computing instances, such as execution lifecycles, memory parameters, run-times, and system error events.

We use cookies and similar tracking technologies to provide, protect, and optimize the functionality of our Service. A cookie is a small text file placed on your device through your browser.

• Essential Cookies: These cookies are strictly necessary to deliver our baseline services. For example, we use essential cookies to maintain your authenticated session state and securely bridge your active browser window to your isolated project container running on our backend. Because the Service cannot function safely without them, these cookies cannot be deactivated.

You can manage your cookie preferences through your individual web browser settings, though disabling all cookies may prevent sections of our workspace platform from running correctly.

Our platform applications, databases, persistence storage clusters, and network routing layers run on servers and web hosting systems provided by third-party infrastructure vendors.

If you choose to use the Service from regions of the world with laws governing data collection and use that may differ from United States or Indian law, please note that your Information may be transferred, processed, and stored outside of those regions. By providing any Information on or to the Service, you consent to this transfer, storage, and processing. We secure these international data flows utilizing standard contractual mechanisms and recognized data privacy frameworks.

To protect your computational workloads and privacy, our platform architecture employs the following isolated security safeguards:

• Compute Isolation: Every computational project run-time scales dynamically inside its own decoupled, containerized execution space. Your code executes inside a completely isolated sandbox environment.
• Persistence Safeguards: Relational user records are isolated within an encrypted production database cluster. Persistent project file directories are managed through distinct storage access layers to ensure complete isolation between different user tenants.
• Network Perimeter Control: Inbound application web traffic is routed securely through application load balancers protected by an active web application firewall. Outbound network requests initiated from inside your running project are managed and filtered through a dedicated proxy server layer to protect the integrity of our internal subnets.
• System Logging & Event Routing: Telemetry and activity indicators are parsed dynamically to monitor system health. Raw code inputs or output values inside your active execution container are omitted from system monitoring captures.

All subscription sales, pay-as-you-go credit pack purchases, invoicing, and localized tax remittance are conducted and fulfilled by Paddle.com (Paddle.com Market Limited), our online reseller and Merchant of Record (MoR).

We do not directly collect, capture, view, or store your payment card numbers or banking details. When you make a purchase, your payment data is submitted directly to Paddle, who serves as the independent data controller for your transaction records. Paddle processes your personal and financial information in accordance with their own legal terms and privacy policies.

You can review Paddle’s Privacy Policy directly at https://www.paddle.com/legal/privacy.

We will not share or expose any of your personal or computational Information to third parties except as explicitly detailed in this Policy and under the following standard circumstances:

• Payment Processing & Billing: We share transaction metadata and account email identifiers with Paddle to handle subscription verification, tax calculation, order fulfillment, and buyer support. For billing inquiries or payment assistance, you can also access Paddle Buyer Support at https://paddle.net.
• Service Providers & Infrastructure Vendors: We share minimal operational information with third-party vendors who supply cloud web hosting, database infrastructure, logging, and application analytics strictly to maintain and run the Service.
• Legal and Regulatory Compliance: When required by subpoenas, court orders, or administrative requests from regulatory and law enforcement entities.
• Security & Platform Defense: When disclosure is vital to preserve the integrity, availability, and physical security of the Service, its users, or the broader public.
• Corporate Transactions: In the event that we undergo a major business transition, such as an asset liquidation, merger, or corporate acquisition.

We retain personal attributes and persistent directory contents only for as long as necessary to fulfill the requirements of your active account subscription, conduct internal audits, or as otherwise required by law. If you would like to access your information or would like us to delete or modify your information, please reference the dynamic account configuration panels or contact support via support@byterun.io.

Additionally, you can export your individual project documents directly out of the application layout interface at any time. To continue to improve the Service, we may anonymize your Information in a way that does not personally identify you and store such anonymized Information perpetually.

The Service allows you to explicitly share or distribute interactive data projects with other users or teams. Please remember that any Information or embedded credentials you deliberately include within public or shared project directories becomes public information accessible to authorized viewers. You should exercise caution when deciding which data configurations or secrets to expose within shared platform spaces.

ByteRun is operated by Sashidhar Thallam, an individual based in India. If you have any questions regarding this Privacy Policy or your personal data rights, please contact us at:

• Data Privacy Enquiries: privacy@byterun.io
• Product Enquiries: support@byterun.io
• Billing & Transaction Assistance: support@byterun.io. You may also reach out directly to Paddle via https://paddle.net

Please review our Terms of Service and Refund & Cancellation Policy.