What the site collects, and why.

This policy applies to the Docs Forge project website at adhit-r.github.io/docs-forge. Docs Forge is maintained by the repository owner adhit-r.

For a private data request, use a non-public contact method listed on the maintainer’s GitHub profile. Do not place an email address, phone number, or other personal information in a public GitHub issue.

GitHub Pages hosting

GitHub hosts this static website. GitHub states that it logs and stores a visitor’s IP address for security purposes when a GitHub Pages site is visited. GitHub handles that data under its own privacy statement.

Cookie and analytics preferences

PostHog currently initializes when a page loads. It uses first-party browser storage through a local-storage-and-cookie persistence mode to maintain an anonymous identifier and measure page views. Docs Forge does not display its own cookie banner.

The site also provides a headless consent bridge for a future external consent manager. Once connected, that manager can become the visitor-facing source of truth, pass analytics choices to PostHog, and store a receipt history with the purpose, choice, time, collection point, and policy version.

The PostHog integration disables autocapture and session recording. It measures page views and a successful form-submission event without sending the form’s email, phone, or message to PostHog.

Contact form

If contact collection is enabled, the form collects your email address, phone number, and message so the maintainer can respond. Consent to use those details for the response is required. Consent for occasional product updates is separate, optional, and unticked by default.

GitHub Pages cannot process a form itself. Until a secure form endpoint is named in the site configuration, the submit button remains disabled and no contact details are sent. Before enabling collection, this notice must be updated with the processor’s name, processing location, and retention terms.

No consent-manager banner is currently connected. Until one is added, you can block or clear this site’s browser storage through your browser settings.

After the external consent manager is connected, its controls can reject analytics, grant it later, or withdraw it. Withdrawing analytics stops PostHog capture and clears its local identity and persistence where the SDK is active.

For contact details already submitted, request access, correction, deletion, or withdrawal through a private contact method on the maintainer’s GitHub profile. If you withdraw product-update consent, the details may still be retained where needed to complete an active enquiry or meet applicable obligations.

PostHog’s browser storage remains on the device until it expires, you clear site data, or a connected consent manager withdraws analytics. Contact retention must be configured and disclosed with the selected form processor before collection is enabled.

Data is not sold. It may be handled by GitHub for hosting, by PostHog for page-view analytics, and by the configured contact-form processor after that service is named and enabled. These providers may process data in countries other than your own under their terms and safeguards.

The site uses HTTPS. No website or transmission method is risk-free, so submit only the information needed for your enquiry.

This notice will be updated when a contact processor, consent manager, analytics region, retention period, or material data practice changes. The effective date and policy version at the top identify the notice linked to each consent receipt.