DRAFT — NOT APPROVED / NOT PUBLISHED Product:[APPROVED PRODUCT NAME — TBD; Fieldnote is internal only] Operator:[LEGAL BUSINESS NAME — TBD] Effective date:[TBD] | Business mailing address:[TBD — no residential address] Privacy:privacy@[future-domain].com | Support:support@[future-domain].com Ohio is under consideration only; no entity, jurisdiction or publication is approved. This notice explains how [Operator] handles information for its service-business management application. It becomes effective only after the placeholders, actual provider settings and companion retention policy have been approved. Information we process Account information includes owner name/email, business details and authentication records. The service stores the records your business enters:customer contact/service addresses, estimates and revisions, appointments, worker names/rates, job expenses, invoices, payment/refund/credit records and associated history. We also process support correspondence and limited operational/security information. Infrastructure providers may process IP addresses, device/request metadata and email-delivery events. Passwords are handled by our authentication provider; we do not ask support users for passwords, recovery codes, session tokens or backup keys. Uses and responsibility We use information to authenticate owners, maintain separate business workspaces, save and recover records, create requested documents, deliver account/security mail, provide support, prevent abuse and meet applicable obligations. Your business decides which customer/worker information to enter and is responsible for its lawful use, notices and instructions. We process that business content to provide the service. For our account administration/security records we determine the operational purposes. No advertising tracking or sale of personal information is part of this beta design. We do not use business content to train AI models. The current product does not send business content to an AI model; operator/support handling must follow this restriction. Service providers and disclosures The proposed beta uses Supabase(database/Auth), Render(hosting), Backblaze(encrypted off-site backups), Resend(account email) and GitHub(private code/operational checks). GitHub checks may read encrypted backup bytes and health metadata; decryption/master/ database credentials are excluded. Final provider contracts, regions and retention must be confirmed before publishing. Providers process information as needed for their functions. We may disclose information to comply with valid legal requirements, protect rights/security or carry out an approved business transfer with appropriate safeguards/notice. We do not promise that every provider processes data only in the US. Cookies and local records Necessary session/access/recovery cookies support login and security. A separate optional local demo stores records in the browser; those records are not silently merged into cloud accounts. Exported JSON/PDF files and local demo data remain on your device until you manage them. No advertising/analytics cookies are proposed. Access, retention and security Owners can export operational records and request assistance with access, corrections or account deletion. A customer/worker whose data belongs to a service business should contact that business; we can help route a request and assist as appropriate. Contact privacy@[future-domain].com. We verify authority, minimize identity evidence, and respond as required by applicable law. We do not require passwords to verify you. The companion retention policy describes active deletion and backup expiry separately. Backups are not immediately erased when an account is deleted; protected copies age out, with deletion requests reapplied before restored data is returned to service. We use tenant access controls, encrypted transport, protected sessions and encrypted independent backups. These reduce risk; no system can guarantee absolute security. Audience and changes The service is for adult business owners, not children. Do not submit government identifiers, full payment-card/bank credentials, medical records or other unsupported sensitive data. We will provide appropriate notice of material policy changes before they apply, subject to lawful emergency/security needs. Contact [Operator] using the approved business address/privacy contact above. REVIEW REQUIRED BEFORE USE Confirm legal operator/contact/address, provider agreements/regions, actual logging and retention, controller/service-provider contract terms, applicable US state privacy laws and any individual-rights supplements. No claim of CCPA/GDPR/HIPAA certification or exemption. Public promises must match tested beta operations, not future plans.