Privacy Policy
How P-Core Assistant collects, uses, and protects your data · Last updated: October 18, 2026
1. Data We Collect
We collect the following non-sensitive data:
- Chat messages: Content you send through the chat interface, stored locally on our servers to provide the service.
- Device information: Device type (mobile, tablet, desktop) for analytics purposes.
- IP address: Your IP address is used in memory for rate limiting (sign-in lockout and request caps) and is never stored in analytics. An IP address (and, for guest chats, your browser's user-agent string) is stored only where the service needs it to work: your login session, guest-chat identity (to restore your chat history, kept up to 14 days), contact-form submissions (abuse handling), the admin audit trail, security logs for blocked prompt-injection attempts. Server request logs in the system journal also carry your IP address and user-agent for operations debugging.
- Page views: Pages visited within the Service for improving user experience.
2. How We Use Data
- To provide and maintain the Service.
- To improve the quality of the Service.
- For analytics to understand how users interact with the Service.
- To prevent abuse and ensure rate limiting.
3. Google User Data We Access
When you connect a Google account, P-Core Assistant receives Google user data from Google's APIs through the scopes you approve. These are the capability groups this app can request:
- Sign-in identity — Google's standard account-identification step of the connection handshake (openid / email / profile), which this app asks for on every connect. We do not store the email address or basic profile that step returns, and we build no profile from it: the link between you and the connected account is keyed by your own account id in this app. Scope URIs requested: openid, email, profile, https://www.googleapis.com/auth/userinfo.email, https://www.googleapis.com/auth/userinfo.profile.
- Gmail — Search, list and read your messages, create and update drafts, send mail you ask the assistant to send, and move messages to the trash. Scope URIs requested: https://www.googleapis.com/auth/gmail.modify, https://www.googleapis.com/auth/gmail.send.
- Google Drive — List, download, upload, update and delete files — limited to files this app creates and files you open with it, not your whole Drive. Scope URIs requested: https://www.googleapis.com/auth/drive.file.
- Google Docs — Create, read, update and delete documents you ask about. Scope URIs requested: https://www.googleapis.com/auth/documents.
- Google Sheets — Create spreadsheets and read, append, update or clear the cell values you point the assistant at. Scope URIs requested: https://www.googleapis.com/auth/spreadsheets.
- Google Calendar — Read the events on your calendars and create or update events for you. Scope URIs requested: https://www.googleapis.com/auth/calendar.events.
- Google Tasks — List, create, update and delete tasks in your task lists. Scope URIs requested: https://www.googleapis.com/auth/tasks.
- Google Contacts — Search, list, create, update and delete contacts in your account. Scope URIs requested: https://www.googleapis.com/auth/contacts, https://www.googleapis.com/auth/contacts.readonly.
- Google Meet — Create and read meeting spaces (meeting links) and list conference records and participants for meetings this app created. Scope URIs requested: https://www.googleapis.com/auth/meetings.space.created, https://www.googleapis.com/auth/meetings.space.readonly.
A scope is requested only from the groups listed above, and only while you are connecting an account. The shipped connect flow asks for all of those groups in a single consent; Google's token response is always authoritative about what was actually granted.
4. How We Use Google User Data
- Google user data is used only to provide the in-app features listed above, at your request. We do not use it for advertising, we do not build advertising or behavioural profiles from it, we do not sell it, and we do not use it to determine creditworthiness or for lending purposes.
- Google user data leaves our servers only in these cases: it is sent to the AI model provider configured for this deployment, solely to generate the reply you asked for (that provider processes the turn under its own terms and privacy policy); the reply — which can contain information read from Google at your request — is returned to the client you asked from, meaning your browser for a web chat or the chat platform's own delivery API (Telegram's Bot API) when the request arrived through the connected Telegram bot; or it is disclosed where the law requires it. It is never transferred to anyone else.
P-Core Assistant's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements — Google API Services User Data Policy.
5. Google Data Storage, Retention and Deletion
- The OAuth access and refresh tokens are encrypted at rest with AES-256-GCM (stored as an enc:v1: value in the account-link table) and are used only to call the Google APIs for the account that granted them. We do not store the email address or profile returned by the identity scopes: the connect handshake uses them for the identification step, the link is keyed by your own account id in this app, and the workspace panel reads back only the granted scopes and the token expiry.
- A started-but-unfinished consent is single-use and expires after 10 minutes; expired rows are purged on the next connect attempt.
- The Google data a tool reads (a message, event, file, document or task) is used to answer that turn and is not stored as Google data. The reply text produced from it is stored in your conversation history exactly like any other message.
- If an administrator ingests a Google document into the assistant's knowledge base, that document's text is stored on our servers until an administrator deletes it from the knowledge list.
- Settings → Workspace → Disconnect asks Google to revoke the grant first and deletes the stored tokens only after Google answers — either with the revocation confirmed or with the token already being invalid. If Google cannot be reached, the disconnect reports a failure and keeps the tokens instead of claiming a disconnect; if this deployment holds no credentials to revoke with, or has no usable stored token to revoke (none saved, or the saved one cannot be read), the local record is removed and the outcome is reported as a local-only removal, never as a revocation Google confirmed. You can also revoke this app's access at any time from your Google Account's third-party access page.
To have your Google-derived data deleted, use Settings → Workspace → Disconnect, then email support@pcore.dev and we will delete the remaining records (conversation history, ingested documents and usage rows) for your account.
6. Security
- Google OAuth tokens are encrypted at rest with AES-256-GCM and never leave our servers — no token is sent to a browser, a bot platform or the AI model provider.
- Google API calls are made server-side only, one account at a time, with the scopes that account granted.
- Sessions are host-only cookies (HttpOnly, SameSite=Lax, Secure) and every response carries strict transport security; the app never asks for a broader Google scope than the Google Workspace integration you turned on.
7. AI and Google User Data
We do not use Google user data, or data derived from it, to develop, improve or train artificial-intelligence or machine-learning models.
We do not use Google APIs or Google user data to create, generate or distribute AI-generated non-consensual intimate imagery (NCII) or any other prohibited content.
8. Data Storage
All data is stored on servers we control. We do not sell your data and do not share it with third parties except as required to operate the Service or as required by law. An IP address (and, for guest chats, your browser's user-agent string) is stored only where the service needs it to work: your login session, guest-chat identity (to restore your chat history, kept up to 14 days), contact-form submissions (abuse handling), the admin audit trail, security logs for blocked prompt-injection attempts. Server request logs in the system journal also carry your IP address and user-agent for operations debugging. Analytics events store no IP address and no user-agent string. Analytics aggregates are kept for up to 30 days and then deleted.
9. Who Can Read Your Conversations
Administrators of the Service can read conversation content; that access is restricted to authenticated administrators.
10. Cookies
We use minimal cookies for session management and preferences. No tracking cookies are used, and traffic analytics run without cookies — only with your consent, and only as aggregate page-path, device-type, referring-host and day counts retained for up to 30 days. For more details, see our Cookie Policy.
11. Your Rights
- You can request access to your personal data.
- You can request deletion of your data at any time.
- You can request correction of inaccurate data.
- You can opt out of analytics collection.
- You can withdraw this app's access to your Google account at any time: use Settings → Workspace → Disconnect inside P-Core Assistant, email us, or remove the grant from your Google Account's third-party access page.
12. Contact for Data Requests
To exercise your data rights or for any privacy-related inquiries, contact us at support@pcore.dev.