How Catoosa Energy collects, stores, and uses personal data submitted through this site — including the /investors email‑capture form and the upcoming /target‑buyers contact form.
This page explains how Catoosa Energy handles personal information that visitors submit through this site. It applies to two surfaces in particular: the /investors email‑capture form our investors use to express interest in the capital raise, and the upcoming /target‑buyers contact form that outbound buyer-side inquiries will route through once it ships.
From the /investors form, we collect the four fields the form exposes. The four columns written to our database are:
Each free‑text field is capped at 255 characters at the server boundary so the form cannot be used to deposit large payloads. Every row is tagged with a source value of 'investors_page' so submissions through this surface are easy to filter later.
Submissions are written to a Postgres table named investor_leads on the managed Postgres instance that backs this site. The table columns are id, email, name, company, message, source, and created_at. email is required; the remaining text columns are nullable so a submitter who leaves the optional fields blank still produces a clean row, and created_at is set automatically on insert.
The table is hosted on the same managed Postgres service that the rest of this site uses, and is created and migrated alongside the rest of the schema using idempotent migrations so a fresh environment reproduces the same shape on first boot.
The lead is used to evaluate the raise: the Catoosa team reads inbound rows, triages outreach against the active capital plan, and replies directly to the email address the submitter provided. We do not enrich the data with third‑party lookups, and we do not sell or share it.
On a successful insert, the server also sends a notification through Polsia's authenticated email proxy at https://polsia.com/api/proxy/email/send. The notification is dispatched server‑side and is addressed to the company inbox resolved from server configuration. Subject and body summarize the new row so the team can react without re‑querying the database.
The notification call is best‑effort: if the proxy call fails (network error, expired key, transient outage), the failure is logged but does not roll back the database row. The stored submission remains the source of truth, and the team still catches up via direct database reads on their next session.
We retain submissions for as long as we are evaluating the raise, the immediate post‑first‑cargo financing window, and any follow‑up relationship that grows out of a submission. Access to the investor_leads table is limited to the Catoosa founders and any delegated operators they explicitly grant read access to — no third‑party processors read the raw rows.
You can request deletion of your submission at any time by emailing the address listed in the site footer. We confirm deletion by replying from the same inbox within a few business days.
This site uses one anonymous Polsia analytics beacon pixel that writes a single randomly‑generated UUID (polsia_vid) to your browser's localStorage and sends the resulting identifier back to the analytics endpoint on each page view. The pixel itself does not include any form content — email, name, company, or message fields are never attached to the beacon payload. There are no advertising pixels, no third‑party retargeting scripts, and no cookies set by this site beyond the analytics UUID.
If we make a material change to how we handle submissions — a new surface shipping, a change to the database schema, or a change to the notification flow — we will update this page and refresh the "Last updated" date at the bottom.
Last updated: 2026‑08‑05