派对
本 DPA 由 Prilog Inc.(“处理者”)与客户(“控制者”)签订。Prilog Inc. 位于 2261 Market Street STE 12675, San Francisco, CA 94114, United States。
// effective date — 12 June 2026
本 DPA 由 Prilog Inc.(“处理者”)与客户(“控制者”)签订。Prilog Inc. 位于 2261 Market Street STE 12675, San Francisco, CA 94114, United States。
一般:hello@prilog.ai
支持:support@prilog.ai
隐私与法律事务:privacy@prilog.ai
地址:2261 Market Street STE 12675, San Francisco, CA 94114, United States
This DPA applies to processing of personal data on behalf of the Controller when using Prilog.ai, including connected observability, repository, task-routing, chat, support, billing, and AI/model workflows.
确定处理个人数据的目的和方式的实体。
Prilog Inc. 按本 DPA 所述代表控制者处理个人数据。
Personal data submitted to Prilog.ai through the service, integrations, support channels, billing workflows, or authorized AI/model workflows.
Provide AI 修复, observability correlation, root-cause summaries, suggested patches, test guidance, pull-request and ticket routing, notifications, billing, support, security, and engineering workflow automation.
For the term of the agreement and any retention period requested by the Controller, configured in the service, stated in an order form, or required by law.
Prilog-controlled service processing occurs in the European Union where available. Customer-enabled integrations, AI/model providers, support, and billing providers may process data in other regions as configured or instructed by the Controller.
Process personal data only on documented instructions from the Controller, including instructions provided through product settings, connected integrations, support requests, and order forms.
确保人员遵守保密义务并接受数据保护培训。
协助控制者处理数据主体请求、DPIA 和监管查询。
Do not use Customer Data to train foundation models or shared model-training datasets. AI/model providers may process prompts, outputs, and context only to provide requested workflows where enabled.
Encryption in transit and at rest, role-based access controls, least privilege, secure authentication, secrets protection, and network controls for systems used to provide the service.
Logging, monitoring, vulnerability and dependency review, access review, incident response procedures, and secure development practices to protect data.
适合服务的备份和弹性实践。
Core providers may include AWS or other cloud infrastructure, PostHog EU analytics, Intercom support messaging, ipapi.co locale lookup, Google Fonts/static delivery, Stripe billing and payment processing where paid billing is used, and SSO providers such as Google, Microsoft, and GitHub when selected.
OpenAI, Anthropic, and customer-configured or self-hosted Ollama-compatible endpoints may process prompts, outputs, and relevant context where the Controller enables AI 修复 workflows.
Controller-enabled providers include observability, logging, tracing, error monitoring, cloud logging, archives, event streams, source control, code hosting, issue tracking, chat, notifications, and session-monitoring tools shown in the service or on the integrations page. Examples include Datadog, SigNoz, Grafana, New Relic, Sentry, Honeycomb, Splunk, Elastic, AWS, GCP, Azure, GitHub, GitLab, Bitbucket, Jira, Linear, Slack, Rollbar, Bugsnag, LogRocket, FullStory, Firebase Crashlytics, Instabug, and Embrace.
我们将通知控制者分包处理者的重大变更,并提供反对的机会。
我们将协助控制者响应数据主体访问、删除或更正数据的请求。
如果我们直接收到请求,我们会将数据发送给控制者。
在意识到个人数据泄露后,我们将立即通知控制者。
通知将包括有关范围、影响和缓解步骤的可用信息。
Prilog-controlled service data is processed in the European Union where available. Transfers outside the EU may occur for customer-enabled integrations, AI/model providers, support, billing, or infrastructure providers based on the Controller's configuration or the provider's infrastructure.
Where international transfers are required, Processor will use appropriate safeguards such as adequacy decisions, Standard Contractual Clauses, or other lawful transfer mechanisms.
终止后,我们将按照指示删除或返还个人数据,除非法律要求保留。
我们将提供合理的信息来证明合规性并在事先通知的情况下接受审核。
Controller employees, contractors, authorized users, support contacts, billing contacts, and end users whose data appears in logs, traces, tickets, alerts, repositories, 代码上下文, Pull Request, support messages, or billing records.
Identifiers, contact details, account roles, authentication metadata, IP-derived locale data, log and trace metadata, error events, stack traces, repository metadata, code snippets, pull-request metadata, ticket and issue metadata, integration configuration, tokens, secrets, billing details, usage data, and support communications.
Collection, storage, retrieval, transmission, analysis, correlation, classification, remediation drafting, ticket and pull-request creation, notification delivery, support, billing, deletion, and export.
Role-based access controls, least privilege, secure authentication, personnel confidentiality obligations, periodic access review, and audit logging.
Encryption in transit and at rest, secure key management, secrets handling, network controls, backup controls, data deletion workflows, and separation between customer workspaces.
备份、监控和灾难恢复程序。
Monitoring, incident response, vulnerability and dependency review, secure development practices, and logging appropriate to the service.