パーティー
本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.