Creator development test terms

Version creator-test-2026-09-27-r2 · Effective September 29, 2026

Who may take part

Buildpane is operated by Shrock Services LLC, formed and primarily operated in Kentucky, United States. Mailing address: 4698 Dunnville Rd., Dunnville, KY 42528. This test is for people in the United States who are at least 18. If you act for a business, you must have authority to do so. Give accurate account information and keep your sign-in details secure.

What the test provides

Creator testing lets you try AI-assisted project development and private development previews. It is a development environment, with features that may be unavailable or change during testing. It does not include production service, public app hosting, domain purchases, or customer email hosting. Do not rely on it for business-critical work. Keep a separate copy of work you need.

Internet access from a development Workspace is limited to HTTP and HTTPS (ports 80 and 443) through Buildpane's metered connection. SSH, direct database connections and other ports do not work inside a Workspace. Internet transfer counts as Compute usage and stops when the Workspace's funded allowance is used.

Use synthetic project data. Do not upload another person's private information, health or financial records, or production credentials. Your registration and support information are still real personal information, handled as described in the privacy notice.

Credits and test payments

Creator has no required monthly subscription. An eligible new account receives one starter grant of 100 Build Credits and 200 Compute Credits. Build Credits pay for AI Builder activity; Compute Credits pay for development infrastructure. The wallets are separate. Credits do not expire merely because you stop signing in.

Credit figures represent service units, not a cash account. Where a dollar equivalent is displayed, 100 credits represents $1 of the applicable service balance. Stripe Test transactions simulate payments and tax; they do not transfer real money. Do not enter a real payment card. See the test payment information.

Development requires enough available Compute Credits above the 100-credit operation reserve. New development time is funded only from Compute Credits, never from Build Credits. A low balance can pause work. A Workspace keeps using Compute while you are active in it or while a Builder run you started is in progress, and sleeps after a period of inactivity.

Some usage is measured after it happens, such as a final provider measurement or the short period while a Workspace stops. That usage is paid from Compute Credits first. If Compute Credits run out, the rest is paid by converting Build Credits to Compute Credits; this conversion is one-way and is used only for usage that has already occurred. When both balances are used up, development is locked until you add Compute Credits. Any remaining usage that had already occurred is recorded as an outstanding Compute balance of no more than 100 credits. Adding Compute Credits first clears any outstanding Compute balance. Optional Auto-Refuel, when available and expressly enabled, uses the selected refill amount, declared use and monthly maximum. It can be disabled in Credits.

Usage is normally finalized within 24 hours. If the final measurement is lower than the amount charged, the difference is credited automatically to your Compute Credits, including any part that was paid by converted Build Credits. Usage that cannot be confirmed from provider records is reviewed by an operator; it is not estimated.

Your projects and AI output

You retain your rights in material you provide. You authorize Buildpane and the service providers involved in your requested work to process that material to operate the test, provide support and protect the service. You must have permission to use material you upload. AI output can be incorrect, insecure or subject to other people's rights; review and test it before use. These terms do not grant rights that Buildpane does not own.

Safety, account access and ending participation

Follow the acceptable-use rules. We may restrict access to address abuse, security incidents or violations. An unverified report alone does not authorize destruction of account data. You may ask for review through [email protected]; the review and recovery process is described in those rules.

You may stop using the test and request account closure through [email protected]. Closing or restricting an account does not mean all records have been erased. Retention, privacy requests and recovery limits are described in the privacy notice. A verified, complete account archive is required before removing customer data under the credit-exhaustion or dormancy process; a workspace checkpoint alone is not that archive.

Questions and changes

For account, billing, privacy or other existing-customer help, contact [email protected]. Prospective customers and general inquiries may contact [email protected].

Material changes will be presented before they apply, with renewed acceptance when needed. No later change gives retroactive permission for a new use of your data. These terms do not remove rights provided by applicable law.