Proofpage privacy
Updated October 18, 2026 · Maintained by Utsav Das
Your workspace
Proofpage stores your library, revisions, reviewed context and settings on your computer. Collection contacts the sources you choose. Optional model requests send selected content to the provider you configure. Optional timestamp anchoring sends a digest. Update checks contact GitHub. The homepage has no analytics or signup form.
Google Docs connection
The optional connector requests read-only Google Docs access. Google grants access to account documents; Proofpage fetches only document IDs you explicitly select after confirming owner permission to retain local snapshots for personal context. It reads body and table text across tabs and stores the returned API document and extracted text locally. It does not fetch your whole Drive, change Docs, read Gmail, or contact your customers.
OAuth authorization and refresh tokens stay in your operating system credential vault, separate from workspace database backups. The connector has no plaintext-token fallback. Official desktop builds may include native OAuth app configuration so you do not need developer setup. That configuration identifies the app; it contains no user authorization. Personal access and refresh tokens are never bundled or committed to the source repository. Your Google documents are not sent to Proofpage servers. Any sharing through an exported context pack, configured model provider or assistant connection is a separate action you control.
Use of Google data
Google API snapshots are limited to personal context in this release and are rejected by the training-example workflow. Proofpage does not sell Google data, use it for advertising or creditworthiness, or use it to train shared or general-purpose AI models. Proofpage's use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Disconnect, retain and remove
Disconnect in Business context to remove local Google authorization and pause document schedules. You can also revoke Proofpage in Google Account connections. Disconnecting keeps previously imported evidence. You control its retention. To remove the entire local workspace, quit Proofpage and delete the Proofpage/data folder in your user folder, plus any backups and exported packs you wish to remove. This permanently removes that local library, including its receipt-signing key. Copies already shared with other services must be removed there separately.
Browser companion
The optional companion has a separate privacy policy. It transfers reviewed content to your paired local app.
Questions
Contact the maintainer at utsavd500@gmail.com. For software issues, use the GitHub issue tracker; never post private documents or tokens there.