Security

Last updated: June 15, 2026

PlugFile handles regulated well-plugging data for Texas oil & gas operators. This page summarizes our security posture in plain English so you can evaluate us during vendor diligence. We make only claims that are true of the current system.

Per-account data isolation (row-level security)

Every saved filing is stored in a Supabase PostgreSQL database with row-level security (RLS) enabled on every table. Each database row is tagged with the authenticated user's ID, and Postgres enforces read and write access at the row level — not just at the application layer. A signed-in user can only ever SELECT, INSERT, UPDATE, or DELETE their own filings. The application frontend uses the public anon key plus the user's session token; the service-role key is never exposed to the browser or returned in any HTTP response, and is used only by trusted server-side processes. Filing shares (operator → plugging company) are scoped to a verified email address claim and restricted so a collaborator cannot change ownership.

Data residency and third parties

All filing data is stored in US-based infrastructure: our Supabase PostgreSQL database is provisioned in a US region, and the application runs on Render in the United States (US-East). The only third party that ever receives filing content is Google Cloud Vision — a US-based company — and only in one narrowly scoped case: when the GAU letter you upload is a scanned image rather than a text PDF, that letter is sent for optical character recognition so the printed text can be read. Nothing else you type or upload leaves our infrastructure. We do not sell filing data, and we do not share it with any other third party for their own use.

No AI writes, calculates, or decides anything on your filing

There is no language model anywhere in the filing path. Every plug depth, plug count and cement volume is computed by deterministic code implementing 16 TAC §3.14: the same inputs always produce the same output, and every figure can be checked by hand against the rule. Your Section IX narrative is assembled from your own words by pattern matching — it is not generated, and nothing is invented to fill a gap. Where a required fact is missing, PlugFile says so rather than writing something plausible.

The one machine-reading step is optical character recognition on a scanned GAU letter. OCR transcribes the characters printed on the page; it does not infer, summarise, or supply anything that is not there. Because a misread digit would matter, a depth obtained this way is always shown to you for confirmation against the letter before it can be used — together with the recognition confidence, so a doubtful digit is visible rather than silent.

Voice dictation

The microphone button uses your browser's own built-in speech recognition. PlugFile never receives, transmits, or stores your audio — only the text your browser produces, which you can edit before it is used. Note that Chrome and Edge implement that feature by sending audio to Google's speech service; this is your browser's behaviour rather than ours. If you would prefer not to use it, type the narrative instead — the result is identical.

Prep, never file

PlugFile prepares a portal-ready or print-ready filing package that you review and submit yourself through the Texas RRC Online System. PlugFile is a preparation tool only — you remain in full control of every submission. The browser extension fills the portal for your review; it never clicks the submit button. Nothing is sent to the RRC without your deliberate action.

TLS and HSTS in transit

All traffic between your browser and PlugFile is encrypted with TLS. The Strict-Transport-Security header (max-age=15552000; includeSubDomains) is served on every response, preventing downgrade attacks. Certificate verification is enforced on all server-side fetches from the Texas RRC — it is never disabled.

Other controls

• Content-Security-Policy: script-src 'self' — no inline scripts, no external script origins beyond the page's own domain.
• Upload limits: document uploads are capped at 10 MB per file.
• Rate limits: per-IP rate limits are applied to the narrative, OCR and lookup endpoints to prevent abuse.
• No CDN scripts: no third-party JavaScript CDN sources are loaded; all scripts are served from our own domain.

Vulnerability disclosure

We follow responsible disclosure. If you discover a security issue, please report it to [email protected] before public disclosure. Our machine-readable disclosure policy is at /.well-known/security.txt (RFC 9116).

We aim to acknowledge reports within two business days and to provide a resolution timeline within five business days. We ask that you give us reasonable time to address the issue before public disclosure and that you not access or modify data belonging to other users during your research.

Contact

Security issues: [email protected]
General: PlugFile LLC · 8055 FM 359 RD S, STE 322, Fulshear, TX 77441 · [email protected]