Verwerkersovereenkomst (DPA)

Partijen

Deze DPA is gesloten tussen Prilog Inc. ("Verwerker") en de klant ("Verwerkingsverantwoordelijke"). Prilog Inc. is gevestigd op 2261 Market Street STE 12675, San Francisco, CA 94114, Verenigde Staten.

Contact

Algemeen: hallo@prilog.ai
Ondersteuning: support@prilog.ai
Privacy en juridisch: privacy@prilog.ai
Adres: 2261 Market Street STE 12675, San Francisco, CA 94114, Verenigde Staten

Reikwijdte

This DPA applies to processing of personal data on behalf of the Verantwortlicher when using Prilog.ai, including connected observability, repository, task-routing, chat, support, billing, and AI/model workflows.

Controleur

De entiteit die het doel en de middelen voor de verwerking van persoonsgegevens bepaalt.

Verwerker

Prilog Inc. verwerkt persoonsgegevens namens de Verwerkingsverantwoordelijke zoals beschreven in deze DPA.

Klantgegevens

Personal data submitted to Prilog.ai through the service, integrations, support channels, billing workflows, or authorized AI/model workflows.

Doel

Provide AI-remediatie, observability correlation, root-cause summaries, suggested patches, test guidance, pull-request and ticket routing, notifications, billing, support, security, and engineering workflow automation.

Duur

For the term of the agreement and any retention period requested by the Verantwortlicher, configured in the service, stated in an order form, or required by law.

Locatie

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 Verantwortlicher.

Instructies

Process personal data only on documented instructions from the Verantwortlicher, including instructions provided through product settings, connected integrations, support requests, and order forms.

Vertrouwelijkheid

Zorg ervoor dat het personeel gebonden is aan vertrouwelijkheidsverplichtingen en getraind is op het gebied van gegevensbescherming.

Hulp

Assisteren van de Verwerkingsverantwoordelijke bij verzoeken van betrokkenen, DPIA’s en vragen van toezichthouders.

No model training

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.

Technische beveiligingen

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.

Operationele beveiligingen

Logging, monitoring, vulnerability and dependency review, access review, Incident Response procedures, and secure development practices to protect data.

Beschikbaarheid

Back-ups en veerkrachtpraktijken die geschikt zijn voor de service.

Kern-subverwerkers

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.

AI and model subprocessors

OpenAI, Anthropic, and customer-configured or self-hosted Ollama-compatible endpoints may process prompts, outputs, and relevant context where the Verantwortlicher enables AI-remediatie workflows.

Customer-enabled integrations

Verantwortlicher-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.

Veranderingen

Wij zullen de Verwerkingsverantwoordelijke op de hoogte stellen van materiële wijzigingen bij subverwerkers en de mogelijkheid bieden om bezwaar te maken.

Hulp

Wij zullen de Verwerkingsverantwoordelijke assisteren bij het reageren op verzoeken van betrokkenen om toegang te krijgen tot gegevens, deze te verwijderen of te corrigeren.

Directe verzoeken

Als wij rechtstreeks een verzoek ontvangen, zullen wij de betrokkene doorverwijzen naar de Verwerkingsverantwoordelijke.

Let op

Wij zullen de Verwerkingsverantwoordelijke zonder onnodige vertraging op de hoogte stellen nadat wij ons bewust zijn geworden van een inbreuk in verband met persoonsgegevens.

Details

Meldingen bevatten beschikbare informatie over de reikwijdte, impact en mitigatiestappen.

EU-first processing

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 Verantwortlicher's configuration or the provider's infrastructure.

Waarborgen

Where international transfers are required, Auftragsverarbeiter will use appropriate safeguards such as adequacy decisions, Standard Contractual Clauses, or other lawful transfer mechanisms.

Einde dienst

Bij beëindiging zullen wij persoonlijke gegevens verwijderen of retourneren zoals aangegeven, tenzij bewaring wettelijk verplicht is.

Controle

We zullen redelijke informatie verstrekken om naleving aan te tonen en audits mogelijk maken met voorafgaande kennisgeving.

Betrokkenen

Verantwortlicher employees, contractors, authorized users, support contacts, billing contacts, and end users whose data appears in logs, traces, tickets, alerts, repositories, codecontext, pull requests, support messages, or billing records.

Gegevenscategorieën

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.

Verwerkingshandelingen

Collection, storage, retrieval, transmission, analysis, correlation, classification, remediation drafting, ticket and pull-request creation, notification delivery, support, billing, deletion, and export.

Toegangsbeheer

Role-based access controls, least privilege, secure authentication, personnel confidentiality obligations, periodic access review, and audit logging.

Gegevensbescherming

Encryption in transit and at rest, secure key management, secrets handling, network controls, backup controls, data deletion workflows, and separation between customer workspaces.

Beschikbaarheid

Back-ups, monitoring en noodherstelprocedures.

Security operations

Monitoring, Incident Response, vulnerability and dependency review, secure development practices, and logging appropriate to the service.