Buildory is a project documentation tool for makers and hobbyists. This policy explains which personal data Buildory processes, why it is needed, and how users can ask for access, correction or deletion.
Who is responsible
Buildory is operated by Henk Salomons. For privacy questions or data requests, contact [email protected].
Data we process
- Account data, such as name, email address, encrypted password and login provider identifiers.
- Project content you create, including project descriptions, sections, tasks, build logs, BOM items, knowledge items and photos.
- Uploaded files and images attached to projects, sections, tasks, build logs, knowledge items and photos.
- Billing metadata from Stripe, such as customer ID, subscription ID, plan, status and billing interval.
- Technical data needed to operate the service, such as server logs, request metadata and signed visitor tokens for public project visit counts.
- MCP connection data, such as granted read or write scopes, token prefixes, last-use timestamps and a limited audit record of project changes made through a connected client.
Why we process data
- To create and secure user accounts.
- To store and display project documentation.
- To make public projects, public sections and public maker profiles available when users choose to publish them.
- To enforce plan limits and process subscriptions.
- To monitor reliability, prevent abuse and fix errors.
- To provide user-authorized ChatGPT, Codex and compatible MCP connections and to make their changes traceable.
Public content
Projects marked as public can be viewed by anyone, including visitors who are not signed in. Public project pages may include project text, sections, tasks, logs, BOM data, knowledge items, images and attached public assets. Private projects are available only to their owner, authorized workspace members and connected clients that the user has authorized, provided MCP access is enabled for that project.
Third-party processors
Buildory may use Stripe for billing, Cloudflare for DNS and file storage, TransIP for hosting, OAuth providers such as Google and GitHub for login, and an email provider for transactional email. These providers process data only as needed to provide their services.
ChatGPT, Codex and MCP connections
When you connect ChatGPT, Codex or another compatible MCP client, Buildory sends that client only the requested data from projects that you may access and that are enabled for MCP. The client receives read access by default; changes are possible only after you explicitly grant write access to both the connection and the individual project. The AI or client provider may process the received data under its own privacy terms. You can exclude individual projects, disable changes per project, revoke personal tokens and disconnect OAuth access. Buildory never sends your password, OAuth token or personal access token as project content.
Cookies and similar storage
Buildory uses essential cookies for login sessions, security and basic preferences. Anonymous public project visit counts use a short-lived signed first-party visitor token. Buildory does not use advertising or cross-site tracking cookies.
View the complete cookie policy
Retention
Account and project data is kept while the account exists. Users can ask for deletion of their account and project data. MCP change-audit records are kept for up to 90 days for security and support. Revoked personal token records may retain their non-secret prefix and timestamps for the same purpose. Some billing records may need to be retained for legal, tax or administrative reasons.
Your rights
Depending on applicable law, you may request access, correction, export or deletion of your personal data. Send requests to [email protected].
Changes
This policy may be updated as Buildory evolves. Significant changes will be reflected by updating the date on this page.