당사자
본 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.