Pilot service terms — DRAFT

BMDO provides architectural visualization and project presentation services described in your order. Outputs may include geometric models, images, and hosted review tools. The order identifies included elements, revisions, assumptions, fees, and hosting term.

Each order states its acceptance window, the correction rounds included, and how a change order is agreed and priced. The Project Workspace subscription and the per-project production packages are described on the pricing page as introductory pilot pricing; where the order and the website differ, the order governs.

Drafting noteDefine the acceptance and correction windows and the change-order process in each order rather than here.

You confirm that you are authorized to submit the drawings and other materials and to permit their processing and sharing for this project.

Owning a building, or holding a copy of a drawing, is not by itself proof of rights in the design. Architectural works can be protected by copyright. If you are not the architect of record, obtain the architect's permission before submitting their drawings. The workspace records this confirmation, together with the version of these terms you accepted, for each submission.

Drafting noteReference: US Copyright Office, Circular 41. The upload consent checkbox text proposed in the brief is “I am authorized to submit these plans and agree to the project service terms.”

You retain your rights in submitted materials. You grant BMDO a limited license to store, reproduce, process, and display them as needed to provide the agreed service and follow your authorized sharing instructions.

Output ownership. [To be resolved] — proposed: on payment, you receive a license to use the delivered models, images and review materials for the project they were made for; BMDO retains its tooling, templates and methods.

Third-party assets. Fonts, entourage, materials and similar assets used in a deliverable are used under their own licenses, which the order lists where they restrict your use.

Export. Any released version can be exported for as long as the project exists in your workspace. An export is a single archive containing every asset in that release — the model file, the measured view images and any illustrative renders — plus a plain-text summary and a machine-readable manifest recording each file's SHA-256 checksum, the drawing set and exact stored version it was built from, the pipeline and calibration references, the architect who approved it, and the stated assumptions and limitations. Download links are issued per request and expire after five minutes; there is no permanent link, so withdrawing someone's access takes effect on their next request. Files already downloaded cannot be recalled. [Still to resolve: whether export survives the end of a paid hosting term, and for how long.]

Project content is accessible to authorized project participants and service personnel who need access to perform or support the service, subject to the access controls described in the Privacy and Security notices.

Service personnel access is tied to assigned work. A person assigned to produce visuals from your drawings receives temporary credentials, valid one hour, that reach exactly one drawing set and one output location — they cannot read or write another project's files, and the restriction is enforced by the hosting platform rather than by our own code alone.

Infrastructure providers used to deliver the service: Amazon Web Services (United States, N. Virginia) for storage, databases, email delivery and malware scanning, and Stripe for subscription payments — card details are entered on Stripe's own pages and never reach BMDO. Your drawings are scanned for malware inside our own AWS account; they are not sent to an outside scanning service. Any other processor — in particular any external AI or rendering service — requires your recorded, per-project permission before it can be used, and the system refuses to record a deliverable produced by a processor you have not approved. [Still to resolve: the written confidentiality and data-handling terms to be flowed down to any future subprocessor, and whether a formal data-processing addendum is required.]

Drafting noteDo not publish this section until the access controls it refers to exist. The security page lists what is in place today; privileged-access logging and access reviews are not yet among them.

You control the recipients, assets, and permissions of project invitations. Recipients must use shared content only for the authorized project purpose. Access may expire or be revoked; previously obtained copies cannot necessarily be recalled.

An invitation is issued to one named recipient for one released version, with the capabilities you choose (view, comment, download) and an expiry you set. “View only” means the workspace does not offer an original-file download; a browser still receives the image and model bytes it displays, and BMDO does not claim to prevent copying.

Drafting noteA separate, short guest confidentiality and use acknowledgement is proposed for recipients to accept before first access. Its text is not yet drafted.

Visualizations may simplify geometry or illustrate details not resolved in the source documents. They are for communication and design review. The architect's issued drawings and professional direction govern construction.

No engineering, permitting, code or accessibility review, measured-dimension accuracy, or certification is included unless separately agreed in writing and qualified in the order. Where an image is AI-assisted it is labelled as illustrative and is not a measured record of the model.

Some steps in producing a visualization are computer-generated or AI-assisted. The order and the deliverables identify which images are illustrative AI-assisted renderings and which are direct snapshots of the reviewed model, together with known limitations.

Default. Your materials are not used to train any model, and are not sent to an external AI provider, unless you have given the specific permission described in the order and the provider's data-handling terms have been verified and recorded. Storage in AWS alone does not mean data never leaves AWS during processing; approved providers and their handling are listed in the privacy notice.

