1. Scope and contact
BuildMode Studio is operated by Jerome Perera as an individual based in Sri Lanka, not through an incorporated company. Contact support@buildmodestudio.com about privacy, access, correction or deletion. This notice covers the website, beta-access requests, workspace and relevant optional features.
During private beta, Jerome Perera personally handles privacy requests. Signed-in users can submit requests through Privacy requests in the app; support@buildmodestudio.com is an alternative, including if you cannot sign in. You do not have to accept a new Terms version to reach the request route.
2. Information we handle
Account and session information: Clerk provides sign-in and account controls. BuildMode uses the authenticated account identifier to scope records; Clerk separately processes the information supplied in its sign-in and profile screens.
Workspace content: project names and descriptions; references, uploaded images, URLs and notes; canvas arrangements and connections; directions, decisions, questions, project memory, blueprints, execution plans and progress. Historical snapshots and soft-deleted Library items may remain.
Operations and security: upload sizes/types and checksums, object identifiers, ownership and retry histories, AI request/response recovery records, usage and cost accounting, timestamps and diagnostic information. Some pending AI results and context are retained to support recovery.
Payments: account-linked checkout attempts, provider transaction/subscription identifiers, purchase status, amounts/currency, refunds, credit grants, reservations and usage. Paddle processes payment information for its checkout. BuildMode does not request full card details through its API or support forms.
Communications: beta-access email addresses, feedback, privacy-case messages and operator review notes, and correspondence you choose to send. Beta-access requests are normalized and deduplicated; submitting the form is not a marketing subscription or proof of email ownership.
Network requests necessarily expose connection information to hosting and authentication providers. The beta limiter records keyed network-derived hashes, counters and expiry times rather than raw IP addresses in its limiter table. Provider log settings are separate.
3. Purposes and choices
We process information to authenticate accounts, save and display work, provide requested AI features, verify purchases and manage entitlements, prevent abuse, maintain reliability and respond to support and privacy requests.
Where applicable law requires a legal basis, contract-related processing, security and service-operation interests, legal obligations and any separately requested consent must be assessed for the particular activity and jurisdiction. Acknowledging this notice is not blanket consent to optional processing or marketing.
Choose what you submit and which AI features you invoke. Do not include unnecessary sensitive personal information or material you cannot authorize us and the relevant providers to process.
4. Providers and external requests
BuildMode uses Clerk for authentication, Neon PostgreSQL for application records, Cloudflare R2 for uploaded objects, Anthropic for requested AI processing, Paddle for paid transactions and subscriptions, and Railway for API hosting. The marketing site is configured for Netlify. These providers process information for their respective functions; their published notices and applicable service agreements have different scopes. Listing a notice does not mean it governs all processing of customer content or that an account-specific agreement has been independently verified.
Paddle is the merchant of record for paid transactions. Opening checkout can load Paddle’s client and contact Paddle. Paddle handles payment, subscription, fraud-prevention, tax, refund and transaction processing under its applicable terms and notices. BuildMode keeps account-linked purchase, subscription, entitlement and financial records, including separate Live billing records; deleting creative content does not by itself cancel a subscription or erase those records.
Uploaded objects are held in private Cloudflare R2 storage with public bucket access disabled and no public development URL or custom public domain configured. This does not prevent authorized application access. An Asia-Pacific location hint is configured, but it is a placement preference, not an exclusive-residency guarantee.
Saving a URL can make a server request to the linked site to obtain metadata. Displaying an externally hosted preview or opening a link can contact that site from your browser. External social links similarly lead to those providers. Their own privacy notices apply.
5. AI processing
When you request AI features, BuildMode supplies relevant project context to Anthropic. This can include project text, saved reference text/link metadata, directions, decisions, current-state notes and questions. For relevant image-aware operations, actual image bytes are supplied. Not every AI operation uses images.
Generated content, source snapshots and recovery results can be retained in application records. Correcting or deleting a visible source item does not automatically remove every earlier snapshot or provider-held copy.
BuildMode does not use customer content to train AI models for this launch. Anthropic states that commercial API inputs and outputs are not used for model training by default. Its published exceptions include feedback or bug reports and an express choice to allow such use. BuildMode has not authorized a new customer-content training use for this launch; this notice does not grant that permission.
Anthropic’s published commercial API standard is deletion of inputs and outputs within 30 days, with exceptions for longer-lived features such as Files, separately agreed arrangements, Usage Policy enforcement and legal requirements. Its API guidance also describes feature-specific retention and Covered Models requiring 30-day retention. These are provider policies, not a verified account-specific zero-data-retention or separate no-training agreement.
Anthropic describes longer retention for flagged policy violations (inputs/outputs up to two years and classification scores up to seven years) and feedback-related data (five years). Applicable features, safety requirements, law and agreements can affect retention. Requests about provider-held information require separate coordination; deleting a BuildMode record is not a guarantee of immediate deletion by Anthropic.
6. Browser storage and optional capture
The reviewed marketing source does not include advertising trackers or an analytics integration and serves its fonts locally. This does not establish the retention or cookies of a hosting, authentication or checkout provider. Clerk uses authentication cookies and related storage.
The workspace can store account-scoped pending AI request identifiers in browser session storage for recovery. An optional capture extension can retain pending image URLs, hashes, operation/status metadata and account scope in extension storage across restarts; its availability depends on the supported release.
You can use browser controls to clear local storage or cookies, but authentication or recovery may stop working. Clearing browser data does not erase server records, financial history or provider copies.
7. Retention and deletion limits
We retain information according to its purpose, the account relationship, support and recovery needs, and applicable legal obligations. There is no single automatic deletion period for all workspace, account or beta-signup records. Detailed schedules for content, operational logs, privacy cases and other records remain subject to operator/legal review; indefinite retention is not justified merely by technical immutability.
Following a verified account-deletion request, the operator will arrange deletion of eligible customer projects and creative data. This is a manual process, not complete automatic account erasure. Historical snapshots, soft-deleted Library content, provenance and retry records, and legacy uploaded objects may require separate handling. We will explain material limitations and applicable retention exceptions rather than treat a received request as proof of erasure.
R2 uses Standard storage and has no automatic expiration rule for ordinary stored objects. Object deletion therefore depends on application-level or authorized manual handling, including legacy objects. Deleting a visible project or reference does not guarantee that every object, history or provider copy has been removed immediately.
The production Neon database has a six-hour history window for point-in-time recovery. This does not limit all backup retention: a separate manual production snapshot created on November 3, 2026 has no configured expiration and remains until separately removed. Its retention requires operator review. Independent snapshots, branches and restored databases must be considered when handling deletion; a restore must not silently undo an approved deletion.
Financial, credit, subscription, refund and legal-acceptance records may need to remain for applicable legal obligations, disputes, fraud prevention or other justified purposes. Any exception must be assessed and explained; deleting an account is not a promise to erase Paddle’s independent transaction records. Privacy-case and completion records can also be needed to document handling of a request.
Signing out, clearing browser storage or deleting an authentication account does not itself erase workspace, financial or provider data. Provider records, logs and recovery copies have separate controls. No immediate removal of all copies, universal purge deadline or automatic backup erasure after six hours is promised.
8. Privacy requests and applicable rights
Depending on applicable law, rights can include access, correction, a copy or portability, erasure, restriction, objection, withdrawal of a consent that was actually used, and a complaint to a competent authority. Rights, exceptions and response periods depend on the applicable law; this notice does not replace them.
Use Privacy requests in the app for access, correction or deletion, or email support@buildmodestudio.com for those or other rights. Include enough context to locate the account without passwords, session tokens, card data or unnecessary identity documents. A signed-in request is recorded against that account; an operator may need further proportionate identity or authority checks before disclosure or action.
Requests are handled personally and manually during private beta. The app records requests and operator audit notes; it does not automatically deliver a complete export, verify every identity, erase an account, notify providers or complete backup handling. The operator reviews account data and relevant provider-held records, explains material gaps or lawful retention exceptions, and coordinates secure delivery or deletion steps as appropriate. A received request or closure note alone is not proof that data was delivered or erased.
Paddle separately handles buyer payment requests at paddle.net. Contact BuildMode for product/account data and Paddle for its transaction information where appropriate; neither route removes rights you otherwise have.
9. International processing and safeguards
The operator is based in Sri Lanka and providers may process information in other countries. The R2 Asia-Pacific hint does not restrict all processing or copies to that region. Actual processing locations, applicable contractual safeguards and any regional representative obligations require legal review. No unverified certification, exclusive residency commitment or account-specific transfer agreement is claimed.
The app uses authentication, ownership checks, upload validation and recovery safeguards. These are not a guarantee against every incident, end-to-end encryption or a particular certification. The service is intended for adults aged 18 or older; automated age verification is not asserted. Contact support if you believe a child supplied information.
10. Changes and contact
A material update will receive a new version. The service can record an acknowledgement of the current notice separately from Terms acceptance; an acknowledgement is not a waiver of rights or consent to unrelated processing. Contact support@buildmodestudio.com for privacy questions.
Contact: support@buildmodestudio.com