Public site privacy boundary.

Effective date: July 5, 2026

This policy applies to the Building Jarvis public website. If a client later approves a private integration with tools like CRM, email, calendar, ads, phone, invoicing, or field-service software, that integration requires a separate scope, access plan, and approval boundary.

What this website may collect

• •Contact details you choose to provide, such as name, email, phone number, business name, and call preferences.
• •Business workflow details you submit for scoping, such as the task you want help handing off and the tools you already use.
• •Basic website analytics, device/browser information, referral source, and server logs if provided by our static website host or analytics tools.

What this site does not ask for

• •Payment details or banking information.
• •Passwords, API keys, OAuth tokens, cookies, or other credentials.
• •Private customer records from your CRM, email, calendar, invoicing, phone, or field-service systems.
• •Government IDs, Social Security numbers, protected health information, or other highly sensitive records.

How information is used

• •Respond to fit-call, intake, and contact requests.
• •Evaluate whether Building Jarvis can help with the workflow you describe.
• •Improve the public website, troubleshoot issues, and protect the site from abuse.
• •Prepare a private implementation plan only after you separately approve the access and scope.