How FLAKPROOF handles your data

Your file and slide text

PDF files, filenames and extracted slide text are held in browser memory while you use the page. We do not write new deck content to browser storage. Selecting a PDF on the homepage checks that it is readable; after navigation, sign-in, checkout, a refresh or a crash, choose it again. Old checkout drafts from the previous version are removed from that tab’s session storage when the upload widget is opened. Your purchase remains linked to your signed-in identity.

The PDF is processed locally in your browser. When a signed-in user requests analysis, the extracted text, filename, selected audience, and meeting context are sent to FLAKPROOF’s server. We send the text and context needed for the task through OpenRouter to the configured AI provider. Rehearsal also sends your answers and report context; revision planning sends your report and available slide text.

Storage and providers

New PDFs, extracted text, generated reports, approved audience context, research results, blueprints and rehearsal feedback are not saved to our database. They are processed in memory for the requested task and remain in the active page until you leave. Download any results you want to keep; those downloads are files you control, not cloud backups. We retain only account-linked purchase and session metadata, usage counts, timestamps and verification hashes. These records are still user-related data, not anonymous records. Sessions have 30 days of included use from the first successful analysis. Re-upload the same deck and re-enter the same meeting and approved audience to regenerate a lost report. Up to three successful recovery regenerations per analysis are available without another purchase; outputs may differ. Contact support if recovery is blocked. Inference requests require zero-retention provider routes and ask providers to deny data collection. Hosting, authentication, and inference services may process operational metadata under their own policies.

Exception for existing saved content: reports and associated results saved before this change are preserved for export, including after their original access period. You can export an existing report from My sessions, then explicitly delete its saved history when you are ready. Exporting alone does not delete it. Deleting a deck’s history ends its remaining included use. We do not automatically erase these legacy records while you are preparing your export.

Audience research

Optional audience research sends the name, company and profile links you enter through OpenRouter to Exa web search and our configured AI provider. Search services process public lookup queries under their own policies; the inference zero-retention requirement does not promise zero retention by search services. Deck text and your private meeting notes are not sent to web search. Audience research does not connect to your LinkedIn or X account or access private profiles. Optional LinkedIn sign-in is a separate identity-only flow.

You must confirm each person and briefing before use. Approved professional facts and your notes are sent with analysis, rehearsal and revision requests. New room drafts and research results remain in memory only; they are not saved to your account. Legacy saved content is the exception described above. Avoid sensitive personal information and use only material you have permission to share. Public sources and identity suggestions can be wrong or outdated; inferred questions are not the person’s actual views.

Sign-in

Account access uses Clerk and your selected sign-in provider, or the original ChatGPT login. Clerk and the provider process and retain the identity, session and security information needed to authenticate you under their own policies. Social sign-in requests basic identity information, not access to your inbox, contacts or private professional content. Flakproof retains stable identity references and, only when you explicitly connect both verified logins, the link to your original purchase account. We do not link accounts by matching email addresses alone. We do not store provider passwords or OAuth access tokens in our database. Pilot-only features check an invited-user list; purchases and saved reports belong to the authenticated user. The public sample report uses fictional company data and requires no deck upload.

Payments

Lemon Squeezy handles checkout. Any checkout marked test mode makes no real charge. FLAKPROOF stores an authenticated user ID, checkout reference and URL, provider order ID, credit state, timestamps, accepted terms version, usage records, and hashes used to recognize analysis retries and revised versions of a deck. Order and usage records remain after deleting report content. Card details are handled by Lemon Squeezy and its payment providers, not FLAKPROOF. Never use real card details in test checkout. See our purchase terms.

Sensitive information

Only upload information you have permission to share with these services. Remove unnecessary personal data and sensitive details before requesting analysis. AI feedback may be incomplete or incorrect.