Triple Peak Property Management

Triple Peak CRM privacy

Updated September 26, 2026

This private CRM is operated by Triple Peak Property Management for its authorized team. It organizes owner and prospective-client relationships, correspondence, call and text activity and follow-ups.

Google email connections

With a mailbox owner’s permission, the CRM uses Google’s read-only Gmail permission. This permission allows mailbox reading; the application limits its searches to saved client email addresses and owner-lead notifications from All Property Management. It reads matching message headers and text, including sent messages and delivered group copies. It does not download attachments. It does not send email, change read status, edit messages, or delete anything from Gmail.

Matching correspondence and source links are stored in the CRM and shared with its three authorized team members: Seth, Brian and Alex. Verified owner-lead notifications automatically create or update a matching contact. Uncertain identities remain in Needs attention rather than being attached to the wrong person. Copies across connected mailboxes are deduplicated. The CRM does not use this connection to scan unrelated personal conversations.

Dialpad calls and texts

The CRM reads existing Dialpad call and text records for phone numbers saved on active client contacts. Matching text message content, direction, dates and available attachment descriptions are stored in the CRM and visible to Seth, Brian and Alex. It does not download MMS attachments or send text messages. Unknown, archived or ambiguous phone matches are not automatically added to contacts. New matched conversations can also update the contact summary and next step as described below.

AppFolio owner and property records

The CRM reads limited owner and property identity information from Triple Peak’s AppFolio, including names, contact details, property addresses, record identifiers and active status. It compares this information with saved CRM contacts and addresses to show whether corresponding records exist and provides links for review. Results and check times are stored in the CRM and visible to its authorized team. This connection is read-only: it does not create or edit AppFolio records and does not download banking, tax or financial records. A match confirms record presence; it does not confirm property ownership links or completion of onboarding.

Automatic summaries and next steps

New matching correspondence and available call transcripts are interpreted using the company’s xAI business API connection to keep contact summaries and next steps current. Only limited text from the contact record and recent matching activities is supplied; attachments, mailbox credentials, unrelated conversations and AppFolio financial records are not supplied. Each automatic change retains its prior values and supporting source excerpts in the CRM audit history. Conversation interpretation does not send messages or change fees, contracts or follow-up dates. Separately, verified email, text and answered-call activity can automatically move a new lead to Contacted. The Update review section shows applied changes, prior values and their sources; marking a change reviewed acknowledges it without applying it again. Conflicting changes and uncertain contact matches remain in Needs attention. Contacts marked Not a property owner are excluded from sales follow-ups and automatic conversation interpretation. It preserves existing information when interpretation fails or the record changes during processing. A text being sent or delivered is not treated as owner acceptance.

Interpretation runs only for new conversation content, with limits on context size, output and daily requests. API responses are requested without persistent Responses storage. The provider’s business API data handling is described in its API data and privacy documentation. Team members can ask Seth to disable automatic interpretation; ordinary source activity syncing can continue independently.

Storage and use

CRM records are stored on the company’s hosted server with authenticated access and HTTPS. Google connection credentials are kept separately with restricted server file permissions and are never included in contact exports or ordinary CRM database backups. Imported correspondence remains until the team requests its removal; archiving a contact hides it and stops new matching imports but does not erase it. Daily CRM backups are retained for up to 14 days.

The CRM uses matching email content only for the client-management features described here, including automatic summaries through the company’s business API provider. It does not use email content for advertising, sell it, or use it to train models. Triple Peak CRM’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Your control

You can revoke Google access through your Google account connections. Revoking access stops future reads; it does not automatically remove previously imported CRM records. You can also disconnect a mailbox under Email connections in the CRM. A check already in progress may finish. To request deletion of imported data, contact seth@triplepeakpm.com. Connection failures are shown in the CRM, and saved records remain available.

Return to Triple Peak CRM