Privgate privacy policy

Effective date: November 16, 2026

Operator and purpose

Privgate is operated by Brian Arnett for personal email and document processing. It accesses authorized data to classify documents, prepare summaries, apply privacy checks, and diagnose processing failures.

Information accessed

With Google account authorization, Privgate can read Gmail message headers, subjects, bodies, attachments, labels, and message identifiers. It also processes configured local documents when available. OAuth credentials allow the application to access the authorized account without storing its Google password.

Google permissions

Privgate requests the Gmail modify permission. That permission is broader than the actions implemented by the current application. The current review-only configuration reads messages without changing them. A separately enabled live configuration can create and add a “Private” label. The current integration does not implement sending, drafting, archiving, trashing, or deleting Gmail messages.

Processing and sharing

Email is retrieved from Google and processed on the operator’s computer. Classification and summarization use a local Ollama model; no cloud AI service is configured in the current pipeline. Current summary delivery and external alert delivery are disabled. The public informational website is separate from the email-processing system.

Local storage and retention

Temporary processing files, summaries, source references, processing status, and diagnostic records may be stored locally. Raw processing files are removed after processing, but this is not a guarantee of secure erasure. Configured cleanup targets are 24 hours for stale processing files, 30 days for review, quarantine, and log files, and 90 days for output files. These are cleanup settings rather than guaranteed maximum retention periods. Database records, backups, continuously updated logs, or failed cleanup jobs may retain information longer.

Control and deletion

Google access can be revoked through the Google account’s third-party connections settings. Revocation stops future authorized access but does not automatically delete previously stored local information. Contact the operator to request review or deletion of local records.

Contact

[email protected]