Parti
Questo DPA è tra Prilog Inc. ("Responsabile del trattamento") e il cliente ("Titolare"). Prilog Inc. si trova presso 2261 Market Street STE 12675, San Francisco, CA 94114, Stati Uniti.
// effective date — 12 June 2026
Questo DPA è tra Prilog Inc. ("Responsabile del trattamento") e il cliente ("Titolare"). Prilog Inc. si trova presso 2261 Market Street STE 12675, San Francisco, CA 94114, Stati Uniti.
Generale: hello@prilog.ai
Supporto: support@prilog.ai
Privacy e legale: privacy@prilog.ai
Indirizzo: 2261 Market Street STE 12675, San Francisco, CA 94114, Stati Uniti
This DPA applies to processing of personal data on behalf of the Responsable when using Prilog.ai, including connected observability, repository, task-routing, chat, support, billing, and AI/model workflows.
L’entità che determina le finalità e i mezzi del trattamento dei dati personali.
Prilog Inc. tratta dati personali per conto del Titolare come descritto in questo DPA.
Personal data submitted to Prilog.ai through the service, integrations, support channels, billing workflows, or authorized AI/model workflows.
Provide Remediation con IA, 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 Responsable, 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 Responsable.
Process personal data only on documented instructions from the Responsable, including instructions provided through product settings, connected integrations, support requests, and order forms.
Garantire che il personale sia vincolato da obblighi di riservatezza e formato sulla protezione dei dati.
Assistere il Titolare con richieste degli interessati, DPIA e richieste normative.
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, respuesta a incidentes procedures, and secure development practices to protect data.
Backup e pratiche di resilienza adeguate al servizio.
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 Responsable enables Remediation con IA workflows.
Responsable-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.
Informeremo il Titolare del trattamento delle modifiche sostanziali ai subresponsabili del trattamento e offriremo l'opportunità di opporsi.
Assisteremo il Titolare nel rispondere alle richieste degli interessati di accesso, cancellazione o correzione dei dati.
Qualora riceviamo direttamente una richiesta, indirizzeremo l'interessato al Titolare.
Informeremo il Titolare senza indebito ritardo dopo essere venuti a conoscenza di una violazione dei dati personali.
Le notifiche includeranno le informazioni disponibili su ambito, impatto e misure di mitigazione.
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 Responsable's configuration or the provider's infrastructure.
Where international transfers are required, Encargado will use appropriate safeguards such as adequacy decisions, Standard Contractual Clauses, or other lawful transfer mechanisms.
Al momento della risoluzione, elimineremo o restituiremo i dati personali come indicato, a meno che la conservazione non sia richiesta dalla legge.
Forniremo informazioni ragionevoli per dimostrare la conformità e consentire gli audit con preavviso.
Responsable employees, contractors, authorized users, support contacts, billing contacts, and end users whose data appears in logs, traces, tickets, alerts, repositories, contesto del codice, 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.
Procedure di backup, monitoraggio e ripristino di emergenza.
Monitoring, respuesta a incidentes, vulnerability and dependency review, secure development practices, and logging appropriate to the service.