Terms of service.

By accessing or using any Runlog tool, you agree to be bound by these terms.

These Terms of Service ("Terms") govern your use of Runlog Atlas, the BlueSage closed-tool portal, and any other Runlog-operated tool or subdomain (collectively, the "Services"). By creating an account, installing the Runlog Chrome extension, or using any Service, you agree to these Terms on behalf of yourself and, where applicable, the organization you represent. If you do not agree, do not use the Services.

Runlog operates a document-intelligence platform and a family of closed tools for partner organizations.

The Services include, without limitation:

• —Runlog Atlas: entity extraction, cross-document linking, and explainable AI over documents you upload
• —Closed tools such as BlueSage: buyer-prospecting workflows, scoring, lead pipelines, and outreach drafting for a specific partner organization under a separate commercial agreement
• —The Runlog Chrome extension: a browser-side execution surface that runs queued actions and captures page content at the user's explicit request
• —Automated scanning, scoring, and background workers that process data on your behalf on a recurring schedule
• —Enrichment and verification services that locate and verify professional contact information at your request
• —Community marketing services in which Runlog manages participation in online communities on your behalf
• —The Runlog API, including metered capabilities and plan-gated endpoints, and Runlog-operated storefront brands through which specific Services are sold

You are responsible for your use of the Services and for compliance with every law, contract, and third-party policy that applies to your activity.

• —Provide accurate account information and keep it current
• —Maintain the security of your Runlog account credentials and the credentials of any third-party channel you connect
• —Use the Services only in compliance with applicable laws and regulations, including but not limited to the CAN-SPAM Act (United States), CASL (Canada), the GDPR and ePrivacy Directive (European Economic Area and United Kingdom), the Telephone Consumer Protection Act, and any other jurisdiction-specific marketing or privacy law that governs your outreach
• —Use the Services only in compliance with the terms of service, acceptable-use policies, and automation policies of every third-party platform you connect (including but not limited to LinkedIn, Doximity, Reddit, Crunchbase, Gmail, Calendly, and GoHighLevel); you are solely responsible for confirming that your use of the Services on those platforms is permitted by those platforms
• —Obtain any consent required under applicable law before sending marketing communications to any individual whose contact information is surfaced, imported, or drafted against by the Services; you acknowledge that several jurisdictions (including, without limitation, Germany, Austria, Italy, Spain, Poland, and Denmark) require prior consent for business-to-business email marketing, and that where the Services offer country-level send gating you remain responsible for its correct configuration
• —Use only truthful sender identities, sending domains, and subject lines in any communication sent through or drafted by the Services; never use a subject line that implies a prior relationship or transaction that does not exist, and never use a domain you are not authorized to use
• —Honor every opt-out, unsubscribe, STOP reply, and do-not-contact request permanently and across every channel; the Services maintain suppression records for this purpose, and you may not circumvent, edit, or re-import around them
• —Refrain from using the Services for unlawful, deceptive, discriminatory, or harmful activities, including impersonation, harassment, or the collection of personal data for purposes other than those you have disclosed to the individuals concerned
• —Respect intellectual property rights, including the rights of third parties whose content is captured, scraped, or surfaced through the Services
• —Not attempt to reverse engineer or compromise the Services or the systems that host them

BlueSage and other closed tools let you connect third-party channels by supplying credentials that Runlog stores for you. This section describes what that grant means.

When you voluntarily enter credentials for a third-party channel (including, without limitation, a username and password, an API token, a Personal Access Token, a refresh token, or a scheduling URL) into a Runlog tool, you grant Runlog the following rights for the duration of the connection:

• —Store the credential at rest in Runlog's Firestore database, encrypted with AES-256-GCM using a key held only by the relay service. The plaintext is never written to disk and is never returned to the frontend
• —Decrypt the credential in-memory on the relay service or on automated worker infrastructure operated by Runlog, for the sole purpose of operating the third-party channel on your behalf in the manner you have directed; this includes, where applicable, running a headless or headed browser session that logs in to the third-party channel, keeps the session alive, navigates to pages you have asked the tool to scan, reads the content of those pages, and posts drafts or scheduled messages you have separately approved
• —Use the credential on a recurring schedule (for example, via a cron-scheduled worker) for the duration of the connection, without requiring a per-run prompt for consent; you consent to recurring automated use at the time of connection and may withdraw that consent at any time by disconnecting the channel
• —Decrypt the credential in the context of Runlog Chrome extension sessions you initiate from the Runlog UI, so the extension can replay the credential into the tab of the third-party platform to maintain or restore an authenticated session
• —Retain the encrypted credential until you disconnect the channel, delete your account, or the underlying data is removed under the Data and Privacy section below. On disconnection the encrypted blob is hard-deleted from Runlog's storage

The Services perform a bounded set of automated actions against third-party platforms. This section describes what is and is not authorized.

