Last updated: 24 August 2026

DevCache is a browser extension and a companion server. This policy describes what the extension and the hosted service at https://devcache.onrender.com collect, why, and where it goes.

If you run your own server, that copy of DevCache is under your control. This policy covers the public add-on talking to the hosted API.


DevCache is operated by the project maintainer. For questions, open an issue on the project repository or email the address listed on the add-on listing.



When you sign in with GitHub we receive, and store:

• GitHub user id
• username
• email, if GitHub provides it
• avatar URL
• a GitHub access token so we can commit solutions to the repository you choose

We also set a session cookie on the DevCache site so the extension can stay signed in.


After a submission is Accepted, the extension may send:

• problem title and URL
• language
• your submitted code
• related metadata needed to write a README and commit to GitHub

This happens only on LeetCode pages while the add-on is installed and you are signed in.


We do not summarize every page you visit.

When you click Summarize this page, the extension sends:

• page URL
• page title
• enough of the page text to write a summary

Notes you type, generated interview questions, job status, and related summaries are stored on the server so they can show up in the popup.


Repository, branch, folder, AI provider, model, and (if you enter one) an API key are stored so summaries and writeups can run. API keys are used to call the provider you selected. They are not used for advertising.

• We do not sell your data.
• We do not use it for ads.
• We do not summarize browsing in the background.
• We do not collect payment or health information.

• Sign you in and keep a session
• Save Accepted solutions and push them to GitHub
• Save topics, notes, and interview questions you asked for
• Call the AI provider you configured so writeups and summaries can be generated

| Party | Why |
| --- | --- |
| GitHub | Sign-in (OAuth) and commits to your repo |
| Your AI provider (for example Groq, OpenAI, Gemini, or Grok) | Code and page text needed to generate writeups, summaries, and questions |
| Hosting (currently Render) and the database behind the API | Store accounts and saved content |

LeetCode is not a DevCache partner. The add-on reads the page in your browser and sends Accepted solutions to the DevCache server.


The hosted site uses a session cookie after GitHub sign-in.

The extension uses browser storage to remember which solutions or pages were already sent, and to show job status. That data stays in your browser unless you clear site data or remove the add-on.


Account, solutions, topics, notes, and settings stay until you delete them or ask us to delete your account. Session cookies last until they expire or you sign out.

• Do not sign in: the add-on will not send solutions or pages to the server.
• Do not click Summarize this page: that URL and page text are not sent.
• Change or remove your AI key in Settings.
• Remove the add-on to stop LeetCode capture.
• Ask us to delete your account and stored content.

DevCache is not directed at children under 13.


If this policy changes in a material way, we will update the date above and the copy linked from the add-on listing.


For Firefox’s built-in consent prompt, DevCache declares:

• browsing activity (URLs of pages and problems you save)
• website content (page text and LeetCode code you choose to save)
• authentication information (GitHub sign-in)