1. Scope and contact
For its initial free private beta, BuildMode Studio is the public brand of a service operated personally by an individual based in Sri Lanka. There is no separately incorporated BuildMode Studio company. The individual operator is responsible for the personal information described in this notice. The operator’s legal name and physical address remain unresolved disclosure requirements, pending the operator’s explicit approval and jurisdiction-specific legal review; neither is supplied by this draft.
The notice covers visits to the website, requests for beta access and use of the workspace when access is available. The operator can monitor hello@buildmodestudio.com for privacy, account-access and deletion requests. Requests are reviewed manually. There is no automated privacy-request or complete account-erasure workflow.
2. Information handled by the service
- Beta requests: your email address, the form used to request access and the time the request was created. Email addresses are trimmed and lowercased; duplicate requests do not create another signup record.
- Accounts and sessions: Clerk handles authentication. BuildMode receives an authenticated user identifier and uses it to associate workspace records with the user. Information entered into Clerk’s sign-in or account screens is also processed by Clerk.
- Creative content: project names and descriptions; reference images, links and notes; canvas positions and relationships; directions, decisions, current-state notes and open questions; generated blueprints, execution plans and step progress.
- Uploads and reliability records: file type, size, dimensions or checksums where recorded, storage identifiers, ownership, operation identifiers, timestamps, retry state and deletion/provenance records. These support safe uploads, duplicate prevention and recovery.
- Technical information: network addresses are processed when requests reach the service. Hosting and authentication providers may process request, device, session and security information. The beta limiter stores keyed hashes derived from client network addresses, counts and expiry times rather than raw IP addresses in its rate-limit table.
- Correspondence: information you choose to include when contacting BuildMode. The email provider and handling arrangements have not yet been confirmed for this draft.
3. Why information is processed
The implemented purposes are managing beta requests, authenticating access, saving and displaying creative work, connecting references and decisions, providing requested AI features, preventing abuse, and maintaining upload and storage integrity.
The beta form records an access request. It does not create a marketing subscription, verify email ownership, send an email or guarantee an invitation. No advertising or analytics integration is included in the reviewed landing-page code. Live hosting and provider configuration still need verification.
For processing subject to UK or EU data-protection law, the proposed bases are taking steps at your request before entering a service contract and performing that contract for account, workspace and requested AI features; and legitimate interests in preventing abuse and maintaining security for operational safeguards. Processing required by an applicable legal obligation would rely on that obligation. These bases, the necessity of each activity and any legitimate-interest assessment require review before publication. No marketing-consent or blanket consent is inferred from browsing or requesting beta access.
4. Service providers and external sites
The application integrates the providers below. Their role in a particular interaction depends on the feature used; visiting the landing page does not itself submit workspace content to the AI provider. Provider contracts and account settings must be reviewed alongside this notice.
- Clerk
- Account authentication and session management.
- Neon
- PostgreSQL storage for workspace records, beta requests and operational ledgers.
- Cloudflare R2
- Object storage for uploaded reference and Library images.
- Anthropic
- Processing supplied project context and, for relevant AI features, reference images to generate suggestions and plans.
- Railway
- Configured backend hosting platform; processes API traffic when the backend is running.
Saving a link can cause BuildMode to request the linked page to extract its title, description and preview-image URL. That site receives a server-side request. Displaying an externally hosted preview or opening a saved link can also send a request from your browser to that site. Its own privacy terms apply to that interaction.
Instagram and X links open external services when followed. The public website host, email provider, provider regions, international-transfer arrangements and any additional operational providers must be confirmed before publication. No guarantee that data stays in one country is made in this draft.
5. AI features and your creative content
When you invoke an AI feature, BuildMode assembles context from the relevant project. This can include project text, saved reference text and link metadata, directions, decisions, current-state notes and open questions. Direction generation can send the actual bytes of reference images to Anthropic. Blueprint and execution-planning features send the context needed for those requests.
AI results that are saved become part of the project’s stored records. Avoid submitting content that you are not permitted to share with the service or its AI provider, including confidential or sensitive personal information without appropriate authority.
Anthropic’s applicable commercial terms, retention rules and data-use policies govern its processing. BuildMode’s account-specific agreements and settings have not been verified for this draft; no zero-retention or model-training guarantee is stated here.
7. Retention and deletion limits
No fixed automatic retention period is implemented for beta email records or ordinary workspace content. The beta rate limiter uses expiring windows and removes expired non-global limiter records during subsequent allowed requests; expiry is not an immediate background deletion job. Provider logs and backups may have separate retention settings that remain unverified.
The application has project and reference deletion operations. Removing a project or reference is not a promise that every stored image, Library item, authentication record, backup or operational record is erased. Some legacy images are deliberately retained for safe storage handling, and upload/provenance ledgers include durable records that guard against unsafe retries or deletion.
A complete account-erasure, provider-erasure and backup-expiry process has not been established in the reviewed implementation. Signing out, or changing or deleting an authentication account through provider controls, must not be assumed to delete workspace data. Retention criteria and an operational request process are publication blockers for this draft.
8. Your choices and applicable rights
Depending on applicable law, you may have rights to access, correct, erase or obtain a copy of personal information; restrict or object to certain processing; withdraw consent where processing relies on it; and complain to a competent data-protection authority. The rights and exceptions depend on your location, the operator’s location and the processing involved.
You can choose not to submit a beta request, not to upload particular content, and not to invoke an AI feature. Existing project and reference controls cover only the records they actually manage; they are not a complete privacy-rights portal.
To raise a privacy request, email hello@buildmodestudio.com and describe the account and request without sending passwords or unnecessary sensitive documents. The individual operator reviews requests manually. Identity checks, secure data delivery, provider coordination and backup handling still need a documented process; this draft does not promise an automated export or account-erasure button.
9. International processing and regional rights
BuildMode is operated from Sri Lanka and intends to support users in Sri Lanka, the United States, the United Kingdom, the European Union and other legally supported markets. Providers may process information in countries different from yours. No particular storage region or international-transfer safeguard has been verified for this draft.
Before publication, the operator must identify actual processing locations, review provider data-processing agreements and applicable transfer safeguards, and determine whether EU or UK representatives are required. Where required, the final notice must explain the safeguards and how to obtain information about them.
If applicable law gives you a right to object, you may object to processing based on legitimate interests. Other rights and exceptions depend on the applicable law and legal basis. You may also complain to a competent supervisory authority, including your EU national authority or the UK Information Commissioner where relevant. Sri Lankan and US state-law requirements must be assessed for the beta’s actual scope; this draft does not assert that every regional law applies or that every implementation requirement has been met.
10. Security and eligible users
The application uses authenticated access checks and ownership checks for workspace operations, upload validation and rate controls. These are safeguards, not a guarantee against every security incident. No end-to-end encryption, particular certification, comprehensive encryption-at-rest guarantee or fixed hosting location is asserted here.
The private beta is intended for people aged 18 or older, including creative professionals and teams, internationally where legally permitted. It is not intended for children. This is an eligibility policy, not a claim of implemented age verification or regional access enforcement. Contact the operator if you believe a child has supplied personal information; any investigation and response would be manual.
11. Updates
This document is a review draft dated 20 October 2026, not an effective policy. A final version must identify its effective date and the process for communicating material changes before publication.
Contact: hello@buildmodestudio.com