Jul 20, 2026privacyhigh
data sharing
Latest stance: sale or sell
“Prevent fraud, abuse, and misuse. We do not sell personal data, and we do not use Customer content or Customer-identifiable usage data to serve third-party advertising.”Open citation
Peppr AI policy evolution
Before/after stance changes across captured policy versions, with exact citations. If no before/after delta is available yet, AIRIN shows the latest citation-backed stance events instead.
Diffs
0
Improved
0
Worsened
0
Changed
0
No before/after stance delta is available for this filter yet. Latest citation-backed stance events are shown below.
Jul 20, 2026trainingmedium
data sharing
Latest stance: third party or vendor sharing
“Peppr uses AI models to transcribe conversations, detect questions, and generate answers grounded in a Customer’s connected knowledge. What this involves - and where the data goes - depends on the deployment model, so we describe each directly. No cross-customer training. We do not use one Customer’s content, transcripts, or AI outputs to train, tune, or improve any model or instance made available to any other Customer. Each deployment is grounded only on the knowledge that Customer connects, for that Customer’s instance alone. In-environment / on-premise (BYOC) deployments. Customers connect Peppr to their own model endpoints - they bring their own models. Customer content and AI outputs never leave the Customer’s environment or reach Peppr-controlled infrastructure, so Peppr has no ability to retain, train on, or improve any model from them. The retention and data-use terms that govern inference are those of the Customer’s own agreement with the model provider it chooses to connect. Hosted (cloud) deployments. Transcription and answer generation are performed by subprocessors Peppr engages to operate the Service (see Section 7), under contractual data-protection terms. Retention and data-use terms depend on the provider and are set out in the applicable order form or data processing addendum. Customers with strict zero-retention requirements can meet them through an in-environment (BYOC) deployment.”Open citation
Jul 20, 2026privacymedium
data sharing
Latest stance: third party or vendor sharing
“We share information only as needed to run the Service: Subprocessors - vetted vendors that provide infrastructure, transcription, model/inference, analytics, and support services on our behalf, under contractual data-protection obligations. A current list of subprocessors is available on request at support@usepeppr.ai. Within a Customer’s organization - the Service surfaces information to Users consistent with the access controls the Customer configures; a User sees only what they are entitled to see. Legal and safety - where required by law or legal process, or to protect the rights, safety, and security of Peppr, our Customers, or others. Business transfers - in connection with a merger, acquisition, or sale of assets, subject to this policy. We do not share Customer content or Customer-identifiable usage data with third parties for their own purposes.”Open citation
Jul 20, 2026traininglow
model training
Latest stance: no training claim
“Peppr uses AI models to transcribe conversations, detect questions, and generate answers grounded in a Customer’s connected knowledge. What this involves - and where the data goes - depends on the deployment model, so we describe each directly. No cross-customer training. We do not use one Customer’s content, transcripts, or AI outputs to train, tune, or improve any model or instance made available to any other Customer. Each deployment is grounded only on the knowledge that Customer connects, for that Customer’s instance alone. In-environment / on-premise (BYOC) deployments. Customers connect Peppr to their own model endpoints - they bring their own models. Customer content and AI outputs never leave the Customer’s environment or reach Peppr-controlled infrastructure, so Peppr has no ability to retain, train on, or improve any model from them. The retention and data-use terms that govern inference are those of the Customer’s own agreement with the model provider it chooses to connect. Hosted (cloud) deployments. Transcription and answer generation are performed by subprocessors Peppr engages to operate the Service (see Section 7), under contractual data-protection terms. Retention and data-use terms depend on the provider and are set out in the applicable order form or data processing addendum. Customers with strict zero-retention requirements can meet them through an in-environment (BYOC) deployment.”Open citation
Generated from live stance events. Informational only, not legal advice.
📢 POLICY UPDATES ALERT
AIRIN Brief
Built for compliance officers, legal counsel, and SaaS founders. Subscribe to the email digest — one short brief when a tracked vendor materially changes its terms, training policy, or risk rating. Prefer in-app? Watch platforms in your alerts inbox instead.