• —Runlog will use stored credentials only for read-oriented operations (profile reads, search results, queue scanning) and for operations you have explicitly approved inside a Runlog tool (for example, clicking Approve on a specific outreach draft within a 24-hour review window)
• —Runlog will not use stored credentials to send messages, post content, connect to other users, or perform any write operation on a third-party platform unless you have approved that specific operation through the Runlog UI or through a workflow you have separately configured
• —Runlog respects per-channel rate limits and human-like timing constraints encoded in the Chrome extension's per-channel content scripts. You may not instruct the Services to bypass those limits
• —You acknowledge that some third-party platforms' terms of service restrict automated access. You are solely responsible for determining whether the Services' automated access to any given platform, as configured by you, is permitted under that platform's then-current terms, and for ceasing such access if the platform prohibits it
• —Runlog may suspend automated access to any channel at any time if Runlog determines, in its reasonable judgment, that such access is exposing Runlog, you, or a third party to legal, reputational, or operational risk

The Runlog Chrome extension is a separate consent surface with its own rules.

• —The extension runs only when explicitly activated by you, either by clicking the extension icon (capture mode) or by clicking "Run on {channel}" inside a Runlog tool (session mode). It does not run in the background when no session is active
• —In capture mode, the extension reads DOM content from the active tab at the moment you click. It does not read passwords, cookies, or local storage from third-party origins. It does not send outreach or messages on your behalf in capture mode
• —In session mode, the extension opens a short-lived, signed WebSocket to the Runlog relay, drains a bounded queue of actions, and closes. Each action is a read or navigation; no write action is performed without your separate, explicit approval in the Runlog UI
• —You may uninstall or disable the extension at any time from chrome://extensions. Uninstalling the extension immediately terminates any active session
• —The extension is distributed as an unpacked developer-mode package during the pilot period. Runlog may in the future publish the extension to the Chrome Web Store; at that point the installation mechanism will change and you may be required to reinstall

Your data privacy and security are important to us.

• —You retain ownership of the data you upload, the chat transcripts you generate, and the outreach drafts the Services produce
• —We process your data according to our Privacy Policy
• —We implement industry-standard security measures, including encryption at rest for stored credentials (AES-256-GCM), signed short-lived tokens for extension WebSocket sessions (HMAC-SHA256), and authenticated relay endpoints for every mutation
• —You may export or delete your data at any time through the relevant tool's settings, or by contacting us at the address in the Contact section. Deleting your account hard-deletes every channel credential tied to it
• —We may use aggregated, anonymized data for service improvement and for benchmarking. We do not sell personal data to third parties
• —The Services process personal data about third parties (for example, prospective buyers surfaced by BlueSage scans). You are the controller of that personal data and Runlog is the processor; the scope of processing is limited to what is necessary to provide the Services and to what you have configured

The Services generate drafts and recommendations based on content from third-party sources. You are responsible for what you send.

