Workflow & Automation · pipedream.comPipedream
Graded against 804 verified platforms, from its own policy text. Automated assessment against a published rubric — not legal advice.
No lens is bandable yet — banding requires fully verified documents with on-criteria findings. The gap is shown honestly, never estimated.
Partially verified: Privacy Policy assessed · Terms of Service pending. Everything below comes only from what was read in full.
Watch: Data retention
Start here. These are the highest-risk verified clauses AIRIN found in the platform's own policy text.
Establishes Pipedream's data retention obligations: retaining data only as long as necessary for the core service, storing workflow code and data store data indefinitely until user deletion, applying account-based retention rules for event and execution log data, deleting most internal and subprocessor logs within 30 days, and retaining a subset of security-investigation logs for longer periods, collectively defining the scope and limits of customer data retention.
This segment restricts user API key usage to testing and CLI scenarios, noting the key provides full cross-workspace access, thereby framing a restriction on when such broad-access credentials should be used.
This segment restricts the permissions of client-side tokens to initiating auth connection flows only, prohibiting them from accessing credentials or performing other REST API operations, and imposes a 4-hour expiry after which a new token must be created.
How to read this page: Overall risk rates what Pipedream's own policy terms mean for your prompts, outputs, and data. The benchmark bands below grade those same verified terms relative to peers — a platform in a risky-by-default category can rate HIGH risk and still grade STRONG against its peer set. Both trace to the cited findings.
Partially verified — Terms of Service — Capture under review; Privacy Policy — Verified (read in full, 37 findings). Findings below are from fully-read, verified documents only; remaining core documents are pending capture.
Needs review
A core policy document is captured but requires review before AIRIN can mark the corpus fully verified.
- Terms of ServiceCompleteness unconfirmedstatic-revalidated
- Privacy PolicyVerified - read in full - 37 citationsstaticLast captured 2026-08-31
Only citation-backed plan differences are shown here; absent cells mean AIRIN has not verified a tier-specific claim.
This segment describes the procedure by which Pipedream handles third-party account linking via OAuth or API keys, explaining how OAuth is preferred and how short-term access tokens are requested, governing how third-party credentials are accessed and managed.
" When you link an account from a third party application, you may be asked to either authorize a Pipedream OAuth application access to your account, or provide an API key or other credentials. This section describes how we handle these gran..."
This segment establishes the procedure for reporting suspected vulnerabilities to Pipedream's security team, including a method for encrypting sensitive disclosures, creating a defined channel for security incident handling.
" If you’d like to report a suspected vulnerability, please contact security@pipedream.com . If you need to encrypt sensitive data as part of your report, you can use our security team’s PGP key . "
This segment describes authentication methods supported by the Pipedream API and recommends OAuth clients over API keys, citing workspace-level administration and scoped access as security reasons, establishing procedural guidance for secure API access.
" The Pipedream API supports two methods of authentication: OAuth and User API keys . We recommend using OAuth clients for a few reasons: ✅ OAuth clients are tied to the workspace, administered by workspace admins"
This segment imposes obligations on the user (secure server-side storage, never exposing secrets in client-side code) and on Pipedream (salting, hashing, and encrypting client secrets at rest, not storing in plaintext), and grants the right to revoke client secrets at any time.
" Pipedream supports client credentials OAuth clients, which exchange a client ID and client secret for a short-lived access token. These clients are not tied to individual end users, and are meant to be used server-side. You must store thes..."
This segment restricts the permissions of client-side tokens to initiating auth connection flows only, prohibiting them from accessing credentials or performing other REST API operations, and imposes a 4-hour expiry after which a new token must be created.
" These tokens can only initiate the auth connection flow. They have no permissions to access credentials or perform other operations against the REST API. They are meant to be scoped to a specific user, for use in clients that need to initi..."
This segment incorporates by reference the REST API Security section for information on how the Pipedream Connect API is secured, cross-referencing security obligations established elsewhere in the document.
" The Pipedream Connect API is a subset of the Pipedream REST API . See the REST API Security section for more information on how we secure the API. "
This segment imposes obligations on the user (not sharing access tokens with end users or storing outside server environment) and describes Pipedream's security measures for tokens (hashing, encryption at rest, 1-hour expiry, revocability), constituting both user-facing restrictions and platform security obligations.
" Since Pipedream uses client credentials grants, access tokens must not be shared with end users or stored anywhere outside of your server environment. Access tokens are issued as JWTs, signed with an ED25519 private key. The public key u..."
This segment restricts user API key usage to testing and CLI scenarios, noting the key provides full cross-workspace access, thereby framing a restriction on when such broad-access credentials should be used.
" ✅ OAuth clients support scopes, limiting access to specific operations When testing the API or using the CLI, you can use your user API key. This key is tied to your user account and provides full access to any resources your user has ac..."
Evidence appendix
Showing priority citations first. The full appendix is available for audit trails; not every citation is a severe risk.
" Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days. We retain a subset of logs for longer periods where required for security investigations. "
Establishes Pipedream's data retention obligations: retaining data only as long as necessary for the core service, storing workflow code and data store data indefinitely until user deletion, applying account-based retention rules for event and execution log data, deleting most internal and subprocessor logs within 30 days, and retaining a subset of security-investigation logs for longer periods, collectively defining the scope and limits of customer data retention.
AI-generated interpretation, not legal advice.
" These tokens can only initiate the auth connection flow. They have no permissions to access credentials or perform other operations against the REST API. They are meant to be scoped to a specific user, for use in clients that need to initiate auth flows. Tokens expire after 4 hours, at which point you must create a new token for that specific user. "
This segment restricts the permissions of client-side tokens to initiating auth connection flows only, prohibiting them from accessing credentials or performing other REST API operations, and imposes a 4-hour expiry after which a new token must be created.
AI-generated interpretation, not legal advice.
" ✅ OAuth clients support scopes, limiting access to specific operations When testing the API or using the CLI, you can use your user API key. This key is tied to your user account and provides full access to any resources your user has access to, across workspaces. "
This segment restricts user API key usage to testing and CLI scenarios, noting the key provides full cross-workspace access, thereby framing a restriction on when such broad-access credentials should be used.
AI-generated interpretation, not legal advice.
" Pipedream implements incident response best practices for identifying, documenting, resolving and communicating incidents. Pipedream publishes incident notifications to a status page at status.pipedream.com and to the @PipedreamStatus Twitter account . Pipedream notifies customers of any data breaches according to our Data Protection Addendum . "
Establishes Pipedream's incident response procedure, including documentation, resolution, public notification via status page and Twitter, and the obligation to notify customers of data breaches per the Data Protection Addendum, linking security incidents to contractual breach-notification duties.
AI-generated interpretation, not legal advice.
" When you link an account from a third party application, you may be asked to either authorize a Pipedream OAuth application access to your account, or provide an API key or other credentials. This section describes how we handle these grants and keys. When a third party application supports an OAuth integration , Pipedream prefers that interface. The OAuth protocol allows Pipedream to request scoped access to specific resources in your third party account without you having to provide long-term credentials directly. Pipedream must request short-term access tokens at regular intervals, and most applications provide a way to revoke Pipedream’s access to your account at any time. Some third party applications do not provide an OAuth interface. To access these services, you must provide the required authorization mechanism (often an API key). As a best practice, if your application provides such functionality, Pipedream recommends you limit that API key’s access to only the resources you need access to within Pipedream. Pipedream encrypts all OAuth grants, key-based credentials, and environment variables at rest in our production database. That database resides in a private network. Backups of that database are encrypted. The key used to encrypt this database is managed by AWS KMS and controlled by Pipedream. KMS keys are 256 bit in length and use the Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM). "
This segment describes the procedure by which Pipedream handles third-party account linking via OAuth or API keys, explaining how OAuth is preferred and how short-term access tokens are requested, governing how third-party credentials are accessed and managed.
AI-generated interpretation, not legal advice.
" Initiate auth with that token, connecting an account for a specific user"
This segment describes the second required step in the authorization procedure: initiating auth with the server-side token to connect an account for a specific user.
AI-generated interpretation, not legal advice.
" Pipedream provides hardware to all new hires. These machines run a local agent that sets configuration of the operating system to hardened standards, including: "
Establishes Pipedream's obligation to provide hardware to new hires configured to hardened security standards via a local agent, governing endpoint security measures that protect customer data access.
AI-generated interpretation, not legal advice.
" Pipedream performs background checks on all new hires. "
Establishes Pipedream's obligation to perform background checks on all new hires, constituting an access-control and personnel security commitment relevant to the protection of customer data.
AI-generated interpretation, not legal advice.
" If you’d like to report a suspected vulnerability, please contact security@pipedream.com . If you need to encrypt sensitive data as part of your report, you can use our security team’s PGP key . "
This segment establishes the procedure for reporting suspected vulnerabilities to Pipedream's security team, including a method for encrypting sensitive disclosures, creating a defined channel for security incident handling.
AI-generated interpretation, not legal advice.
" The Pipedream API supports two methods of authentication: OAuth and User API keys . We recommend using OAuth clients for a few reasons: ✅ OAuth clients are tied to the workspace, administered by workspace admins"
This segment describes authentication methods supported by the Pipedream API and recommends OAuth clients over API keys, citing workspace-level administration and scoped access as security reasons, establishing procedural guidance for secure API access.
AI-generated interpretation, not legal advice.
" Pipedream supports client credentials OAuth clients, which exchange a client ID and client secret for a short-lived access token. These clients are not tied to individual end users, and are meant to be used server-side. You must store these credentials securely on your server, never allowing them to be exposed in client-side code. Client secrets are salted and hashed before being saved to the database. The hashed secret is encrypted at rest. Pipedream does not store the client secret in plaintext. You can revoke a specific client secret at any time by visiting https://pipedream.com/settings/api . "
This segment imposes obligations on the user (secure server-side storage, never exposing secrets in client-side code) and on Pipedream (salting, hashing, and encrypting client secrets at rest, not storing in plaintext), and grants the right to revoke client secrets at any time.
AI-generated interpretation, not legal advice.
" Pipedream provides annual security training to all employees. Developers go through a separate, annual training on secure software development practices. "
Establishes Pipedream's obligation to provide annual security training to all employees and separate annual secure-development training to developers, constituting a personnel security measure that governs protection of customer data.
AI-generated interpretation, not legal advice.
" The Pipedream Connect API is a subset of the Pipedream REST API . See the REST API Security section for more information on how we secure the API. "
This segment incorporates by reference the REST API Security section for information on how the Pipedream Connect API is secured, cross-referencing security obligations established elsewhere in the document.
AI-generated interpretation, not legal advice.
" Pipedream monitors our code, infrastructure and core application for known vulnerabilities and addresses critical vulnerabilities in a timely manner. "
Imposes an obligation on Pipedream to monitor code, infrastructure, and applications for known vulnerabilities and to address critical vulnerabilities in a timely manner, constituting a security commitment that governs the protection of customer data and platform integrity.
AI-generated interpretation, not legal advice.
" Pipedream delivers emails to users for the purpose of email verification, error notifications, and more. Pipedream implements SPF and DMARC DNS records to guard against email spoofing / forgery. You can review these records by using a DNS lookup tool like dig : "
Describes Pipedream's obligation to implement SPF and DMARC DNS records to protect users against email spoofing and forgery, establishing a security measure governing how user communications are protected.
AI-generated interpretation, not legal advice.
" Pipedream uses GitHub to store and version all production code. Employee access to Pipedream’s GitHub organization is protected by multi-factor authentication. Only authorized employees are able to deploy code to production. Deploys are tested and monitored before and after release. "
Establishes Pipedream's obligations regarding secure software development: using GitHub with MFA-protected access, restricting production deployments to authorized employees, and requiring pre/post-release testing and monitoring, all of which govern how customer data and code are protected.
AI-generated interpretation, not legal advice.
" When you use the Pipedream web application at https://pipedream.com , traffic between your client and Pipedream services is encrypted in transit. When you create an HTTP interface in Pipedream, the Pipedream UI defaults to displaying the HTTPS endpoint, which we recommend you use when sending HTTP traffic to Pipedream so that your data is encrypted in transit. All Pipedream-managed certificates, including those we create for custom domains , are created using AWS Certificate Manager . This eliminates the need for our employees to manage certificate private keys: these keys are managed and secured by Amazon. Certificate renewal is also handled by Amazon. "
Imposes an obligation on Pipedream to encrypt data in transit between clients and its services, and describes the technical mechanism (AWS Certificate Manager) used to manage certificates, establishing a security commitment regarding customer data handling.
AI-generated interpretation, not legal advice.
" The execution environment refers to the environment in which your sources, workflows, and other Pipedream code is executed. Each version of a source or workflow is deployed to its own virtual machine in AWS. This means your execution environment has its own RAM and disk, isolated from other users’ environments. You can read more about the details of the virtualization and isolation mechanisms used to secure your execution environment here . Instances of running VMs are called workers . If Pipedream spins up three VMs to handle multiple, concurrent requests for a single workflow, we’re running three workers . Each worker runs the same Pipedream execution environment. Workers are ephemeral —AWS will shut them down within ~5 minutes of inactivity —but you can configure dedicated workers to ensure workers are always available to handle incoming requests. "
This segment describes Pipedream's obligation to isolate each user's execution environment in its own virtual machine with separate RAM and disk, preventing cross-user data access, and defines key technical terms (workers, VMs) relevant to privacy and data isolation commitments.
AI-generated interpretation, not legal advice.
Clause detail — protections, your obligations, and coverage
Every clause below is a verbatim quote from Pipedream's own published policy, read in full and linked to its exact location. Protections and user obligations are reported separately from risk because they are different kinds of clause — an obligation on you is not a risk to your data. Informational only, not legal advice.
✅ Protections found
17 verified clausesClauses in Pipedream's policies that work in your favour — commitments the platform made to you.
- Privacy & data use
“When you link an account from a third party application, you may be asked to either authorize a Pipedream OAuth application access to your account, or provide an API key or other credentials. This section describes how we handle these grants and keys. When a…”
This segment describes the procedure by which Pipedream handles third-party account linking via OAuth or API keys, explaining how OAuth is preferred and how short-term access tokens are requested, governing how third-par…
📍 Privacy Policy › “Third party OAuth grants, API keys, and environment variables”Jump to exact text → - Data retentiondeletion rights & post-termination survival
“Access to administer these keys is limited to specific members of our team. Keys are automatically rotated once a year. KMS has achieved SOC 1, 2, 3, and ISO 9001, 27001, 27017, 27018 compliance. Copies of these certifications are available from Amazon on requ…”
This segment imposes obligations on Pipedream regarding key security: access is limited to specific team members, keys are rotated annually, execution environments are isolated per user, and credentials are not logged by…
📍 Privacy Policy › “Third party OAuth grants, API keys, and environment variables”Jump to exact text → - Audit rights, DPA & residency
“Pipedream is committed to the privacy and security of your data. Below, we outline how we handle specific data and what we do to secure it. This is not an exhaustive list of practices, but an overview of key policies and procedures. It is also your responsib…”
This segment establishes Pipedream's commitment to privacy and security, outlines the scope of the document as covering key policies and procedures for data handling, references SOC 2 compliance, and imposes a shared-res…
- Designated security contact: security@pipedream.com
📍 Privacy Policy › “Skip to main content”Jump to exact text → - Privacy & data use
“When you use the Pipedream web application at https://pipedream.com , traffic between your client and Pipedream services is encrypted in transit. When you create an HTTP interface in Pipedream, the Pipedream UI defaults to displaying the HTTPS endpoint, which…”
Imposes an obligation on Pipedream to encrypt data in transit between clients and its services, and describes the technical mechanism (AWS Certificate Manager) used to manage certificates, establishing a security commitm…
📍 Privacy Policy › “Encryption of data in transit, TLS (SSL) Certificates”Jump to exact text → - Privacy & data use
“Pipedream supports client credentials OAuth clients, which exchange a client ID and client secret for a short-lived access token. These clients are not tied to individual end users, and are meant to be used server-side. You must store these credentials securel…”
This segment imposes obligations on the user (secure server-side storage, never exposing secrets in client-side code) and on Pipedream (salting, hashing, and encrypting client secrets at rest, not storing in plaintext),…
📍 Privacy Policy › “OAuth clients”Jump to exact text → - Privacy & data useproduct telemetry/usage tracking
“Since Pipedream uses client credentials grants, access tokens must not be shared with end users or stored anywhere outside of your server environment. Access tokens are issued as JWTs, signed with an ED25519 private key. The public key used to verify these t…”
This segment imposes obligations on the user (not sharing access tokens with end users or storing outside server environment) and describes Pipedream's security measures for tokens (hashing, encryption at rest, 1-hour ex…
📍 Privacy Policy › “OAuth tokens”Jump to exact text →
+ 11 more verified clauses of this kind on this platform, cited in full in the report.
📋 Rules you must follow
2 verified clausesWhat Pipedream requires of YOU. These are your obligations, not risks to your data or IP, so they are cited here and excluded from this platform's risk rating.
- Moderation & enforcement
“Pipedream provides a client-side SDK to initiate authorization or accept API keys on behalf of your users in environments that can run JavaScript. You can see the code for that SDK here . When you initiate authorization, you must:”
This segment describes the procedure for using Pipedream's client-side SDK to initiate authorization or accept API keys on behalf of users, including a mandatory two-step process for initiating authorization.
📍 Privacy Policy › “Client-side SDK”Jump to exact text → - Moderation & enforcement
“If you suspect Pipedream resources are being used for illegal purposes, or otherwise violate the Pipedream Terms , report abuse here .”
This segment establishes the procedure for reporting suspected illegal use of Pipedream resources and incorporates the Pipedream Terms by reference, creating an enforcement channel for platform abuse.
📍 Privacy Policy › “Reporting abuse”Jump to exact text →
What the policies actually cover
3 topics- Product telemetry & usage tracking2 protective6 clauses
- Deletion rights & post-termination survival4 protective5 clauses
- Breach-notification promises2 protective2 clauses
24 further verified clauses are cited on this page but not yet assigned a topic.
Clause intelligence
Canonical clauses and stance patterns extracted from the same gate-verified citations shown on this page.
The clause allows indefinite, perpetual, or necessity-based retention.
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days....”Open source citation
The clause allows indefinite, perpetual, or necessity-based retention.
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days....”Open source citation
The clause allows indefinite, perpetual, or necessity-based retention.
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days....”Open source citation
The clause allows indefinite, perpetual, or necessity-based retention.
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days....”Open source citation
The clause imposes arbitration, class-action waiver, or jury-trial waiver terms.
“6.1 Governing Law. This Agreement will be governed by and interpreted in accordance with the laws of the state of California, without reference to its conflict of laws principles. If Licensee is located outside of the United States, any dispute, controversy or claim arising out of or relating to this Agreement will be referred to and finally determined by arbitration in accordance with the JAMS International Arbit...”Open source citation
Tier matrix
Plan-level conditions detected from citation-backed clauses. Empty tiers mean AIRIN has not captured decisive tier language yet.
| Tier | Surface | Verdict | Risk | Citations |
|---|---|---|---|---|
| All applicable tiers | data retention | conditional | MEDIUM | 8 |
| All applicable tiers | governing law disputes | conditional | MEDIUM | 2 |
| All applicable tiers | indemnity liability | conditional | MEDIUM | 2 |
| Free | commercial use | worsens | HIGH | 4 |
Policy evolution
Open full timelineBefore/after stance changes across captured policy versions. When no material delta exists yet, AIRIN shows the latest citation-backed stance events instead.
Latest stance: indefinite or necessity based on data retention
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days. We retain a subset of logs for longer periods where required for security investigations.”Open timeline citation
Latest stance: third party or vendor sharing on data retention
“If you choose to delete your Pipedream account, Pipedream deletes all customer data and event data associated with your account. We also make a request to all subprocessors to delete any data those vendors store on our behalf. Pipedream deletes customer data in backups within 30 days.”Open timeline citation
Latest stance: indefinite or necessity based on data retention
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days. We retain a subset of logs for longer periods where required for security investigations.”Open timeline citation
Latest stance: third party or vendor sharing on data retention
“If you choose to delete your Pipedream account, Pipedream deletes all customer data and event data associated with your account. We also make a request to all subprocessors to delete any data those vendors store on our behalf. Pipedream deletes customer data in backups within 30 days.”Open timeline citation
Latest stance: third party or vendor sharing on data retention
“If you choose to delete your Pipedream account, Pipedream deletes all customer data and event data associated with your account. We also make a request to all subprocessors to delete any data those vendors store on our behalf. Pipedream deletes customer data in backups within 30 days.”Open timeline citation
Latest stance: indefinite or necessity based on data retention
“Pipedream retains data only for as long as necessary to provide the core service. Pipedream stores your workflow code, data in data stores, and other data indefinitely, until you choose to delete it. Event data and the logs associated with workflow executions are stored according to the retention rules on your account . Pipedream deletes most internal application logs and logs tied to subprocessors within 30 days. We retain a subset of logs for longer periods where required for security investigations.”Open timeline citation
Latest stance: sublicensable or transferable on commercial use
“1.1 License. Subject to the terms and conditions of this Agreement, Pipedream hereby grants to Licensee a non-exclusive, royalty-free, worldwide, non-transferable, non-sublicenseable license during the term of this Agreement to use, prepare modifications and derivative works, distribute (including without limitation in source code or object code form) and reproduce copies of the Software (the “License”). Licensee is not granted the right to, and Licensee shall not, exercise the License for an Excluded Purpose. For purposes of this Agreement, “Excluded Purpose” means any commercial use of the software including, but not limited to, making available any software-as-a-service, platform-as-a-service, infrastructure-as-a-service or other online service that competes with the Software or any other Pipedream products or services.”Open timeline citation
Latest stance: broad license on commercial use
“1.1 License. Subject to the terms and conditions of this Agreement, Pipedream hereby grants to Licensee a non-exclusive, royalty-free, worldwide, non-transferable, non-sublicenseable license during the term of this Agreement to use, prepare modifications and derivative works, distribute (including without limitation in source code or object code form) and reproduce copies of the Software (the “License”). Licensee is not granted the right to, and Licensee shall not, exercise the License for an Excluded Purpose. For purposes of this Agreement, “Excluded Purpose” means any commercial use of the software including, but not limited to, making available any software-as-a-service, platform-as-a-service, infrastructure-as-a-service or other online service that competes with the Software or any other Pipedream products or services.”Open timeline citation
Capture recency
- Terms of Service:Last captured 2026-08-07· verified 2026-07-03
- Privacy Policy:Last captured 2026-08-31· verified 2026-08-31
Dates state when our pipeline captured and verified each document — not when the vendor last changed it. Documents are re-scanned on a recurring cadence; a document verified once says so until a re-scan confirms it again.
↑ 26 more findings this quarter vs last (88 vs 62). First scan: June 2026.
Compare and stack are saved in your browser. Open compare · View your stack. A correction triggers an automated re-read of Pipedream's policies — no human edits the data.
Need this for procurement or legal diligence?
Free shows today's risk. A Stack Audit gives you a citable, verbatim-sourced PDF across your whole AI stack — and flags the moment a vendor's terms change.
Know where the missing document lives?
We haven't yet verified Pipedream's Terms of Service. Point us at the official page and our pipeline will attempt to capture and read it in full. Submissions are candidates only — nothing is published until it passes the same verification gates as every other document on this site.
Every finding above is a verbatim quote from Pipedream's own published policy, captured to an immutable snapshot and read in full through a two-gate verification pipeline. Confidence labels and any analysis are AI-generated and informational only — not legal advice.
AIRIN Brief
Built for compliance officers, legal counsel, and SaaS founders. Subscribe to the email digest — one short brief when a tracked vendor materially changes its terms, training policy, or risk rating. Prefer in-app? Watch platforms in your alerts inbox instead.