# How Does Drippi's Credit System Work? Source: https://drippi.mintlify.app/Credit-System/credits-explained Guide to understanding Drippi's credit system Drippi Credits symbolize our commitment to ensuring the value you receive from Drippi aligns seamlessly with your investment in our service. They play an essential role in accessing various features such as scraping leads, generating AI personalizations, sending messages, and scanning lead profiles to evaluate quality. Drippi offers three distinct credit categories: **AI Credits**, **Lead Credits**, and **Message Credits**. As implied by their names, **AI Credits** cater to AI-intensive tasks such as crafting personalized messages, analyzing Twitter profiles, and executing advanced filtering. **Lead Credits** are designated for importing leads directly from Twitter using the Lead Scraper or the CSV import feature. **Message Credits** are used when sending DMs to leads through automations, follow-ups, or manual outreach. ## Message Credits Message credits are consumed whenever you send a direct message to a lead. Here's how they work: | Action | Credits charged | | ------------------------------------------------------ | ---------------------------- | | Message sent (automations, follow-ups, manual) | 10 credits per message | | Split message (each part) | 10 credits per split message | | Lead skipped — closed DMs | 1 credit | | Lead skipped — previously contacted (if check enabled) | 1 credit | Message credits apply to all outbound messaging: automated cold DMs, follow-up sequences, and manually sent messages. Split messages (messages longer than Twitter's character limit that are sent as multiple parts) charge 10 credits for each part sent. When a lead is skipped (e.g., closed DMs or previously contacted by one of your accounts), 1 credit is deducted. You will not be charged twice for the same lead — only one skip reason applies per lead. ## Utilizing Drippi Credits Below is a comprehensive guide on the various ways you can use Drippi Credits, along with the average amount of credits each action typically consumes: ### AI Credit Usage Screenshot 2025-10-28 at 9.45.22 AM.png ### Lead Credit Usage Screenshot 2025-10-28 at 9.46.31 AM.png For more information on Drippi's CSV format go here: [https://drippi.mintlify.app/leads/csv-import](https://drippi.mintlify.app/leads/csv-import) ### Leads Scanned vs Leads Imported What’s the difference between ***leads scanned*** and ***leads imported***? Let’s say, for example, if you have a lead source that imports followers of an account with 1M followers. Then you apply a filter that removes 98% of the leads to create a lead list of 20,000 users. Our system needs to retrieve and scan all 1M accounts to find the 20,000 that meet your filters. In this case, credits are used when scanning each of the 1M accounts so the import would use 1M lead credits total to import a total of 20,000 leads. If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Add Lead to Campaign Source: https://drippi.mintlify.app/api-reference/endpoint/add-lead-to-campaign POST /lead-sources/{id}/lead Adds a single lead to a lead source (campaign). Supports three import types: **username** (Twitter handle), **profile_url** (x.com profile URL), or **json** (full Twitter user object). **Lead Credits:** Adding a lead by `username` or `profile_url` consumes **Lead Credits**, as the system looks up the Twitter profile. Adding by `json` does not consume Lead Credits. Adds a single lead to a lead source (campaign). You can add a lead in three ways: * By username — Pass a Twitter username; the system looks up the profile. Consumes Lead Credits. * By profile URL — Pass an x.com profile URL (e.g. `https://x.com/username`); the username is extracted and the profile is looked up. Consumes Lead Credits. * By JSON — Pass a full Twitter user object. Does not consume Lead Credits. The `username` and `profile_url` import options use Lead Credits. Use `json` when you already have the user data (e.g., via the enrichment API) to avoid spending Lead Credits. # Enrich Lead via Navigator Source: https://drippi.mintlify.app/api-reference/endpoint/enrich-lead-navigator POST /navigator/enrich Submit lead input (name and optional company, job title, location, etc.). Navigator searches for a matching X (Twitter) profile. If a match is found, returns the **full lead** (same structure as the add-lead-to-campaign JSON payload) and deducts **1 Navigator credit**. If no match is found, returns `match: null` and does **not** deduct any credit. The returned lead can be passed directly to Add lead to campaign (JSON import) if desired. Submit lead input (either `fullName` or `firstName` + `lastName`, plus optional fields like company, job title, location, headline). Navigator searches for a matching X (Twitter) profile. If a match is found, the API returns the full lead in the same structure as the [Add lead to campaign](/api-reference/endpoint/add-lead-to-campaign) JSON payload, and one Navigator credit is deducted. If no match is found, the response has `match: null` and no credit is deducted. The returned `match` object can be passed directly to Add lead to campaign (using `importType: "json"` and `json: match`) to add that lead to a campaign without a second lookup. Navigator credits are deducted only when a match is returned. No match means no deduction. # Get Account by ID Source: https://drippi.mintlify.app/api-reference/endpoint/get-account-by-id GET /accounts/{id} Returns a specific account by its ID Returns a specific account by its ID. Use this endpoint to retrieve detailed information about a particular connected social media account. # Get All Accounts Source: https://drippi.mintlify.app/api-reference/endpoint/get-accounts GET /accounts Returns all connected social media accounts for the authenticated user Returns all connected social media accounts for the authenticated user. This endpoint provides access to account information including platform, username, status, and connected campaigns. # Get Automation Action Log Source: https://drippi.mintlify.app/api-reference/endpoint/get-automation-action-log GET /automations/{id}/actionLog Returns the action log for a specific automation within a specified time period Returns the action log for a specific automation within a specified time period. This endpoint provides detailed information about all actions performed by the automation, including timestamps and action details. Use the `from` and `to` query parameters to filter by date range. # Get Automation by ID Source: https://drippi.mintlify.app/api-reference/endpoint/get-automation-by-id GET /automations/{id} Returns a specific automation by its ID Returns a specific automation by its ID. Use this endpoint to retrieve detailed information about a particular automation campaign. # Get Automation Replies Source: https://drippi.mintlify.app/api-reference/endpoint/get-automation-replies GET /automations/{id}/replies Returns all replies for a specific automation within a specified time period Returns all replies for a specific automation within a specified time period. This endpoint provides access to reply data including message content, sentiment analysis, and timestamps. Use the `from` and `to` query parameters to filter by date range. # Get Automations Source: https://drippi.mintlify.app/api-reference/endpoint/get-automations GET /automations Returns all automations for the authenticated user within a specified time period Returns all automations for the authenticated user within a specified time period. You can filter results by providing `from` and `to` query parameters in ISO 8601 format. # Get Lead Source by ID Source: https://drippi.mintlify.app/api-reference/endpoint/get-lead-source-by-id GET /lead-sources/{id} Returns a specific lead source by its ID Returns a specific lead source by its ID. Use this endpoint to retrieve detailed information about a particular lead source. # Get Lead Source Statistics Source: https://drippi.mintlify.app/api-reference/endpoint/get-lead-source-stats GET /lead-sources/{id}/stats Returns statistics for a specific lead source Returns statistics for a specific lead source. This endpoint provides counts of new and contacted leads within the lead source, giving you insights into lead progression and engagement. # Get Lead Sources Source: https://drippi.mintlify.app/api-reference/endpoint/get-lead-sources GET /lead-sources Returns all lead sources for the authenticated user Returns all lead sources for the authenticated user. This endpoint provides access to lead source information including name, type, creation date, and total lead count. # Introduction Source: https://drippi.mintlify.app/api-reference/introduction Drippi Public API for automation and lead management ## Welcome to the Drippi Public API The Drippi Public API provides programmatic access to your automation data, lead sources, and account information. This API allows you to integrate Drippi's automation and lead management capabilities into your own applications. Create an API key in the [Drippi dashboard](https://app.drippi.ai/settings/api) to get started. ## Authentication All API endpoints require authentication using an API key. Include your API key in the `x-api-key` header with every request. ## Rate Limiting The API implements rate limiting to ensure fair usage. Each API key is limited to 30 requests per minute. When you exceed this limit, you'll receive a 429 status code with rate limit information. ## Base URL The base URL for all API requests is `https://app.drippi.ai/api/v1/`. ## Response Format All API responses follow a consistent format: * **Success responses** include a `status` field set to `"success"` and the requested data * **Error responses** include a `status` field set to `"error"` and a `message` describing the error ## Available Endpoints The API provides access to three main resource types: * **Accounts**: Manage your connected social media accounts * **Automations**: Access automation data, replies, and action logs * **Lead Sources**: Retrieve lead source information and statistics ## Getting Started 1. **Get your API key** from your Drippi dashboard 2. **Make your first request** to test the connection 3. **Explore the endpoints** to integrate with your applications For detailed information about each endpoint, see the API reference documentation below. # Auto DM - New Followers Source: https://drippi.mintlify.app/automation/auto-dm-new-followers Automatically message any new followers For an in depth video tutorial on how to automatically message new followers go here: [https://www.youtube.com/watch?v=81qnp9\\\_-IRw](https://www.youtube.com/watch?v=81qnp9\\_-IRw) If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Auto DM - Tweet Interactions Source: https://drippi.mintlify.app/automation/auto-dm-tweet-interactions Direct message anyone who interacts with your X / Twitter posts. For a full video tutorial on how to automatically message anyone that interacts with your posts, go here: [https://www.youtube.com/watch?v=x5SYQoTrOF4](https://www.youtube.com/watch?v=x5SYQoTrOF4) If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Cold DM Source: https://drippi.mintlify.app/automation/cold-dm How to Set Up A New Cold DM Automation ## Campaign Setup (Video): For a quick video on how to set up campaigns and a step-by-step easy to follow SOP please go to: [https://start.drippi.ai/campaign](https://start.drippi.ai/campaign) ## Campaign Setup (SOP): For a full step-by-step, easy to follow, guide on how to set up campaigns, please go here: [https://drippi.mintlify.app/quickstart](https://drippi.mintlify.app/quickstart) If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Frequenlty asked Questions Source: https://drippi.mintlify.app/faq/frequently-asked-questions Description of your new file. Yes, otherwise twitter will block you from sending messages to almost everyone (people who do not follow you or you don't have previous messages with). And it also gives you a tone of credibility. # How To Connect Accounts To Drippi Source: https://drippi.mintlify.app/getting-started/connecting-accounts Guide to connecting and reconnecting X accounts from Drippi ## Connecting Your X Account Open up settings and navigate to the \_accounts \_section: [https://www.app.drippi.ai/settings/accounts](https://www.app.drippi.ai/settings/accounts)  Look for a button that says: *+ Connect New X Account* Screenshot 2025-10-28 at 9.34.15 AM.png If you already have accounts connected, it should appear under your last account. As soon as you click that button, either a pop-up will appear, or the pop-up will open up in a new tab. Screenshot 2025-10-28 at 9.34.51 AM.png MANUALLY (no password managers) enter your username, password, and 2fa codes if applicable.  ## **Account Connection Troubleshooting** If you get any error when trying to connect any of your accounts, please take the following steps: 1. Make sure you’re NOT using any password managers 2. Make sure you’re using the correct USERNAME to sign in 3. Make sure you’re using the CORRECT password to sign in If none of these are the issue: 4. Log into X / Twitter regularly, change your password, then try connecting your account to Drippi using the new password. If none of these work, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) ## **Reconnecting Accounts** Whenever an account's been disconnected, you can reconnect it by navigating to your settings, and clicking on the \_accounts \_section: [https://www.app.drippi.ai/settings/accounts](https://www.app.drippi.ai/settings/accounts)  Then, locate the disconnected account and click on the 3 vertical dots in the upper right corner: Screenshot 2025-10-28 at 9.36.06 AM.png Then click *reconnect.* Screenshot 2025-10-28 at 9.36.30 AM.png And then clicking "reconnect account" once again Screenshot 2025-10-28 at 9.36.53 AM.png A couple things can happen: 1. The account gets reconnected instantly, removing the \_account disconnected \_banner, and you’ll see an *account connected* notification in the top left corner. Screenshot 2025-10-28 at 9.37.29 AM.png Screenshot 2025-10-28 at 9.37.13 AM.png Before moving on to step 2, please make sure the account hasn’t been banned by checking its status directly on X / Twitter. 2. The account does NOT get reconnected instantly, the X / Twitter login pop-up shows up again, you type in your password, and then another 2 things can happen: 1. Your account gets reconnected; or 2. You’ll need to pass an arcane puzzle to prove you’re human, and then your account will be reconnected.  If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Quickstart Source: https://drippi.mintlify.app/getting-started/quickstart Start automating you cold DM outreach in less than 5 minutes For a video tutorial go here: https://start.drippi.ai/campaign ## Set up your first campaign 1. Open up [Drippi.ai](http://Drippi.ai) and login 2. Go to Leads on the menu on the left side of the screen: Screenshot2025 10 22at10 11 33AM Pn 3. Select + New Lead Source: image.png 4. Select Lead Scraper: Screenshot 2025-10-27 at 7.56.07 AM.png 5. Select account or tweet source: Screenshot 2025-10-27 at 7.56.24 AM.png 6. Paste the first lead source into the link space provided and wait for the profile to load: Screenshot 2025-10-27 at 7.56.45 AM.png 7. Select followers and/or following (depending on campaign) and hit add source on the bottom right hand corner Screenshot 2025-10-27 at 7.57.04 AM.png 8. Add more sources by repeating steps 7, 8, and 9 until the lead size is enough to where you think AFTER filters the campaign will have AT LEAST 20,000 leads 9. Hit Next: Screenshot 2025-10-27 at 7.57.21 AM.png 10. Select Bio Contents Screenshot 2025-10-27 at 7.57.40 AM.png 11. Hit *add element* and then hit *Quick Add* Screenshot 2025-10-27 at 7.57.56 AM.png 12. Watch this video for the quick add feature: [https://www.loom.com/share/e0c0b7ac04dc40caae626d8fc0043d9f](https://www.loom.com/share/e0c0b7ac04dc40caae626d8fc0043d9f)  13. After you’ve got your keywords, repeat the process for negative keywords 14. Add a *number of followers* filter (if applicable) 15. Check how many leads are remaining Screenshot 2025-10-27 at 7.59.06 AM.png 16. If it’s LESS than 20,000 then go back to step 7 and add more lead sources. 17. Once you’ve got over 20,000, hit NEXT  Screenshot 2025-10-27 at 7.59.26 AM.png 18. Name the lead source in the following manner: CLIENT NAME \<> DATE \<> SCRIPT \<> ACCOUNT NAME Screenshot 2025-10-27 at 7.59.46 AM.png 19. Hit Save Screenshot 2025-10-27 at 8.00.01 AM.png 20. Go to the automations tab: Screenshot 2025-10-27 at 8.00.14 AM.png 21. Hit *add new* Screenshot 2025-10-27 at 8.01.57 AM.png 22. Select *Cold DM 2.0* then hit *Next* Screenshot 2025-10-27 at 8.02.34 AM.png 23. Hit select lead source and select the one you just made and hit next Screenshot 2025-10-27 at 8.02.52 AM.png 24. Select Script Personalizer and hit next Screenshot 2025-10-27 at 8.03.06 AM.png 25. Select *Advanced*, Add *Context*, and then hit *Script* Screenshot 2025-10-27 at 8.03.23 AM.png 26. Add the corresponding script, make sure the variables are the correct ones, and hit *settings* Screenshot 2025-10-27 at 8.04.13 AM.png If you need help with scripts go here: [https://start.drippi.ai/scriptwriting](https://start.drippi.ai/scriptwriting) 27. Make sure you set the settings just like below. If you have questions about the *Split Messages* toggle, please reach out to us at [support@drippi.ai](mailto:support@drippi.ai) Screenshot 2025-10-27 at 8.04.26 AM.png 28. Make sure these are turned on as well, and hit next on the left Screenshot 2025-10-27 at 8.04.59 AM.png 29. Hit *Next* on variables (or add any variable you'd like) 30. Hit *add followup* Screenshot 2025-10-27 at 8.05.27 AM.png 31. Select the cadence below and add the follow up scripts from the google doc and hit NEXT Screenshot 2025-10-27 at 8.06.48 AM.png 32. Hit advanced settings and make sure these settings are set up: Screenshot 2025-10-27 at 8.07.10 AM.png 33. Give the automation a name, following convention below, select the account, and hit create CLIENT NAME \<> DATE \<> SCRIPT \<> ACCOUNT NAME Screenshot 2025-10-27 at 8.07.28 AM.png If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Introduction Source: https://drippi.mintlify.app/introduction Welcome to drippi! Drippi is an AI-powered tool designed to automate and personalize your Twitter direct message (DM) outreach. It helps you find leads, create tailored messages based on profile details and activity, and track performance with detailed analytics. With features like inbox management, automated follow-ups, and advanced lead filtering, Drippi makes it easy to connect with your audience and run effective outreach campaigns. If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) ## Getting Started Your guide to mastering the essentials and launching your first campaign. Start automating you cold DM outreach in less than 5 minutes Explore Drippi’s diverse options for importing and finding leads. Learn how to automate personalized outreach ## Advanced Dive deeper into Drippi's advanced features Build custom integrations and automations with Drippi's API endpoints & webhooks # CSV Import Source: https://drippi.mintlify.app/leads/csv-import How to use Drippi.ai's CSV import feature ## How to Use Drippi's CSV Import Feature (video) [https://www.youtube.com/watch?v=YNZkV\_d3Luc](https://www.youtube.com/watch?v=YNZkV_d3Luc) ## How to Use Drippi's CSV Import Feature (SOP) Importing a lead list into drippi by their usernames is fairly straightforward Just make sure your CSV is formatted similarly to the one you'll find below👇 1. Head to the find leads page, then select new lead source. Screenshot 2025-10-27 at 9.19.23 AM.png Screenshot 2025-10-27 at 9.19.38 AM.png 2. Select CSV import: Screenshot 2025-10-27 at 9.19.59 AM.png 3. Upload a file by selecting "browse files" or by dragging and dropping a CSV file: Screenshot 2025-10-27 at 9.22.27 AM.png In order to upload a file, it must be in the correct format. Files only NEED usernames. DO NOT INCLUDE "@" symbol or links.\ \ Example: penunurialex NOT @penunurialex NOT [https://twitter.com/penunurialex](https://twitter.com/penunurialex) Our CSV import system supports the addition of any custom personalization fields you may have, more information on that below. 4. Ensure you select the column containing the list of usernames in the dropdown menu. Then name and save your lead source Screenshot 2025-10-27 at 9.22.48 AM.png By username we are referring to "handle" or "@" NOT their "name"\ \ Example: Screenshot 2025-10-27 at 9.24.48 AM.png ## **Importing with Drippi's CSV format** CSV's that use Drippi's CSV format will be imported much faster and do not require additional lead credits to import. Here's an example of our required format👇 [https://docs.google.com/spreadsheets/d/1CR8eQECeIezDCas2RBoo7SFhde-fyRfQRKntFinSDss/edit?usp=sharing](https://docs.google.com/spreadsheets/d/1CR8eQECeIezDCas2RBoo7SFhde-fyRfQRKntFinSDss/edit?usp=sharing) This is the same format that is used when you export leads from Drippi by clicking the download button on the page of that lead source. Screenshot 2025-10-27 at 9.30.41 AM.png If your CSV matches Drippi's export format you will see an indicator that verifies your document is formatted correctly: Screenshot 2025-10-27 at 9.32.50 AM.png To integrate data from external sources into Drippi's system, it's essential to ensure that every field is both accurate and formatted correctly. Uploading data that's incorrect or not properly formatted can disrupt your automation processes or prevent the data from being successfully imported. ## **Importing Custom Variables (Custom Personalization Info)** Our CSV import system supports the addition of any custom personalization fields you may have. To include this data in the lead source. verify that the column has a descriptive name and the field exists for every lead. Example: Screenshot 2025-10-27 at 9.34.14 AM.png Then after uploading your data, select the custom variables you would like to import. Screenshot 2025-10-27 at 9.34.56 AM.png **Incomplete personalization in your CSV can disrupt your campaigns.** Ensure every lead has the necessary custom data before using the variable. If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Downloading Lists Source: https://drippi.mintlify.app/leads/downloading-lists How To Download a Scraped List ## Downloading a List Scraped With [Drippi.ai](http://Drippi.ai) Lists up to 100k can be downloaded directly within the lead scraping dashboard. Simply select the list you want to download, then hit the download button in the top right corner. Screenshot 2025-10-27 at 2.46.35 PM.png Depending on your list size, the file will either be emailed to you (check spam) or appear directly in your downloads. If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Lead Scraper Source: https://drippi.mintlify.app/leads/lead-scraper The lead scraper enables you to import leads from either the Likers and/or Retweeters of a post, or from the Followers and/or Following of an account ## How To Use Drippi's Lead Scraping Features (Video) [https://www.youtube.com/watch?v=8-bmJl7h8X8](https://www.youtube.com/watch?v=8-bmJl7h8X8) ## Data Sources Drippi's Lead Scraper allows you to scrape from a Tweet Source, or from an Account Source. Screenshot 2025-10-27 at 2.00.58 PM.png ### Tweet Sources In the space provided, add a link to any tweet of your choice. Then select the data you want to include, and then hit *add source*. Screenshot 2025-10-27 at 2.07.20 PM.png You can then add as many other Tweet or Account sources as you'd like. Once done, hit *next.* Screenshot 2025-10-27 at 2.09.53 PM.png Scroll down on this page for information on how our filters work. ### Account Sources In the space provided, add a link to any x / twitter of your choice. Then select the data you want to include; following, followers, or both. Then hit *add source*. Screenshot 2025-10-27 at 2.13.43 PM.png You can then add as many other Tweet or Account sources as you'd like. Once done, hit *next.* image.png ## Filters Add filters to increase the quality of your list by removing unqualified prospects. ### Combining Filters Understanding how filters can be combined is the most important aspect of creating highly targeted lists Lets look at some examples: Elements inside the same bio contents filter are combined using an OR operator. So if we add just this filter. Users whose bios contain “cat” OR “dog” OR “\$” will be included from the list. Screenshot 2025-10-27 at 2.22.47 PM.png But if we add these filters ⬇️ Screenshot 2025-10-27 at 2.23.56 PM.png The filters are combined using an AND operator. So, only users who’s bios contain “\$” AND “dog” AND “cat” will be be included in our list ### Bio Contents This filter will remove anyone that does NOT have AT LEAST ONE of the elements added to this filter in their bio. Screenshot 2025-10-27 at 2.18.09 PM.png This filter allows words, phrases, symbols, and links. For importing a list, add a comma separated list of keywords through the *Quick Add* element. Screenshot 2025-10-27 at 2.18.48 PM.png ### Exclude Bio Contents This filter will remove anyone that HAS have AT LEAST ONE of the elements added to this filter in their bio. Screenshot 2025-10-27 at 2.25.37 PM.png This filter allows words, phrases, symbols, and links. For importing a list, add a comma separated list of keywords through the *Quick Add* element. Screenshot 2025-10-27 at 2.27.42 PM.png ### Number of Followers & Following These 2 separate filters allow you to remove anyone that does not have your desired follower or following volume. Screenshot 2025-10-27 at 2.33.28 PM.png These filters can be set to: greater than, less than, or between. Screenshot 2025-10-27 at 2.29.40 PM.png ### Number of Tweets This filter allows you to remove anyone that doesn't match your desired tweet (post) volume. Screenshot 2025-10-27 at 2.32.12 PM.png This filter can be set to: greater than, less than, or between. Screenshot 2025-10-27 at 2.34.04 PM.png ### Saved Filters You can save filters by selecting *save* whenever you set up a new filter Screenshot 2025-10-27 at 2.36.59 PM.png To find your saved filters, hit \_Saved Filter \_and select your desired filters. Screenshot 2025-10-27 at 2.35.55 PM.png If you have any questions, please reach out to us @ [support@drippi.ai](mailto:support@drippi.ai) or book a call with our customer support team here: [https://cal.com/team/drippi/customer-support-chat](https://cal.com/team/drippi/customer-support-chat) # Do Not Sell My Personal Information Source: https://drippi.mintlify.app/policies/Do-Not-Sell-MyPersonal-Information **Last Updated: October 27, 2025** **Your California Privacy Rights** If you are a California resident, the California Consumer Privacy Act (CCPA) provides you with specific rights regarding your personal information, including the right to opt-out of the “sale” of your personal information. **Our Data Practices** **Drippi Labs Inc. does not sell your personal information.** We do not, and will not, sell, rent, or trade your personal information to third parties for monetary or other valuable consideration. We may share your personal information with service providers who assist us in operating our business (such as payment processors, hosting providers, and analytics services), but these service providers are contractually prohibited from using your information for any purpose other than providing services to us. **What Does “Sale” Mean Under CCPA?** Under the CCPA, “sale” is broadly defined and may include sharing personal information with third parties in exchange for something of value, even if no money changes hands. This could include sharing data with advertising networks or data brokers. **Your Right to Opt-Out** Even though we do not sell your personal information, you have the right to request that we do not sell your personal information in the future. If our data practices change, we will honor any opt-out requests we have received. **How to Submit an Opt-Out Request** If you would like to submit a "Do Not Sell My Personal Information" request, you can do so by: **Option 1: Email** Send an email to [**support@drippi.ai**](mailto:support@drippi.ai) with the subject line: **"Do Not Sell My Personal Information Request"** Please include the following information in your request: * Your full name * Your email address associated with your [Drippi.ai](http://Drippi.ai) account * A clear statement that you are requesting that we do not sell your personal information **Option 2: Contact Form** Visit your account settings at [**https://www.app.drippi.ai/settings**](https://www.app.drippi.ai/settings) and submit a privacy request through our support system. **Option 3: Mail** Send a written request to: **Drippi Labs Inc.**\ Attn: Privacy Request\ 551 Rockwood Ct\ Annapolis, MD 21401\ United States **Verification Process** To protect your privacy and security, we may need to verify your identity before processing your request. We will ask you to provide information that matches the information we have on file for your account. **Response Timeline** We will acknowledge receipt of your request within 10 business days and will respond to your request within 45 days. If we need additional time (up to 90 days total), we will notify you of the reason and extension period. **No Discrimination** We will not discriminate against you for exercising your CCPA rights. This means we will not: * Deny you goods or services * Charge you different prices or rates for goods or services * Provide you a different level or quality of goods or services * Suggest that you may receive a different price or rate for goods or services or a different level or quality of goods or services **Other California Privacy Rights** In addition to the right to opt-out of the sale of your personal information, California residents have the following rights under the CCPA: **Right to Know** You have the right to request that we disclose: * The categories and specific pieces of personal information we have collected about you * The categories of sources from which we collected your personal information * The business or commercial purpose for collecting your personal information * The categories of third parties with whom we share your personal information **Right to Delete** You have the right to request that we delete the personal information we have collected from you, subject to certain exceptions. **Right to Correct** You have the right to request that we correct inaccurate personal information we maintain about you. To exercise any of these rights, please contact us at [**support@drippi.ai**](mailto:support@drippi.ai) or visit our Privacy Policy for more information. **Authorized Agents** You may designate an authorized agent to submit requests on your behalf. If you use an authorized agent, we may require: * Written permission from you authorizing the agent to act on your behalf * Verification of your identity directly with us * Verification that the authorized agent has been properly authorized to act on your behalf **Additional Information** For more information about how we collect, use, and share your personal information, please review our complete Privacy Policy. If you have questions about this notice or our privacy practices, please contact us at [**support@drippi.ai**](mailto:support@drippi.ai). **Contact Information** **Drippi Labs Inc.**\ Email: [support@drippi.ai](mailto:support@drippi.ai)\ Phone: (443) 994-1537\ Address: 551 Rockwood Ct, Annapolis, MD 21401, United States **Effective Date:** October 27, 2025 # Affiliate Policy Source: https://drippi.mintlify.app/policies/affiliate-policy ## Drippi.ai Affiliate Program Policy ### **Payout Threshold** Commissions will be paid out once they reach a minimum of \$150. ### **Commission Aging Period** Commissions must be at least 60 days old to be eligible for payout. ### **Notification** Affiliates who have accrued over \$150 in commissions for 60 days or more should request a payout by clicking the 'request payout' button on the [affiliate dashboard](https://www.app.drippi.ai/affiliate). ### **Commission Structure** * For each signup using your referral link, you will receive: * **25% of lifetime revenue** generated from the referral. * Referrals will receive: * **25% off their first 2 months.** ### **Exclusion** Commissions will not be paid out in the Drippi Partner program or any other Drippi affiliate programs if there are duplicates between the two programs. ### **Payout Frequency** Payouts will be processed promptly upon meeting the threshold and aging period requirements. ### **Payment Method** Payments will be made through a method chosen by the affiliate during the payout process. ### **Compliance** Affiliates are expected to adhere to the terms and conditions outlined in the affiliate agreement. Any violation may result in the forfeiture of commissions and termination from the program. ### **Policy Updates** This policy is subject to periodic review and may be updated as necessary. Affiliates will be notified of any changes in advance. ### **Self Referrals** Self-referrals are defined as any attempt by an affiliate to generate commissions through the registration of their own account, referrals to their own business, or any account directly controlled or influenced by the affiliate, for the purpose of earning commissions. This includes, but is not limited to: * Creating multiple accounts under different names or email addresses. * Referring family members, friends, associates, or their own business where the primary intention is to benefit from the referral commission. * Using any method or tactic that circumvents the spirit of the referral program to gain commissions improperly. Any detected self-referral activities will result in the immediate forfeiture of all earned commissions and possible termination from the affiliate program. ### **Transparency** This policy is designed to ensure that our customers have a transparent and fair understanding of how the Drippi.ai Affiliate Program operates. We are committed to providing quality service and support to enhance your experience with our software. By participating in our affiliate program, you agree to abide by the terms and conditions outlined in this policy. ### **Contact** Please contact us at [support@drippi.ai](mailto:support@drippi.ai) if you have any questions or concerns regarding this policy. # Cookie Policy Source: https://drippi.mintlify.app/policies/cookie-policy Description of your new file. **Last Updated: October 27, 2025** **1. Introduction** This Cookie Policy explains how Drippi Labs Inc. ("[Drippi.ai](http://Drippi.ai)," "we," "us," or "our") uses cookies and similar tracking technologies when you visit our website at [https://www.drippi.ai](https://www.drippi.ai) and use our Services. This policy should be read together with our Privacy Policy, which explains how we collect, use, and protect your personal information. By using our website, you consent to the use of cookies as described in this policy. If you do not agree to our use of cookies, you should change your browser settings accordingly or refrain from using our website. **2. What Are Cookies?** Cookies are small text files that are placed on your computer or mobile device when you visit a website. They are widely used to make websites work more efficiently and to provide information to website owners. Cookies allow websites to recognize your device and remember information about your visit, such as your preferences and actions. **3. Types of Cookies We Use** We use the following categories of cookies on our website: **3.1. Strictly Necessary Cookies** These cookies are essential for the operation of our website and Services. They enable core functionality such as security, network management, and accessibility. Without these cookies, our Services cannot function properly. **Examples:** * Session cookies that keep you logged in * Authentication cookies that verify your identity * Security cookies that protect against fraud **Legal Basis:** These cookies are necessary for the performance of our contract with you. **3.2. Analytics and Performance Cookies** These cookies help us understand how visitors interact with our website by collecting and reporting information anonymously. This helps us improve the functionality and performance of our Services. **Cookies we use:** image.png **Third-Party Privacy Policy:** Google Analytics Privacy Policy - [https://policies.google.com/privacy](https://policies.google.com/privacy) **How to Opt-Out:** You can opt-out of Google Analytics by installing the Google Analytics Opt-out Browser Add-on - [https://tools.google.com/dlpage/gaoptout](https://tools.google.com/dlpage/gaoptout) **3.3. Advertising and Marketing Cookies** These cookies are used to deliver advertisements that are relevant to you and your interests. They also help us measure the effectiveness of our advertising campaigns. **Cookies we use:** image.png **Third-Party Privacy Policies:** * Facebook Privacy Policy - [https://www.facebook.com/privacy/explanation](https://www.facebook.com/privacy/explanation) * Google Ads Privacy Policy - [https://policies.google.com/privacy](https://policies.google.com/privacy) **How to Opt-Out:** * Facebook: Adjust your Facebook Ad Preferences - [https://www.facebook.com/ads/preferences](https://www.facebook.com/ads/preferences) * Google: Visit Google Ad Settings - [https://adssettings.google.com/](https://adssettings.google.com/) **3.4. Functional Cookies** These cookies enable enhanced functionality and personalization, such as live chat support and remembering your preferences. **Cookies we use:** image.png **Third-Party Privacy Policy:** Intercom Privacy Policy - [https://www.intercom.com/legal/privacy](https://www.intercom.com/legal/privacy) **4. How to Manage Cookies** You have the right to decide whether to accept or reject cookies. You can exercise your cookie preferences by adjusting the settings in your web browser. **4.1. Browser Settings** Most web browsers allow you to control cookies through their settings. You can set your browser to: * Block all cookies * Block third-party cookies only * Delete cookies when you close your browser * Alert you when a website tries to place a cookie **How to manage cookies in popular browsers:** **Chrome:** 1. Open Chrome and click the three dots in the top right corner 2. Go to Settings > Privacy and security > Cookies and other site data 3. Choose your preferred cookie settings **Firefox:** 4. Open Firefox and click the three lines in the top right corner 5. Go to Settings > Privacy & Security 6. Under "Cookies and Site Data," choose your preferred settings **Safari:** 7. Open Safari and go to Preferences 8. Click on Privacy 9. Under "Cookies and website data," choose your preferred settings **Microsoft Edge:** 10. Open Edge and click the three dots in the top right corner 11. Go to Settings > Cookies and site permissions 12. Click on "Cookies and site data" and choose your preferred settings **Please note:** If you choose to block or delete cookies, some features of our website may not function properly, and you may not be able to access certain parts of our Services. **4.2. Opt-Out Tools** You can also opt-out of interest-based advertising by visiting: * Network Advertising Initiative (NAI) Opt-Out Page - [http://www.networkadvertising.org/choices/](http://www.networkadvertising.org/choices/) * Digital Advertising Alliance (DAA) Opt-Out Page - [http://www.aboutads.info/choices/](http://www.aboutads.info/choices/) * European Interactive Digital Advertising Alliance (EDAA) Opt-Out Page - [http://www.youronlinechoices.eu/](http://www.youronlinechoices.eu/) **4.3. Mobile Device Settings** If you access our Services through a mobile device, you can manage advertising preferences through your device settings: **iOS:** 13. Go to Settings > Privacy > Advertising 14. Enable "Limit Ad Tracking" **Android:** 15. Go to Settings > Google > Ads 16. Enable "Opt out of Ads Personalization" **5. Other Tracking Technologies** In addition to cookies, we may use other tracking technologies: **5.1. Web Beacons (Pixels)** Web beacons are small graphic images (also known as "pixel tags" or "clear GIFs") that may be included on our website and in our emails. They allow us to count users who have visited certain pages or opened an email and to track the effectiveness of our marketing campaigns. **5.2. Local Storage** We may use local storage technologies, such as HTML5, to store content information and preferences. Local storage is similar to cookies but can store larger amounts of data. **6. Third-Party Cookies** Some cookies on our website are placed by third-party services. We do not control these cookies or how the third parties use them. We encourage you to review the privacy policies of these third-party services to understand how they collect and use your information. **Third parties that may place cookies on our website:** * Google (Analytics, Ads, DoubleClick) * Facebook (Pixel, Social Plugins) * Intercom (Live Chat) **7. Updates to This Cookie Policy** We may update this Cookie Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. The updated version will be indicated by an updated "Last Updated" date at the top of this policy. We encourage you to review this Cookie Policy periodically to stay informed about our use of cookies. **8. Contact Us** If you have any questions about our use of cookies or this Cookie Policy, please contact us at: **Email:** [support@drippi.ai](mailto:support@drippi.ai) **Address:**\ Drippi Labs Inc.\ 551 Rockwood Ct\ Annapolis, MD 21401\ United States **Your Consent** By continuing to use our website, you consent to our use of cookies as described in this Cookie Policy. If you do not agree to our use of cookies, please adjust your browser settings or discontinue use of our website. # Fulfillment Policy Source: https://drippi.mintlify.app/policies/fulfillment-policy Fulfillment Policy for Drippi.ai **Effective Date: October 25, 2025** **1. Introduction** This Fulfillment Policy describes how Drippi Labs Inc. ("[Drippi.ai](http://Drippi.ai)," "we," "us," or "our") delivers our Services to customers, including information about service delivery, refunds, cancellations, and credits. This policy applies to all purchases made through our website at [https://www.drippi.ai](https://www.drippi.ai) and our platform at [https://app.drippi.ai](https://app.drippi.ai). This Fulfillment Policy should be read in conjunction with our Terms of Service, which govern your use of our Services. **2. Service Description** [Drippi.ai](http://Drippi.ai) is a software-as-a-service (SaaS) platform that enables users to send Twitter/X direct messages at scale, scrape publicly available lead information, and manage outreach campaigns. Our Services are delivered entirely online through our web-based platform and are accessible immediately upon account creation and payment. **2.1. What You Receive** When you subscribe to [Drippi.ai](http://Drippi.ai), you receive: * **Immediate Access:** Access to the [Drippi.ai](http://Drippi.ai) web platform at [https://app.drippi.ai](https://app.drippi.ai) * **Account Dashboard:** A personalized dashboard to manage your campaigns, leads, and settings * **Credits:** A specified number of credits based on your subscription plan, which can be used for sending messages and scraping leads * **Connected Account Integration:** The ability to connect your Twitter/X accounts to automate direct messaging * **Analytics and Reporting:** Performance tracking and analytics for your outreach campaigns * **Customer Support:** Access to our customer support team via email at [support@drippi.ai](mailto:support@drippi.ai) and live chat through Intercom * **Documentation:** Access to our user guides, best practices, and technical documentation **2.2. Service Delivery Timeline** **Immediate Delivery:** Our Services are delivered digitally and are available immediately upon successful payment and account creation. You will receive: * Instant access to your account dashboard * Immediate ability to connect Twitter/X accounts * Immediate credit allocation based on your subscription plan * Instant access to all platform features included in your plan There is no physical product delivery or shipping involved. All Services are provided online through our cloud-based platform. **3. Subscription Plans and Billing** **3.1. Subscription-Based Service** [Drippi.ai](http://Drippi.ai) operates on a subscription basis. When you subscribe, you select a plan that determines: * The number of credits you receive per billing cycle * The features and functionality available to you * The billing frequency (monthly, quarterly, or annual) * The subscription price **3.2. Payment and Billing** * **Payment Due:** All subscription fees are due in advance at the start of each billing cycle * **Payment Processing:** Payments are processed securely through Stripe, our third-party payment processor * **Accepted Payment Methods:** We accept major credit cards and debit cards as processed by Stripe * **Billing Currency:** All prices are in United States Dollars (USD) unless otherwise specified * **Automatic Renewal:** Your subscription will automatically renew at the end of each billing cycle unless you cancel in accordance with Section 5 below **3.3. Price Changes** We reserve the right to change our subscription prices at any time. If we increase the price of your subscription, we will notify you at least thirty (30) days before the price change takes effect. Price changes will apply to your next billing cycle after the notice period. If you do not agree to the price change, you may cancel your subscription before the new price takes effect. **4. Credit System** **4.1. How Credits Work** [Drippi.ai](http://Drippi.ai) operates on a credit-based system. Credits are the currency used within our platform to perform actions such as: * Personalizing messages * Scraping publicly available lead information * Other platform actions as described in our Documentation **4.2. Credit Allocation** * **Initial Credits:** Upon subscribing, you will receive a specified number of credits based on your chosen subscription plan * **Credit Renewal:** Credits are replenished at the start of each billing cycle according to your plan * **Credit Consumption:** Credits are consumed as you use the Services, as described in our Documentation **4.3. Credit Rollover** **Unused credits do not automatically roll over to the next billing cycle.** Credits reset at the start of each new billing cycle, and any unused credits from the previous cycle are forfeited. In certain exceptional circumstances, we may, at our sole discretion, allow unused credits to roll over to the next billing cycle. Such decisions are made on a case-by-case basis and do not establish a precedent or obligation for future credit rollovers. We are under no obligation to provide credit rollovers, and you should not rely on the possibility of rollover when planning your usage. **4.4. No Refunds for Unused Credits** **Important:** We do not provide refunds, credits, or prorated amounts for unused credits. Once credits are allocated to your account, they are considered consumed for billing purposes, regardless of whether you use them. **5. Cancellation Policy** **5.1. How to Cancel** You may cancel your subscription at any time by: * **Option 1:** Contacting your account manager directly via email * **Option 2:** Using the cancellation feature in your account settings at [https://app.drippi.ai/settings](https://app.drippi.ai/settings) **5.2. Cancellation Notice Period** **You must provide at least five (5) days' notice prior to your next renewal date for your cancellation to take effect before the next billing cycle.** * If you cancel with at least 5 days' notice before your renewal date, you will not be charged for the next billing cycle * If you cancel with less than 5 days' notice before your renewal date, you will be charged for the next billing cycle, and your cancellation will take effect at the end of that cycle **5.3. Cancellation Call Requirement** In some instances, you may be required to schedule a cancellation call with your account manager as part of the cancellation process. However, **attendance at such call is not mandatory for the cancellation to be processed.** If you schedule a call but do not attend, your cancellation will still be processed according to the notice period requirements. **5.4. When Cancellation Takes Effect** Your cancellation will become effective at the end of your current paid subscription term. This means: * You will retain access to the Services until the end of your current billing cycle * You will not be charged for subsequent billing cycles * After your subscription expires, you will lose access to the platform and all associated features **5.5. No Refunds Upon Cancellation** **No refunds or credits will be provided for any partial subscription periods or unused credits.** If you cancel mid-cycle, you will not receive a prorated refund for the remaining days in your billing cycle. **6. Refund Policy** **6.1. No Refunds** **All subscription fees are non-refundable.** Once you have paid for a subscription period, you are not entitled to a refund, regardless of: * How much of the subscription period has elapsed * How many credits you have used * Whether you have used the Services at all * Whether you are satisfied with the Services **6.2. Exceptions** We may, at our sole discretion, provide refunds in exceptional circumstances, such as: * Technical issues on our end that prevent you from accessing the Services for an extended period * Billing errors or duplicate charges * Other circumstances we deem appropriate Any such refunds are provided on a case-by-case basis and do not establish a precedent or obligation for future refunds. **6.3. How to Request a Refund** If you believe you are entitled to a refund due to exceptional circumstances, please contact us at [support@drippi.ai](mailto:support@drippi.ai) with: * Your account email address * Your order or transaction ID * A detailed explanation of why you believe you are entitled to a refund * Any supporting documentation We will review your request and respond within 5-7 business days. Our decision is final. **7. Chargebacks and Payment Disputes** **7.1. Chargeback Policy** **If you initiate a chargeback or payment dispute with your credit card company or bank, we will consider your account to be in breach of our Terms of Service.** Consequences of initiating a chargeback include: * **Immediate Account Suspension:** Your account will be immediately suspended, and you will lose access to the Services * **Data Ownership Transfer:** You explicitly agree to transfer ownership of all Customer Data within the account to us to cover the costs and damages incurred by the chargeback * **Legal Action:** We reserve the right to pursue legal action to recover any outstanding fees, chargeback fees, and damages **7.2. Dispute Resolution** If you have a billing dispute or issue with a charge, **please contact us at **[**support@drippi.ai**](mailto:support@drippi.ai)** before initiating a chargeback.** We are committed to resolving billing issues fairly and promptly. Most disputes can be resolved through direct communication. **8. Service Availability and Limitations** **8.1. Service Uptime** While we strive to provide uninterrupted access to our Services, we do not guarantee 100% uptime. Our Services may be temporarily unavailable due to: * Scheduled maintenance * Technical issues * Third-party platform disruptions (e.g., Twitter/X downtime) * Force majeure events We will make reasonable efforts to notify you of scheduled maintenance in advance. **8.2. Third-Party Platform Dependencies** **Important:** The availability and functionality of our Services depend on third-party platforms, particularly Twitter/X. We have no control over these platforms and are not responsible for: * Changes to Twitter/X's API or terms of service * Twitter/X suspending or terminating your account * Twitter/X limiting or restricting API access * Any other actions taken by Twitter/X or other third-party platforms **No refunds will be provided if third-party platforms restrict, suspend, or terminate your access or our ability to provide the Services.** **8.3. Account Suspension Risk** **You acknowledge and accept that using automation tools may violate Twitter/X's terms of service.** As a result: * Your Twitter/X account may be suspended, banned, or restricted * You assume all risk and liability associated with such use * We are not responsible for any consequences arising from third-party platform actions * No refunds will be provided if your Twitter/X account is suspended or banned **9. Customer Responsibilities** To receive and use our Services, you are responsible for: * **Internet Connection:** Maintaining a stable internet connection * **Compatible Browser:** Using a modern, up-to-date web browser * **Twitter/X Account:** Having an active Twitter/X account to connect to our platform * **Compliance:** Ensuring your use of the Services complies with all applicable laws and third-party platform terms of service * **Account Security:** Maintaining the security and confidentiality of your account credentials We are not responsible for any inability to access or use the Services due to your failure to meet these requirements. **10. Changes to This Policy** We may update this Fulfillment Policy from time to time to reflect changes in our business practices, legal requirements, or for other operational reasons. The updated version will be indicated by an updated "Effective Date" at the top of this policy. If we make material changes to this policy, we will notify you by: * Posting a notice on our website * Sending an email to the address associated with your account * Displaying a notification in your account dashboard Your continued use of the Services after the effective date of any changes constitutes your acceptance of the updated policy. **11. Contact Information** If you have any questions about this Fulfillment Policy, our billing practices, or need assistance with your subscription, please contact us: **Email:** [support@drippi.ai](mailto:support@drippi.ai) **Phone:** (443) 994-1537 **Address:**\ Drippi Labs Inc.\ 551 Rockwood Ct\ Annapolis, MD 21401\ United States **Support Hours:** Monday - Friday, 9:00 AM - 5:00 PM EST We aim to respond to all inquiries within 24-48 business hours. **Last Updated:** October 25, 2025 This Fulfillment Policy is incorporated into and governed by our Terms of Service. In the event of any conflict between this Fulfillment Policy and our Terms of Service, the Terms of Service shall prevail. # Privacy Policy Source: https://drippi.mintlify.app/policies/privacy-policy **Last Updated: October 27, 2025** **1. Introduction** This Privacy Policy describes how and why Drippi Labs Inc. ("[Drippi.ai](http://Drippi.ai)," "we," "us," or "our") collects, stores, uses, and shares ("processes") your information when you use our services (the "Services"). This includes when you: * Visit our website at [https://www.drippi.ai](https://www.drippi.ai), or any of our websites that link to this policy. * Create an account and use our Twitter/X promotional and lead scraping platform. * Engage with us in other related ways, including sales, marketing, or events. Reading this Privacy Policy will help you understand your privacy rights and choices. **If you do not agree with our policies and practices, please do not use our Services.** If you still have any questions or concerns, please contact us at [support@drippi.ai](mailto:support@drippi.ai). **2. What Information We Collect** We collect personal information from several sources to provide and improve our Services. The types of information we collect depend on how you interact with us. **2.1. Personal Information You Disclose to Us** We collect personal information that you voluntarily provide to us when you register for an account, express an interest in our products, or contact us. This information includes: * **Identifiers:** Your name, email address, and username. * **Professional Information:** Your job title and company name. * **Contact Preferences:** Your preferences for receiving marketing communications. * **Payment Data:** We collect data necessary to process your payments, such as your payment instrument number and security code. All payment data is stored and processed by our third-party payment processor, Stripe. You can find their privacy policy here: [https://stripe.com/privacy](https://stripe.com/privacy). **2.2. Information from Your Connected Twitter/X Accounts** When you connect your Twitter/X account to our Services, you grant us permission to access and process data from that account. This is essential for the core functionality of our platform. This information includes: * **Profile Information:** Your Twitter/X username, profile picture, bio, and other public profile information. * **Account Activity:** We access your account to send direct messages and perform other automation tasks on your behalf as directed by you through the Services. * **Direct Message Content:** We process the content of the direct messages you send through our platform, including the text and the recipients' information. * **Analytics Data:** We collect data about the performance of your outreach campaigns, such as send rates, reply rates, and other engagement metrics. We do not control, and are not responsible for, the privacy practices of Twitter/X. We recommend you review their privacy policy to understand how they handle your data. **2.3. Information About Third Parties (Scraped Leads)** When you use our lead generation and scraping features, you may collect publicly available information about third parties from Twitter/X. This information may include usernames, profile information, bios, follower counts, and public tweets or posts. **Important Information About Third-Party Data:** * **Your Responsibility:** You are solely responsible for ensuring that your use of our lead scraping features complies with applicable laws, including data protection laws, and Twitter/X's terms of service. You must have a lawful basis for processing any personal information you collect through our Services. * **Data Storage:** Information about third parties that you scrape through our Services is stored in your account and is considered part of your Customer Data. We process this data on your behalf as a data processor. * **Third-Party Rights:** If you are a third party whose information has been collected by a [Drippi.ai](http://Drippi.ai) user through our lead scraping features, and you wish to exercise your privacy rights (such as requesting access, correction, or deletion of your information), please contact us at [support@drippi.ai](mailto:support@drippi.ai). We will work with the relevant user to address your request, or we may direct you to contact the user directly, as they are the data controller for the information they collect. * **Retention:** Scraped lead data is retained for as long as it remains in the user's account. Users can delete this data at any time through their account settings. **2.4. Information We Collect Automatically** When you visit, use, or navigate our Services, we automatically collect certain information. This information does not reveal your specific identity but may include device and usage information. This information includes: * **Log and Usage Data:** Service-related, diagnostic, usage, and performance information, including your IP address, browser type, device characteristics, operating system, and activity within the Services (e.g., features used, pages viewed). * **Device Data:** Information about the computer, phone, or tablet you use to access the Services, including IP address, device and application ID numbers, location, and hardware model. * **Cookies and Tracking Technologies:** We use cookies and similar technologies (like web beacons and pixels) to collect and store your information. For more details, please see our Cookie Policy. **3. How We Process Your Information** We process your information for a variety of reasons, depending on how you interact with our Services. Our primary goal is to provide, improve, and administer our Services. We process your information to: * **Provide and Manage the Services:** We use your information to create and manage your account, process payments, and deliver the core functionality of our platform, including sending automated direct messages and scraping public lead information as you direct. * **Communicate with You:** We may use your information to respond to your inquiries, provide customer support, and send you service-related announcements, such as updates to our terms or policies. * **Improve Our Services:** We analyze usage data to understand how our Services are being used, identify trends, determine the effectiveness of our marketing campaigns, and develop new features. * **Ensure Security and Prevent Fraud:** We process your information as part of our efforts to keep our Services safe and secure, including monitoring for fraudulent activity and violations of our Terms of Service. * **Comply with Legal Obligations:** We may process your information to comply with applicable laws, regulations, court orders, or other legal processes. * **Market Our Services:** We may use your information to send you marketing communications about our products and services. You can opt-out of these communications at any time. **4. What Legal Bases Do We Rely On to Process Your Information?** We only process your personal information when we believe it is necessary and we have a valid legal reason (i.e., legal basis) to do so under applicable law. The legal bases we rely on depend on the Services you use and how you use them. We rely on the following legal bases: * **Performance of a Contract:** We process your personal information to provide you with our Services and to fulfill our contractual obligations to you as outlined in our Terms of Service. This includes creating your account, processing payments, and performing the automation tasks you request. * **Legitimate Interests:** We may process your information when we have a legitimate business interest in doing so, and those interests are not outweighed by your rights and interests. This includes improving our Services, ensuring security, preventing fraud, and for our marketing activities. When we process data from your Connected Twitter/X accounts for outreach and related activities, we do so based on our legitimate interest in providing a B2B marketing tool, and your legitimate interest in conducting such activities. * **Consent:** We may process your information for a specific purpose if you have given us your consent to do so. This may include sending you promotional communications or using certain cookies. You can withdraw your consent at any time. * **Legal Obligations:** We may process your information where it is necessary for compliance with a legal obligation, such as to respond to a court order or a request from a law enforcement agency. **5. When and With Whom Do We Share Your Personal Information?** We may share your personal information in specific situations with the following categories of third parties. * **Service Providers (Sub-processors):** We share your information with third-party vendors, consultants, and other service providers who perform services on our behalf and require access to such information to do that work. These include payment processors, data analytics providers, cloud hosting services, and customer support tool providers. Our major sub-processors include: * **Stripe:** For payment processing. * **Google Cloud Platform (GCP) / Firebase:** For cloud hosting and infrastructure. * **Intercom:** For customer support and live chat. * **Google Analytics:** For website analytics. * **Facebook / Meta:** For advertising and marketing analytics. *   We have contracts in place with our service providers, which are designed to help safeguard your personal information. They are prohibited from using your personal information for any purpose other than to provide the services we have contracted them for. * **Business Transfers:** We may share or transfer your information in connection with, or during negotiations of, any merger, sale of company assets, financing, or acquisition of all or a portion of our business to another company. * **Legal Obligations:** We may disclose your information where we are legally required to do so in order to comply with applicable law, governmental requests, a judicial proceeding, court order, or legal process, such as in response to a court order or a subpoena. * **Vital Interests and Legal Rights:** We may disclose your information where we believe it is necessary to investigate, prevent, or take action regarding potential violations of our policies, suspected fraud, situations involving potential threats to the safety of any person and illegal activities, or as evidence in litigation in which we are involved. We do not sell or share your personal information with third parties for their direct marketing purposes. **6. International Data Transfers** Your information may be transferred to - and maintained on - computers located outside of your state, province, country, or other governmental jurisdiction where the data protection laws may differ from those in your jurisdiction. Specifically, our Services are hosted by Google Cloud Platform (GCP) / Firebase in the United States. If you are accessing our Services from the European Economic Area (EEA), United Kingdom (UK), or Switzerland, please be aware that your information will be transferred to, stored, and processed in the United States. When we transfer your personal information to other countries, we will protect that information as described in this Privacy Policy. We take steps to ensure that international transfers of personal information are subject to appropriate safeguards. For transfers of personal data from the EEA, UK, and Switzerland, we rely on the Standard Contractual Clauses (SCCs) as a legal basis for the transfer. **7. How Long Do We Keep Your Information?** We will only keep your personal information for as long as it is necessary for the purposes set out in this Privacy Policy, unless a longer retention period is required or permitted by law (such as tax, accounting, or other legal requirements). Generally, we will keep your personal information for the period of time in which you have an account with us. When your account is terminated, we will either delete or anonymize your information. When we have no ongoing legitimate business need to process your personal information, we will either delete or anonymize such information, or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible. **8. How Do We Keep Your Information Safe?** We have implemented a system of organizational and technical security measures designed to protect the security of any personal information we process. These measures include: * **Encryption:** We use encryption (such as SSL/TLS) to protect your data in transit. * **Access Controls:** We limit access to your personal information to employees, contractors, and agents who have a business need to know. * **Secure Infrastructure:** Our services are hosted on secure servers provided by Google Cloud Platform (GCP) / Firebase. However, despite our safeguards and efforts to secure your information, no electronic transmission over the Internet or information storage technology can be guaranteed to be 100% secure. Therefore, we cannot promise or guarantee that hackers, cybercriminals, or other unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information. Although we will do our best to protect your personal information, transmission of personal information to and from our Services is at your own risk. **8.1. Data Breach Notification** In the event of a data breach that compromises the security, confidentiality, or integrity of your personal information, we will take the following actions: * **Notification to You:** We will notify affected users without undue delay and, where required by applicable law (such as GDPR), within 72 hours of becoming aware of the breach. Notification will be sent to the email address associated with your account. * **Information Provided:** Our notification will include: * A description of the nature of the breach * The categories and approximate number of individuals affected * The categories and approximate number of personal data records concerned * The likely consequences of the breach * The measures we have taken or propose to take to address the breach and mitigate its potential adverse effects * Contact information for further inquiries * **Regulatory Notification:** Where required by law, we will also notify the relevant data protection authorities of the breach within the timeframes required by applicable law. * **Remediation:** We will take immediate steps to contain and remediate the breach, including conducting a thorough investigation, implementing additional security measures, and working with law enforcement and cybersecurity experts as appropriate. If you have reason to believe that your interaction with us is no longer secure (for example, if you feel that the security of your account has been compromised), please immediately notify us at [support@drippi.ai](mailto:support@drippi.ai). **9. Do We Collect Information from Minors?** We do not knowingly solicit data from or market to children under 18 years of age. By using the Services, you represent that you are at least 18 or that you are the parent or guardian of such a minor and consent to such minor dependent's use of the Services. If we learn that personal information from users less than 18 years of age has been collected, we will deactivate the account and take reasonable measures to promptly delete such data from our records. If you become aware of any data we may have collected from children under age 18, please contact us at [support@drippi.ai](mailto:support@drippi.ai). **10. What Are Your Privacy Rights?** In some regions, such as the European Economic Area (EEA), United Kingdom (UK), and California, you have rights that allow you greater access to and control over your personal information. These may include the right to: * **Access Your Data:** Request access to and obtain a copy of your personal information. * **Request Rectification or Erasure:** Request that we correct or delete your personal information. * **Restrict Processing:** Request that we restrict the processing of your personal information. * **Data Portability:** Request that we transfer your personal information to another organization. * **Object to Processing:** Object to our processing of your personal information. To exercise any of these rights, please contact us at [support@drippi.ai](mailto:support@drippi.ai). **10.1. California Residents** If you are a California resident, you are granted specific rights regarding access to your personal information under the California Consumer Privacy Act (CCPA). You have the right to request that we disclose what personal information we collect, use, and share, and to request that we delete your personal information. You also have the right to opt-out of the sale of your personal information. **We do not sell your personal information.** To exercise your rights under the CCPA, please contact us at [support@drippi.ai](mailto:support@drippi.ai) or visit our “Do Not Sell My Personal Information” page. **10.2. European Economic Area (EEA) and UK Residents** If you are a resident of the EEA or UK, you have the right to complain to a data protection authority about our collection and use of your personal information. For more information, please contact your local data protection authority. **11. Do We Make Updates to This Notice?** Yes, we will update this notice as necessary to stay compliant with relevant laws. We may update this Privacy Policy from time to time. The updated version will be indicated by an updated "Last Updated" date. If we make material changes to this notice, we may notify you either by prominently posting a notice of such changes or by directly sending you a notification. We encourage you to review this Privacy Policy frequently to be informed of how we are protecting your information. **12. How Can You Contact Us About This Notice?** If you have questions or comments about this notice, you may contact our Data Protection Officer (DPO) Jaen, by email at [support@drippi.ai](mailto:support@drippi.ai), by phone at (443) 994-1537, or by post to: **Drippi Labs Inc.**\ Jaen\ 551 Rockwood Ct\ Annapolis, MD 21401\ United States # Terms of Service Source: https://drippi.mintlify.app/policies/terms-of-service **Last Updated:** October 27, 2025 **1. Introduction and Acceptance** This Terms of Service Agreement (the “Agreement”) is a binding legal contract between you, the user or the entity you represent (“Customer,” “you,” or “your”), and Drippi Labs Inc. (“[Drippi.ai](http://Drippi.ai),” “we,” “us,” or “our”). This Agreement governs your access to and use of the [Drippi.ai](http://Drippi.ai) software-as-a-service platform, including any associated applications, application programming interfaces (APIs), and services (collectively, the “Services”). By clicking “I Agree,” creating an account, placing an order, or by accessing or using the Services in any manner, you represent and warrant that you have the authority to bind the entity you represent to this Agreement, and you unconditionally consent to be bound by all terms, conditions, and notices contained or referenced herein. If you do not agree to all of the terms of this Agreement, you must not access or use the Services. We may amend or modify this Agreement at any time by posting the revised version on our website and providing notice to you. We may, but are not obligated to, notify you of such changes via the email address associated with your account. Your continued use of the Services after the effective date of any such modifications constitutes your acceptance of the amended Agreement. It is your responsibility to review this Agreement periodically. **PLEASE READ THIS AGREEMENT CAREFULLY, AS IT CONTAINS AN ARBITRATION AGREEMENT AND OTHER IMPORTANT INFORMATION REGARDING YOUR LEGAL RIGHTS, REMEDIES, AND OBLIGATIONS.** **2. Definitions** As used in this Agreement, the following terms shall have the meanings set forth below: * **“Affiliate”** means any entity that directly or indirectly controls, is controlled by, or is under common control with a party, where “control” means the direct or indirect ownership of more than 50% of the voting securities of such entity. * **“Connected Account”** means any third-party social media account, specifically including any Twitter account, that you link, integrate, or otherwise connect to the Services. * **“Customer Data”** means any and all information, data, text, content, and materials submitted, uploaded, or transmitted by or on behalf of the Customer to the Services, including but not limited to content for direct messages, lead information, and data scraped from public sources. * **“Documentation”** means the official user guides, technical documentation, and best practice recommendations for the Services provided by [Drippi.ai](http://Drippi.ai). * **“Intellectual Property Rights”** means all past, present, and future rights of every kind and nature, including, without limitation, copyrights, trademarks, trade secrets, patents, moral rights, and any other proprietary rights, whether registered or unregistered. * **“Order Form”** means a written or electronic document executed by you and [Drippi.ai](http://Drippi.ai) that specifies the Services to be provided, including the Subscription Term, fees, and any other applicable terms. * **“Permitted User”** means an employee, contractor, or agent of the Customer who is authorized by the Customer to access and use the Services on its behalf. * **“Platform”** means the proprietary cloud-based technology, infrastructure, and software, including any APIs, used by [Drippi.ai](http://Drippi.ai) to deliver the Services. * **“Services”** means the [Drippi.ai](http://Drippi.ai) software-as-a-service platform for sending Twitter direct messages at scale, including all related features such as lead scraping, analytics, and account management, as described on our website and in the Documentation. * **“Subscription Term”** means the initial term of your subscription to the Services as specified in an Order Form, and any subsequent renewal terms. * **“Third-Party Platforms”** means any software, applications, or services not provided by [Drippi.ai](http://Drippi.ai) that are integrated with or accessible through the Services, including but not limited to Twitter. **3. The Services** **3.1. Provision of Services** Subject to the terms and conditions of this Agreement and the applicable Order Form, [Drippi.ai](http://Drippi.ai) will provide the Services to the Customer for the Subscription Term. The Services are provided on a subscription basis and include access to the [Drippi.ai](http://Drippi.ai) platform for sending Twitter direct messages at scale, lead scraping, and other related features as described in our official Documentation. **3.2. Access and Permitted Users** Customer may access and use the Services solely for its own internal business purposes and in accordance with the scope of use restrictions designated in the applicable Order Form. Access is granted only to Permitted Users. Customer is responsible for all actions taken by Permitted Users and for ensuring their compliance with this Agreement. User accounts are for named individuals and may not be shared. **3.3. Connected Accounts and Third-Party Platform Compliance** To utilize the full functionality of the Services, you must connect one or more Twitter accounts to the [Drippi.ai](http://Drippi.ai) platform. By granting [Drippi.ai](http://Drippi.ai) access to a Connected Account, you represent, warrant, and acknowledge that: (a) You are an authorized user of the Connected Account and have the authority to grant us access; (b) **You are solely responsible for ensuring that your use of the Services complies with the terms of service, policies, and rules of any Third-Party Platform, including Twitter/X.** You acknowledge that the use of automation tools may violate the terms of service of certain Third-Party Platforms, and you assume all risk and liability associated with such use; (c) You grant [Drippi.ai](http://Drippi.ai) permission to access, store, and use your Connected Account data to the extent necessary to provide the Services, including sending messages, scraping public information, and analyzing performance on your behalf; (d) [******You understand and accept that Third-Party Platforms, including Twitter/X, may suspend, ban, or take other adverse action against your Connected Account as a result of using automation tools, and you agree that Drippi.ai has no liability or responsibility for any such actions taken by Third-Party Platforms;******](http://Drippi.ai) (e) You will not hold [Drippi.ai](http://Drippi.ai) responsible for any consequences arising from your use of the Services, including but not limited to account suspension, termination, data loss, or any other penalties imposed by Third-Party Platforms. Customer acknowledges that the availability of the Services is dependent on the continued availability of the APIs and services of Third-Party Platforms like Twitter. [Drippi.ai](http://Drippi.ai) shall have no liability for any unavailability of the Services or any feature that results from the decision of a Third-Party Platform to suspend, terminate, or change its API or services. **3.4. General Restrictions** You shall not (and shall not permit any third party to): (a) Rent, lease, sublicense, or provide access to the Services to any third party;\ (b) Use the Services to build a competitive product or service;\ (c) Reverse engineer, decompile, or otherwise attempt to discover the source code or non-public APIs of the Platform;\ (d) Use the Services for any illegal, harmful, or fraudulent activities;\ (e) Interfere with the security, integrity, or performance of the Platform. **4. Subscription, Renewal, and Fees** **4.1. Subscription Term and Auto-Renewal** Your subscription to the Services will commence on the date specified in your Order Form and will continue for the initial Subscription Term. **Unless you cancel your subscription in accordance with Section 4.4, your subscription will automatically renew for additional periods of the same duration as the initial Subscription Term at our then-current fees.** **4.2. Fees and Payment** You agree to pay all fees specified in the applicable Order Form. All fees are due in advance at the start of the Subscription Term and are non-refundable. Payments will be processed through a third-party payment processor, and you agree to abide by their terms and conditions. **4.3. Credits** The Services operate on a credit-based system. Upon subscribing, you will receive a specified number of credits that can be used for various actions within the platform, such as sending messages or scraping leads. Credits are consumed as described in the Documentation. Unused credits may or may not roll over, depending on the terms of your specific subscription plan. We do not provide refunds for unused credits. **4.4. Cancellation Policy** You may cancel your subscription by contacting your account manager or through your account settings at least five (5) days prior to your next renewal date. In some instances, you may be required to schedule a cancellation call with your account manager as part of the cancellation process; however, attendance at such call is not mandatory for the cancellation to be processed. Your cancellation will become effective at the end of the current paid Subscription Term. **4.5. Chargebacks** If you initiate a chargeback or payment dispute with your credit card company, we will consider your account to be in breach of this Agreement. Your account will be immediately suspended, and you explicitly agree to transfer ownership of all Customer Data within the account to us to cover the costs and damages incurred. We reserve the right to pursue legal action to recover any outstanding fees and damages. **5. Acceptable Use Policy** You agree not to use the Services to: (a) Send spam, unsolicited messages, or any other communication that violates applicable laws;\ (b) Harass, abuse, threaten, or defame any person or entity;\ (c) Distribute illegal, obscene, hateful, or otherwise objectionable content;\ (d) Infringe upon the intellectual property rights of any third party;\ (e) Engage in any activity that is fraudulent, deceptive, or misleading;\ (f) Scrape data in a manner that violates the terms of the source website or any applicable laws;\ (g) Introduce any viruses, worms, trojan horses, or other malicious code into the Platform. A breach of this Acceptable Use Policy constitutes a material breach of this Agreement, and we reserve the right to suspend or terminate your account immediately, without notice and without refund, if we determine, in our sole discretion, that you have violated this policy. **6. Intellectual Property Rights** [******6.1. Drippi.ai IP******](http://Drippi.ai) As between the parties, [Drippi.ai](http://Drippi.ai) owns all right, title, and interest, including all Intellectual Property Rights, in and to the Services, the Platform, the Documentation, and any improvements, modifications, or derivative works thereof. We grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Services during the Subscription Term, strictly for the purposes permitted by this Agreement. No rights or licenses are granted except as expressly set forth herein. **6.2. Customer Data** As between the parties, you own all right, title, and interest in and to your Customer Data. You hereby grant [Drippi.ai](http://Drippi.ai) a non-exclusive, worldwide, royalty-free right and license to use, copy, store, transmit, modify, and display your Customer Data solely to the extent necessary to provide, maintain, and improve the Services for you. **6.3. Feedback** If you provide us with any suggestions, comments, or other feedback relating to the Services (“Feedback”), you hereby assign to us all right, title, and interest in and to such Feedback. We are free to use, implement, and exploit any such Feedback for any purpose without any obligation or compensation to you. **7. Confidentiality** Each party (the "Receiving Party") understands that the other party (the "Disclosing Party") may disclose business, technical, or financial information relating to the Disclosing Party's business that is marked as confidential or should reasonably be known to be confidential (hereinafter referred to as "Confidential Information"). The Receiving Party agrees to take reasonable precautions to protect such Confidential Information and not to use or divulge to any third person any such Confidential Information, except as expressly permitted herein. The Disclosing Party agrees that the foregoing shall not apply with respect to any information that the Receiving Party can document (a) is or becomes generally available to the public, or (b) was in its possession or known by it prior to receipt from the Disclosing Party, or (c) was rightfully disclosed to it without restriction by a third party. **8. Warranties and Disclaimers** **8.1. Mutual Warranties** Each party represents and warrants that it has the legal power and authority to enter into this Agreement. **8.2. Customer Warranties** You warrant that you have obtained all necessary rights, consents, and permissions to provide and use the Customer Data in connection with the Services and that your use of the Services will not violate any applicable laws or third-party rights. **8.3. Disclaimer** EXCEPT AS EXPRESSLY PROVIDED FOR HEREIN, THE SERVICES AND ALL RELATED COMPONENTS AND INFORMATION ARE PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS WITHOUT ANY WARRANTIES OF ANY KIND, AND WE EXPRESSLY DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. YOU ACKNOWLEDGE THAT [DRIPPI.AI](http://DRIPPI.AI) DOES NOT WARRANT THAT THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE. THE USE OF THE SERVICES IS AT YOUR OWN RISK. [DRIPPI.AI](http://DRIPPI.AI) IS NOT RESPONSIBLE FOR THE ACTIONS OR POLICIES OF ANY THIRD-PARTY PLATFORM, INCLUDING TWITTER. **8.4. Third-Party Platform Risk and Compliance Disclaimer** **YOU EXPRESSLY ACKNOWLEDGE AND AGREE THAT:** (a) **THE SERVICES INVOLVE AUTOMATION THAT MAY VIOLATE THE TERMS OF SERVICE OF THIRD-PARTY PLATFORMS, INCLUDING TWITTER/X;** (b) [**DRIPPI.AI**](http://DRIPPI.AI)\*\* MAKES NO REPRESENTATION OR WARRANTY THAT YOUR USE OF THE SERVICES WILL COMPLY WITH THE TERMS OF SERVICE OF ANY THIRD-PARTY PLATFORM;\*\* (c) **YOU ARE SOLELY RESPONSIBLE FOR DETERMINING WHETHER YOUR USE OF THE SERVICES COMPLIES WITH THE TERMS OF SERVICE OF ANY THIRD-PARTY PLATFORM AND FOR ANY CONSEQUENCES OF NON-COMPLIANCE;** (d) [**DRIPPI.AI**](http://DRIPPI.AI)\*\* SHALL HAVE NO LIABILITY WHATSOEVER FOR ANY SUSPENSION, TERMINATION, OR OTHER ADVERSE ACTION TAKEN BY ANY THIRD-PARTY PLATFORM AGAINST YOUR ACCOUNT, INCLUDING BUT NOT LIMITED TO PERMANENT BANS, TEMPORARY SUSPENSIONS, LOSS OF DATA, OR LOSS OF ACCESS;\*\* (e) [******YOU ASSUME ALL RISK ASSOCIATED WITH USING AUTOMATION TOOLS ON THIRD-PARTY PLATFORMS, AND YOU AGREE TO HOLD DRIPPI.AI HARMLESS FROM ANY AND ALL CLAIMS, DAMAGES, OR LOSSES ARISING FROM OR RELATED TO ACTIONS TAKEN BY THIRD-PARTY PLATFORMS AGAINST YOUR ACCOUNT.******](http://DRIPPI.AI) **9. Limitation of Liability** IN NO EVENT SHALL [DRIPPI.AI](http://DRIPPI.AI), ITS AFFILIATES, DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION, LOSS OF PROFITS, DATA, USE, GOODWILL, OR OTHER INTANGIBLE LOSSES, RESULTING FROM (I) YOUR ACCESS TO OR USE OF OR INABILITY TO ACCESS OR USE THE SERVICES; (II) ANY CONDUCT OR CONTENT OF ANY THIRD PARTY ON THE SERVICES; (III) ANY CONTENT OBTAINED FROM THE SERVICES; (IV) UNAUTHORIZED ACCESS, USE, OR ALTERATION OF YOUR TRANSMISSIONS OR CONTENT; (V) **ANY ACTION TAKEN BY ANY THIRD-PARTY PLATFORM, INCLUDING BUT NOT LIMITED TO ACCOUNT SUSPENSION, TERMINATION, OR RESTRICTION;** AND (VI) **YOUR VIOLATION OF ANY THIRD-PARTY PLATFORM'S TERMS OF SERVICE,** WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), OR ANY OTHER LEGAL THEORY, WHETHER OR NOT WE HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE. IN NO EVENT SHALL [DRIPPI.AI](http://DRIPPI.AI)’S AGGREGATE LIABILITY FOR ALL CLAIMS RELATING TO THE SERVICES EXCEED THE GREATER OF (A) ONE HUNDRED U.S. DOLLARS (\$100) OR (B) THE TOTAL AMOUNT OF FEES PAID BY YOU TO [DRIPPI.AI](http://DRIPPI.AI) FOR THE SERVICES DURING THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM. **10. Indemnification** You agree to defend, indemnify, and hold harmless [Drippi.ai](http://Drippi.ai), its Affiliates, and their respective officers, directors, employees, and agents from and against any and all claims, damages, obligations, losses, liabilities, costs, or debt, and expenses (including but not limited to attorney's fees) arising from: (a) Your use of and access to the Services;\ (b) Your violation of any term of this Agreement;\ (c) Your violation of any third-party right, including without limitation any copyright, property, or privacy right;\ (d) Any claim that your Customer Data caused damage to a third party;\ (e) Your violation of any applicable laws, rules, or regulations;\ (f)**Your violation of any Third-Party Platform's terms of service, policies, or rules, including but not limited to Twitter/X's Terms of Service;**(g) [******Any action taken by any Third-Party Platform against your account or against Drippi.ai as a result of your use of the Services; or******](http://Drippi.ai)(h) **Any claim by any third party arising from your use of automation tools on Third-Party Platforms.** **11. Dispute Resolution and Arbitration Agreement** **11.1. Governing Law** This Agreement shall be governed by and construed in accordance with the laws of the State of Maryland, without regard to its conflict of law principles. **11.2. Arbitration** Any dispute, claim, or controversy arising out of or relating to this Agreement or the breach, termination, enforcement, interpretation, or validity thereof, including the determination of the scope or applicability of this agreement to arbitrate, shall be determined by arbitration in Maryland before one arbitrator. The arbitration shall be administered by JAMS pursuant to its Comprehensive Arbitration Rules and Procedures. Judgment on the Award may be entered in any court having jurisdiction. **11.3. Class Action and Jury Trial Waiver** YOU AND [DRIPPI.AI](http://DRIPPI.AI) AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN YOUR OR ITS INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE PROCEEDING. Further, unless both you and [Drippi.ai](http://Drippi.ai) agree otherwise, the arbitrator may not consolidate more than one person's claims, and may not otherwise preside over any form of a representative or class proceeding. YOU AND [DRIPPI.AI](http://DRIPPI.AI) HEREBY WAIVE ANY CONSTITUTIONAL AND STATUTORY RIGHTS TO SUE IN COURT AND HAVE A TRIAL IN FRONT OF A JUDGE OR A JURY. You and [Drippi.ai](http://Drippi.ai) are instead electing that all claims and disputes shall be resolved by arbitration under this Arbitration Agreement. **12. General Provisions** **12.1. Entire Agreement** This Agreement, together with any Order Forms and any other policies referenced herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, or representations, written or oral, concerning its subject matter. **12.2. Severability** If any provision of this Agreement is held by a court of competent jurisdiction to be contrary to law, the provision will be modified by the court and interpreted so as best to accomplish the objectives of the original provision to the fullest extent permitted by law, and the remaining provisions of this Agreement will remain in effect. **12.3. Assignment** You may not assign or transfer this Agreement, by operation of law or otherwise, without our prior written consent. Any attempt by you to assign or transfer this Agreement, without such consent, will be null and of no effect. We may assign or transfer this Agreement, at our sole discretion, without restriction. **12.4. Notices** All notices under this Agreement will be in writing and will be deemed to have been duly given when received, if personally delivered; when receipt is electronically confirmed, if transmitted by facsimile or e-mail; the day after it is sent, if sent for next day delivery by recognized overnight delivery service; and upon receipt, if sent by certified or registered mail, return receipt requested. Notices to [Drippi.ai](http://Drippi.ai) should be sent to [support@drippi.ai](mailto:support@drippi.ai). **12.5. Contact Information** If you have any questions about these Terms of Service, please contact us at [support@drippi.ai](mailto:support@drippi.ai). # Webhook Events Source: https://drippi.mintlify.app/webhooks/events Complete reference for all Drippi webhook events and their payloads ## Event Types Drippi sends webhooks for the following automation events: | Event Type | Description | Triggers | | ------------------------- | ------------------------------- | ------------------------------------------------------ | | `cold_dm.sent` | Cold DM successfully sent | When an initial message is sent to a new lead | | `followup.sent` | Follow-up message sent | When a follow-up message is sent to an existing lead | | `reply.received` | Lead replied to automation | When a lead responds to your automation messages | | `automation.paused` | Automation automatically paused | When system pauses automation due to limits or issues | | `automation.out_of_leads` | Automation has no more leads | When automation runs out of available leads to contact | ## Common Payload Structure All webhook events share a common base structure: ```json theme={null} { "event": "event_type", "user_id": "string", "created_at": "2024-01-15T10:30:00.000Z", "data": { // Event-specific data } } ``` ### Base Fields | Field | Type | Description | | ------------ | ------ | ------------------------------------------ | | `event` | string | The webhook event type | | `user_id` | string | Drippi user ID who owns the automation | | `created_at` | string | ISO 8601 timestamp when the event occurred | | `data` | object | Event-specific payload data | ## Event Details ### cold\_dm.sent Triggered when a cold DM is successfully sent to a new lead. ```json Example Payload theme={null} { "event": "cold_dm.sent", "user_id": "user_123456", "created_at": "2024-01-15T10:30:00.000Z", "data": { "event": "cold_dm.sent", "user_id": "user_123456", "automation_id": "automation_789", "lead_twitter_id": "1234567890", "lead_data": { "id": "1234567890", "name": "John Doe", "username": "johndoe", "created_at": "2020-01-01T00:00:00.000Z", "protected": false, "location": "San Francisco, CA", "url": "https://johndoe.com", "description": "Tech entrepreneur and investor", "verified": false, "entities": { "url": { "urls": [] }, "description": { "urls": [], "hashtags": [], "mentions": [], "cashtags": [] } }, "profile_image_url": "https://pbs.twimg.com/profile_images/123/avatar.jpg", "public_metrics": { "followers_count": 1500, "following_count": 300, "tweet_count": 850, "listed_count": 25 }, "pinned_tweet_id": null }, "message": "Hi John, I noticed you're interested in tech startups..." } } ``` ```typescript TypeScript Type theme={null} type ColdDmSentWebhook = { event: 'cold_dm.sent'; user_id: string; created_at: string; data: { event: 'cold_dm.sent'; user_id: string; automation_id: string; lead_twitter_id: string; lead_data: DrippiTwitterUser; message: string; }; }; ``` ### followup.sent Triggered when a follow-up message is sent to an existing lead. ```json Example Payload theme={null} { "event": "followup.sent", "user_id": "user_123456", "created_at": "2024-01-15T14:45:00.000Z", "data": { "event": "followup.sent", "user_id": "user_123456", "automation_id": "automation_789", "lead_twitter_id": "1234567890", "lead_data": { "id": "1234567890", "name": "John Doe", "username": "johndoe", "created_at": "2020-01-01T00:00:00.000Z", "protected": false, "location": "San Francisco, CA", "url": "https://johndoe.com", "description": "Tech entrepreneur and investor", "verified": false, "entities": { "url": { "urls": [] }, "description": { "urls": [], "hashtags": [], "mentions": [], "cashtags": [] } }, "profile_image_url": "https://pbs.twimg.com/profile_images/123/avatar.jpg", "public_metrics": { "followers_count": 1500, "following_count": 300, "tweet_count": 850, "listed_count": 25 }, "pinned_tweet_id": null }, "message": "Just wanted to follow up on my previous message about..." } } ``` ```typescript TypeScript Type theme={null} type FollowupSentWebhook = { event: 'followup.sent'; user_id: string; created_at: string; data: { event: 'followup.sent'; user_id: string; automation_id: string; lead_twitter_id: string; lead_data: DrippiTwitterUser; message: string; }; }; ``` ### reply.received Triggered when a lead replies to your automation messages. ```json Example Payload theme={null} { "event": "reply.received", "user_id": "user_123456", "created_at": "2024-01-15T16:20:00.000Z", "data": { "event": "reply.received", "user_id": "user_123456", "automation_id": "automation_789", "lead_twitter_id": "1234567890", "lead_data": { "id": "1234567890", "name": "John Doe", "username": "johndoe", "created_at": "2020-01-01T00:00:00.000Z", "protected": false, "location": "San Francisco, CA", "url": "https://johndoe.com", "description": "Tech entrepreneur and investor", "verified": false, "entities": { "url": { "urls": [] }, "description": { "urls": [], "hashtags": [], "mentions": [], "cashtags": [] } }, "profile_image_url": "https://pbs.twimg.com/profile_images/123/avatar.jpg", "public_metrics": { "followers_count": 1500, "following_count": 300, "tweet_count": 850, "listed_count": 25 }, "pinned_tweet_id": null } } } ``` ```typescript TypeScript Type theme={null} type ReplyReceivedWebhook = { event: 'reply.received'; user_id: string; created_at: string; data: { event: 'reply.received'; user_id: string; automation_id: string; lead_twitter_id: string; lead_data: DrippiTwitterUser; }; }; ``` ### automation.paused Triggered when an automation is automatically paused by the system (not by user action). ```json Example Payload theme={null} { "event": "automation.paused", "user_id": "user_123456", "created_at": "2024-01-15T18:00:00.000Z", "data": { "event": "automation.paused", "user_id": "user_123456", "automation_id": "automation_789", "details": "automation paused - daily_message_limit_reached" } } ``` ```typescript TypeScript Type theme={null} type AutomationPausedWebhook = { event: 'automation.paused'; user_id: string; created_at: string; data: { event: 'automation.paused'; user_id: string; automation_id: string; details: string; }; }; ``` **Pause Reasons:** * `automation paused - too many messages` * `automation paused - account is not verified` * `automation paused - daily_message_limit_reached` * `disconnected pause` ### automation.out\_of\_leads Triggered when an automation runs out of available leads to contact. ```json Example Payload theme={null} { "event": "automation.out_of_leads", "user_id": "user_123456", "created_at": "2024-01-15T20:15:00.000Z", "data": { "event": "automation.out_of_leads", "user_id": "user_123456", "automation_id": "automation_789" } } ``` ```typescript TypeScript Type theme={null} type AutomationOutOfLeadsWebhook = { event: 'automation.out_of_leads'; user_id: string; created_at: string; data: { event: 'automation.out_of_leads'; user_id: string; automation_id: string; }; }; ``` ## Lead Data Structure The `lead_data` field contains detailed Twitter profile information for the lead: ```typescript theme={null} type DrippiTwitterUser = { id: string; // Twitter user ID name: string; // Display name username: string; // Twitter handle (without @) created_at: string; // ISO 8601 account creation date protected: boolean | null; // Whether account is protected location: string | null; // User's location url: string | null; // User's website URL description: string | null; // Bio/description verified: boolean | null; // Twitter verification status entities: { url: { urls: any[]; }; description: { urls: any[]; hashtags: any[]; mentions: any[]; cashtags: any[]; }; }; profile_image_url: string; // Profile picture URL public_metrics: { followers_count: number; // Number of followers following_count: number; // Number of following tweet_count: number; // Total tweets listed_count: number; // Times listed }; pinned_tweet_id: string | null; // ID of pinned tweet gqlId?: string; // GraphQL ID (optional) }; ``` ## Handling Webhook Events ### Example Event Handler ```javascript theme={null} app.post('/webhook', (req, res) => { const { event, user_id, created_at, data } = req.body; switch (event) { case 'cold_dm.sent': console.log(`Cold DM sent to @${data.lead_data.username}`); // Track successful outreach break; case 'followup.sent': console.log(`Follow-up sent to @${data.lead_data.username}`); // Track follow-up engagement break; case 'reply.received': console.log(`Reply from @${data.lead_data.username}`); // Notify sales team break; case 'automation.paused': console.log(`Automation paused: ${data.details}`); // Alert user to take action break; case 'automation.out_of_leads': console.log(`Automation ${data.automation_id} needs more leads`); // Trigger lead generation process break; default: console.log(`Unknown event type: ${event}`); } res.status(200).send('OK'); }); ``` ### Idempotency Implement idempotency to handle duplicate webhook deliveries: ```javascript theme={null} const processedEvents = new Set(); app.post('/webhook', (req, res) => { const { event, user_id, created_at, data } = req.body; // Create unique event identifier const eventId = `${event}_${user_id}_${created_at}_${data.automation_id}`; // Check if already processed if (processedEvents.has(eventId)) { console.log(`Duplicate event ignored: ${eventId}`); return res.status(200).send('OK'); } // Process the event processEvent(req.body); // Mark as processed processedEvents.add(eventId); res.status(200).send('OK'); }); ``` ## Next Steps * [Webhook Verification](/webhooks/verification) - Learn how to verify webhook signatures * [Webhooks Overview](/webhooks/introduction) - Get started with webhooks # Webhooks Overview Source: https://drippi.mintlify.app/webhooks/introduction Real-time notifications for automation events in your Drippi account ## What are Webhooks? Webhooks allow you to receive real-time HTTP notifications when specific events occur in your Drippi automations. Instead of polling our API repeatedly, webhooks push data to your application instantly when events happen. ## How Webhooks Work When you create a webhook endpoint, Drippi will send HTTP POST requests to your specified URL whenever the subscribed events occur. Each webhook payload contains detailed information about the event, including: * Event type and timestamp * User and automation identifiers * Lead information (when applicable) * Message content (for message events) ## Webhook Events Drippi supports the following webhook events: | Event | Description | | ------------------------- | ------------------------------------------------------------------ | | `cold_dm.sent` | Triggered when a cold DM is successfully sent to a lead | | `followup.sent` | Triggered when a follow-up message is sent to a lead | | `reply.received` | Triggered when a lead replies to your automation | | `automation.paused` | Triggered when an automation is automatically paused by the system | | `automation.out_of_leads` | Triggered when an automation runs out of available leads | ## Getting Started ### 1. Create a Webhook Endpoint Use the [Drippi dashboard](https://app.drippi.ai/settings/webhooks) to create a webhook endpoint by providing: * **URL**: Your endpoint that will receive webhook notifications * **Events**: Array of event types you want to subscribe to ### 2. Verify Webhook Signatures All webhook requests include a signature in the `X-Drippi-Signature` header that you should verify to ensure the request came from Drippi. ### 3. Handle Webhook Payloads Your endpoint should: * Respond with a 2xx status code to acknowledge receipt * Process the webhook payload asynchronously if possible * Implement idempotency to handle duplicate deliveries ## Webhook Delivery ### Retry Logic Drippi implements an exponential backoff retry strategy: * **Retries**: Up to 5 attempts * **Initial Interval**: 1 second * **Strategy**: Exponential backoff ### Timeouts Webhook requests have a 30-second timeout. Your endpoint should respond quickly to avoid timeouts. ### Filtering Webhooks are automatically filtered by: * **User ID**: You only receive events for your account * **Event Types**: Only subscribed event types are delivered * **Status**: Only successful events trigger webhooks (errors are not sent) ## Best Practices 1. **Verify Signatures**: Always verify the `X-Drippi-Signature` header 2. **Respond Quickly**: Return a 2xx status code as soon as possible 3. **Handle Duplicates**: Implement idempotency using the event timestamp and IDs 4. **Process Asynchronously**: Queue webhook processing to avoid timeouts 5. **Monitor Failures**: Set up alerts for webhook delivery failures ## Security * Webhook URLs should use HTTPS * Verify webhook signatures to prevent spoofing * Consider implementing IP allowlisting for additional security * Store signing secrets securely ## Next Steps * [Webhook Verification](/webhooks/verification) - Learn how to verify webhook signatures * [Webhook Events](/webhooks/events) - Detailed documentation of all webhook events # Webhook Verification Source: https://drippi.mintlify.app/webhooks/verification How to verify webhook signatures to ensure requests are authentic ## Overview All Drippi webhook requests include a signature in the `X-Drippi-Signature` header that you must verify to ensure the request authentically came from Drippi and hasn't been tampered with. ## Signature Format The signature is a HMAC-SHA256 hash of the request body using your webhook's signing secret: ``` X-Drippi-Signature: sha256= ``` ## Getting Your Signing Secret When you create a webhook endpoint, Drippi generates a unique signing secret for that endpoint. This secret is returned in the API response and should be stored securely in your application. ## Verification Examples ### Node.js ```javascript theme={null} const crypto = require('crypto'); function verifyWebhookSignature(payload, signature, secret) { // Remove 'sha256=' prefix from signature const receivedSignature = signature.replace('sha256=', ''); // Calculate expected signature const expectedSignature = crypto.createHmac('sha256', secret).update(payload, 'utf8').digest('hex'); // Compare signatures using timing-safe comparison return crypto.timingSafeEqual(Buffer.from(receivedSignature, 'hex'), Buffer.from(expectedSignature, 'hex')); } // Express.js example app.post('/webhook', express.raw({ type: 'application/json' }), (req, res) => { const signature = req.headers['x-drippi-signature']; const payload = req.body; const secret = process.env.DRIPPI_WEBHOOK_SECRET; if (!verifyWebhookSignature(payload, signature, secret)) { console.error('Invalid webhook signature'); return res.status(401).send('Unauthorized'); } // Process the webhook const event = JSON.parse(payload); console.log('Received webhook:', event.event); res.status(200).send('OK'); }); ``` ### Python ```python theme={null} import hashlib import hmac import json from flask import Flask, request, abort app = Flask(__name__) def verify_webhook_signature(payload, signature, secret): """Verify the webhook signature""" # Remove 'sha256=' prefix from signature received_signature = signature.replace('sha256=', '') # Calculate expected signature expected_signature = hmac.new( secret.encode('utf-8'), payload, hashlib.sha256 ).hexdigest() # Compare signatures using timing-safe comparison return hmac.compare_digest(received_signature, expected_signature) @app.route('/webhook', methods=['POST']) def handle_webhook(): signature = request.headers.get('X-Drippi-Signature') payload = request.get_data() secret = os.environ.get('DRIPPI_WEBHOOK_SECRET') if not verify_webhook_signature(payload, signature, secret): print('Invalid webhook signature') abort(401) # Process the webhook event = json.loads(payload) print(f'Received webhook: {event["event"]}') return 'OK', 200 ``` ### PHP ```php theme={null} ``` ### Go ```go theme={null} package main import ( "crypto/hmac" "crypto/sha256" "encoding/hex" "encoding/json" "fmt" "io" "log" "net/http" "os" "strings" ) func verifyWebhookSignature(payload []byte, signature, secret string) bool { // Remove 'sha256=' prefix from signature receivedSignature := strings.TrimPrefix(signature, "sha256=") // Calculate expected signature mac := hmac.New(sha256.New, []byte(secret)) mac.Write(payload) expectedSignature := hex.EncodeToString(mac.Sum(nil)) // Compare signatures using timing-safe comparison return hmac.Equal([]byte(receivedSignature), []byte(expectedSignature)) } func webhookHandler(w http.ResponseWriter, r *http.Request) { if r.Method != http.MethodPost { http.Error(w, "Method not allowed", http.StatusMethodNotAllowed) return } signature := r.Header.Get("X-Drippi-Signature") secret := os.Getenv("DRIPPI_WEBHOOK_SECRET") payload, err := io.ReadAll(r.Body) if err != nil { http.Error(w, "Error reading request body", http.StatusBadRequest) return } if !verifyWebhookSignature(payload, signature, secret) { log.Println("Invalid webhook signature") http.Error(w, "Unauthorized", http.StatusUnauthorized) return } // Process the webhook var event map[string]interface{} if err := json.Unmarshal(payload, &event); err != nil { http.Error(w, "Error parsing JSON", http.StatusBadRequest) return } log.Printf("Received webhook: %s", event["event"]) w.WriteHeader(http.StatusOK) fmt.Fprint(w, "OK") } func main() { http.HandleFunc("/webhook", webhookHandler) log.Fatal(http.ListenAndServe(":8080", nil)) } ``` ## Security Best Practices ### 1. Always Verify Signatures Never process webhook payloads without first verifying the signature. This prevents malicious actors from sending fake webhook requests. ### 2. Use Timing-Safe Comparison Use timing-safe comparison functions (like `crypto.timingSafeEqual()` in Node.js) to prevent timing attacks when comparing signatures. ### 3. Store Secrets Securely Store your webhook signing secrets in environment variables or a secure key management system. Never hardcode them in your application. ### 4. Use HTTPS Always use HTTPS endpoints for your webhooks to prevent man-in-the-middle attacks. ### 5. Validate Payload Structure After verifying the signature, validate that the payload structure matches the expected webhook format. ## Troubleshooting ### Common Issues **Signature Mismatch** * Ensure you're using the correct signing secret for the webhook endpoint * Verify you're using the raw request body (not parsed JSON) for signature calculation * Check that you're removing the 'sha256=' prefix from the signature header **Missing Signature Header** * Ensure your webhook endpoint URL is correctly configured * Check that you're reading the `X-Drippi-Signature` header (case-sensitive) **Encoding Issues** * Use UTF-8 encoding when calculating the HMAC signature * Ensure consistent encoding between signature calculation and verification ## Testing Your Implementation You can test your webhook verification by: 1. Creating a test webhook endpoint in the Drippi dashboard 2. Triggering test events from your automations 3. Logging successful and failed verification attempts 4. Using webhook testing tools to send sample payloads ## Next Steps * [Webhook Events](/webhooks/events) - Learn about all available webhook events and their payloads