Security
Last updated: 2026-11-19
This page is for anyone who has found a security problem in Drudgle, and for customers who want to know how the service is built and who handles their data. Drudgle is run by one person, Abel Mohler, trading as Drudgle; where this page says we, it means him. How we handle personal data in detail is in the Privacy Policy.
1. Reporting a vulnerability
Email security@drudgle.com. The same address is published in /.well-known/security.txt. Please include what you found, the URL or API route involved, the steps to reproduce it, and what you think an attacker could do with it. Send only as much of anyone's data as you need to show the problem.
What we promise.
- We acknowledge your report within 5 business days.
- We send a first assessment, with the severity we gave it, within 10 business days.
- We aim to fix confirmed problems within 7 days for critical issues, 30 days for high, and 90 days for medium and low, and we tell you when the fix is live.
- We credit you by name when the fix is announced, if you want that. There is no bug bounty: we do not pay for reports.
In scope.
- drudgle.com and the app at drudgle.com/app.
- The API at api.drudgle.com, including the MCP endpoint at api.drudgle.com/mcp.
- How Drudgle itself handles the projects it generates for you: their storage, their isolation from other customers' projects, and the evolve and deploy flows that run on our servers.
Out of scope.
- Denial-of-service attacks, load or volume testing, and anything that degrades the service for other people.
- Social engineering, phishing, and physical attacks on people or premises.
- The services of our providers (section 3), such as Google sign-in, Stripe Checkout, Cloudflare or Vercel. Report those to the provider.
- The code of a project you generated and then deployed to your own Vercel account, except where the problem comes from Drudgle's systems.
- Reports from automated scanners with no demonstrated impact, missing best-practice headers with no attack that uses them, and clickjacking on pages with no sensitive action.
Rules for testing.
- Use only your own account, and only projects you created.
- Do not access, change or delete anyone else's data. If you reach it by accident, stop, tell us, and keep none of it.
- Do not run generation or evolve in volumes beyond what your own credits pay for.
- Give us a reasonable time to fix the problem before you disclose it. We will agree a date with you, normally when the fix is live or 90 days after your report, whichever is sooner.
Safe harbor. If you make a good-faith effort to follow this policy, we consider your research authorised. We will not pursue or support legal action against you for it, including under computer-misuse or anti-circumvention laws, and if a third party takes action against you for research that followed this policy, we will make it known that you acted with our authorisation. We cannot authorise testing of systems we do not own, which includes our providers.
2. How Drudgle is built
- The website and app shell (drudgle.com) are static files served by Cloudflare Pages.
- The API and everything behind it run on a single Oracle Cloud (OCI) virtual machine in Ashburn, Virginia, United States: the API, the task workers, the Postgres database, the message broker, the vector search index, the project store (one git repository per project), and our own logs and metrics.
- Traffic. Every request to api.drudgle.com goes through Cloudflare. Your browser's connection to Cloudflare uses TLS, and Cloudflare's connection to our server uses TLS too, checked against an origin certificate ("Full (strict)" mode). Our server presents no certificate that a browser would trust, so it is reachable only through Cloudflare.
- Where your data is stored. Your account, projects, files and the search index live on the server's disk. Oracle encrypts its block and boot volumes at rest by default. Backups go to OCI as full-disk backups of the server and as nightly copies to a private OCI Object Storage bucket. The server can write copies to that bucket but cannot read or delete them.
- Language models. Planning, generation and search embeddings use OpenAI. The evolve flow, which writes code into your project, uses MiniMax. The MiniMax key is held only on a separate proxy server on a private network: each evolve run gets a short-lived token with its own spending limit and deadline, and never sees the key itself.
- Sign-in and keys. You sign in with Google, so Drudgle stores no password for you. API keys are stored as a hash, never in full. A Vercel token you connect is stored encrypted, and you can disconnect it at any time.
- Operator access. The server's SSH and cluster-management ports are closed to the internet. The operator reaches them only through a private VPN (WireGuard).
- Monitoring. Alerts reach the operator by email from our own monitoring, and an independent OCI health check alerts if the API stops answering.
3. Sub-processors
These providers process customer data on our behalf. The Privacy Policy's list of recipients gives each one's exact role and links its privacy policy; the two lists are kept in step.
| Provider | What they do for us | Customer data they handle | Where |
|---|---|---|---|
| Oracle Cloud (Oracle America, Inc.) | Runs the server: API, database, task workers, project storage; stores backups; sends operator alert email; checks the API's health | everything Drudgle stores | United States (Ashburn, Virginia) |
| Cloudflare (Cloudflare, Inc.) | Serves drudgle.com, proxies every request to the API, DNS, and forwards mail sent to our addresses | web requests, including your IP address; email you send us | United States and Cloudflare's global network |
| Google (Google LLC) | Sign in with Google; Google Analytics only after you consent | the fact you signed in; analytics after consent | United States |
| OpenAI (OpenAI, L.L.C.) | Language models for planning and generation, and search embeddings | your business vision and project content, without your email or ids | United States |
| MiniMax (international API) | Language models that implement and evolve project code | your business vision, project content and your evolve instructions, without your email or ids | outside the United States and the EU |
| Stripe (Stripe, Inc.) | Payments and sales tax for credit purchases | your email and account id; Stripe collects card and billing details itself | United States |
| Vercel (Vercel Inc.) | Hosts a project you choose to deploy, only if you connect your own Vercel account | the project files you deploy | United States |
Services that hold no customer data. GitHub stores Drudgle's own source code and the container images the server runs. When an evolve run builds your project, it downloads open-source packages from public registries such as npm and PyPI. When Drudgle generates ideas, it may read public news feeds. None of these receives your data.
4. Data retention and deletion
| Data | How long we keep it |
|---|---|
| Your account, and the projects, files and messages you create | Until you delete them or your account. |
| Request and application logs, which can include the text you send the service | 14 days. |
| Service metrics, not tied to you | 30 days. |
| The credit ledger (grants, purchases, charges) | 7 years, for tax and accounting records. After you delete your account it keeps only an internal id, never your email. |
| Backups | Database copies on the server: 14 days. Nightly off-server copies: 14 days, and weekly copies 13 weeks. Full-disk backups of the server: daily ones 7 days, weekly ones 4 weeks, monthly ones 12 months, and yearly ones 5 years. |
Deleting your account. With your token, DELETE /api/v1/auth/me deletes your account at once: its sign-in records, API keys, testbeds, projects' business plans, tickets and evolve runs, chats, feedback, connected accounts and cookie choices, in one step. A background job then removes your projects' files, their git repositories and their search-index entries. You can also email privacy@drudgle.com from the address on your account, and we delete it within 30 days.
Deleting a project. DELETE /api/v1/projects/{id} deletes the project and its business plan, tickets, evolve runs, tasks and deployment records at once. A background job then removes its files, repository and search-index entries. It is refused while an evolve run is still working on the project.
What deletion does not reach. The credit ledger is kept as the table says. Deleted data stays in a backup until that backup expires; backups are used only to recover the service after a failure. A task that was already running on a project when you deleted it can write to it afterwards; we remove such leftovers when we see them.
The full rules, including feedback and cookie choices, are in the Privacy Policy's sections on retention and your rights.
5. How we run it
- Accounts. Every operator account that controls the service (Oracle Cloud, Cloudflare, GitHub, Google) requires multi-factor authentication.
- Secrets. Production keys live in the server's secret store and in the operator's password manager, never in source control. We rotate a key whenever it may have been exposed.
- Changes. Every change to the code reaches production through a pull request; nothing is committed straight to the main branch. The server runs container images named by the exact commit they were built from.
- Vulnerabilities. Dependabot checks our dependencies weekly and opens fixes for known vulnerabilities, and GitHub secret scanning blocks credentials from being pushed to the repository.
- Backups run nightly, and restoring from them has been tested.
- Incidents. We keep a written incident-response plan. If an incident affects your data, we tell you by email without undue delay, and we notify the relevant authority within 72 hours where the law requires it.
- Review. This page and the policies behind it are reviewed at least once a year, and whenever the architecture changes.
6. Contact
Security reports: security@drudgle.com. Privacy requests: privacy@drudgle.com. Abel Mohler, trading as Drudgle, North Carolina, United States.