First signed client document: BAA and vendor approval.

1. Public office basis

Smile With Style Orthodontics publicly presents orthodontic care in Gahanna, Ohio, under Walter Buchsieb II, DDS. The public service mix includes traditional braces, LightForce braces, Invisalign, retainers, habit appliances, space maintainers, TMJ/TMD treatment, dental technology, emergency orthodontics, braces emergencies, referral support, care instructions, and patient information. Codee may use these public facts only to prepare office workflow templates, campaign pages, contract routing, and staff approval screens.

2. Managed Codee bucket authorization

The practice authorizes Codee to manage a private Office OS storage area for the specific office and future approved office locations. The storage area may hold demo packets, signed approval records, contract-link records, metadata, audit files, review indexes, approved campaign assets, and future client-approved patient paperwork after the PHI launch gates are complete.

• Primary path: gs://codee-clients/clients/smilewithstyle/office-os/
• Office location path: gahanna-oh-43230
• Expansion model: each additional office receives a separate location slug and staff access group.
• No public bucket access is authorized for contracts, approvals, patient documents, payment paperwork, or protected health information.

3. Proposed staff group and titles

The named doctor below is based on public office information. Other positions are role placeholders for approval and can be replaced with the client's real staff names before production.

4. BAA-readiness and vendor boundaries

Before real ePHI is stored, the covered entity must approve the vendor relationship, BAA path, access model, retention rules, breach contact, staff training, and production go-live. Codee may continue building demo and approval workflows now. Codee should not intentionally accept real patient PHI until the production flag is enabled by an authorized admin after approvals.

• Codee keeps cloud credentials server-side and does not expose GCS keys in browser pages.
• Staff access should use named accounts, MFA, least privilege, and role review.
• Review links should be short-lived or protected by authenticated staff access.
• Storage should be encrypted at rest, transmitted over HTTPS, and tracked with audit metadata.
• Retention and deletion rules must be approved before live patient paperwork.

5. Client approval scope

By signing this approval, the signer confirms that Codee may continue configuring the Smile With Style Office OS managed bucket, role model, approval pages, demo-safe contract flow, vendor-readiness records, and location-based storage structure. This signature does not authorize unrestricted PHI launch by itself. Production PHI remains blocked until the remaining compliance and office controls are approved.

Signature will appear here after the approval packet is generated.