Rules for what you can and cannot do with Pypeo (https://pypeo.com), operated by KVESTERA UAB. This policy forms part of the Terms of Service and covers Pipelines, inlets, joints, connector calls, API traffic and everything else your account can trigger through the Service.
1. Duty of care
You are responsible for what your Pipelines pull in, produce and push out. Design them so they comply with the law where you and the people affected are, and so they respect those people’s rights. When a Pipeline acts on external systems — writing into a CRM, posting to Slack, calling an outside API — the action lands with your identity, and the responsibility lands with you too.
2. Illegal or harmful conduct and content
Do not use Pypeo to plan, prepare, promote, execute or help others carry out anything unlawful. Do not generate or distribute child sexual abuse material or content sexualising minors, incitement to violence or terrorism, targeted harassment, threats, doxxing, content promoting self-harm, or non-consensual intimate imagery. Do not produce material that infringes copyright, trademark or database rights, that leaks trade secrets, or that discloses personal data you have no right to share.
3. Deception and impersonation
No Pipelines that impersonate a real person, brand or institution without their authorisation, no fabricated credentials or attributions, no flood of synthetic reviews or comments, no social-engineering pretexts (phishing, vishing, romance or investment scams), and no interference with elections or democratic processes.
4. Malicious technical activity
No malware, exploit or ransomware development. No unauthorised scanning, probing or intrusion of systems you do not have written permission to test. No credential stuffing, brute forcing, denial-of-service or coordinated abuse. No scraping that violates the target’s terms or the law. No attempts to bypass Pypeo’s safety filters, extract another workspace’s data, or manipulate the ledger.
5. Sensitive use cases
Take extra care where an Output could shape a life-affecting decision — medical, legal, financial, employment, insurance, education, immigration, criminal justice, welfare eligibility. Keep a competent human reviewer in the loop, disclose AI involvement where the law requires it, and follow the domain-specific rules that apply to you.
6. Personal and sensitive data
Only put personal data into a Pipeline if you have a lawful basis and the data subjects have been informed. Do not send special-category data (health, race, political opinion, sexual orientation, biometric identifiers and so on) or children’s data through the Service unless you have all the legal grounding you need and have taken appropriate protective measures.
7. Your API keys and connected services
The keys you supply for model providers and connectors are your responsibility. Do not upload keys you are not authorised to use, do not share workspace access with people who are not authorised to spend against those keys, and revoke keys promptly if you suspect they have leaked. When a Pipeline uses a built-in feature or connects to a service you have set up, respect that service’s rules — robots directives, rate limits, API terms of use, no-scrape signals. Do not point Pypeo at systems as a way of camouflaging your own outbound traffic to evade blocks or attribution.
8. Fair use of the platform
Do not resell raw Pypeo capacity as if it were your own product. Do not run bulk automated Pipelines solely to exhaust promotional tokens or to farm bonuses. Do not create multiple accounts to bypass suspensions, rate limits or fraud controls.
9. Enforcement
We may investigate suspected breaches, ask you for information, restrict features, throttle Pipelines, quarantine outputs, suspend a Pipeline or an account, or terminate access. In serious cases we may act immediately and without warning. Where an incident involves child safety, credible threats to life, or activity that is clearly criminal, we may preserve evidence and cooperate with the relevant authorities.
10. Reporting
To report a suspected breach of this policy by another user or by a Pipeline you have encountered, write to [email protected] with as much detail as you can — identifiers, timestamps, outputs. We treat reports confidentially so far as we can, and we do not tolerate retaliation for a good-faith report.
Contact
KVESTERA UAB · Company code 308067032 · Laisvės pr. 60, LT-05120 Vilnius, Lithuania · +370 661 02858 · [email protected]