> ## Documentation Index > Fetch the complete documentation index at: https://support.parker.work/llms.txt > Use this file to discover all available pages before exploring further. # Data, privacy, and sharing > What Parker keeps from each thing you send and for how long, where the Salesforce copy ends up, what the audit records, and who sees what you share. Salesforce is the source of truth for your records. Parker also keeps its own copy of your chats, and of some of what you send in them, so you can reopen a conversation and see what was said. This page says what stays where. For the legal terms, see the [Privacy policy](https://parker.work/privacy). ## What Parker keeps from what you send | You send | Salesforce gets | Parker keeps | Processed by | | - | - | - | - | | A message, on any channel | Nothing, unless you confirm a change | The text, in your chat history | Parker's AI provider, to understand and answer it | | A photo for a case (Parker app) | The photo, attached to the case when you confirm | Held in a separate encrypted store until it's attached, or for 24 hours, then deleted. It isn't added to your Files. | Parker's AI provider, to read the label or fault | | A photo or document in an ordinary chat (web app or Parker app) | The file, if you ask Parker to attach it to a record | The file, in your [Files](https://support.parker.work/library/files.md), until you delete it | Parker's AI provider, to read it | | A business-card photo | A lead or contact, when you confirm | Nothing. The photo is read once, in memory, and isn't stored. | Parker's AI provider, to read the card | | A shared contact (vCard) | A lead or contact, when you confirm | The name, company, title, phone numbers, and email addresses, with the message. Birthdays, addresses, and web links are dropped. | Parker | | A voice note | The change you confirm, if any | The transcript, as your message in the chat, marked as a voice note. The recording is never stored. | A speech-to-text provider, for the transcript | | Your location, to check in | The visit you confirm, on the account | Nothing. Parker reads the coordinates once to find nearby accounts and then redacts them. They never go into the message text or Parker's memory. If check-in isn't turned on for your workspace, a shared pin arrives as a plain message with its coordinates, like any text. | Parker | | A video | The video, attached as it is when you confirm | As a chat attachment | Nobody reads it | | A file you attach in the web app | Nothing, unless you ask Parker to attach it | The file, in your Files, until you delete it. Deleting a chat keeps its files unless you choose **Delete it too**. Deleted files are purged after 30 days. | Parker's AI provider, to read it | **Memories** are separate. Parker saves lessons and preferences from your chats, and you can see, edit, mute, or forget them in **Settings** > **Memories**. See [How memory works](https://support.parker.work/chat/memory-and-private-chats.md). ## What Parker records about a Salesforce change | Where | What it shows | | - | - | | **The record in Salesforce** | **Created By** or **Last Modified By** is the person who confirmed the change, because Parker saves it with their own Salesforce login. The timestamp is when Salesforce saved it. | | **Salesforce field history** | Only if your Salesforce admin has turned on history tracking for that object and field. Parker doesn't change what Salesforce tracks. | | **Parker's write audit** (**Settings** > **Connections** > **Salesforce** > **Advanced** > **Recent Salesforce writes**) | Who, which object and record, which fields, whether it was Test or Live, and whether it succeeded. Field names only: Parker never stores the values. | | **The chat** | The card you confirmed, and Parker's reply with the result. | Parker never writes to Salesforce under a service account for anything you do in chat or in the Parker app. If a person's Salesforce login isn't connected, Parker says so rather than using someone else's. ## Who can see what you share Parker checks your Salesforce permissions every time it reads Salesforce. Sharing changes who can see what has **already** been produced. | You share | The recipient sees | New questions run as | | - | - | - | | **A chat** | Every message in it so far, including answers and files attached to it, whatever their own Salesforce access. Shares default to **participant**, which lets them ask follow-ups in the chat. **Read-only** lets them read it. | Themselves. A follow-up they ask uses their own Salesforce login, so they may see less than you did. | | **A page** | The published version. They don't see drafts you're still editing. Pages that refresh on a schedule publish a new version each time, which recipients see. | The page's owner. A refresh runs with the owner's Salesforce login, not the recipient's. | | **A routine's results** | The run's chat and page, shared with each recipient at the level you chose. | The routine's owner. The routine runs with the owner's Salesforce login, and stops if the owner leaves the workspace. | So before you share, ask: would this person be allowed to see these records in Salesforce? Parker won't filter an answer that already exists. See [Find, organise, and share chats](https://support.parker.work/chat/sharing-and-history.md) and [Find and share your pages](https://support.parker.work/library/pages.md). ## What your admin can see * **Recent Salesforce writes** for the whole workspace, as above. * **Automations** across the workspace, in **Automations admin**. * **Rule checks** and their results, in **Oversight**. * **Memories** marked as team memories. Admins don't see your private chats unless you share them. ## Still need help? Check [Troubleshooting](https://support.parker.work/reference/troubleshooting.md) for the exact message you see. If a setting is admin-only, ask your Parker admin. For anything else, [contact support](https://support.parker.work/reference/contact-support.md). ## Related > [card] [How Parker acts on your behalf](https://support.parker.work/get-started/how-parker-acts.md) > > Confirm, Test and Live mode, and audit. > [card] [Governance](https://support.parker.work/admin/governance.md) > > For admins: controls and records. > [card] [Limits and supported files](https://support.parker.work/reference/limits.md) > > Sizes, counts, and time windows. > [card] [Permissions](https://support.parker.work/reference/permissions.md) > > Admins, members, and Parker support. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.