← Back to DevLynx AI

Privacy Policy

Last updated: March 2026

Short version: We don't sell your data, track your browsing, or store your API key. The extension runs in your browser. License verification is the only data that touches our server.

Who we are

DevLynx AI is a Chrome browser extension that provides AI-powered developer tools. This policy explains what data is collected when you use the extension and our website.

What we do NOT collect

Your OpenAI API key (BYOK)

If you choose to use your own OpenAI API key (Bring Your Own Key), that key is stored exclusively in your browser using the Chrome Storage API. It is sent directly from your browser to OpenAI's servers when you use AI features. It never passes through the DevLynx server.

What our server does receive

The DevLynx feed server (hosted on Vercel) receives the following when you use server-side features:

Device ID

A random device identifier is generated in your browser the first time you use DevLynx AI. This ID is used only to track your trial usage count and enforce license device limits. It is not linked to your identity, email address, or any other personal information.

License and payments

Payments are processed by Gumroad. When you purchase DevLynx Pro, Gumroad handles your payment information according to their own privacy policy. We receive only your license key and optionally your email address from Gumroad for support purposes.

Third-party services

Data retention

Chrome Web Store permissions

DevLynx AI requests the following permissions and uses them solely for the stated purpose:

Your rights

You can delete all locally stored data at any time by going to Chrome Settings → Extensions → DevLynx AI → Clear data, or by uninstalling the extension. For server-side data (trial count, license activation), contact us and we will delete it within 30 days.

Contact

Questions about this privacy policy or requests to delete your data:
support@devlynx.dev

Changes to this policy

If we make material changes to this policy, we will update the date at the top of this page. Continued use of the extension after changes constitutes acceptance of the updated policy.