Privacy Policy

Last updated: September 2026

This plain-English policy describes the Practical Builds website, update forms, Developer Tools, and the Agent Utilities developer preview.

Information you provide

Practical Builds may collect information you choose to send, such as an email address, product interest, support request, or other message content.

Website and form services

The website may use hosting, security, email delivery, and form services to operate the site and send requested updates. Practical Builds does not sell update-list information.

Planned Agent Utilities accounts and requests

If public API access is enabled, operating an API account may require contact and account identifiers. The service may process API-key identifiers or prefixes, submitted target URLs, endpoint and timing metadata, request IDs, response status, and usage-metering records needed to authenticate requests, apply limits, diagnose errors, and account for credits. API keys are designed to be stored as server-side hashes rather than plaintext values.

Page content and retention

When enabled, page normalization necessarily processes the content returned by a submitted public URL. This website repository does not contain the Agent Utilities backend or establish whether normalized page content is retained after a response, the contents of operational logs, or their retention periods. Those details require owner verification against the deployed service before broader API availability; no transient-only or fixed-retention promise is made here.

Billing and service providers

If credit purchases are enabled, Practical Builds may store customer, transaction, and shared Agent Utilities credit-balance and ledger information needed to provide the service. Stripe handles payment-card entry and processing on its systems; Practical Builds should not receive or store full payment-card numbers. Cloudflare may process network and security metadata while providing hosting, delivery, and abuse-protection infrastructure.

Owner/legal review required: confirm production logging, page-content persistence, retention, account deletion, Stripe data fields, and any model-training policy before general availability.

Browser extensions and local-first tools

Some Practical Builds tools are designed to work locally in the browser where practical. Product-specific store listings or documentation should be treated as the source of truth for each extension's permissions and behavior.

Future Bitbucket and Atlassian app

Review Triage for Bitbucket is still in development. Final data access, storage, and permission details will be documented before any public Atlassian Marketplace listing.

Your choices

You can unsubscribe from update emails using the unsubscribe link in those messages. You can also contact Practical Builds to ask about information associated with your email or support request.

Contact

Questions about privacy can be sent through Deahr Creative Collective at [email protected].

For product-specific permissions, storage, and network behavior, see Security & Transparency.