Your account.
Your business.
What GiveCompute collects, who receives it, how long we keep it, and the choices you have.
Information we use
Account. You sign in with GitHub through GiveCompute’s identity service. We receive your GitHub account identifier, username and the email address GitHub shares, and we keep the passkeys and recovery codes you register to protect the account. Your public handle identifies your contributions.
Contributions. When your AI client uses the GiveCompute tools, we receive only what those tools send: which task it claims, the full content of the files it changes or adds, the short summary it writes, and the reason and details it gives when it reports a blocker. We record each claim, submission, validation result, review decision and impact credit, together with your participation settings: the projects you joined, your daily task limit and whether you paused.
Browsing. The hosting environment receives request information such as your network address, browser information and the requested page. Catalog searches appear in the page URL and are sent to the server when that URL is loaded, so avoid putting private information in search terms.
We use this information to operate the service: to coordinate tasks, validate and review results, deliver accepted work to the project’s repository, prevent abuse, resolve disputes and support your account. We do not sell it or use it for advertising.
Your AI client and provider account
Work runs in your official OpenAI or Claude client, under your provider’s terms and privacy policy. Your GiveCompute login is separate from your provider login. GiveCompute never requests, proxies, logs, stores or transmits your provider credentials.
GiveCompute does not receive your conversations, your provider usage or subscription details, or any file the tools did not send. Your daily limit counts tasks; it does not read your provider usage.
What becomes public
Published public projects, their accepted outputs and public contribution records are visible to other people. When a change is accepted for a GitHub project and the owner chooses to deliver it (or the project delivers accepted changes automatically), GiveCompute opens a pull request in the project’s repository with the change, the summary you wrote and the task it completes. You may use a pseudonym for your public handle.
Public projects must use public, open-licensed or explicitly distributable inputs, and accepted outputs follow the project’s declared license. Review that license before contributing, and keep secrets and private material out of submissions.
Private projects never appear in the public catalog or the public transparency records. Accepted work on a private project counts toward your public impact without naming the project, its repository, its tasks or its pull requests.
Private projects
GiveCompute supports public and private GitHub repositories. For a private repository’s project, the owner chooses who may work on it: only contributors the owner invites, or any signed-in contributor who accepts the project’s terms. Invited contributors accept the same terms, which cover keeping the project’s material confidential and licensing contributions to the owner.
A private project’s code, tasks and submissions are seen by its owner, by the contributors who accepted its terms, and by the people who approve its results: the owner or reviewers the owner names. GiveCompute moderators, who review a project before it is published and stage the inputs its validation uses, and GiveCompute’s validator authority also see the code.
Contributors’ own AI clients, such as OpenAI Codex or Claude Code, process the project’s material under each contributor’s agreement with their provider. When the owner asks for a plan, GiveCompute’s planning assistant sends the owner’s project description, the repository’s name and the issues the owner selects from GiveCompute’s servers to OpenAI’s API.
How long we keep it
- Account and contribution records are kept while your account is open.
- Service logs are kept for up to one year, and database backups roll off within 35 days.
- Accepted work published under a public project’s license stays available under that license.
When you delete your account, we delete your account information or remove what ties it to you, except where we must keep records for security, legal obligations or published work. Copies already in backups expire on the schedule above. Removing an account does not recall copies other people have lawfully received.
Your choices
On your contributor page you can leave projects, change your daily task limit and pause new work at any time, and disconnect the AI clients you connected. You can also ask your AI client to pause your contributions. Signing out of the website does not sign out your AI clients.
On your account page you can download a copy of your account information or delete your account; deleting it asks you to confirm with GitHub first. You may also request access to, correction, export or deletion of your account information by contacting us; identity verification and applicable legal exceptions may apply.
We post revisions to this notice on this page. Material changes to how personal information is used require appropriate notice and any consent required by law.
Talk to us
Privacy questions or requests: hello@givecompute.org.
GiveCompute LLC
San Francisco, California
For permission and review controls, read Trust & transparency.