Guardian CRM Privacy Notice
Last updated: September 19, 2026
This notice explains how Guardian Paver Sealing uses Google account and Calendar information in Guardian Paver CRM, its private, owner-operated business workspace. It supplements the Guardian website Privacy Policy. For Google data handled by the CRM, the specific limits in this notice apply if the general website policy describes broader practices.
Who can use the connection
The CRM is restricted to its authorized owner. Google sign-in authorizes the optional Calendar connection; it does not make the CRM public or create customer login accounts. The public CRM overview does not contain customer records.
Google data accessed and stored
With the owner’s permission, Guardian identifies the connected Google account by its email address and stores authorization tokens so the CRM can access Google Calendar on that account’s behalf. Guardian does not receive the account’s Google password.
The connection creates a dedicated Guardian Paver Sealing calendar and accesses events in that calendar. Stored information includes the calendar identifier, account email, event identifiers, titles, descriptions, locations, start and end times, time-zone information, cancellation status, change metadata and synchronization history. Event records can also contain organizer or attendee details and other metadata returned by Google when those fields are present. Please do not place unrelated personal information in the Guardian calendar.
The connection does not request access to existing personal calendars, Gmail messages, Google Contacts or Google Drive file contents. A separate calendar created for Guardian is not the account’s primary personal calendar.
How the information is used
Guardian uses this information to identify the connected account, schedule project visits, synchronize appointment changes, identify conflicts, prevent duplicate appointments, record cancellations and diagnose connection problems. When the owner confirms Sync Now, the CRM may upload customer or company names, project titles, service addresses, visit dates, times and notes to Google. Sync can include past eligible visits.
Changes made in the Guardian calendar can update linked CRM visits. Google-created appointments remain unassigned until the owner links them to an existing project. Conflicting changes are held for review. Deleting a linked Google appointment cancels the CRM visit rather than deleting its project.
Sync is currently requested manually. The setup test creates, reads, reschedules and removes a labeled temporary appointment without uploading customer visits. Always-on background synchronization is not currently enabled.
Storage, sharing and security
Google processes appointment information transmitted to Google Calendar. CRM records are stored in Guardian’s private hosted application, operated using OpenAI Sites and Cloudflare infrastructure. These hosting services process information needed to run and secure the application. Google authorization tokens are encrypted by the CRM before storage and are kept server-side, rather than in public website pages or browser code. Access to CRM records is restricted to the authorized owner. No system can guarantee absolute security.
Guardian does not sell Google account or Calendar data, provide it to data brokers, or use it for advertising or credit decisions. Use and disclosure are limited to the described CRM features, necessary security and support activities, the account owner’s specific direction, and applicable legal requirements. Any support access must be authorized for the relevant information or necessary for security or legal purposes.
The Calendar connection does not automatically send event information to an AI model. Private automatic ChatGPT quote uploads and Outlook email integration are not currently enabled. A future connection or materially different data use will require updated disclosures and any necessary separate permission before it is enabled.
Guardian’s use and transfer of information received from Google APIs is limited by this notice and the Google API Services User Data Policy, including its applicable Limited Use requirements.
Retention, deletion and disconnecting
The current CRM does not automatically erase imported Calendar records or synchronization history after a fixed number of days. Information remains available for project scheduling, business records, troubleshooting and recovery until removed through applicable CRM controls or an approved deletion request, subject to legal, security and recordkeeping needs.
Moving a CRM record to Trash is not permanent erasure. Trash is not emptied automatically. Records linked to payment history are protected from permanent deletion. Limited identifiers and synchronization metadata may be retained to prevent duplicate or accidentally recreated records. Deleting a project or visit does not necessarily erase every related synchronization record. Contact Guardian to request review or removal of retained Google-derived information.
The owner can choose Connections → Disconnect to remove the CRM’s stored Google authorization tokens and stop further access through that connection. Disconnecting does not delete the dedicated Google calendar, its appointments or previously imported CRM information. The owner can separately revoke Guardian’s access in Google Account connections and manage the Guardian calendar in Google Calendar. Existing CRM records remain subject to the retention and deletion rules above.
Questions and requests
For questions or requests to access, correct or delete Google-derived information held by Guardian, email guardianpaversealing@outlook.com or call (407) 205-8014. We may need to verify the requester’s identity before acting.
This notice will be updated when the connection’s data practices change. Material changes will be disclosed before the new use, with renewed consent where required. See the Guardian CRM Use Terms for the application’s intended use.