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, notebooks, 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
• Apple ID

(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:

• Your internet protocol (IP) address, operating system, browser configuration, and access timestamps.
• 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 notebook container running on our backend. Because the Service cannot function safely without them, these cookies cannot be deactivated.
• Analytics and Performance Technologies: We may use privacy-first analytics applications to gather aggregated, anonymized metrics detailing how users navigate the Service interface. These metrics do not collect or store personally identifiable data and are used purely to improve platform execution, reduce resource latency, and tailor user experience layouts.

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 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 notebook 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 notebook 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 notebook 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 credit card processing, invoicing, subscription management, and localized tax assessments are managed entirely by Paddle, who acts as our external Merchant of Record (MoR).

We do not collect, capture, view, or retain your financial credentials or credit card digits. Paddle operates as the legal reseller of our platform licensing and serves as the independent data controller for all transactional actions. They handle your payment indicators under their own corporate privacy terms, executing cross-border payment safety and localized tax remittance on our behalf.

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

• To Perform Service Functionality: We share minimal information with third-party vendors who supply software applications, web hosting, payment processing, and other technologies strictly for the functionality of the Service. They are legally obligated to not use your data for any independent purpose.
• 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 the administration channels linked in your application dashboard.

Additionally, you can export your individual notebook 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 notebooks with other users or teams. Please remember that any Information or embedded credentials you deliberately include within public or shared notebook 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.

Have any privacy questions? Contact us at privacy@yourdomain.com. See also our Terms of Service.