Privacy Policy
Effective October 17, 2026
This Privacy Policy describes how POWERHOUSE 24 SI, operated by Braxton Heritage Group (“we,” “us”), handles information through powerhouse24ai.com and the connected POWERHOUSE workspace. Contact: terrencejones37@gmail.com.
Information we process
- Account and team information: sign-in identifiers, email addresses, names where provided, invitations, company assignments, roles, permissions, and saved preferences.
- Work you provide: dealership and customer records, contact details, notes, follow-up dates, drafts, uploaded files, company materials, project information, and work or timekeeping records.
- Connected services: information returned by services you authorize, limited to the permissions granted and the functions you use.
- Operational information: request and error logs, security information, and identifiers needed to operate the website and maintain sessions.
Google account access and use
Connecting Google is optional and requires Google authorization. The current connection requests your account identity, permission to read Gmail messages, permission to send Gmail messages, and permission to read calendars and manage calendar events. Enabling another Google API in a Cloud project does not itself grant POWERHOUSE access to your account or activate an integration.
We use authorized Gmail data to display messages, prepare replies or forwards, maintain selected-inbox preferences, and import sent-message details into contact history. Imported history can include the sender, recipients, subject, snippet, message identifiers, and date. Authorized Calendar data is used to display events and carry out the event actions you request. Email drafts submitted through the workspace email approval workflow remain unsent until the owner approves them.
We use Google user data only to provide or improve the user-facing features for which access was granted. We do not sell Google user data, use it for advertising, or use it to develop, improve, or train generalized artificial-intelligence or machine-learning models. POWERHOUSE 24 SI’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google data is not made available for unrestricted human review. Human access is limited to the account or company users you authorize and access allowed for support with your permission, security, legal compliance, or other purposes permitted by Google’s policies. If you choose to include connected-service information in an AI request, that information may be transmitted to the configured AI provider to fulfill that request; the provider’s applicable terms govern its handling. The no-generalized-training restriction above continues to apply to Google user data.
Company workspaces and employee monitoring
A company owner may connect work mailboxes they are authorized to manage and review company records and activity made available by the configured integrations. Employees may access assigned records when employee access is enabled. Owners are responsible for providing appropriate notice and obtaining any required authorization for employee monitoring. A Google administrator role alone does not connect every mailbox. Personal accounts are not automatically included. Sent-folder history is not proof of delivery, opens, clicks, or the identity of a particular employee using a shared mailbox.
Why we use information
We process information to authenticate users, enforce access permissions, save and retrieve work, support connected-service features, prepare requested AI drafts, record approval outcomes, provide support, and maintain service reliability and security. Features depend on their actual configuration and availability.
Service providers and sharing
POWERHOUSE uses hosting, authentication, database, and file-storage services, including infrastructure provided through OpenAI Sites and Cloudflare. Google processes information for authorized Google services. Optional AI, communications, payment, or other providers receive information when a configured feature requires it. We share only information needed for those functions, authorized company collaboration, security, or legal obligations. We do not sell personal information or share it for cross-context behavioral advertising. Third-party websites and services have their own policies.
Storage and security
Saved workspace records and imported sent history are stored in the service’s cloud database; uploaded files are stored in cloud file storage. Google refresh tokens are encrypted before storage. Browser storage is also used for preferences and drafts, and authentication or authorization cookies maintain sessions and connection flows. Information may be processed in countries where our service providers operate. Access controls and encryption reduce risk but cannot guarantee absolute security.
Retention, disconnecting, and deletion
We retain records while needed to provide your workspace and connected features or meet legitimate security and legal requirements. Disconnecting a mailbox removes its saved connection token from POWERHOUSE; it does not automatically erase previously imported history, company records, or messages already sent through Google. You may also revoke access in your Google Account connections.
To request access, correction, export, or deletion of information, contact terrencejones37@gmail.com with the account email and the data concerned. We may verify identity and company authority before acting. We delete information from systems under our control when a request is verified and applicable retention obligations permit it; backups and independent provider records may follow their own retention schedules. Company-owned employee records may require coordination with the company administrator. Removing information from POWERHOUSE does not delete it from Google unless a separate authorized Google action is performed.
Children and changes
POWERHOUSE is a business service intended for adults and is not directed to children under 13. We may update this policy as the service changes. The effective date identifies the current version; material changes will be described through the service or appropriate contact channels.
