Privacy policy
Last updated 5 November 2026
PipelineLabs ("we", "us") is outreach software operated by Tatiana Libreros in Dubai, United Arab Emirates. This policy explains what personal data we handle when you use pipelinelabs.live, the PipelineLabs app, the PipelineLabs Chrome extension and the PipelineLabs AI assistant connector. Contact: hello@pipelinelabs.live.
Two kinds of data
- Your account data. We are responsible for it (controller).
- Your leads and conversations, the contacts you import or find and the messages exchanged with them. You decide what to collect and why; we process it on your instructions (processor). You are responsible for having a lawful basis to contact them.
What we collect
- Account: name, email, company, password (stored hashed by our authentication provider), plan and billing status.
- Connected channels: to send from your own accounts we store the access tokens Google or Microsoft give us for your mailbox (encrypted), and the connection status your Chrome extension reports for WhatsApp, LinkedIn and Instagram. Your passwords for those services never reach us.
- Outreach content: leads (names, companies, emails, phone numbers, profile links), campaigns, sequences, messages sent and replies received.
- Usage and safety data: send counts, daily limits, account-safety events, logs needed to run and secure the service.
- AI assistant connections: when you connect Claude, ChatGPT or another assistant, we store the connection's name, access level and last use. Its access key is stored only as a one-way hash.
- Website visitors: Google Analytics and the Meta Pixel on our public pages measure visits and ad performance using cookies.
How we use it
- To run the service: send your campaigns, receive replies, enforce daily limits and pause sequences when someone replies.
- To draft messages and replies with AI, which you can review before they go out.
- To find public business information for lead discovery when you turn that on.
- To bill you, provide support, keep accounts safe and meet legal obligations.
We do not sell personal data, and we do not use your leads or conversations to train AI models.
Service providers
We share data only with providers that help us run PipelineLabs, under their data protection terms:
- Supabase (database and authentication) and Vercel (hosting).
- Stripe (payments; we never see full card numbers).
- Anthropic (AI drafting; content is sent for processing and not used to train their models).
- Google and Microsoft (sending and reading email from mailboxes you connect).
- Our email delivery provider (our own service emails, such as account-safety alerts).
- Apify (collecting public business listings for lead discovery).
- Google Analytics and Meta (website measurement, public pages only).
These providers may process data outside your country, including in the United States and the European Union.
Google user data
Data we receive from Google APIs is used only to send your outreach email, detect replies and show them in your inbox. Its use complies with the Google API Services User Data Policy, including the Limited Use requirements. It is not used for advertising and not shared except as needed to provide these features.
AI assistants
A connected assistant can only do what you approved: read status, campaigns and recent replies, and with manage access pause or resume campaigns and add leads. It cannot send messages. What the assistant does with the data it reads is governed by that assistant provider's own privacy policy. Disconnect any time in Settings, Integrations, AI assistants; access ends immediately.
Retention
We keep your data while your account is active. When you close your account we delete it, along with your leads and conversations, within 30 days, except records we must keep for tax or legal reasons.
Your rights
You can access, correct, export or delete your data, and object to or restrict its use, by emailing hello@pipelinelabs.live. If you are a lead contacted through PipelineLabs, you can ask us to stop processing your details; we will pass the request to the customer who contacted you and remove you from their campaigns. You may also complain to your local data protection authority.
Security
Data is encrypted in transit, mailbox tokens are encrypted at rest, access keys are stored as hashes, and each workspace can only reach its own data.
Changes
We will post updates here and tell account holders by email about significant changes.