Drafting noteDo not name a provider or describe its policy here until it has been verified. Approved providers for client material at this draft: none.

These terms do not grant BMDO any portfolio, publicity, testimonial or training license. If you would like a project shown publicly, we ask separately and in writing for the specific assets, any identifying details (firm, practice, location), the channels, and how withdrawal is handled.

You can withdraw that permission at any time. Removal from channels BMDO controls follows within 30 days of a written request, and sooner where it is a single web page; copies already distributed — printed, downloaded, or reshared by others — cannot necessarily be recalled. [Owner to confirm 30 days is the commitment they want to make.]

The schedule below is a proposal and not yet a commitment. Before these terms take effect it will be replaced with the schedule actually configured and tested, including backup retention, lawful-hold handling, account closure and export options.

Proposed retention (not yet a commitment)

Data class	Proposed policy
Abandoned multipart uploads	Abort after 24 hours
Rejected/quarantined submissions	Delete within 7 days unless actively investigating an incident
Active plan sets and deliverables	Retain during purchased active/hosting period; clearly state renewal/archive terms
User-requested project deletion	Revoke access promptly; complete primary-store purge within 30 days, subject to documented lawful hold
Disaster-recovery copies	Age out within 90 days under a documented schedule; restricted and unavailable for routine service use
Security/audit events	Proposed 12 months, minimized fields; align contractual/statutory needs with counsel
Marketing samples	Independent consent and retention; revocation process separate from private-project storage

A deletion request covers the original files, all stored versions, derived images, thumbnails, metadata, jobs, cached delivery copies, local operator copies and copies held by approved subprocessors. Storage is versioned, so an ordinary delete leaves earlier versions in place until the purge completes; that is why the schedule states a purge window rather than an instant.

Recipients you authorized may keep copies they obtained while their access was valid; deletion by BMDO does not reach those copies. Export your releases before requesting deletion — deletion removes every stored version of the source drawings, the produced assets, the production records and the export archives themselves, and that is not reversible.

Fees, deposits and payment milestones are stated in the order. Workspace subscriptions are billed in advance, monthly or yearly, through Stripe. Production packages are invoiced per project against the fixed quote that follows a Plan Review. Unless the order says otherwise, quoted work is invoiced as a 50% deposit when you accept the quote and the balance on delivery; each invoice is due within 15 days and can be paid through Stripe by ACH bank transfer or card. The payment terms are shown on the quote before you accept it. Included correction rounds are stated in the order; requests outside scope are quoted before work starts.

If required inputs arrive after the agreed date, the schedule moves and any rush pricing applies only as quoted. Public prices are introductory pilot pricing and may change for new orders; the order governs.

Cancellation and refunds. [To be specified]. Hosting renewal and archive. [To be specified]. Taxes. [To be specified by jurisdiction].

Drafting noteDo not place unvalidated prices or turnaround commitments in this section; the pricing page carries the introductory figures with their qualifiers.

You must not upload unlawful content or malware; materials you are not authorized to share; patient records or any other clinical or health information, which the pilot does not handle; or attempt to access another firm's or project's content.

Every upload is checked before it is kept: declared type, exact size and checksum are re-verified, the file is examined for active content such as embedded scripts or auto-run actions, and it is scanned for malware. A file that fails any of these is refused, deleted, and reported to you with the reason. Nothing is promoted out of quarantine until those checks pass.

BMDO may suspend access proportionately while an issue is investigated and will tell you why, except where notice is prohibited or would defeat the investigation. The procedure followed, including who responds and in what order, is recorded in the service's internal incident runbook; because BMDO currently operates with a single responder, no response-time commitment is made and none should be inferred.

[Counsel to supply]: warranties and disclaimers, limitation of liability, indemnities, the dispute process, governing law of the State of Ohio, and the statutory exceptions that cannot be excluded.

Drafting noteThis draft assumes no universal boilerplate is sufficient without review for the pilot's business-to-business use and launch markets.

Version: [Effective date/version]. BMDO will notify you of material changes at least [notice period] before they apply, and will ask for renewed acceptance where a change affects your rights or obligations. Earlier versions remain available, and material you submitted under an earlier version is not put to a new use without appropriate treatment.

Support: hello@buildmydentaloffice.com. Privacy: hello@buildmydentaloffice.com. Post: Build My Dental Office (Zachary Bowman), [Address].