पार्टियाँ
यह DPA Prilog Inc. ("Processor") और ग्राहक ("Controller") के बीच है। Prilog Inc. का पता 2261 Market Street STE 12675, San Francisco, CA 94114, United States है।
// effective date — 12 June 2026
यह DPA Prilog Inc. ("Processor") और ग्राहक ("Controller") के बीच है। 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 में वर्णित अनुसार Controller की ओर से personal data प्रोसेस करता है।
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.
सुनिश्चित करें कि कर्मचारी गोपनीयता दायित्वों से बंधे हैं और डेटा सुरक्षा पर प्रशिक्षित हैं।
डेटा विषय अनुरोधों, डीपीआईए और नियामक पूछताछ में नियंत्रक की सहायता करें।
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 requests, 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.