• —Outreach drafts produced by the Services (including drafts in BlueSage's Outreach column) are generated suggestions, not communications sent by Runlog. No draft is sent to any recipient until you approve it and the underlying channel is configured to send
• —You are solely responsible for reviewing every draft for accuracy, tone, legal compliance, and recipient eligibility before approving it. You are responsible for honoring opt-out requests, unsubscribe requests, and Do-Not-Contact signals
• —Runlog provides a 24-hour review window on every auto-send-scheduled draft within which you may cancel the send. After that window the send occurs through the channel you have connected (for example, via your Gmail send scope); Runlog does not independently deliver messages
• —Content surfaced from third-party platforms (LinkedIn posts, Doximity profiles, Crunchbase company pages, Reddit threads, etc.) is shown to you for context only. You may not copy, reproduce, or redistribute that content beyond the scope of your own use of the Services without the underlying rights holder's permission

Some Services locate and verify professional contact information at your request. This section describes the division of responsibility.

• —Enrichment and verification run as per-request orchestration over third-party data providers, public registries, and web research. Runlog does not maintain, sell, or license a standing database of personal contact information; results are produced for your request and delivered to you
• —For personal data located or verified at your request, you are the data controller and Runlog is your processor. You are responsible for having a lawful basis for the processing, for providing any notice owed to the individuals concerned (including notices required when data is obtained from a source other than the individual, such as GDPR Article 14), and for honoring their rights
• —Each delivered contact carries provenance: the type of source it was recovered from, the date, and a confidence assessment. Provenance is provided so you can meet your own notice obligations; do not discard it
• —A contact matching a Runlog-maintained suppression record is returned as suppressed, without the underlying contact information
• —Verification verdicts (including catch-all and unknown classifications) are assessments, not guarantees of deliverability; you remain responsible for the consequences of sending to any address
• —You may not use enrichment output to build a product or dataset for resale, to populate a data-broker service, or to locate individuals for purposes unrelated to lawful business communication you have disclosed

Where Runlog manages participation in online communities on your behalf, these rules apply.

• —Community participation operated for you follows a disclosed-affiliation policy: where your business is named or linked in managed content, the affiliation is disclosed consistent with the FTC Endorsement Guides and platform rules. You may not instruct Runlog to conceal a material connection
• —Every managed post naming your business is subject to your approval before it is published; nothing publishes autonomously on community channels
• —Runlog cannot and does not guarantee any community outcome, including post survival, ranking, engagement, or the continued standing of any participating account; platforms remove content and suspend accounts at their sole discretion
• —Managed participation follows each community's own rules; Runlog may decline, pause, or withdraw participation in any community where continued activity would in Runlog's reasonable judgment violate platform policy or community norms, or expose you or Runlog to moderation action
• —Impact reporting (posts, threads reached, engagement, referral traffic where measurable) is provided as measured; platform-reported figures are the platform's own and may change

The Services generate content with AI systems. This section describes what that output is and is not.

• —Deliverables, drafts, research, and answers produced by the Services are generated by AI systems, in some engagements supplemented by human review; where a deliverable materially depends on human work, the human/agent split is disclosed in the deliverable
• —Cited output links claims to source locations. A citation that resolves to a source is not a warranty that the source supports every inference you draw from it; you are responsible for verifying any output you rely on for a legal, financial, medical, or regulatory decision
• —The Services are configured to decline emitting claims whose sources cannot be resolved rather than to guess; an output marked as unresolvable, suppressed, or low-confidence must not be treated as a finding
• —Output produced for you does not constitute legal, tax, investment, medical, or appraisal advice, and no output states a professional opinion reserved by law to licensed practitioners

How your corrections make the Services better, and the rights you grant when you make them.

• —When you correct, accept, reject, or annotate an output of the Services (a "Correction"), you grant Runlog a perpetual, irrevocable, royalty-free license to use that Correction — including the output it corrects and the immediate context needed to interpret it — to evaluate, improve, and train the Services, including model routing, extraction, retrieval, and quality-scoring systems
• —Corrections used for improvement are processed with identifying customer content removed where the Correction's value does not depend on it; Corrections are never published, shared with other customers in identifiable form, or sold
• —This grant covers Corrections and their immediate context only. It is not a license to train on your uploaded documents, your project corpus, or your outputs generally, which remain governed by the Data and Privacy section
• —Where an engagement's separate commercial agreement excludes this grant, that agreement controls for that engagement

How usage-based Services are measured, purchased, and consumed.

• —Subscription tiers include a usage allowance measured in dollars of metered work over rolling windows (for example, weekly and five-hour windows). When an allowance window is exhausted, work pauses until the window rolls or you continue on credits; the Services state which window applied
• —Purchased credits draw at the published credit rate, which is higher than the allowance rate. Granted, promotional, and referral credits draw at the same credit rate, are consumed before purchased credits, are non-refundable, and never convert to cash
• —Refunds of purchased balances return only the purchased portion; consumed and granted amounts are not refundable. One-time unit purchases are refundable before delivery and at Runlog's discretion after delivery
• —Metered usage may include third-party services (including model inference and communications channels) that Runlog purchases and resells at a markup as part of the Service; the meter's recorded charge is the price of the Service, not a pass-through of any vendor's price
• —Annual prepayments purchase a term at the published annual price; the allowance during an annual term equals the corresponding monthly tier's. Mid-term upgrades prorate; downgrades take effect at renewal
• —Some API endpoints and capabilities are available only on designated plan tiers; a call from a key on a lower tier is refused with the required tier named

Runlog operates some Services under their own product names and domains.

• —Certain Services are offered under distinct product names, brands, and domains operated by or for Runlog (each a "Storefront"). Unless the Storefront's own terms state otherwise, these Terms govern your use of a Storefront's services, with the Storefront's named entity as the contracting party where one is identified at checkout
• —Credits and account balances are denominated in one currency across Runlog-operated Services; a credit granted on one surface is visible to you when signed in and draws under the same rules everywhere

Terms related to billing, payments, and subscription management.

• —Runlog Atlas subscription fees are billed monthly or annually in advance
• —Usage-based charges, where applicable, are billed monthly in arrears
• —Closed tools such as BlueSage are governed by a separate commercial agreement with the partner organization; the pricing, billing cadence, and payment terms of that agreement supersede this section for that tool
• —You may cancel your subscription at any time through the settings of the relevant tool or by contacting us
• —Refunds are provided according to our refund policy
• —We may suspend service for non-payment after reasonable notice

Important limitations on our liability for your use of the Services.

To the maximum extent permitted by law, Runlog, its officers, employees, and affiliates shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, loss of data, loss of business opportunities, reputational harm, or third-party platform suspensions or bans, arising from or in connection with your use of the Services, your connection of any third-party channel, the automated use of any stored credential, the accuracy or completeness of any draft or recommendation produced by the Services, or any third-party content surfaced through the Services. Nothing in this section limits liability that cannot be excluded or limited under applicable law.

You agree to defend and indemnify Runlog in certain scenarios arising from your use of the Services.

You agree to defend, indemnify, and hold harmless Runlog and its officers, employees, and affiliates from and against any claim, demand, loss, liability, damage, fine, or expense (including reasonable attorneys' fees) brought by a third party and arising out of or relating to (a) your violation of these Terms, (b) your violation of any applicable law or of any third-party platform's terms of service, (c) your decision to send any outreach message drafted or recommended by the Services, (d) your connection of any third-party channel that you were not authorized to connect, or (e) the personal data you surfaced, imported, or processed through the Services without a valid legal basis.

Questions about these terms reach us at

hello@runlogai.com