PONSPrivacy & data
What Forkd processes, why it is used, and the limits of pseudonymity.
Information processed
Forkd stores the site-scoped account identifier associated with a request or vote, the submitted repository, project description, detected license, pinned revision, build and accounting records, and activity timestamps. Acceptance of the current terms is recorded with request activity.
A connected wallet address is displayed in the current browser session. The site does not ask for a seed phrase or private key. Hosting and service providers may process network identifiers and operational logs under their own policies.
Why it is used
Information is used to save and display requests, enforce ownership and limits, inspect source, operate builds, reconcile budgets, verify transactions and investigate service problems. Do not submit private source, personal information or confidential business data in a public project specification.
Service providers and disclosure
Source checks send the repository identifier to GitHub. Configured model and sandbox providers receive the selected public source material and build instructions needed for a job. Hosting services provide storage and account access. Provider processing may occur in other countries.
Source candidates, requests and project activity are visible to people permitted to access the site. If public access is enabled later, publish a clear notice about the expanded audience. Runner artifact URLs can be accessed by anyone possessing the URL; only public source should be included.
Blockchain data and pseudonymity
Blockchain transactions and addresses are public and may be linked to other records. Pseudonymous use is not a guarantee of anonymity. Forkd cannot erase chain history or prevent independent indexing. Do not include personal identifiers in on-chain metadata.
Retention and requests
Operational records are retained while necessary to deliver the service, reconcile costs, investigate issues or meet legal obligations. Browser memory holds temporary form and wallet state. The documentation sidebar may store its display preference in a local cookie.
A verified operator privacy contact and defined retention process are required before public operation. Requests for access or deletion must be authenticated and remain subject to legal, accounting and blockchain limitations. No claim is made that a request can remove data from independent third parties.