Skip to main content
  • Polars

    The compute engine for open data.

    Code window with a Polars query over a blue and teal aurora
     

    Polars Nanook

    The compute platform for all your workloads.

    Code window configuring a Polars Nanook compute context
     
    Platform
    • On-Premises

      Run the engine inside your own network.

    • Benchmarks

      Polars benchmark results against other engines.

    • Enterprise Support

      Named engineers, response times and an SLA.

  • Documentation
    • User Guide

      Every concept, worked through end to end.

      (opens in a new tab)
    • Getting Started

      Install it and run your first query.

      (opens in a new tab)
    • GitHub

      The source, the issues and the releases.

      (opens in a new tab)
     
    API Reference Guides
    • Rust

      The crate, module by module.

      (opens in a new tab)
    • Python

      The package, module by module.

      (opens in a new tab)
  • Learn
    • Academy

      Courses and guides to learn Polars.

    • Blog

      Releases, engineering notes and benchmarks.

    • Case Studies

      What teams moved off, and what it saved them.

     
    Company
    • About

      Who builds Polars, and why.

    • Careers

      Open roles across engineering and go to market.

     

    Polars Cloud becomes Polars Nanook

    Polars Cloud becomes Polars Nanook: a full data platform for cloud and on-premises.

    Announcements05 Nov 263 mins
  • Pricing
40k+(opens in a new tab)Log inTalk to usGet started

Responsible disclosure policy

Terms of use “Polars Nanook”Data processing agreement “Polars Nanook”Sub-processors “Polars Nanook”Privacy statement PolarsCookie policy

Contents

1. Scope2. How to report3. What we ask of you4. What we commit to5. Safe harbor6. Disclosure7. Rewards8. Changes

Polars B.V. (“Polars”, “we” or “us”) welcomes reports from security researchers and anyone else who finds a vulnerability in our services. This policy explains what you can test, how to report what you find, and what you can expect from us in return. It is also known as a vulnerability disclosure or coordinated vulnerability disclosure (CVD) policy.

1. Scope

This policy covers:

  • pola.rs, polars.tech and all of their subdomains;
  • the Polars Nanook service, including the portal and the API;
  • the Polars Nanook software we distribute, such as the Python client, the compute packages and container images, the Helm chart and the CloudFormation template.

The following are out of scope:

  • The Polars open-source library. Report vulnerabilities in it as described in its security policy.
  • Our development and staging environments, such as *.dev.nanook.pola.rs and *.stg.nanook.pola.rs.
  • Services that third parties run for us under our domains. Report vulnerabilities in those services to their providers. A misconfiguration on our side, such as a subdomain that can be taken over, is in scope.
  • Polars Nanook deployments that our customers run in their own cloud accounts or on their own hardware. Do not test them. A vulnerability in our software that you reproduce in a deployment of your own is in scope.
  • Physical security, and social engineering of our employees, customers or suppliers.

If you are unsure whether something is in scope, ask us at security@polars.tech before you start.

2. How to report

Email your report to security@polars.tech, in English. Please include:

  • the affected service, URL or product, and the version if it is software you run yourself;
  • a description of the vulnerability and its impact;
  • the steps to reproduce it, or a proof of concept;
  • how we can reach you, if you want to hear back from us.

Only report vulnerabilities you have confirmed yourself. If you use AI tools or automated scanners, check their findings and include a working proof of concept. We may close reports without a proof of concept, or that appear to be unverified AI output, without a reply.

You can report anonymously, but then we cannot keep you informed.

3. What we ask of you

  • Only use accounts you created yourself or have explicit permission to use. The free Developer plan is enough to test Polars Nanook.
  • Do not degrade the service for others. No denial-of-service or load testing, and throttle automated tools.
  • Do not use compute or other resources for anything beyond what you need to show the vulnerability.
  • Access as little data as possible. If you come across personal data or data of another customer, stop, report it to us, and do not keep, copy or share it. Delete any data you obtained once you have reported it.
  • Do not change or delete data that is not yours, and do not leave backdoors or other changes behind in our systems.
  • Do not use social engineering, phishing, spam or physical attacks.
  • Keep the vulnerability confidential until we agree otherwise (see section 6).
  • Do not demand payment or anything else in return for your report.

4. What we commit to

  • We assess the vulnerability, prioritise it by severity, and keep you informed about our progress if you gave us your contact details.
  • We handle your report confidentially and do not share your personal details with third parties without your permission, unless the law requires us to.
  • We fix vulnerabilities in the services we host as soon as we can. For software you run yourself, we decide case by case how and in which versions we ship a fix.

More about how we secure Polars Nanook is on our trust center.

5. Safe harbor

If you act in good faith and follow this policy, we:

  • consider your research authorised, and will not take legal action against you or report you to the police;
  • waive any restriction in our terms of use that would prevent you from doing research in line with this policy, such as the restriction on penetration testing;
  • will make it known that you acted in line with this policy if a third party takes legal action against you.

This only covers claims that are ours to make. It does not bind third parties, and you remain responsible for complying with the law.

6. Disclosure

We decide whether, when and how a vulnerability is published, and do not publish every vulnerability. Do not publish or share details of a vulnerability without our written agreement. If you want to publish, tell us, and we will agree on the timing together.

7. Rewards

We decide on rewards case by case and at our discretion. A report does not entitle you to a reward. Polars employees, contractors and members of their households are not eligible.

We are grateful for every report, but the following usually do not qualify for a reward:

  • missing security headers or cookie flags without a demonstrated impact;
  • SPF, DKIM or DMARC configuration;
  • output of AI tools or automated scanners that you have not validated;
  • self-XSS, and clickjacking on pages without sensitive actions;
  • user or email enumeration;
  • missing rate limits on endpoints that are not sensitive;
  • disclosure of software versions;
  • issues that require a compromised device or a man-in-the-middle position.

8. Changes

We may change this policy. The version on this page applies.

Last updated: 16 November 2026

One framework.
Start anywhere.

Install Open Source in seconds, or talk to us about running Polars at scale.

Get startedTalk to us
Platform
  • Polars Open Source
  • Polars Nanook
  • Integrations
  • Enterprise Support
  • Trust & Security(opens in a new tab)
Resources
  • Blog
  • Case Studies
  • Talks
  • Updates
Company
  • About Us
  • Careers
  • Academy
GitHub(opens in a new tab)
LinkedIn(opens in a new tab)
Discord(opens in a new tab)
Bluesky(opens in a new tab)
X.com(opens in a new tab)
Terms of UsePrivacy PolicyCookie PolicyResponsible Disclosure

© Polars 2026. All rights reserved.