Lintrule Documentation


    Lintrule never stores, logs, or trains on customer code.

    We enforce this with Lintrule itself. We've got a rule that looks a bit like the following. If you'd like us to add a stricter rule, contact us.

    Never store (in redis, postgres, or any other datastore) customer code or documents.
    Here's some examples of things to prevent from passing the code review:
    // Don't log customer data!"Some log", { document })
    // Don't log bodies of requests!{ body: req.body })
    // Don't include bodies in error messages!
    throw new Error("Some error", { body: req.body })
    // Don't store customer code in a database!
    db.insert({ document })
    // Don't store it in kv / redis!
    kv.set("some-key", { document })

    For larger customers, Lintrule can run on-premises. Contact us if you feel like this is a good fit for your organization.

    Lintrule uses OpenAI, which does not train on customer code, and deletes after 30 days.

    Really! They changed their policies for API usage:

    Starting on March 1, 2023, we are making two changes to our data usage and retention policies:

    1. OpenAI will not use data submitted by customers via our API to train or improve our models, unless you explicitly decide to share your data with us for this purpose. You can opt-in to share data.

    2. Any data sent through the API will be retained for abuse and misuse monitoring purposes for a maximum of 30 days, after which it will be deleted (unless otherwise required by law).

    Normal OpenAI employees cannot see the data. We should know, Lintrule is built by former OpenAI folks.