Privacy Policy

The operator of ReuseForge decides why and how personal data is processed, and is the "controller" under laws such as the EU and UK GDPR. The operator is the maintainer of the open-source project at github.com/Longfordjames/Claude-1. A legal entity and postal address will be added here before paid features launch. How to reach us is in section 14.

This policy covers reuseforge.com, the web app, the API and the MCP endpoint. It does not cover sites we link to, GitHub, or a self-hosted ReuseForge node run by someone else. The operator of such a node is responsible for it.

The table lists each kind of data, why we need it and where it comes from. The legal bases we rely on are in section 7. "You" means data you give us. "Automatic" means data created when you use the Service.

We do not ask for your real name, phone number, government ID or date of birth. We do not collect payment card data, because the Service does not take cards. We do not run KYC checks in the beta; we may have to add them before real payments start, and we will update this policy then.

The planner. The planner on the home page and the demo run entirely in your browser; the goal and budget you type there are not sent to us. The planner in the app (/app/plan) also computes in your browser, but to find candidate listings it sends our search API the capability names and up to two matched keywords per need, not your whole goal. It remembers your last goal and budget in your browser, and puts them in the page address so you can share a plan. When you load or share such an address, the address, goal text included, reaches our servers and Cloudflare's request logs like any other web address. Do not put secrets in a goal. If we add a planner that runs on our servers, we will say so where you type and update this policy.

Email. We use your email address only for messages about your account and organisations: email verification, password reset, security notices (for example when your password, email address or two-factor setting changes, or your account is deleted) and organisation invitations. In-app notifications are not sent by email. We send no marketing email.

Email delivery is not switched on yet. The Service has no email sending configured, so today it sends no email at all. Verification and password-reset links cannot be delivered, a forgotten password cannot be reset by email, and a changed email address stays unverified. Accounts created with GitHub arrive with GitHub's verified email already marked verified. We will update this policy when email is switched on.

• We show no advertising and we do not sell or rent your personal data.
• We do not use third-party advertising, social or tracking scripts, tracking pixels or third-party fonts. Scripts, styles and fonts come from our own domain. The one outside script our security policy allows is Cloudflare's Web Analytics (section 4.3).
• We do not build advertising profiles and we do not make decisions about you by solely automated means that have legal or similarly significant effects.
• We do not use your private listings or files to train AI models.

The Service sets at most two cookies. Both are first party and strictly necessary, and they are set only when you sign in, sign up or start a GitHub sign-in. They do not need consent under the ePrivacy rules, so there is no cookie banner. If you only read the website, no cookie is set.

Local storage stays in your browser. The one value that also reaches us is your theme, and only if you are signed in and choose it in Settings. Local storage is written only when you use the feature that needs it. We set no analytics or advertising cookies and no third-party cookies. Cloudflare, our host, may set its own security cookies in some cases, for example when it challenges a suspicious request; those are not ours.

Hosting analytics. We add no analytics code to our pages, but Cloudflare can inject its Web Analytics script into pages it serves, and our security policy lets that script and its endpoint load. When it is switched on, Cloudflare counts page views and performance for us (page address, referrer, browser type, country and load timings). Cloudflare says it does not use cookies or local storage for this and does not track people across sites. We use it only for aggregate numbers. We use no other analytics. If this changes, we will list the change here.

These are public by design: your handle, display name, bio, avatar, website, location and profile links; your public listings, versions and files; your reviews, discussions and comments, shown with your handle; who you follow and who follows you; the organisations you belong to; your public collections; and star counts on listings. Actions such as publishing, starring or reviewing a public listing can appear in your public activity feed. Do not put anything in these that you want kept private. Unlisted listings are not shown in lists or search, but anyone with the link can open them. Private listings are visible only to you, your organisation's members and our administrators.

Append-only records in the open-source protocol. In the ReuseForge protocol, nodes record listings, orders, deliveries and votes as signed events in a hash-linked, append-only log and copy that log to each other. Events are signed with a public key, not your name, but your handle or key may be linked to them. If you sign events with the ReuseForge command-line tool or run a node, an event that has been copied to another node cannot be recalled by anyone, including us. The hosted service at reuseforge.com keeps accounts, listings, reviews and discussions in its own database today and does not publish them to that log. What happens to that data when you delete it is described in section 8.2.

Blockchains. A payment on USDC, USDT or Bitcoin is a public transaction on a public ledger that nobody can delete. Addresses and amounts are visible to anyone. Do not use an address that you have linked to your identity if you want the payment to be unlinked from you. In test mode no such transaction is made.

Staff access. ReuseForge administrators can see account details, including email addresses, status and last sign-in time; every listing in any state, including private and removed ones; reports; and the audit log with IP addresses and browser strings. They use this to handle reports, abuse and security problems. Nobody becomes an administrator by signing up. Administrator actions are written to the audit log, and administrator tools need a sign-in from the last 12 hours.

We use a small number of service providers (processors) that handle data on our behalf, and we deal with a few other parties as part of the product.

We do not share your data with data brokers. If the project is transferred to another operator, your data may move with it, and we will tell you before it does if this changes how your data is handled.

Where the GDPR or UK GDPR applies, we rely on these legal bases:

