Bricks

Bricks Privacy Policy

Effective June 14, 2026. Bricks is a workspace-based field intelligence app for solar and home-services teams. This policy explains the data Bricks handles to record pitches, score field conversations, coach reps, and run a protected company workspace.

What Bricks Collects

Account details such as name, email, role, office, workspace, login activity, and access status.
Field recording details such as customer name, address, phone or email when entered, pitch type, outcome, score, transcript, audio file, coaching notes, clips, and review history.
Optional location context when a rep allows location access, including coordinates or address context used to tag a recording or inspect a nearby roof.
Operational data such as app version, request state, audit events, processing status, and error information needed to run and secure Bricks.

How Bricks Uses Data

To let reps record pitches, upload or save audio, and review feedback.
To transcribe, score, summarize, and coach recordings using the Bricks Way and manager-approved rubrics.
To help managers and owners review team activity, assign coaching, manage access, and monitor retention or failed processing.
To keep Bricks secure, prevent unauthorized access, debug issues, and maintain audit history.

AI Processing

Bricks sends recordings, transcripts, and related coaching context to server-side AI providers only to transcribe, score, summarize, and generate coaching outputs for the signed-in workspace.
API keys stay on Bricks servers and are not stored in the iOS app.
Bricks does not sell field recordings, transcripts, or coaching data.

Sharing And Access

Workspace owners and managers can access recordings and coaching data according to their role and office permissions.
Service providers such as hosting, database, email, maps, storage, and AI infrastructure process data only as needed to operate Bricks.
Bricks may disclose information if required to comply with law, protect the service, or prevent misuse.

Retention And Deletion

Workspace owners can configure recording retention. When audio is removed by retention policy, Bricks keeps the business record, score, transcript, coaching output, and audit evidence unless the workspace removes access or data separately.
Access deactivation keeps historical recordings and audit history intact for manager and owner review.
Account deletion, data export, access removal, or retention requests can be started from Bricks Support and should come from the workspace owner or authorized administrator.

Security

Bricks uses authenticated access, role and office scoping, HTTPS, security headers, audit events, and server-side secrets.
No mobile build should contain Google, OpenAI, Anthropic, Resend, Convex, Vercel, or other private service keys.

Contact

For support, privacy, data export, account deletion, access removal, or retention requests, contact your Bricks workspace owner or authorized workspace administrator.