A Redshift-native SQL IDE for VS Code, with an MCP server built in.
Version 1.0 — effective 12 August 2026 Effective date: 12 August 2026 — the day the production catalogue went live Licensor / Publisher: Diego Borjan, an independent software developer based in Mexico (“the Publisher”, “we”, “us”). Software: RedLens Pro — the paid Visual Studio Code extension that extends the free RedLens extension.
This Agreement governs RedLens Pro only. The base RedLens extension is open source under the MIT licence and is not covered by anything below: its source is at https://github.com/redlens-io/redlens and its terms are in that repository’s LICENSE file. You can install, use, modify and redistribute the free extension under MIT whether or not you ever accept this Agreement. Contact: support@lensql.dev · https://lensql.dev/support — the channels for support AND legal notices (section 20.5).
Copyright © 2026 Diego Borjan. All rights reserved.
This summary is here so you know what you are signing up for without reading twenty sections. It is orientation, not the contract: where the summary and the numbered clauses differ, the numbered clauses win.
1.1 By installing, activating, or using RedLens Pro, you agree to this Agreement. If you do not agree, do not use the Software and uninstall it. Uninstalling RedLens Pro leaves the free RedLens extension working: it is a separate extension under a separate licence, and nothing in this Agreement restricts your use of it.
1.2 If you install or use RedLens Pro on behalf of a company or other organisation, you confirm you are authorised to bind that organisation, and “you” means both you and it.
1.3 You must be old enough to enter a binding contract where you live.
1.4 RedLens Pro is offered primarily to businesses and to individuals acting in the course of a trade, profession or business. It is not sold as business-only, because an independent developer paying with a personal card is a real and expected customer at the individual tier. If you are acquiring it as a consumer, sections 9, 14, 15 and 21 contain savings clauses that preserve the rights your local law gives you, and we do not ask you to waive them.
1.5 Buying through Polar also constitutes acceptance of this Agreement, which is linked from the RedLens product page at checkout.
.vsix, updates), including its documentation and any files we ship with it. It does not include the free RedLens extension, which is separately licensed under MIT.All licences below are non-exclusive, non-transferable (except as allowed in 20.1), non-sublicensable, worldwide, and subject to the restrictions in section 4.
You may install and use the Free Features on any number of machines, for personal or commercial purposes, for as long as we distribute the Software. No payment, no account, and no conditions on the kind of work you do with it. The Free tier comes with no support obligation and no availability guarantee; see section 11 for how it can change.
(a) The first time RedLens activates on a machine, a 14-day Trial of the full Pro feature set starts automatically. No payment method, no account, no sign-up.
(b) The Trial is for evaluating whether RedLens is fit for your needs. One Trial per person and per machine.
(c) When the 14 days end, Pro Features lock and RedLens continues as a Free installation. Nothing you created is deleted.
(d) You may not restart or extend the Trial by reinstalling, changing your system clock, creating additional machine identities, using virtual machines or containers for that purpose, or modifying the Software. Doing so is a material breach and ends your right to use the Software.
(a) A Pro licence is granted to one identified individual, named in the entitlement. That individual may install and use the Software on up to three machines they personally use — for example a work laptop, a desktop and a personal machine.
(b) A Pro licence may not be shared, pooled, rotated between people, or used concurrently by more than the one named individual, whatever the machine count allows.
(c) If you replace or rebuild a machine, use the support channel at https://lensql.dev/support and we will re-issue the entitlement. There is no automated deactivation service — see 3.6(d).
(d) The current published price is USD 99 per user per year; the price that applies to you is the one shown at checkout.
(a) A Team licence is sold per Seat, with a minimum of five Seats, at the published price (currently USD 199 per user per year). Total concurrent Authorised Users may never exceed the number of Seats purchased.
(b) Authorised Users may be employees or individual contractors doing work for you or for Your Group. They may not be your customers, and Seats may not be used to provide a service to third parties (see 4.1(c)).
(c) Seats are reassignable on a permanent change of personnel — when someone leaves, or changes role — and are not to be rotated, shared or timeshared between people.
(d) Seats added during a term are charged at the then-current price for the remainder of the term.
An Enterprise tier, including offline licence files for air-gapped environments, is planned but is not offered under this Agreement. If we offer it, it will be governed by a separate order form that incorporates this Agreement, and that order form controls where the two conflict.
(a) Your entitlement is confidential. Do not share, sell, publish or post it — not in a public or shared repository, a paste site, a screenshot, a container image, a dotfiles repo, or a CI configuration readable by people who are not Authorised Users. Entitlements carry the licensee’s identity precisely so that a leaked one is traceable.
(b) Publishing an entitlement, distributing a modified build, or distributing a means of bypassing the licence check terminates your licence immediately and without refund, and we may decline to renew.
(c) The current release verifies your entitlement entirely locally, using a public key embedded in the extension. If the entitlement names a machine identifier, it is checked against this machine. The Software makes no network call of any kind to verify a licence: there is no activation count, no online re-validation, and no check that can fail because a server was unreachable. After the expiry date, Pro Features continue for a 14-day grace period and then lock.
This clause deliberately describes only what the shipped code does. The three-machine allowance in 3.3(a) is therefore a contractual limit you honour, not one the Software counts or enforces. If a future release adds activation management, this clause will be updated in that same release, never after it.
(d) Be aware of what this design does not include: we operate no licence server in the request path and have no remote kill switch. We cannot disable your installation, revoke an entitlement already on your machine, or manage seats on your behalf. Every enforcement statement in this Agreement is a contractual obligation on you, not something we do to your computer.
4.1 You may not:
(a) copy the Software except as needed to install and back it up, or distribute, publish, sell, rent, lease, lend or sublicense it;
(b) modify, adapt, translate, repackage or republish the Software or the .vsix, or create derivative works of it;
(c) use the Software to provide a service bureau, timesharing, managed service or hosted offering to third parties who are not Authorised Users;
(d) circumvent, disable, or interfere with the licensing, tier gating or entitlement verification, or use the Software with an entitlement you did not lawfully obtain;
(e) remove, obscure or alter any copyright, trademark, licence or attribution notice, or the RedLens name and branding;
(f) use the code or trade secrets of the Software to build a substantially similar competing product;
(g) use the Software to access any system you are not authorised to access, or in violation of any law or third-party right.
4.2 Reverse engineering. You may not reverse engineer, decompile or disassemble the Software, except to the extent that this restriction is prohibited by mandatory applicable law — including the rights to observe, study, test, and to decompile for interoperability under Articles 5 and 6 of Directive 2009/24/EC in the European Union, and equivalent provisions elsewhere. Where you rely on such a right, please contact us first: we will usually give you the interface information you need without the work.
4.3 Nothing in this Agreement restricts you from publishing your honest opinion of the Software, including benchmarks and reviews.
5.1 Licensed, not sold. The Software is licensed, not sold. The Publisher retains all right, title and interest in it, including all intellectual property rights. You get the rights expressly granted here and nothing more.
5.2 Your Content is yours. We claim no ownership of and no licence over Your Content or Your Environment. SQL you write, results you retrieve, exports you produce, DDL and CLI commands RedLens generates for you, and AI output you accept are yours to use however you wish. We never receive them (see section 8).
5.3 Feedback. If you send us ideas, bug reports, feature requests or suggestions, you grant us a non-exclusive, worldwide, royalty-free, perpetual and irrevocable licence to use them in the Software without obligation, attribution or compensation. You keep everything else.
5.4 Third-party and open-source components. The Software includes third-party components listed with their licences in the NOTICES.md file shipped with the extension. Those components are governed by their own licences, and nothing in this Agreement limits any right those licences grant you.
5.5 Publicity. We will not use your name or logo as a customer reference without your prior written permission.
RedLens is a professional tool for people who work with production data warehouses. It assumes you know what a DROP, an UNLOAD and a GRANT do. You are responsible for:
(a) selecting the Software, deciding it is fit for your purpose, and reviewing everything it generates before you run it;
(b) Your Environment: your credentials, your IAM policies, your network, and the security of the machines you install RedLens on;
(c) being lawfully authorised to access every database and AWS account you connect to;
(d) all charges your own AWS account incurs as a result of using RedLens — including Redshift compute, Data API calls, CloudWatch GetMetricData charges, S3 transfer, and anything triggered by commands RedLens generates and you choose to run;
(e) your own backups. RedLens is not a backup tool and does not protect you from a statement you executed;
(f) your own regulatory and contractual compliance, including any obligations covering the data in the warehouses you connect to.
7.1 We do not operate an AI model. The AI features — natural language to SQL, plan explanation, query optimisation, error fixing, object description and the chat participant — run through the AI model provider configured in your editor, under your own agreement with that provider (for example GitHub Copilot). We are not a party to that agreement, we do not host or fine-tune any model, and we have no control over what your provider does with a prompt once it leaves your editor.
7.2 AI output can be wrong. Generated SQL, optimisations, explanations and DDL may be incorrect, incomplete, out of date, or destructive. You are solely responsible for reviewing anything the AI produces before executing it against any system. RedLens is designed so that generated statements open in an editor for you to review rather than being executed for you; do not defeat that design.
7.3 The MCP server. The embedded MCP server exposes a read-only tool set over a local loopback connection to whatever AI agent you connect to it. You choose which agents you run and you are responsible for what they do. The read-only guard and the read-only transaction wrapper are safety measures, not guarantees, and they do not make an untrusted agent safe to point at a production warehouse.
7.4 PII-safe mode is best-effort. PII-safe mode applies heuristics and your configuration to reduce the chance that identifiable values leave the extension. It is not warranted to be complete or correct, and you must not rely on it as a compliance control or as a substitute for your own data-protection measures. Verify its behaviour against your own requirements before using it with regulated data.
7.5 If any AI feature ever becomes hosted by the Publisher rather than running on your provider, this section will be rewritten and you will be notified before that version is installed.
This section describes how the Software is built. The Privacy Policy at https://lensql.dev/privacy covers the purchase relationship and is the controlling privacy document.
8.1 No server, no proxy. The Publisher operates no backend for the Software. RedLens runs entirely inside your editor and connects directly to your own Redshift clusters and AWS account using credentials you supply. Your queries, results, schemas, connection endpoints, database names and credentials are never sent to the Publisher.
8.2 Credentials. Secrets are stored using VS Code’s SecretStorage, which is backed by your operating system’s credential store. They are never written to settings files, never logged, and never included in telemetry.
8.3 Telemetry. The current release ships with no telemetry endpoint configured and sends nothing. The emitter is constrained by an allowlist so that, if telemetry is ever enabled in a future version, it can only ever send two events: activate (no fields) and command (one field: a command identifier from the extension’s own declared list). It can never carry SQL text, schema, table or column names, connection endpoints, database names, AWS account identifiers, error messages, row counts or query results, because there is no free-text field in the payload. Telemetry honours VS Code’s global telemetry.telemetryLevel, and redlens.telemetry.enabled can only turn it further off — never back on against your global preference.
8.4 Licence re-validation. When you activate a paid licence, and roughly weekly thereafter if a network is available, RedLens may contact the licensing service operated by Polar to confirm your entitlement is current. That request carries only your entitlement identifier and a machine identifier. It carries none of Your Content and none of Your Environment.
8.5 Where data does leave your machine. For completeness, data leaves your machine to: (a) your own AWS account and databases, at your instruction; (b) the AI model provider you configured in your editor, when you invoke an AI feature; (c) the Marketplace, when you download or update the extension, under Microsoft’s or Open VSX’s terms; (d) Polar, when you buy or re-validate a licence. Only (d) involves us, and only indirectly.
8.6 Purchase data. When you buy, Polar collects your name, email and billing information as merchant of record, and provides us with the limited information needed to issue and support your licence. We use it to issue entitlements, provide support, and send licence and renewal notices — nothing else.
9.1 Polar is the merchant of record. RedLens licences are sold by Polar Software, Inc. as merchant of record and authorised reseller. You buy the product from Polar; the right to use the Software is licensed to you by the Publisher under this Agreement. Polar’s terms govern the payment transaction; this Agreement governs the licence. Where a term of Polar’s is about payment and a term here is about the licence, both apply in their own domain.
9.2 Prices and taxes. Prices are per user, per year, as displayed at checkout. Polar collects and remits sales tax, VAT and equivalent charges as merchant of record; displayed prices may exclude tax added at checkout. We may not, and will not, invoice you or take payment directly.
9.3 Renewals. Subscriptions renew automatically through Polar unless you cancel before the renewal date, using the customer portal Polar provides. Price changes take effect at renewal, and we will give you at least 30 days’ notice before a renewal at a higher price.
9.4 Refunds — fourteen days, no questions asked. Ask within 14 days of a purchase or a renewal and we will request a full refund on your behalf; we do not ask why. Because Polar is the merchant of record, the money is returned by Polar under Polar’s own buyer terms (linked from your receipt and from the checkout page) and we cannot issue it directly — but the commitment above is ours, and we will make the request.
Beyond 14 days we will still consider a request, particularly for a renewal you did not intend. Use the support channel at https://lensql.dev/support.
There is little reason to need this: the 14-day trial is the whole product, before any payment.
9.5 Statutory rights. Nothing in this section affects refund or withdrawal rights that consumer law gives you and that you cannot waive — including, where it applies, the right to withdraw from a distance contract within 14 days.
9.6 Chargebacks. If you initiate a chargeback instead of asking for a refund, your licence terminates on the date the chargeback is filed. Please just ask us first.
10.1 A paid licence runs for the term you purchased, starting on purchase, and the expiry date is carried inside your entitlement.
10.2 Grace period. Pro Features keep working for 14 days after the expiry date, so a lapsed payment or a week offline never locks you out mid-task.
10.3 What expiry does and does not do. When the grace period ends, Pro Features lock and RedLens reverts to the Free tier. Nothing of yours is deleted or made inaccessible: connection profiles, saved queries, notebooks, history and settings remain, and your databases are untouched. Renewing restores Pro Features immediately.
10.4 Fallback licence after twelve months. If you have paid without interruption for twelve months or more, you keep a perpetual right to use the Pro Features of the last version released during your paid term, for as long as you like, even after you stop paying. What you do not keep is upgrades: newer versions require an active licence, and the fallback comes with no support and no security updates.
If you stop paying before twelve months, this does not apply and you revert to the Free tier — which itself never expires.
We do this because a subscription that leaves you with nothing after years of payment is a reason not to start paying at all. Technically it costs us nothing: the fallback is an entitlement pinned to a version.
11.1 Tier stability. Features included in a paid tier when you bought will not be moved out of that tier during your paid term. Any change to what a tier includes takes effect at your next renewal, and we will tell you before it does.
11.2 Always free. Safety features — read-only mode, the production safeguard, autocommit control, PII-safe mode — and connection management are Free permanently, and there is no cap on the number of connections in any tier.
11.3 Other changes. We may otherwise add, change, deprecate or discontinue features, and may stop distributing the Software. If we discontinue the Software entirely during a paid term, we will ask Polar to refund the unused portion of your term.
12.1 Support for active Pro and Team licences is best-effort support through https://lensql.dev/support, in English or Spanish, during the term. There is no response-time commitment and no SLA. The Free tier and the Trial come with no support obligation, though we usually answer anyway.
12.2 Updates are delivered through the Marketplace at our discretion. We do not promise any particular release cadence or that any specific feature will be maintained.
12.3 Security updates. We intend to provide security fixes for the current released version for at least 24 months from the date of this version’s release. Report vulnerabilities privately at https://github.com/redlens-io/redlens/security/advisories/new or through the support channel marked “Security”, and see SECURITY.md for what we ask you to include.
13.1 You may terminate at any time by uninstalling the Software. Termination does not by itself entitle you to a refund; see section 9.
13.2 We may terminate this Agreement:
(a) on 10 days’ written notice if you materially breach it and have not fixed the breach within that period; or
(b) immediately if you share or publish an entitlement, circumvent the licence check, or redistribute or modify the Software — in which case no refund is due.
13.3 On termination, all rights granted to you end and you must stop using the Software and remove all copies. You keep Your Content.
13.4 Survival. Sections 4, 5, 6, 8, 9, 14, 15, 16, 17, 20 and 21 survive termination.
14.1 The Software is provided “as is” and “as available”. To the maximum extent permitted by law, we disclaim all warranties, whether express, implied or statutory, including merchantability, fitness for a particular purpose, non-infringement, accuracy, and any warranty that the Software will be uninterrupted, error-free, secure, or that it will meet your requirements.
14.2 In particular, we do not warrant that generated SQL, AI output, optimisation advice, cost estimates or masking will be correct, complete or safe to run.
14.3 Some jurisdictions do not allow the exclusion of implied warranties, and some give consumers rights that cannot be excluded. To the extent an exclusion above is prohibited where you live, it does not apply to you, and nothing in this Agreement excludes or limits any right you have that cannot lawfully be excluded.
15.1 Excluded damages. To the maximum extent permitted by law, we are not liable for indirect, incidental, special, consequential, exemplary or punitive damages, nor for loss of profits, revenue, business, goodwill, or loss, corruption or destruction of data, however caused and on any theory of liability, even if we were told such damages were possible.
15.2 Cap. To the maximum extent permitted by law, our total aggregate liability arising out of or relating to the Software and this Agreement is limited to the amount you actually paid for the Software in the 12 months before the event giving rise to the claim, or USD 50 if that amount is zero.
15.3 What is never limited. Nothing in this Agreement excludes or limits our liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, for gross negligence or wilful misconduct, or for any other liability that cannot lawfully be excluded or limited — including, where applicable, liability under mandatory product-liability law.
15.4 Basis of the bargain. The pricing of the Software reflects this allocation of risk. If you need a different allocation, contact us before purchase and we will discuss a separate agreement.
If you are not a consumer, you will defend and indemnify us against third-party claims, and the resulting losses and reasonable legal costs, arising from: your use of the Software; Your Content or Your Environment; your breach of this Agreement; or your violation of any law or third-party right. We will notify you promptly of any such claim and let you control the defence, provided any settlement that admits liability on our part needs our consent.
We provide no intellectual-property indemnity under this Agreement. Enterprise customers who need one should contact us to negotiate it separately.
You represent that you are not located in, ordinarily resident in, or acting on behalf of anyone in a comprehensively sanctioned jurisdiction (currently Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk and Luhansk regions of Ukraine), and that you are not on any restricted-party list maintained by the United States, the European Union, the United Kingdom or Mexico. You will not export or re-export the Software in violation of applicable export-control or sanctions laws. These rules apply because the Software is distributed through a US-operated marketplace and sold through a US merchant of record, regardless of where you or we are located.
The Software is distributed through the Visual Studio Marketplace and may also be distributed through Open VSX or other channels. Microsoft is not a party to this Agreement, gives no warranty for the Software, and has no support or licence obligation for it: those are ours. Your use of the Marketplace itself is governed by Microsoft’s terms. We may change distribution channels.
19.1 We may update this Agreement for future versions of the Software. The current version is always published at https://lensql.dev/eula and shipped inside the extension; superseded versions stay archived at that URL with their version numbers and dates.
19.2 Changes never apply retroactively to a term you have already paid for. For paid licences, a new version takes effect at your next renewal, and we will give you notice beforehand. For the Free tier and the Trial, a new version takes effect for versions of the Software released after it; continuing to use a version released after the change means you accept it.
19.3 If you do not accept a change, your remedy is not to renew and, for the Free tier, to stop using the Software.
20.1 Assignment. You may not assign this Agreement without our consent, except that a Team licence may transfer with a merger, acquisition or sale of substantially all your assets, on written notice to us. We may assign this Agreement to a successor in interest, or to a company we form to carry on the RedLens business, on notice to you.
20.2 Entire agreement. This Agreement, plus any order form and the documents it links to, is the whole agreement about the Software and replaces any prior statement, including anything on a website, a Marketplace listing or in marketing material.
20.3 Severability. If a provision is held unenforceable, it is limited or removed to the minimum extent needed and the rest stays in force.
20.4 No waiver. Not enforcing a provision on one occasion does not waive it.
20.5 Notices. Notices to us go through the support channel in section 22, marked “Legal notice”. Notices to you go to the email address associated with your purchase, or, for Free-tier users, are given inside the Software or on the RedLens website.
20.6 Independent parties. Nothing here creates a partnership, joint venture, employment or agency relationship.
20.7 Force majeure. Neither party is liable for a delay or failure caused by events beyond its reasonable control.
20.8 Language. The English version of this Agreement is the authoritative one. If a Spanish courtesy translation is published, this English version controls, except where Mexican consumer law mandates otherwise for Mexican consumers.
20.9 UN CISG. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
21.1 This Agreement is governed by the laws of the United Mexican States, without regard to conflict-of-law rules.
21.2 The courts of Ciudad de México, Mexico have exclusive jurisdiction, and both parties waive any other venue. (Draft default — item 3 of the review list asks counsel to confirm the venue.)
21.3 Consumers. If you are a consumer, clause 21.2 does not deprive you of the protection of the mandatory provisions of the law of your country of habitual residence, or of the right to bring proceedings in the courts of that country.
21.4 Business disputes. If you are not a consumer, before filing suit the parties will try in good faith to resolve the dispute by email and, if useful, a call, for 30 days from written notice of the dispute.
21.5 Either party may bring a claim in a small-claims court with jurisdiction over the other, and either party may seek injunctive relief for infringement of intellectual property rights in any competent court.
21.6 Relationship to Polar’s terms. Polar’s buyer terms govern the payment transaction and may specify a different governing law and forum for disputes about the payment. This Agreement governs the licence. Neither displaces the other.
Publisher: Diego Borjan · independent software developer · Mexico Support: support@lensql.dev · https://lensql.dev/support Legal notices: either support channel above, marked “Legal notice” Security: https://github.com/redlens-io/redlens/security/advisories/new Privacy Policy: https://lensql.dev/privacy