Sourcebot procurement policy evidence
Only topics backed by verified findings appear below. Each row preserves the platform's exact policy words and capture provenance.
| Topic | Plan or tier | Risk | Their words | Source |
|---|---|---|---|---|
| DPA, audit rights & data residency | All applicable tiers | low | “ 4.4 License Compliance. In accordance with this Agreement and the Documentation, Provider has the right to (i) verify electronically (or otherwise), and generate, or (ii) require Customer to generate and provide, reports related to Customer’s installation of, access to, and use of the Software to ensure compliance with the terms of this Agreement. Customer shall maintain Customer Records during the term of this Agreement and for two (2) years thereafter. Provider may, upon thirty (30) days prior written notice to Customer and during Customer’s normal business hours and subject to industry-standard confidentiality obligations, hire an independent third-party auditor to audit the Customer Records only to verify the amounts payable under this Agreement with respect to Customer usage of the Software. If an audit reveals underpayment, Customer shall promptly pay the deficiency to Provider plus late fees pursuant to Section 5. Provider shall bear the cost of an audit unless the audit reveals underpayment by more than 5% of the Fees payable for the audited period, in which case Customer shall promptly pay Provider for the reasonable costs of the audit.” | Captured 2026-09-25Open source →Finding permalink → |
| DPA, audit rights & data residency | All applicable tiers | unknown | “ Depending on where you live, you may have rights to access, correct, delete, export, or restrict our processing of your personal data, and to object to processing or withdraw consent. To exercise any of these rights, email legal@sourcebot.dev.” | Captured 2026-09-25Open source →Finding permalink → |
| DPA, audit rights & data residency | All applicable tiers | unknown | “ 1.6 “Customer Records” means books, records, contracts and accounts, records of Software usage and the number of Users, as each relates to the payments due to Provider under this Agreement.” | Captured 2026-09-25Open source →Finding permalink → |
| Data retention | All applicable tiers | unknown | “ 7.4 Effect of Termination. Upon any expiration or termination of this Agreement: (a) all licenses granted hereunder shall immediately terminate; (b) Customer shall cease all use of the Software; (c) each Party shall promptly return or destroy all Confidential Information of the other Party; and (d) Provider shall submit a final invoice for all outstanding Fees, which Customer shall pay in accordance with Section 5.” | Captured 2026-09-25Open source →Finding permalink → |
| Data retention | All applicable tiers | low | “ Self-hosted product telemetry: Retained in aggregate; identifiable session-level events deleted within 12 months. Service Ping data: Retained for the lifetime of the deployment plus 24 months, to support historical trend analysis and customer success. Trial and subscription records: Retained for the duration of your relationship with us and for a reasonable period afterward to comply with legal and tax obligations. Cloud accounts: Retained while your account is active. You can delete your account at any time; we will delete your personal data within 30 days, except where retention is required by law. Website analytics: Retained for up to 24 months.” | Captured 2026-09-25Open source →Finding permalink → |
| Subprocessors & data sharing | All applicable tiers | unknown | “ When you check out from inside your self-hosted deployment to start a trial or purchase a subscription, we receive the information necessary to perform the checkout. This consists of: The full name, email address, and organization name that you provided to Sourcebot during onboarding. For paid subscriptions, your payment information, which is collected and processed directly by Stripe, our payment processor. We do not see or store your payment card details. This is the only situation in which identifiable information about your users is transmitted to us from a self- hosted deployment, and it only happens when you initiate a checkout. We use this information to:” | Captured 2026-09-25Open source →Finding permalink → |
| Subprocessors & data sharing | All applicable tiers | medium | “ We share personal information only with service providers who help us run our business, under contractual confidentiality and data protection obligations. These currently include: Stripe: payment processing for subscriptions, including checkouts initiated from inside self-hosted deployments PostHog: product analytics, telemetry, and session recordings (website and cloud only; session recordings are not collected from self-hosted deployments) Reo.dev: website visitor identification and enrichment of Service Ping data (deployment hostname and the IP address the ping was sent from) to associate visits and self-hosted deployments with organizations Google Analytics: website traffic, campaign attribution, and usage analytics (marketing site only) LinkedIn: advertising measurement and attribution for visits and conversions associated with LinkedIn campaigns (marketing site only) X: advertising measurement and attribution for visits and conversions associated with X campaigns (marketing site and documentation) Cloud infrastructure providers: for hosting the cloud deployment and supporting services Email and communications providers: for transactional and product update emails We may also disclose information when required by law, to protect our rights or those of our users, or in connection with a merger, acquisition, or sale of assets.” | Captured 2026-09-25Open source →Finding permalink → |
| Subprocessors & data sharing | All applicable tiers | unknown | “ Standard web analytics and campaign measurement data via Google Analytics, PostHog, LinkedIn, X, and Reo.dev (pages visited, referrer, campaign parameters, approximate location from IP, and browser type) Session recordings via PostHog, which capture how you interact with the site (clicks, navigation, scrolls). We use these to understand and improve the user experience. Sensitive form inputs are masked. Cookies and similar browser storage used to remember preferences, attribute campaigns, and measure site usage We use this to respond to your inquiries and improve the site.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | medium | “However: Free tier: Blocking Service Ping does not affect your ability to use Sourcebot. Pro tier with an online license: The Service Ping endpoint is the same endpoint that verifies your license. Blocking it will prevent license verification and, after an extended period, cause the software to suspend operation as described in our Software License Agreement . If you need to operate in a fully air-gapped environment on the Pro tier, contact us about an offline license.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | unknown | “ 5.4 Add-On User Activation. During the Subscription Term, Customer may, subject to this Agreement, activate and use Add-On Users. For the avoidance of doubt, Customer shall not have the right to report less than the number of Users originally purchased under the Subscription, and all Add-On Users shall be co-termed to the underlying Subscription Term.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | medium | “ 2.2 Free Software. Customer acknowledges and agrees that Free Software may be: (i) modified and/or updated, without notice, and (ii) limited in functionality, features, maintenance, support and contain other limitations not present in Software purchased pursuant to an Order Form or Web-Portal Purchase. DESPITE THE “WARRANTY”, “LIMITATION OF LIABILITY”, AND “INDEMNIFICATION” SECTIONS BELOW, FREE SOFTWARE AND SOFTWARE OFFERED ON A TRIAL BASIS (AS STATED IN AN ORDER FORM OR WEB-PORTAL PURCHASE) ARE PROVIDED “AS-IS” WITHOUT ANY WARRANTY AND PROVIDER SHALL HAVE NO INDEMNIFICATION OBLIGATIONS NOR LIABILITY OF ANY TYPE WITH RESPECT TO SUCH FREE SOFTWARE AND SOFTWARE OFFERED ON A TRIAL BASIS, UNLESS SUCH EXCLUSIONS OF LIABILITY ARE NOT ENFORCEABLE UNDER APPLICABLE LAW, IN WHICH CASE PROVIDER’S TOTAL CUMULATIVE LIABILITY WITH RESPECT TO SUCH FREE SOFTWARE SHALL NOT EXCEED ONE THOUSAND U.S. DOLLARS ($1,000.00 USD).” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | medium | “ 1.9 “Free Software” means the free, feature-limited version of Software provided to a Customer, User, end user, partner, or any other third party including but not limited to, the lowest tier offering of Software as made available by Provider and Software provided for evaluation purposes.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | unknown | “ Show Hide Capitalized terms used in this Agreement shall have the meanings ascribed to them in this Section 1 or as otherwise defined herein. 1.1 “Add-On User(s)” means additional Users in excess of those that have been purchased under a Subscription via an executed Order Form or Web-Portal Purchase.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | unknown | “ 7.2 Subscription Term. A Subscription Term (subject to Section 5.6 (Monthly Billing)) shall begin as of the Subscription Start Date and remain in effect for the term length as indicated on the Order Form (the “Initial Term”) and automatically renew for successive twelve (12) month terms (each a “Renewal Term”), with the same number of Users set forth in the applicable Order Form, or, for Web-Portal Purchases, the Pricing Page, plus any Add-On User(s) activated and/or used during such Subscription Term. To prevent automatic renewal, or to reduce the number of User licenses upon renewal, either Party must provide written notice at least thirty (30) days prior to the expiration of the then-current Subscription Term.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | unknown | “ 5.8 Price Protection. Unless otherwise expressly set forth in an Order Form, any updates to Provider’s list pricing or pricing policies shall not apply during the then-current Subscription Term. All Fees for the Subscription Term, including Fees for Add-On Users invoiced pursuant to Section 5.5, shall be based on the per-seat rates set forth in the applicable Order Form, or, for Web-Portal Purchases, the Pricing Page. Updated pricing shall apply only to (a) any Renewal Term, and (b) any new or subsequent orders entered into after the effective date of such updated pricing.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | unknown | “ 5.6 Monthly Billing. Notwithstanding Section 5.5, where Customer enters a Web-Portal Purchase on a monthly billing basis (as indicated at checkout), (a) the Subscription Term shall be one (1) month, automatically renewing for successive one (1) month periods unless cancelled through the Web- Portal interface or by written notice to Provider prior to the end of the then-current monthly period; (b) Fees, including Fees for Add-On Users, shall be invoiced and charged monthly on a prorated basis through Provider’s payment processor; (c) Section 5.5 (Add-On User Reconciliation) shall not apply to such Subscription, and Add-On User reconciliation shall instead be effected through the monthly billing mechanism described in this Section; and (d) all references in this Agreement to a twelve (12) month Subscription Term, Renewal Term, or reporting period (other than for purposes of Section 9.3 (Limitation on Total Liability)) shall be deemed to refer to the applicable one (1) month period for such Subscription.” | Captured 2026-09-25Open source →Finding permalink → |
| Tier differences | All applicable tiers | unknown | “ 5.5 Add-On User Reconciliation. With respect to purchases from Provider for Add-On Users, at the end of each three (3) month period, commencing upon the Subscription Start Date, (each a “Quarter”) during the Subscription Term, Provider will: (i) per Section 4.5, generate a report of Add-On User(s) activated and/or used during the Quarter (“Quarterly Add-On Report”), and (ii) invoice Customer on a prorated basis for the remaining portion of the Subscription Term, with respect to the Add-On User(s) activated and/or used during the Quarter as captured by the Quarterly Add-On Report. For the avoidance of doubt, Add-On User(s) will not be invoiced for the Quarter in which they were activated and/or used. A Quarterly Add-On Report will be generated during the first three (3) Quarters of a Subscription Term. Upon expiration of the Subscription Term, Customer’s renewal of the Software shall be for the same number of User licenses purchased for the most recent Subscription Term, plus any Add-On Users activated and/or used during such Subscription Term, unless otherwise agreed to between the Parties. Add-On User(s) that have been identified within the Quarterly Add-On Report, shall be considered due and payable in accordance with this Section 5.” | Captured 2026-09-25Open source →Finding permalink → |
Informational only, not legal advice. Terms can change; verify every cited source and capture date during procurement review.
📢 POLICY UPDATES ALERT
AIRIN Brief
Built for compliance officers, legal counsel, and SaaS founders. Subscribe to the email digest — one short brief when a tracked vendor materially changes its terms, training policy, or risk rating. Prefer in-app? Watch platforms in your alerts inbox instead.