Legal
Privacy Policy
OutcomeEdge is an early-stage bookkeeping service. This page explains what we collect when you fill out our /intake form, how we use it, how long we keep it, and who else might see it.
The only personal information we collect today comes from the /intake form: your name, email address, company name, current bookkeeping setup, monthly revenue range, and an optional free-text description of your biggest bookkeeping headache.
We use first-party form fields and our own backend to receive those answers — no third-party analytics or advertising tags fire on the intake submission.
Every submission lands on our internal intake triage queue. The form posts to /api/intake, which stores the row in our database and sends a notification to the operator — that notification goes through our hosted email proxy at POLSIA_EMAIL_PROXY_URL.
We use what you wrote to route your request to the right delivery team (bookkeeping, legal intake, etc.) and to follow up with you within 24 hours. We don't sell, rent, or trade your information with anyone outside the delivery flow.
We're a small operation and we hold onto intake submissions only until triage and follow-up are complete. Once a request has been routed and a conversation is underway (or it's clear the conversation isn't going to happen), the row is removed from our intake queue.
We don't keep backups of intake rows outside the database that backs the running app. If you want a submission deleted sooner, just email us — we'll remove it on the spot.
Today, three systems outside our app see intake data — the database that stores the row, the email proxy that delivers the operator notification, and an optional AI summarizer that's only invoked for future triage workflows:
- Hosting / database (Postgres). The intake row is persisted to a managed Postgres database that ships with the deployed app. No row is exported to a separate warehouse or BI tool.
- Email proxy. The triage notification is sent through the Polsia email module, which routes through
POLSIA_EMAIL_PROXY_URL. Attachments, cc/bcc, and a custom From aren't supported by this proxy. - AI triage summarizer (optional). If we turn on automated triage summaries for inbound requests, the request text will be sent through the Polsia AI module proxy at
POLSIA_AI_BASE_URL. When it's off — which is the default today — no AI subprocessor sees your data.
Questions about this policy, or a request to delete an intake row? Reach the operator at josh@getoutcomeedge.com.
We respond to deletion and access requests as soon as we can — usually within a few business days.