Proof of Absence
Generated live, on this exact request: 2026-09-14 10:59:14 PDT
Don't take our word for it.
Our Privacy Policy and Security page describe what we store and don't. This page doesn't describe it a third time — it queries the real, running database behind forzara.ai the moment you load it, and shows you the answer. Every number and table below came from that query, just now, not from a document someone wrote once and forgot to update.
1. Is there a table for document content anywhere in this schema?
We checked, live, for any column across every table named the way a place to store a generated resume, letter, or petition would be named (document, resume_text, letter_body, petition_text, generated_content, draft_body, and close variants).
Matches found: 0. There is no such column anywhere in this schema, right now.
2. The four tables most likely to hold something, in full
Not a curated excerpt — every column, in schema order, for the four tables an account's identity and activity actually live in. milestone_submissions is the one table here with free-text columns (note, review_note) — that's the short optional note described in our Privacy Policy, not document content.
3. Every table in the schema
48 tables exist in this database, total. None is named documents, and the search in Section 1 already covers every column in every one of them, not just these four:
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
A handful of these do hold short, encrypted free text tied to an account — messages, a milestone or follow-up note, a support request, an optional private focus note. That's not a gap in this page, it's the same list our Privacy Policy (Section 2) and Security page (Section 3) already name. What none of these tables has, anywhere, is a column meant to hold something you generated with a tool.
4. Standing schema hash
A SHA-256 hash of every table name, column name, and column type in this database, computed live and shown below. Reload this page after any real schema change and the hash changes with it — there's no separate "last updated" date to trust, because there's nothing cached to go stale.
a0f00b856b7e82b3187df704fd8e7eabca4ca79b2a4b73f4abb03444cd25202f
5. If we're served with a subpoena or court order
The same standing list our Security page names: account basics (name, email, join date), organization membership, and milestone status, always. If the specific account used messaging, notes, wellness check-ins, or support requests, those are producible too, encrypted at rest but not beyond our own ability to decrypt for a valid legal process. What's never in that packet, for any account, is document content — the resume, letter, or petition text itself — because none is ever stored to begin with.
Illustrative example, not a real account:
| Field | Sample value |
|---|---|
| Account basics | Jane R., jane@example.com, joined 2026-03-14 |
| Organization membership | Second Chance Reentry Services — participant |
| Milestone status | 7 of 18 milestones approved |
| Document content | — none exists to produce — |
Have a question about any number on this page, or found something that doesn't match what we say elsewhere? support@forzara.ai.