• Contract (Art. 6(1)(b)): to create and run your account, show your listings and, once ordering is on, take orders, hold escrow and pay out.
• Legitimate interests (Art. 6(1)(f)): to keep the Service secure (sessions, security log, rate limits), prevent fraud and abuse, moderate content, measure usage in aggregate and fix bugs. You can object (section 10).
• Legal obligation (Art. 6(1)(c)): to keep records, answer lawful requests and, once real payments start, meet financial rules.
• Consent (Art. 6(1)(a)): not used today. If we add an optional feature that needs it, such as marketing email, we will ask first and you can withdraw it at any time.

Deleting your account (Settings, Account; you confirm with your password, or by typing your handle if you have no password). You cannot do it while you are the only owner of an organisation: transfer or delete the organisation first. It cannot be undone from the app. Deleting:

• signs you out everywhere and revokes your API tokens;
• replaces your email address with a placeholder and erases your password hash, two-factor secret, recovery codes and notification settings;
• clears your display name, bio, avatar (the image file is deleted), website, location and profile links, and removes your verified badge, so your profile is no longer shown;
• removes your linked GitHub sign-in, your notifications, your follows and followers, your organisation memberships and any pending email links, and cancels invitations sent to you;
• archives your listings, which hides them from lists and search; and
• keeps your handle reserved, so nobody else can take it and pose as you.

Deleting does not erase everything. These stay:

• Archived listings are hidden, not erased. Their files and version history stay in our database.
• Reviews, discussion posts, comments, stars, activity records and reports you filed stay, and reviews, posts and comments may still appear under your handle. You can delete your own reviews before you close your account. For anything else, contact us and we will remove it where we can.
• Security log entries about your account, with their IP addresses and user agents, and the record of your revoked API tokens. We do not delete them on a schedule yet.
• Records we must keep by law, such as payment records once payments are live, and copies in backups until they age out.

Traffic uses HTTPS with HSTS. Passwords are hashed with PBKDF2-SHA256, a per-password salt and a secret pepper. Session and API token values are stored only as SHA-256 hashes. The session cookie is HttpOnly, Secure and SameSite. A strict Content-Security-Policy blocks inline scripts and scripts from other sites, apart from Cloudflare's analytics script. All database queries use bound parameters. Details, and what is not yet done, are on the Security page.

No system is perfectly secure. If a breach puts your personal data at risk, we will tell affected users and, where the law requires, the regulator, without undue delay.

Whatever law applies to you, we will try to honour these requests. Under the GDPR, UK GDPR and similar laws you have the right to:

• Access a copy of the personal data we hold about you.
• Correct data that is wrong. You can edit your profile, email and password in Settings.
• Erase your data, subject to section 5 and section 8.2.
• Export your data in a common format. Settings, Your data, downloads one JSON file with your profile and preferences, linked sign-ins, active sessions, API token details, your security log, organisation memberships, your listings and version records, stars, reviews, discussions and comments, collections, follows and followers, notifications, activity and the reports you filed. It never contains your password hash, API token secrets or recovery codes. It does not contain the files inside your listings (download those from each listing). You can export 3 times an hour, and very large accounts are cut off at fixed limits, for example 1,000 listings and 2,000 security-log entries; ask us for the rest.
• Object to processing based on legitimate interests, and ask us to restrict processing while we look at a complaint.
• Withdraw consent where we rely on it.
• Not be subject to a decision based only on automated processing with legal effects. We make none.

Settings lets you see your sessions and your last 50 security events and sign out other devices (Security), turn on two-factor sign-in (Security), revoke API tokens (API tokens), choose which notifications you get (Notifications), export your data (Your data) and delete your account (Account). If a control is not available when you read this, ask us and we will do it by hand.

To use a right that Settings does not cover, contact us (section 14). We may need to check it is you. We aim to answer within 30 days, which is the usual legal limit, and will say so if we need more time. Requests are free unless they are plainly unfounded or excessive.

California and some other US states give residents similar rights to know, delete and correct, and to opt out of the sale or sharing of personal data. We do not sell or share personal data for advertising.

You can complain to your data protection authority. In the EU you may choose the authority where you live or work. In the UK it is the Information Commissioner's Office. We would like the chance to fix the problem first.

Cloudflare runs a global network, and requests may be handled in many countries. We have not committed to keeping your data in a particular region. GitHub also processes data in the United States and elsewhere. When personal data from the EEA, the UK or Switzerland is transferred to a country without an adequacy decision, we rely on the safeguards in our providers' data processing terms, which include the European Commission's Standard Contractual Clauses and, where the provider is certified, the Data Privacy Framework.

Public content and append-only records can be read from anywhere in the world.

The Service is for people aged 18 and over. We do not knowingly collect data from anyone younger. If you think a child has given us data, tell us and we will delete it.

We will update this page when what we collect or who we share it with changes, and change the effective date at the top. Where we can, we will tell you in the app or on the site before a change that reduces your protection, and at least 14 days before it applies to you where the law or fairness calls for it. The source of this page is in our public repository, so its history is visible.

For privacy questions and requests, open an issue in the project repository that says only "privacy request" and no personal details. We will move to a private channel with you. Do not post your email address, account data or other personal information in a public issue. A dedicated privacy email address will be added here when it exists. For security vulnerabilities, use the private advisory process.