Orchknowledge Privacy Policy
Last updated: October 15, 2026
1. Application purpose
Orchknowledge is a privately operated project-knowledge management application.
It manages authorized project material, maintains local operational evidence, and publishes selected documents to Google Drive.
2. Information processed
Orchknowledge processes authorized project documents, publication identifiers, publication metadata, and related operational records.
The application also processes Google OAuth credentials required for its authorized Google Drive operations.
3. Google authorization
Orchknowledge requests the Google Drive drive.file permission.
This permission supports access to Google Drive files used with the application, rather than unrestricted access to all files in a Google account.
OAuth refresh credentials are stored locally on an operator-controlled computer using restricted filesystem permissions.
4. Google Drive data use
Orchknowledge uploads selected, authorized project documents to Google Drive.
It may update designated Drive publications and retrieve their contents to verify publication integrity.
Publication operations are managed through explicit authorization and verification procedures.
5. Google NotebookLM
Selected Google Drive publications may be manually added to Google NotebookLM for source-grounded analysis and synthesis.
Orchknowledge maintains local records identifying these manually verified routing operations.
NotebookLM output does not automatically become authoritative project knowledge.
6. Other service providers
Google Drive stores selected published documents. Google NotebookLM may process material manually supplied for analysis.
Cloudflare provides domain, DNS, and public static website-hosting services.
Cloudflare may process technical website-access and security information in providing those services.
Privacy inquiries are received at privacy@orchknowledge.com and processed through Zoho Mail, the email-service provider.
These static website pages do not include application-operated submission forms or analytics scripts.
7. Retention
Orchknowledge retains local project records, publication metadata, and operational evidence until their removal is deliberately reviewed and authorized.
There is no fixed automatic expiration period for durable project records.
OAuth credentials and historical credential records are managed separately and may remain locally stored until explicitly reviewed and removed.
Information published to Google Drive or supplied to NotebookLM is subject to separate management through those services and their applicable retention practices.
8. Revocation and deletion
Google account authorization may be revoked through Google's account security settings.
Revoking authorization does not automatically delete local project records, stored credentials, or previously published documents.
Removal of local records, Google Drive publications, and NotebookLM sources requires separate review and appropriate actions.
Requests concerning personal information may be directed to the application operator using the contact information below.
9. Security
Orchknowledge uses limited Google Drive authorization and restrictive local credential-file permissions.
Publication and routing activities are recorded through separate verification procedures.
10. Contact
Application operator contact: privacy@orchknowledge.com