How your workspace uses data
This internal Kirpa Properties app uses your managed Google account to identify your active CRM employee account. It requests your basic identity only, with no access to Gmail messages, Drive files or Calendar.
When you register a lead, the pasted client message is sent to the configured OpenAI API for field extraction and saved in Kirpa’s CRM with the lead. The app requests that OpenAI not store the response; the provider’s applicable data handling terms still apply. No advertising trackers are installed.
The app uses an essential sign-in cookie for up to eight hours. It temporarily stores drafts and submission receipts in the company Cloudflare account to prevent duplicate submissions and resolve unconfirmed saves. Unsubmitted drafts expire after one day; completed receipts expire after 30 days. Unconfirmed writes remain for IT review. CRM records follow Kirpa’s CRM retention practices.
The portal reads current CRM leads assigned to you or credited to you as the original generator. Client contact details, requirements, comments and activities are shown only while you are the assigned handler. Submission history shows your own receipts. Stage changes and comments are managed in CRM.
A company identity registry binds your verified Google subject to one CRM employee. Lead detail access is recorded with your CRM employee ID, the lead ID and time, retained for 90 days. It does not copy client messages into the access log. Sign-in identities remain until removed by Kirpa IT.
Historical source credit is indexed from explicit employee references and verified source routes. The index stores CRM lead IDs, employee IDs and source evidence; unresolved attribution is held for review. It contains no client contact fields. Operations staff can see service-health summaries and redacted error references. Operational error records expire after 30 days.
Content and Schedule read only the Content OS creator profile explicitly linked to your employee account. They display production status, recorded dates and version history. Only the latest available approved file can be streamed or downloaded through the signed-in portal. Google Drive credentials remain in Content OS. The portal does not request Drive or Calendar permission from your Google account.
Performance reads your own published Momentum figures through a server-authenticated connection. It preserves the source ranking rules and pending data. CRM care counts your authored comments on checked assigned leads and activities you created in the last 30 days. It does not measure CRM login time. Cached checks and portal visit-day records expire after 90 days.
Requests and their responses are stored for you and portal operations. Operations publishes company resource links; your acknowledgement records the resource version. These records remain until Kirpa IT removes them under the company’s retention process. No external message is sent when you create a request. In-portal notifications and access audit records expire after 90 days.
Use only client information Kirpa is authorized to process. Contact Kirpa IT for access, correction or deletion requests.