Provyn Dashboard Terms of Service
Think Tank Products, LLC d/b/a Provyn
Published at: https://provyn.com/dashboard-terms
Version 1.2. Last updated: November 16, 2026.
1. About These Terms
1.1 Who these Terms are between. These Terms of Service ("Terms") govern the Provyn Dashboard, a hosted software service that Think Tank Products, LLC, a Colorado limited liability company doing business as Provyn ("Provyn", called "Consultant" in the Master Agreement), operates for its clients. "Client" means the business that has signed a Master Agreement and a Dashboard SOW with Provyn. The Dashboard is offered to businesses only, not to consumers.
1.2 How these Terms become part of the agreement. These Terms apply only when a Statement of Work signed by Provyn and Client includes the Dashboard and refers to these Terms at https://provyn.com/dashboard-terms (a "Dashboard SOW"). The Dashboard SOW is issued under the Master Services Agreement or the Consulting Agreement between Provyn and Client, whichever applies (the "Master Agreement"). By signing the Dashboard SOW, Client agrees to these Terms in the version posted on the Dashboard SOW's effective date. A later version applies to Client only as Section 23 provides.
1.3 Relationship to the Master Agreement. The Master Agreement governs the overall relationship between Provyn and Client. These Terms add the rules that are specific to the Dashboard. Capitalized terms not defined in these Terms have the meanings given in the Master Agreement. The Dashboard is part of the "Services" under the Master Agreement. References in these Terms to a section of the "MSA" mean that section of the Master Services Agreement or, where the Master Agreement is the Consulting Agreement, the corresponding section of the Consulting Agreement listed in Appendix D.
1.4 Order of precedence. If these documents conflict, they apply in this order: (a) the Master Agreement; (b) the Dashboard SOW, but only for fees, the features ordered, the term, any pilot terms, and any provision of these Terms that the Dashboard SOW expressly says it changes; (c) these Terms; and (d) the Dashboard's in-product help text and user guides, which are descriptive only. As an exception, these Terms control over the Master Agreement on the following Dashboard-specific points, if and only if the Dashboard SOW names them as MSA Section 9.7 requires: (i) Section 18 (export, deletion, and the retention of backup copies and records), which applies in place of MSA Section 3.4(c) for Client Data held in the Dashboard; (ii) Section 18.6, last sentence (confidentiality of retained records beyond the period in MSA Section 5.5); and (iii) Section 13 (security incident notice), to the extent it adds duties the Master Agreement does not contain.
1.5 Authorized Users. Individuals who use the Dashboard on Client's behalf (Section 4) do not become parties to these Terms. Client is responsible for their use of the Dashboard and for making them aware of Sections 4.3 and 15.
2. Definitions
2.1 Dashboard. The Provyn Dashboard web application at https://dashboard.provyn.com, together with its scheduled jobs, its connections to Connected Accounts, and Provyn's related setup and support.
2.2 Authorized User. An individual whose email address Provyn or a Client Administrator has added to Client's Dashboard.
2.3 Connected Account. An account with a third-party service that is connected to Client's Dashboard, such as HubSpot, Microsoft 365, Google Workspace, LinkedIn (through the LinkedIn Automation Service), Google Analytics, Fathom, Memoket, FreshBooks or GetLeads.
2.4 Credentials. API keys, client secrets, access and refresh tokens, and similar secrets that let the Dashboard reach a Connected Account.
2.5 Client Data. All data and content that Client provides to Provyn through the Dashboard or that the Dashboard processes for Client, including data read from Connected Accounts, data and files that Authorized Users type in or upload, and output the Dashboard generates for Client, including AI Output. Client Data is "Client Data" under MSA Section 6.6.
2.6 Core Features and Add-Ons. Core Features are the features every Dashboard client receives. Add-Ons are optional features that are switched on for Client only as the Dashboard SOW states or as Client asks in writing.
2.7 Automated Action. An action the Dashboard takes in a Connected Account on a schedule, without a person clicking to approve that specific action. Examples: sending a daily batch of LinkedIn connection requests, or withdrawing old LinkedIn invitations that were never answered.
2.8 AI Output. Text, files and data produced by an artificial intelligence model for Client through the Dashboard, such as draft comments, invitation notes, messages, summaries, answers (for example from Ask the Dashboard), suggested plans, the values read from a receipt photo, and Results under Section 7A.
2.9 Service Provider. A third party that Provyn uses to host, run or support the Dashboard and that may store or process Client Data. Service Providers are the "third-party service providers" referred to in MSA Section 5.2. They are listed in Appendix A.
2.10 Closing. Provyn's act of ending Client's use of the Dashboard at the end of service, described in Section 18.
2.11 Client Administrator. An Authorized User whom Client has made an administrator of Client's Dashboard. Client names its first Client Administrators in the Dashboard SOW or in a written request to Provyn; a Client Administrator may make other Authorized Users Client Administrators.
2.12 LinkedIn Automation Service. The third-party LinkedIn automation service through which Client's LinkedIn account is connected to the Dashboard (Section 8). Provyn holds and pays for the account with it. Appendix A identifies it by type; Section 11.4 says how Client may learn its name.
3. The Dashboard
3.1 What it is. The Dashboard is a private website that brings Client's CRM, email and calendar, LinkedIn activity and EOS planning (vision, rocks, scorecard) into one place, and lets Authorized Users act on it: close CRM tasks, review new leads, and review and send drafted outreach. It reads data from Connected Accounts, shows it on cards, runs scheduled jobs, and uses AI to draft text for a person to review. Provyn sets up, operates and supports the Dashboard for Client.
3.2 A hosted service; nothing installed. The Dashboard runs on servers operated for Provyn and is used in a web browser. Provyn does not install software on Client's computers or devices, and these Terms do not grant a license to any downloadable software.
3.3 Right to use. Subject to these Terms, the Master Agreement and payment of Fees, Provyn grants Client a non-exclusive, non-transferable, non-sublicensable right, during the term of the Dashboard SOW, for its Authorized Users to access and use the Dashboard for Client's internal business purposes. The Dashboard is provided as a Service. It is not a Deliverable, and MSA Section 4.2 does not assign the Dashboard or any part of it to Client. The Dashboard, its software, designs, templates and know-how are Consultant Materials under MSA Section 4.3 and remain Provyn's. Client Data, including reports and exports generated from it, remains Client's under Section 9.1. Provyn reserves all rights not expressly granted in these Terms.
3.4 Core Features and Add-Ons. At the date of these Terms, the Core Features are: HubSpot cards and tasks; Microsoft 365 (or Google Workspace) calendar and inbox counts; LinkedIn reading and the LinkedIn analytics exports; Company Page cards; the EOS Vision, Traction, SWOT and Rocks cards; EOS Quarterly Rock Planning; Website (Google Analytics); the monthly results report; and Settings, including the Your Voice card (Section 7.6). The Add-Ons are: LinkedIn Outreach (including LinkedIn posts and post ideas drawn from Client's call recordings), with lead research as an option; Cold Outreach; Accounting (FreshBooks), including Receipt Photos; Conversations (meeting recordings from Fathom or Memoket, including Ask the Dashboard); Contracts (e-signature through Provyn's e-signature account, Section 16.5); EOS Level 10 Prep; Surveys (Section 6A); and the Solution Factory (Section 7A). The Dashboard SOW states which Add-Ons Client orders. An Add-On that is switched off cannot be used, not merely hidden. Provyn switches Add-Ons on only as the Dashboard SOW states or as Client asks in writing; for this purpose an email from an authorized representative of Client is enough.
3.5 Changes to the Dashboard. Provyn improves the Dashboard over time and may add, change or remove features. Provyn will not materially reduce the Core Features during a paid term without at least 30 days' notice. If it does, Client may terminate the Dashboard SOW by notice before the change takes effect and receive a refund of any Fees prepaid for the period after termination. If a Service Provider or other vendor the Dashboard relies on ends a feature without giving Provyn advance notice (for example because it stops its service or goes out of business), Provyn will notify Client as soon as practicable after Provyn learns of it, and Client has the same right to terminate and receive that refund. Technical descriptions in these Terms are accurate at their date. Provyn may change how the Dashboard works if the change does not materially reduce the protection of Client Data.
3.6 Pilot. If the Dashboard SOW describes the engagement as a pilot (a "Pilot"), the Pilot runs for 90 days and is paid, at the fee and with the features stated in the Dashboard SOW. At the end of the Pilot, the Dashboard SOW renews automatically and continues month to month under Section 17.1, at the fee the Dashboard SOW states for after the Pilot, unless either party gives notice under Section 17.1 before the Pilot ends.
4. Sign-In and Authorized Users
4.1 Adding and removing users. Provyn adds Client's first Authorized Users at setup. After that, a Client Administrator may add and remove Client's Authorized Users on the Dashboard Users card in Client's Dashboard, and Provyn will do so at Client's written request. The Dashboard keeps at least one active Client Administrator for Client and will not remove the last one. Each Authorized User signs in with a one-time code that Cloudflare, Provyn's sign-in provider, emails to the user's address. The Dashboard has no password. Only addresses that have been added can receive a working code. A sign-in lasts up to one week; after that the user requests a new code.
4.2 One client per sign-in. Each sign-in belongs to one client and shows only that client's data.
4.3 Authorized Users' duties. Each Authorized User must keep access to his or her own mailbox secure, must not share sign-in codes or a signed-in session, must use the Dashboard only for Client's business, and must follow Section 15.
4.4 Client's responsibility for its users. Client is responsible for the acts and omissions of its Authorized Users in the Dashboard as if they were Client's own. Client will remove a person's access promptly, or ask Provyn to, when the person should lose it, for example when the person leaves Client. Provyn will remove that access within two business days after Client's request. A Client Administrator can also remove access at once on the Dashboard Users card (Section 4.1).
4.5 What Authorized Users can change. Every Authorized User can read Client's Dashboard, edit Client's EOS content, upload LinkedIn analytics exports, read Client's voice profile, connect Client's accounts with vendors that sign in through their own consent screen, and approve or send items in the Add-Ons Client has. In the Solution Factory, Authorized Users may also file Requests, answer the agent's questions and approve Results (Section 7A). Client Administrators can also add and remove Authorized Users (Section 4.1), change Client's settings within the limits Provyn sets for them, change Client's voice profile (Section 7.6), send replacement Credentials through the Connection Keys card (Section 5.3), read Client's past monthly reports, and manage Solution Factory schedules (Section 7A.7). Add-Ons, the limits on settings, and scheduled jobs are changed by Provyn at Client's request.
5. Connected Accounts and Credentials
5.1 Whose accounts they are. Most Connected Accounts belong to Client and are held under Client's own contract with the vendor: HubSpot, Microsoft 365 or Google Workspace, Google Analytics, Fathom, Memoket, FreshBooks and, for the Cold Outreach Add-On, GetLeads. As MSA Section 6.5(d) provides, Client is responsible for those accounts, their subscriptions and fees, and its compliance with their terms. Three accounts are held by Provyn: (a) Provyn's account with the LinkedIn Automation Service (one seat for each client), through which Client's LinkedIn account is connected (Section 8); (b) unless Client provides its own key, the Anthropic API account used for AI features (Section 7); and (c) with the Contracts Add-On, Provyn's e-signature account, through which Client's agreements are sent for signature (Section 16.5).
5.2 Authority to connect. Client represents that it has the authority to connect each Connected Account and to grant the permissions each connection needs, including permissions that reach the data of other people in Client's organization. In particular, the Microsoft 365 connection works through an application that Client's IT administrator creates in Client's own Microsoft tenant. Unless Client's administrator narrows it, that application's calendar permission covers every calendar in Client's organization, and the application can also read and send from one mailbox Client designates. Client confirms that it may grant that access, that it will inform its own staff about it as its policies and applicable law require, and that its administrator may narrow or remove it at any time.
5.3 How Credentials reach Provyn. Credentials are entered in the Dashboard. They must never be sent by email, chat or text message, in either direction. Provyn enters Credentials on an administrator-only card during setup, or Client's IT administrator enters them through a single-use secure link Provyn sends. The link carries no Credential itself, expires after one use or 72 hours, and stores what is entered directly in the encrypted store without displaying it to anyone. When a key Client made in its own vendor account must be replaced (for example a new HubSpot service key, a new Microsoft 365 client secret or a new Fathom API key), a Client Administrator sends it through the Connection Keys card in Client's Dashboard. Vendors that sign in through a browser (for example Google, Fathom, FreshBooks and Memoket) are connected through the vendor's own consent screen. Provyn will never ask for Client's or any user's LinkedIn password.
5.4 How Credentials are stored. Credentials are stored encrypted and are write-only: no screen in the Dashboard displays a stored Credential, or any part of it, to anyone, including Provyn staff. Credentials are used only to operate the Dashboard for Client. Provyn holds the encryption key outside the database and outside the backups, so backup copies contain Credentials only in encrypted form.
5.5 Client may revoke access at any time. Client may revoke the Dashboard's access in any vendor at any time, for example by deleting the HubSpot service key, removing the Microsoft 365 application's secret, removing Provyn's application in Google or Fathom, or disconnecting its LinkedIn account from the LinkedIn Automation Service. Features that rely on a revoked connection stop working. Client should tell Provyn when it revokes access so Provyn can stop the related scheduled jobs. Revoking access does not by itself reduce the Fees.
5.6 Lapse notices. When a vendor refuses a connection during a refresh (for example because a key expired or was revoked), the Dashboard shows Client's Authorized Users a notice that names the connection, gives the date it stopped working, says that the affected cards show the last figures received, and says what to do. Provyn is alerted at the same time. Provyn may also send Client's listed contacts an email notice, once when a connection stops working and once when it works again. Lapse notices are a convenience. Provyn does not promise to detect every failure, and data that could not be read during a lapse may not be recovered later.
5.7 Vendor changes. Vendors change their products, prices, permissions and terms. As MSA Sections 6.5(c) and 9.3 provide, Provyn is not responsible for a vendor's acts, availability or changes. Provyn will make reasonable efforts to adapt the Dashboard. If a vendor change makes a feature impossible, uneconomic or unlawful to provide, Provyn may remove that feature with as much notice as is reasonably possible, and Section 3.5 applies if the feature is a Core Feature.
6. What the Dashboard Does in Connected Accounts
6.1 Reading. The Core Features mostly read and report. Appendix B lists what the Dashboard reads from each Connected Account. Refreshes run on a schedule and when a user presses Refresh Data. A refresh reads; it does not send anything or change data in a Connected Account.
6.2 Changes made on a click. Some features change data in a Connected Account only when an Authorized User or a Provyn administrator presses the button for that specific action. Examples: completing a HubSpot task, setting a contact's type, sending a meeting request or reply on LinkedIn, posting a comment or reaction, publishing or scheduling a LinkedIn post, attaching an approved receipt to a FreshBooks expense, and sending an agreement for e-signature.
6.3 Automated Actions. Only certain Add-Ons take Automated Actions, for example sending a daily batch of LinkedIn connection requests or withdrawing old LinkedIn invitations that were never answered. Every Automated Action is off by default. Provyn turns one on only after Client has agreed in writing to that specific Automated Action, using the opt-in in Appendix C, which also records its limits. Client may ask Provyn to turn any Automated Action off at any time, and Provyn will do so within two business days after the request. Client can also stop all activity on a LinkedIn account at once by disconnecting it under Section 5.5.
6.4 Scheduled messages to Client itself. The Dashboard also sends scheduled messages to Client itself: the monthly results report, the EOS Level 10 meeting sheet (with that Add-On), assignment emails to people on Client's People list (off until turned on), and lapse notices. These go only to the recipients Client designates. They are sent from Client's own connected Microsoft 365 mailbox or, for a Google Workspace client or a client whose Microsoft 365 permission is read-only, from Provyn's dashboard mailbox (dashboardnotification@provyn.com) with Client's address as the reply-to address. Nothing is ever sent from a Google mailbox. They are sent only if recipients are listed. A lapse of Client's own Microsoft 365 mailbox is shown in the Dashboard only, since that mailbox cannot send the notice. Survey invitations, which go to people Client chooses and not only to Client itself, are covered by Section 6A.
6.5 Records of actions. The Dashboard keeps records of the actions it takes in Connected Accounts, including clicks that changed vendor data and invitations it sent or withdrew. These records are Client Data and are included in the export under Section 18.2.
6A. Surveys Add-On
6A.1 What it is. The Surveys Add-On lets Authorized Users build surveys in the Dashboard and share them with people Client chooses (the "Respondents") by email invitation, by a link, or by a QR code, including in a live meeting. Respondents answer on a web page that needs no sign-in. Their answers are stored in Client's Dashboard.
6A.2 Client's lists and consent. Client chooses every Respondent and every list it sends a survey to, whether the list comes from a Connected Account such as HubSpot, from Client's People list, or is typed in or uploaded. Client represents that it has the right to contact each Respondent it sends a survey to and to collect the answers its surveys ask for, and that its surveys and invitations comply with applicable law, including laws on commercial email and privacy. Client will not use a survey to ask for passwords, payment card numbers, government identification numbers or health information, and will not send a survey to people because they are, or were, its patients. Section 15.1 applies to surveys and survey invitations.
6A.3 How invitations are sent, and unsubscribes. Survey invitations are sent one email to each Respondent from Client's own connected Microsoft 365 mailbox. They are never sent from Provyn's dashboard mailbox, so a client whose mail goes from that mailbox, including every Google Workspace client, shares surveys by link or QR code only. The Dashboard sends at most 200 survey invitations a day for Client, a limit Provyn may raise at Client's request. Every invitation contains an unsubscribe link. The Dashboard records an unsubscribe at once and sends that person no further survey invitation from Client's Dashboard. The Dashboard also skips anyone whom Client's HubSpot shows as unsubscribed from all email. Client will not re-enter an unsubscribed person's address, or use another address for that person, to get around an unsubscribe. As the sender, Client remains responsible for its own compliance with the laws on commercial email, including putting its valid postal address in the text of each invitation. On request, Provyn will give Client the list of people who have unsubscribed from Client's survey invitations, and Client is responsible for honoring those requests in its other systems.
6A.4 Answers are Client Data. Surveys, Respondents' names and email addresses, and their answers are Client Data under Section 9, and Provyn processes them as Client's service provider under Section 9.2. The answer page identifies Client as the party running the survey. A Respondent can type anything into a free-text answer; Client is responsible for what its surveys ask and for any privacy notice its Respondents are owed.
6A.5 How long answers are kept. Free-text answers, and the link between an answer and a named Respondent, are deleted automatically 24 months after a survey closes. Scores and counts remain, without names. Client may delete a survey and its answers sooner at any time. At the end of service, Section 18 applies to everything that remains.
6A.6 The public answer page. Anyone who has a survey's link or QR code can open its answer page. Provyn may limit the number of answers a survey accepts, add a check that a Respondent is a person and not an automated program, or close a link that is being misused. Provyn is not responsible for false, duplicate or automated answers submitted through a link or QR code.
7. AI Features
7.1 The AI provider. AI features use Anthropic's Claude models through Anthropic's paid commercial API. To produce a draft, the Dashboard sends Anthropic the facts from Client Data that the draft needs (for example a contact's public profile details, a post, a meeting summary, a receipt photo, or Client's voice profile). Client's AI work runs only through that API. It does not run through consumer AI apps.
7.2 How Anthropic handles the data. Under Anthropic's commercial terms at the date of these Terms, content sent through the API is not used to train Anthropic's models and is normally kept for up to 30 days (up to 2 years if it is flagged for a usage policy review). Provyn has not opted in to any Anthropic program that would allow Client Data to be used for training. Anthropic's terms may change. Appendix A links to them. Files and working sessions used by the Solution Factory are the exception described in Section 7A.2.
7.3 Drafts are drafts. AI Output is a draft for a person to review. As MSA Section 6.5 says, it may be inaccurate, incomplete or unsuitable, and Provyn does not warrant it. The Dashboard does not send AI Output to anyone outside Client unless a person clicks to send that specific item. The only exception is the scheduled messages to Client itself under Section 6.4, which may include AI-written summaries.
7.4 Responsibility for what is sent. Client is responsible for the content of everything sent from its accounts through the Dashboard, whether drafted by AI, by Provyn or by Client, once an Authorized User approves or sends it, and for each Automated Action that Client has opted into under Section 6.3, including compliance with laws on marketing messages and with the vendor's terms. Provyn is responsible for the Dashboard carrying out an Automated Action as configured, for example staying within the limits recorded in Appendix C and acting only on Client's own account, subject to the Master Agreement's limits of liability.
7.5 AI allowance or Client's own key. AI use is included within a monthly allowance for Client stated in the Dashboard SOW. When the allowance is used up, AI drafting pauses for Client until the next month or until Provyn raises the allowance. There is no overage charge unless the Dashboard SOW provides one. The Solution Factory (Section 7A) is not part of this allowance: its use does not count toward the allowance or pause AI drafting, it has its own Factory Allowance (Section 7A.5), and its Factory Charges are billed in addition to the Fees (Section 7A.6). Alternatively, Client may provide its own Anthropic API key, in which case Client's Anthropic account pays for its AI use and Anthropic's terms with Client apply to it.
7.6 Voice profile. Client's voice profile tells the AI features how Client's drafts should sound. Client Administrators set and change it on the Your Voice card, and every Authorized User can read it. Provyn may also set it up or change it at Client's request, and Provyn is told when a Client Administrator changes it. The Dashboard keeps earlier versions so that a Client Administrator can restore one. Until Client's voice profile is complete, the Dashboard does not draft for Client. Where Client supplies its own posts or writing samples so that drafts sound like Client, those samples are used as examples inside the AI requests. They are not used to train any AI model. Client confirms it has the right to provide them.
7A. Solution Factory Add-On
7A.1 What it is. The Solution Factory is an Add-On. An Authorized User files a request in the Dashboard (a "Request") for a report, a cleaned-up data file, a report that runs on a schedule, or a card for the Dashboard. An AI agent works the Request, asks the Authorized User when something is unclear, and hands back files or data (the "Results"). The agent runs on Anthropic's systems, in a separate work area for each Request. Any code the agent writes runs only there, never in the Dashboard; only files and data come back.
7A.2 What is sent to Anthropic, and its deletion. For each Request, the Dashboard sends Anthropic: (a) the Request, including its instructions, its checklist and the Authorized User's answers to the agent's questions; (b) any files an Authorized User uploads to it; and (c) the Client Data that an Authorized User chooses to export from the Dashboard for it, which the Request lists. If Provyn has made live access available to Client and an Authorized User chooses it for a Request, the Dashboard also places a read-only Credential for one Connected Account in Anthropic's credential store, for that Request only. The Credential is not shown to the agent, it can be used only on that vendor's own sites, and Provyn deletes it when the Request ends. Sections 7.1 and 7.2 apply to everything sent; in particular, Anthropic does not use a Request, its files, the exported Client Data or the Results to train its models. Once a Request closes, whether its Results are handed back or it is stopped or fails (after any automatic retry), Provyn deletes, through Anthropic's deletion functions, the files uploaded to Anthropic for that Request, the Request's working session at Anthropic (its record, its history and any files the agent wrote there) and, if live access was used, the Credential placed for it. Anthropic states that deleted files and sessions cannot be recovered and stop being available shortly after deletion. Unlike the content described in Section 7.2, these files and sessions are not deleted automatically after 30 days; they are kept until Provyn deletes them. Anthropic may still keep content for longer where the law requires it, or where its automated safety systems flag the content for a usage policy review, in which case Anthropic's terms allow up to 2 years for the content and longer for the resulting safety scores. The Request's page in the Dashboard tells Authorized Users that this deletion will take place and, once Anthropic has confirmed each deletion, shows when it took place.
7A.3 Review of Results. Results are AI Output, and Section 7.3 applies to them: they may be inaccurate, incomplete or unsuitable, and Provyn does not warrant them. A Result is not shown as a card, run again or otherwise used in the Dashboard until an Authorized User approves it. While Provyn's review is on for Client, a Provyn administrator also checks each Result before Client sees it. That check looks for obvious problems only. It does not replace Client's own review, and it does not change Section 7.3. Provyn's administrators can see every Request and Result (Section 10). An Authorized User may choose to receive the agent's questions on a phone through Provyn's notification server (Appendix A); the question's text then appears on that phone unless the user hides it.
7A.4 No regulated data. Client will not put into a Request, by upload, export or answer, any health information or patient details (for example names with dates of birth, medical record numbers, or member or insurance numbers), including protected health information under HIPAA, or any Social Security numbers, payment card numbers, or data about children, as Section 9.5 provides for the whole Dashboard. The Dashboard checks each uploaded file for obvious patient identifiers and refuses a file that shows any, and Provyn may review an uploaded file before its Request starts. Provyn may refuse any file or Request. These checks are a safeguard and do not relieve Client of this duty.
7A.5 Request Caps and the Factory Allowance. Each Request runs under a spending cap shown on the Request (its "Request Cap"). A Request that reaches its Request Cap pauses, and is not lost, until an Authorized User raises the cap or stops the Request. The Solution Factory also has its own monthly spending allowance for Client (the "Factory Allowance"), shown on Client's Factory screens. The Factory Allowance is separate from the AI allowance in Section 7.5: Solution Factory use does not count toward that allowance and does not pause Client's other AI drafting. A Request does not start, and a Request Cap is not raised, when the amount it could then spend would take Client past the Factory Allowance. Provyn sets the Factory Allowance for Client. Provyn may lower it at any time and will raise it only at Client's written request; an email from Client's authorized representative is enough.
7A.6 Charges. The Solution Factory is charged by use. Each Request is charged at the amount shown for it on the Factory Spend card in Client's Dashboard (the "Factory Charges"). The amount is Provyn's price for the Request. It includes Provyn's AI costs and a service charge, is not a pass-through of Provyn's costs, and is limited by the Request Cap shown on the Request (Section 7A.5). Factory Charges are billed in addition to the Fees; they are not covered by the AI allowance in Section 7.5 and are not an overage charge under it. Factory Charges are counted by calendar month in Mountain Time, added to Client's next invoice with a statement listing each Request, and invoiced and paid under MSA Section 2. Work done when a Request is sent back with a note, when an approved Result is run again, and when it runs on a schedule is charged the same way. A Request that fails, is stopped or reaches its Request Cap is charged for the work done up to that point. Provyn may waive a charge, which then shows as waived. There is no subscription fee for the Add-On itself, with one exception: if Client uses its own Anthropic API key (Section 7.5), Client's Anthropic account pays for the AI use, no Factory Charges are invoiced, and Client instead pays the monthly Solution Factory fee stated in the Dashboard SOW. Section 16.4 applies to Factory Charges as it does to the Fees: a change to how Factory Charges are calculated for Client, or to the monthly Solution Factory fee, takes effect only after at least 60 days' written notice.
7A.7 Schedules. Despite Section 4.5, Client Administrators, and the Authorized Users to whom a Client Administrator grants that permission, may put an approved Result on a weekly or monthly schedule, and pause or remove that schedule. Each run is a new Request that uses fresh data, is held for review like the first, and is charged under Section 7A.6. A scheduled run takes no action in a Connected Account, so it is not an Automated Action under Section 6.3.
7A.8 Ownership. Results are Client Data and, as between the parties and to the extent any rights exist in them, belong to Client under Section 9.1. The Solution Factory itself, including its instructions to the agent, its templates and checks and the software that runs it, is part of the Consultant Materials under Section 3.3 and remains Provyn's. Provyn's templates and methods used in a Result remain Consultant Materials, which Client may use as part of that Result.
7A.9 Switching it off. Provyn may suspend the Solution Factory, or a part of it such as live access, under Section 17.3, or when Anthropic changes, limits or ends the service it relies on. Provyn may also end the Add-On on 30 days' notice. Before switching it off, Provyn stops any Request in progress, which is charged for the work done. Results already handed back remain Client Data. Any monthly Solution Factory fee (Section 7A.6) ends from the day the Add-On is switched off, and Provyn will refund any part of it that Client prepaid for the period after that day.
8. LinkedIn
8.1 How the LinkedIn connection works. LinkedIn features use the LinkedIn Automation Service (Section 2.12). Client's own LinkedIn account (and Client's LinkedIn Company Page, if it has one) is connected to an account with the LinkedIn Automation Service that Provyn holds and pays for. Client connects its LinkedIn account itself, from an invitation link that Provyn sends through the LinkedIn Automation Service, so Client never gives Provyn its LinkedIn password, and Client's own access to the LinkedIn Automation Service shows only Client's account. The Dashboard reads LinkedIn data through the LinkedIn Automation Service and, in the Add-Ons, acts on Client's LinkedIn account through it. Client's LinkedIn account remains Client's, or the individual account holder's, under LinkedIn's User Agreement with that person.
8.2 LinkedIn's rules and the risk to the account. LinkedIn's User Agreement restricts the use of third-party software, bots and other automated tools to access LinkedIn or act on an account. Using the LinkedIn Automation Service, including for reading only, may be treated by LinkedIn as a breach of those terms. LinkedIn may warn, limit, restrict, suspend or permanently close an account it believes uses automation, without notice and without any right of appeal. Client acknowledges this risk and that, by connecting its LinkedIn account, Client chooses to accept it.
8.3 Separate opt-in for automated sending. The Core Features only read from LinkedIn. Provyn keeps the LinkedIn Automation Service's shared-engagement features (for example, pools that like or comment on other users' posts) switched off for Client's account. Sending on LinkedIn (connection requests, messages, comments, reactions, posts and withdrawals of invitations) is available only in Add-Ons. Each LinkedIn Automated Action also requires the separate written opt-in in Appendix C, signed by Client and acknowledged by the person who holds the LinkedIn account. A LinkedIn post that a named Authorized User approves individually, and that is then published at once or scheduled for a time that user chooses, is a change made on a click under Section 6.2 and not an Automated Action, so it needs no Appendix C opt-in. A post on a person's own LinkedIn profile is published or scheduled only by that person.
8.4 Pacing and limits. Provyn sets the Dashboard's LinkedIn sending limits well below LinkedIn's published limits, and the LinkedIn Automation Service applies its own caps and pacing. These measures reduce the risk of a restriction but do not remove it.
8.5 No responsibility for LinkedIn's actions. Provyn does not warrant that LinkedIn will not restrict Client's account. To the extent permitted by law, Provyn is not liable for any warning, restriction, suspension or closure of a LinkedIn account, or for any resulting loss of connections, content, subscriptions or business, except to the extent caused by Provyn exceeding the limits recorded in Appendix C or acting on an account Client did not authorize, and then only within the limits of MSA Section 7. If LinkedIn restricts Client's account, Provyn will promptly turn off Automated Actions for that account and help Client respond.
8.6 Client's indemnity for LinkedIn use. Client's indemnity under MSA Section 8.2 includes third-party claims, including claims by LinkedIn, arising from content sent from Client's accounts through the Dashboard and from Client's use of LinkedIn automation, except to the extent caused by Provyn's breach of these Terms.
8.7 Provyn's account with the LinkedIn Automation Service. Because Provyn holds the account: (a) the LinkedIn Automation Service's charges for Client's connection are included in the Fees; (b) Provyn can access, through the LinkedIn Automation Service, the LinkedIn data of Client's connected account, and uses it only to operate the Dashboard for Client; and (c) at Closing, Provyn will remove Client from Provyn's account with the LinkedIn Automation Service and delete Client's LinkedIn account from it. Client should also review the active sessions and connected applications in its LinkedIn settings.
8.8 LinkedIn exports. Client's Authorized Users may upload LinkedIn analytics exports for Client's own LinkedIn account and Company Page. Client confirms it is entitled to download and use them.
9. Client Data
9.1 Ownership. As between the parties, Client owns Client Data, as MSA Sections 4.1 and 6.6 provide. Provyn claims no ownership of Client Data.
9.2 Provyn's role. For personal information in Client Data, Provyn acts as Client's service provider (a "processor" under the Colorado Privacy Act and similar state laws, where they apply). Provyn processes Client Data only on Client's documented instructions, which are the Master Agreement, these Terms, the Dashboard SOW, Client's settings and Client's written requests. Provyn does not sell Client Data and does not use it for targeted advertising. If applicable law requires additional terms for Provyn's processing of Client Data, the parties will enter into a data processing addendum as MSA Section 6.6 provides. On request, Provyn will sign its Data Processing Addendum with Client, which restates Provyn's duties as Client's processor under these Terms; if the Data Processing Addendum and these Terms or the Master Agreement differ, these Terms and the Master Agreement control.
9.3 How Provyn uses Client Data. Provyn uses Client Data only to provide, support, secure and maintain the Dashboard for Client, to comply with law, and as Client instructs.
9.4 Aggregate and de-identified data. Provyn may create aggregate or de-identified information from use of the Dashboard (for example counts of jobs run, timing, AI cost per feature, or average invitation acceptance rates across clients) that does not identify Client, its personnel or its contacts, and may use it to operate and improve the Dashboard and in describing Provyn's services. Provyn takes reasonable measures to ensure that this information cannot be linked to Client or to any individual, commits not to re-identify it, and requires anyone it shares it with to make the same commitment. Provyn will not publish a case study or results that identify Client without Client's prior written consent, consistent with MSA Section 4.5. Any figure Provyn uses in describing its services combines data from at least three clients.
9.5 Client's responsibilities for Client Data. Client is responsible for the lawfulness of the Client Data it connects or provides, and for the notices, consents and legal bases required, as MSA Section 6.6 provides. The Dashboard is not designed for protected health information under HIPAA. Provyn is not a business associate of Client and will not sign a business associate agreement. Client will not connect an account, calendar, mailbox, CRM, survey list or recording source that contains protected health information or other patient details, and will not put them into the Dashboard in any other way. Client also will not put into the Dashboard Social Security numbers, payment card numbers or data about children. If Client learns that such data has reached the Dashboard, Client will tell Provyn promptly, and Provyn may delete it and suspend the affected connection. Client is responsible for any consent required to record a meeting whose recording or transcript reaches the Dashboard.
9.6 Operational records. Operating the Dashboard also creates records about the service, such as job and refresh logs, records of actions taken, the administrator audit log (Section 10.4), AI cost records (one line per AI request, with the job, model, size, cost and Client's identifier), and training progress records (which Dashboard training videos each Authorized User has watched, and how much), which Client's administrators and Provyn's administrators can see. Section 18.6 says which of these Provyn keeps after Closing.
9.7 Google user data. If Client connects Google Workspace, Provyn's use of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. Provyn does not use Google user data to develop, improve or train generalized AI models.
9.8 Privacy policy. Provyn's privacy policy at https://provyn.com/privacy describes how Provyn handles personal information. If the privacy policy and these Terms differ on Client Data, these Terms and the Master Agreement control.
10. Provyn's Access to Client Data
10.1 Provyn administrators can see Client Data, by design. Provyn's administrators can open Client's Dashboard and see everything Client's Authorized Users see, plus the technical side of the service: job records, usage and cost records, and the status of each connection. Provyn's administrators also have technical access to the server and its files for maintenance, backups, restores and deletion.
10.2 Who. Access is limited to Provyn personnel and contractors with an administrator sign-in who are bound by confidentiality duties under MSA Section 5.2. At the date of these Terms, that is Paul Brown.
10.3 Why. Provyn uses this access only to set up the Dashboard, to provide support Client asks for, to find and fix failures, to keep the service secure, to comply with law, and as Client instructs.
10.4 Changes are logged. Every change a Provyn administrator or a Client Administrator makes to Client's Dashboard settings and access (for example switching features on or off, adding or removing users, entering Credentials, changing settings, closing or deleting the account) is recorded with who made it and when. Client may ask for a copy of the log entries about its account.
10.5 What Provyn staff cannot see. Provyn staff cannot see stored Credentials (Section 5.4) and never receive Client's LinkedIn password. Each client's data is kept in its own separate database, a sign-in belongs to one client only, and the Dashboard's software refuses to read one client's data, keys or settings for another client.
10.6 AI support tools. Provyn uses AI coding assistants (at the date of these Terms, Anthropic's Claude Code) to build, operate and troubleshoot the Dashboard. When Provyn investigates a failure or a problem Client reports, these tools may read Client Data on the Dashboard's server or in Client's Dashboard, only for the purposes in Section 10.3 and under the same confidentiality duties. These tools run on Provyn's individual Anthropic plan, not on the paid API the Dashboard's own AI features use. Client Data read this way is processed by Anthropic under Anthropic's terms for that plan, and Provyn keeps the setting that would allow that data to be used to train Anthropic's models switched off.
11. Service Providers
11.1 Use of Service Providers. Provyn uses the Service Providers listed in Appendix A to host, run and support the Dashboard, as MSA Section 5.2 permits. Appendix A states what each one does, what Client Data it may handle, and where. Provyn chooses Service Providers whose terms include confidentiality and security commitments where such terms are available.
11.2 Client's own vendors are not Service Providers. The vendors of Client's own Connected Accounts (Section 5.1) are not Provyn's Service Providers. Their handling of Client's data is governed by Client's own contracts with them.
11.3 Notice of new Service Providers. Provyn will update Appendix A at the URL of these Terms where the change affects what it shows, and will email Client's notice contact, naming the new Service Provider, at least 15 days before a new Service Provider begins processing Client Data. No notice is given for a provider that processes only other clients' data. Where a change is urgent (for example to replace a provider after an outage or incident), Provyn will notify Client promptly after the change. If Client reasonably objects on data protection grounds, the parties will discuss it in good faith, and Client may terminate the Dashboard SOW by notice as its sole remedy, with a refund of any Fees prepaid for the period after termination.
11.4 Names of Service Providers. Appendix A identifies some Service Providers by type rather than by name. On request, Provyn will give Client the name of every Service Provider that processes Client Data. Client will treat those names as Provyn's Confidential Information under MSA Section 5. A notice under Section 11.3, and a Security Incident notice under Section 13 that involves a Service Provider, will name that Service Provider.
12. Security
12.1 Safeguards. Provyn maintains reasonable administrative, technical and physical safeguards appropriate to its size and to the data, including: sign-in through Cloudflare Access with a one-time emailed code and a list of approved addresses; a separate database for each client, with software checks that block code from opening another client's data; encrypted Credentials, with the encryption key held outside the data volume and the backups; encrypted connections (HTTPS) to the Dashboard; logging of administrator changes; and hosting in a United States data center (Railway, US East). Railway states that it encrypts data stored on its platform at rest (AES-256), and Dropbox states the same for the nightly backups.
12.2 Backups. A nightly backup copy of the whole server, which includes Client Data, is stored in Provyn's Dropbox account, which may also be synced to Provyn's own secured computers; the newest 30 nightly copies are kept. Railway keeps its own snapshots of the data volume for the period Railway's settings provide, currently up to 89 days. Before a software update, Provyn may keep short-term recovery copies of databases; Provyn deletes them within 30 days, except the copies from the most recent update. Backup and recovery copies are used only to restore the service.
12.3 Client's part. Client will keep its email accounts secure (sign-in codes are sent there), use multi-factor authentication on its Connected Accounts where the vendor offers it, remove departing users promptly (Section 4.4), and never send Credentials by email (Section 5.3).
12.4 No perfect security. No system is perfectly secure. Provyn does not promise that the Dashboard will be free of security incidents, only that it will take the measures in this Section 12 and respond as Section 13 provides.
13. Security Incidents
13.1 What counts. A "Security Incident" is a confirmed unauthorized access to, or acquisition, disclosure or loss of, Client Data or Credentials held by Provyn or by a Service Provider for Provyn.
13.2 Notice. Provyn will investigate a suspected Security Incident promptly. Provyn will notify Client without undue delay, and in any event within 72 hours, after Provyn confirms a Security Incident affecting Client Data or Credentials, including one at a Service Provider that Provyn learns of.
13.3 What the notice will say. The notice will describe, to the extent known: what happened and when; which Client Data and Credentials were or may have been affected; which Service Provider was involved, if any; what Provyn has done and will do; what Client should do (for example, replace particular keys through the Connection Keys card); and a contact at Provyn. Provyn will update Client as it learns more.
13.4 Response. Provyn will take reasonable steps to contain and investigate the Security Incident, replace its own affected keys (including the encryption key for Credentials), and cooperate with Client's legal notice obligations. Because Client controls its contacts' data, notices to Client's contacts or to regulators are Client's decision and responsibility, unless the law requires Provyn to give them. Each party bears its own costs of the notices it gives. A notice under this Section 13 is not an admission of fault or liability.
14. Availability and Support
14.1 No uptime guarantee. Provyn aims for 99% monthly availability of the Dashboard itself, not counting outages at Service Providers or at Client's own vendors, and maintenance announced in advance. This is a target, not a guarantee: Provyn does not guarantee uninterrupted or error-free service, and no service credit applies unless the Dashboard SOW states one. Provyn measures the Dashboard's availability and reports the month's figure to Client in the monthly results report.
14.2 Maintenance. Provyn updates the Dashboard from time to time, normally outside Client's business hours, which may cause brief interruptions.
14.3 Outages outside Provyn's control. The Dashboard depends on hosting, sign-in and vendor services that Provyn does not control. Their outages, changes and incidents are covered by MSA Sections 6.5(c) and 9.3.
14.4 Support. Client may contact Provyn for support by email at support@provyn.com, Monday to Friday, 8:00 AM to 5:00 PM Mountain Time, excluding US federal holidays. Provyn aims to respond within one business day, and on the same business day when the Dashboard is unavailable.
14.5 Time zone. Scheduled jobs and dates in the Dashboard use Mountain Time.
15. Acceptable Use
15.1 Rules. Client and its Authorized Users will not: (a) use the Dashboard to send spam or any message that breaks the law (including laws on commercial email and calls) or a vendor's terms, other than the LinkedIn automation risk Client accepts under Section 8; (b) try to reach another client's data, or probe, test or defeat the Dashboard's security; (c) share sign-in codes or sessions, or let anyone other than an Authorized User use the Dashboard; (d) copy, reverse engineer, resell, or provide the Dashboard to any third party; (e) upload malicious code or unlawful content; (f) upload data Client has no right to use; (g) use the Dashboard to impersonate any person; (h) interfere with the Dashboard's operation or other clients' use of it; (i) use the Dashboard, its documentation, or any of Provyn's Confidential Information learned through it, to build, or to help a third party build, a product or service that competes with the Dashboard; (j) use the AI features or the Solution Factory in a way that breaks the AI provider's usage policies (for Anthropic, https://www.anthropic.com/legal/aup); (k) use AI Output as the basis, or a substantial factor, in a decision about an individual's employment, credit, housing, insurance, education or health care; (l) access the Dashboard by automated means, or copy its screens, text, templates or data structures in bulk, other than through the export features Provyn provides; (m) try to obtain the instructions, prompts or templates that the AI features and the Solution Factory use; (n) add as an Authorized User anyone who works for a business offering a product that competes with the Dashboard, without Provyn's written consent; or (o) give a third party, or publish, screenshots or recordings of the Dashboard's non-public screens, or the results of technical tests of it, without Provyn's written consent. Item (i) is limited to that use. It is not a general restriction on competition, and nothing in it limits Client's own business, Client's use of its own Client Data, or ideas and information Client had or developed independently of the Dashboard.
15.2 Enforcement. Provyn may suspend access under Section 17.3 for a material breach of this Section 15.
16. Fees
16.1 Fees. Fees for the Dashboard, including any one-time setup fee, are stated in the Dashboard SOW and are invoiced and paid under MSA Section 2. These Terms contain no prices.
16.2 What the Fees cover. Unless the Dashboard SOW says otherwise, the Fees cover hosting, setup and support of the Dashboard, Provyn's account with the LinkedIn Automation Service for Client, and AI use within the allowance in Section 7.5. Factory Charges for the Solution Factory (Section 7A.6) and Envelope Charges for the Contracts Add-On (Section 16.5) are not covered by the Fees and are billed in addition to them. Client pays its own vendors directly for its own Connected Accounts (for example HubSpot, Microsoft 365 or Google Workspace, Fathom and FreshBooks).
16.3 Non-payment. MSA Section 2.3 applies, including Provyn's right to suspend the Dashboard on written notice if amounts remain unpaid more than 45 days after the invoice date.
16.4 Fee changes. Provyn may change the Fees by written notice at least 60 days before the change takes effect. If Client does not accept a change, Client may end the Dashboard SOW under Section 17.1 before the change takes effect. Each notice of a fee change will say how Client can end the Dashboard SOW, including by email to support@provyn.com.
16.5 E-signature envelopes. With the Contracts Add-On, Client's agreements are sent for signature through Provyn's e-signature account. Each agreement sent for signature through the Dashboard (an "envelope") is charged by use, in addition to the Fees, at the amount per envelope stated in the Dashboard SOW (the "Envelope Charges"). Envelope Charges are counted by calendar month in Mountain Time, added to Client's next invoice with the number of envelopes sent, and invoiced and paid under MSA Section 2. Section 16.4 applies to Envelope Charges as it does to the Fees: a change to the amount per envelope takes effect only after at least 60 days' written notice.
17. Term, Suspension and Termination
17.1 Term. After any Pilot, the Dashboard SOW runs month to month and renews automatically each month, unless the Dashboard SOW states a different term. Each monthly renewal begins on the first day of a calendar month. Either party may end it at any time by at least 30 days' prior written notice, as MSA Section 3.2 provides. Client may give that notice by email to support@provyn.com from the address of an authorized representative of Client, and the notice is effective when sent.
17.2 Termination. Either party may terminate the Dashboard SOW as MSA Sections 3.2 and 3.3 provide. Terminating the Dashboard SOW does not end any other SOW. Terminating the Master Agreement ends the Dashboard SOW.
17.3 Suspension. Provyn may suspend all or part of the Dashboard immediately if reasonably needed: (a) to prevent harm to the Dashboard, to other clients or to a Connected Account (for example a suspected compromise, or a warning from LinkedIn); (b) to comply with law or a vendor's requirement; (c) for a material breach of Section 15; or (d) for non-payment under Section 16.3. Provyn will tell Client promptly, limit the suspension to what is needed, and restore access when the cause is resolved. Turning off an Automated Action at Client's request is not a suspension.
17.4 Effect of termination. When the Dashboard SOW ends for any reason, Section 18 applies.
18. End of Service: Export and Deletion
18.1 Closing. When the Dashboard SOW ends, Provyn closes Client's account: Authorized Users can no longer sign in, every feature is switched off, and no scheduled job runs for Client.
18.2 Export. At Closing, Provyn prepares one export of the Client Data held in the Dashboard. It contains: (a) each of Client's databases, as SQLite files; (b) every table of those databases as CSV files, which open in Excel; (c) Client's settings, documents (for example signed agreements) and the files Client uploaded; and (d) a manifest listing every file with its size and checksum. The export never contains Credentials, tokens or sign-in files, any other client's data, or Provyn's internal working files, logs and records (such as AI drafting work folders, job and vendor call logs, and Provyn's AI cost records). Provyn delivers the export through a secure file-sharing link that expires (password-protected where available) or another secure transfer, never as an email attachment. The link remains available for 14 days, and Provyn will issue a new link on request during the Grace Period. The structure of the export is provided so Client can use its own Client Data and is not licensed for building a competing product.
18.3 Grace period. Provyn keeps Client Data for 30 days after Closing (the "Grace Period"). During the Grace Period Client may ask for another export or for the account to be reopened under a new Dashboard SOW. Client may ask Provyn to shorten the Grace Period and delete sooner.
18.4 Revoking connections. At Closing, Provyn deletes every Credential and sign-in file stored for Client, disconnects Google and Fathom through their own disconnect functions (removing Client's Fathom webhook), and removes Client from Provyn's account with the LinkedIn Automation Service, deleting Client's LinkedIn account from it (Section 8.7). Provyn will give Client a list of access that only Client can remove, for example the HubSpot service key, the Microsoft 365 application and its secret, Provyn's application in Fathom (Fathom offers no way for Provyn to revoke it), and any Google Analytics viewer access. Client should remove that access promptly.
18.5 Deletion. After the Grace Period, Provyn deletes from the live service: Client's databases, settings, documents, uploaded files, logs and working folders; Client's pre-update recovery copies; Client's export files on the server and in Provyn's Dropbox; and Client's platform records (feature switches, colors, logo, AI allowance, mail settings and user list). Provyn will also delete Client's scheduled job definitions, any copy of the export Provyn made to share it, receipt photos and messages for Client in Provyn's receipts mailbox, and questions and notifications for Client held on Provyn's notification server. Provyn will confirm the deletion to Client by email and, on request, with a signed certificate of deletion.
18.6 What remains after deletion, and for how long. After deletion: (a) the nightly backups in Provyn's Dropbox, each a copy of the whole server, age out within about 30 days, and Railway's volume snapshots within the period in Section 12.2; they are used only to restore the service, and if a restore ever brings back Client Data, Provyn will delete it again; (b) Provyn keeps indefinitely a closed record of Client (name, short name, and the dates the account was created, closed and deleted) and the audit log entries about Client, with the email addresses of Client's users removed at deletion; (c) Provyn keeps its AI cost records for Client (job, model, size, cost and Client's identifier) as business records; (d) hosting logs that may name Client remain for the hosting provider's log retention period (30 days on Provyn's Railway plan); (e) Service Providers keep data under their own terms (for example Anthropic, Section 7.2); (f) logs of Provyn's job scheduler and notification server that may name Client remain until they age out under those systems' log retention; (g) support emails with Client and the session records of the AI tools Provyn uses for support (Section 10.6), which may contain Client Data, are kept as Provyn's support records on Provyn's own systems and computers and deleted when no longer needed; and (h) data in Client's own vendor accounts is not affected. Section 22 continues to apply to anything Provyn retains for as long as it is retained.
18.7 Requests about individuals during the term. If one of Client's contacts or users asks to have personal information deleted or corrected, Client will handle it in the source system (for example HubSpot), and the change will reach the Dashboard at the next refresh. Provyn will help Client remove the information from the Dashboard where the refresh does not, and will reasonably assist Client in responding to requests that individuals make under applicable privacy law.
19. Warranties and Disclaimers
19.1 Warranty. Provyn will provide the Dashboard in a professional and workmanlike manner and materially as described in these Terms. If the Dashboard does not meet this warranty, Provyn will correct it within a reasonable time after Client's notice. If Provyn cannot, Client may terminate the Dashboard SOW and receive a refund of Fees prepaid for the period after termination and of the Fees paid for the month in which Client gave notice. This is Client's only remedy for breach of this warranty, without limiting Section 13.
19.2 Disclaimers. MSA Sections 6.4 and 6.5 apply to the Dashboard. In particular, AI Output and third-party services are provided without warranty, and figures shown in the Dashboard are only as accurate and current as the data received from Connected Accounts. The Dashboard does not provide legal, tax, accounting or financial advice. Any use of the Dashboard provided at no charge, such as a test account, is provided as is, as MSA Section 7.3 provides.
20. Limitation of Liability
20.1 The Master Agreement applies. MSA Section 7 applies to the Dashboard. Fees paid under the Dashboard SOW are the fees used to calculate the cap in MSA Section 7.2.
20.2 Owners and personnel. The exclusions and limits in MSA Section 7 and in these Terms also apply to claims against Provyn's owners, managers, personnel and contractors, who may rely on this Section. The limits apply in total, not separately for each of them.
21. Indemnification
21.1 The Master Agreement applies. MSA Section 8 applies to the Dashboard. Client's indemnity under MSA Section 8.2 also covers third-party claims arising from: (a) content sent from Client's accounts through the Dashboard (Section 7.4); (b) Client's use of LinkedIn automation (Section 8.6); and (c) Client's lack of authority to connect an account or grant a permission (Section 5.2), or to provide Client Data (Section 9.5); in each case except to the extent caused by Provyn's breach of these Terms.
22. Confidentiality
22.1 Client Data and Credentials. Client Data and Credentials are Client's Confidential Information under MSA Section 5.
22.2 Provyn's information. The Dashboard's non-public features, code, designs and documentation, and the names of Service Providers given to Client under Section 11.4, are Provyn's Confidential Information.
22.3 Feedback. "Feedback" means suggestions, ideas and comments that Client or its Authorized Users give Provyn about the Dashboard. Client grants Provyn a perpetual, irrevocable, worldwide, royalty-free right to use Feedback for any purpose, including for other clients, without obligation or payment to Client, and any improvement Provyn makes to the Dashboard from Feedback is part of the Consultant Materials under MSA Section 4.3. Client's Confidential Information and Client Data are never Feedback, even when they are included with it, and Provyn will not disclose them as part of using Feedback. The general idea for a feature or report that Client asks for, including in a Solution Factory Request, is Feedback; the Request's data and its Result are not.
23. Changes to These Terms
23.1 Posting new versions. Provyn may publish a new version of these Terms at https://provyn.com/dashboard-terms with a new "Last updated" date. Provyn will keep previous versions and provide them on request.
23.2 When a new version applies to Client. A new version applies to Client only: (a) when Client agrees to it in writing, for example in an amendment or a new Dashboard SOW that refers to it; or (b) from the start of the first renewal of the Dashboard SOW's term that begins at least 30 days after Provyn emails Client's notice contact a copy of the new version and a summary of what changed. Until then, the version that applies to Client stays in effect. Provyn's email will say how Client can end the Dashboard SOW, including by email to support@provyn.com. If a change in a new version materially and adversely affects Client, Client may terminate the Dashboard SOW by notice before the change applies to Client and receive a refund of any Fees prepaid for the period after termination.
23.3 Changes required by law or for security. A change that the law requires, or that is reasonably needed to protect the security of the Dashboard or of Client Data, applies to Client when Provyn emails Client's notice contact about it. If such a change materially and adversely affects Client, Client may terminate the Dashboard SOW by notice within 30 days after Provyn's email and receive a refund of any Fees prepaid for the period after termination.
23.4 Limits. A change to these Terms cannot change the Master Agreement or a signed Dashboard SOW, and cannot change the Fees except as Section 16.4 provides.
24. General
24.1 Governing law, venue and jury waiver. MSA Sections 9.5 and 9.6 apply: Colorado law, courts in Arapahoe County, Colorado (or the U.S. District Court for the District of Colorado where federal jurisdiction is exclusive), and the jury trial waiver.
24.2 Notices. Legal notices are given as MSA Section 9.4 provides. Provyn's address for notices: Think Tank Products, LLC d/b/a Provyn, Attn: Paul Brown, 7612 S Overlook Way, Littleton, CO 80128, paul@provyn.com. Operational notices under these Terms (for example lapse notices, maintenance notices and Service Provider changes) may be given by email to Client's designated contact or inside the Dashboard. An email is confirmed for MSA Section 9.4 if it is sent to the notice address and no delivery failure is received. Notices of fee changes, of new versions of these Terms and of termination are legal notices.
24.3 Survival. Sections 7A.6 (for work done before the end of service), 9, 15.1(d) and 15.1(i) (for anything learned before the end of service), 10.5, 13 (for incidents that occurred before the end of service), 18, 19, 20, 21 and 22 survive the end of the Dashboard SOW.
24.4 Entire agreement. MSA Section 9.7 applies. These Terms, the Master Agreement and the Dashboard SOW are the whole agreement about the Dashboard.
Appendix A: Service Providers
Service Providers that may store or process Client Data, at the date of these Terms. Client's own vendors (HubSpot, Microsoft 365 or Google Workspace, Google Analytics, Fathom, Memoket, FreshBooks and GetLeads) are not listed because they are not Provyn's Service Providers (Section 11.2). A Service Provider shown by type is named to Client on request, in confidence (Section 11.4). Data processing terms: Anthropic, anthropic.com/legal/data-processing-addendum (for the API only; Provyn's AI support tools run on Provyn's individual Anthropic plan under Anthropic's terms for that plan, Section 10.6); Railway, railway.com/legal/dpa; Microsoft, the Microsoft Products and Services Data Protection Addendum (microsoft.com/licensing); the e-signature service, on request.
Railway Corporation
What it does for the Dashboard: Hosts the Dashboard's servers, data volume, job scheduler (n8n, run by Provyn on Railway) and Provyn's notification server
Client Data it may handle: All Client Data, including encrypted Credentials
Location: United States (US East)
Cloudflare, Inc.
What it does for the Dashboard: Sign-in (Cloudflare Access) and the network in front of the Dashboard and its public survey pages
Client Data it may handle: Authorized Users' email addresses, sign-in events, and traffic passing to and from the Dashboard
Location: Global network
Dropbox, Inc.
What it does for the Dashboard: Nightly backups; hand-off of the export at Closing
Client Data it may handle: Full backup copies of Client Data (Credentials encrypted); Client's export
Location: As provided in Dropbox's terms for Provyn's account
Anthropic, PBC
What it does for the Dashboard: AI features through its API, including drafting and reading receipt photos (unless Client uses its own key); the Solution Factory's agent (Section 7A); and, on Provyn's individual Anthropic plan, Provyn's AI support tools (Section 10.6)
Client Data it may handle: The facts sent for each draft, and the draft; receipt photos and the values read from them; a Request's instructions, files, exported Client Data and Results (Section 7A), and, with live access, one read-only Credential for that Request; Client Data an AI support tool reads during support
Location: As provided in Anthropic's terms
The LinkedIn Automation Service (a third-party LinkedIn automation service, named to Client on request under Section 11.4)
What it does for the Dashboard: LinkedIn connection, through Provyn's account
Client Data it may handle: Client's LinkedIn data read, actions taken on Client's LinkedIn account, and posts and their media, held until publication when scheduled
Location: Not stated by the provider; data may be processed outside the United States
Microsoft Corporation (Provyn's own Microsoft 365)
What it does for the Dashboard: Email Provyn sends to Client and to itself, such as job alerts and notices; with Receipt Photos (part of the Accounting Add-On), the receipts mailbox to which Client's Authorized Users may email receipt photos
Client Data it may handle: Client's name, connection status, the content of those messages, and receipt photos emailed to that mailbox
Location: As provided in Microsoft's terms for Provyn's tenant
An e-signature service (Provyn's account)
What it does for the Dashboard: E-signature of Provyn's own agreements with Client and, with the Contracts Add-On, of the agreements Client sends for signature through the Dashboard
Client Data it may handle: Names and email addresses of signers, and the agreements' content
Location: As provided in the provider's terms for Provyn's account
When an Authorized User receives Solution Factory questions on an iPhone (Section 7A.3), Provyn's notification server sends a wake-up signal through ntfy.sh's relay service so that Apple can deliver it. The wake-up signal carries no message text; the phone then fetches the question from Provyn's own notification server.
Appendix B: What the Dashboard Reads and Writes
HubSpot (Client's)
Feature: Core
Reads: Contacts, companies, owners, lists, tasks and notes (no deals)
Writes or sends: On a click: completes or creates tasks, sets a contact's type or lead status; with Contracts, can mark a contact as a customer and create or update its company
Microsoft 365 (Client's)
Feature: Core
Reads: Calendar events (the permission can cover every calendar in Client's organization, Section 5.2); unread and total counts of the designated inbox; with Email to Task, messages whose subject starts with "New Task"
Writes or sends: Sends the monthly report, Level 10 sheet and assignment emails from the designated mailbox, only to recipients Client lists
Microsoft 365 (Client's)
Feature: Surveys Add-On
Reads: Nothing beyond the Core row
Writes or sends: Sends the survey invitations Client starts or schedules, one email to each Respondent (Section 6A.3)
Google Workspace (Client's)
Feature: Core, alternative to Microsoft 365
Reads: Calendar events on calendars the user owns; inbox counts
Writes or sends: None. The monthly report, Level 10 sheet, assignment emails and lapse notices are sent from Provyn's dashboard mailbox with Client's address as reply-to (Section 6.4)
LinkedIn through the LinkedIn Automation Service (Provyn's account with it, Client's LinkedIn account)
Feature: Core reads; LinkedIn Outreach and Cold Outreach Add-Ons write
Reads: Profile, connections, followers, profile viewers, posts and engagement, invitations, messages in conversations the Dashboard manages
Writes or sends: Add-Ons only. On a click: meeting requests, follow-ups and replies, comments, reactions, connection requests, and posts (text, images, PDF documents) on Client's profile or Company Page. Automated, only with the Appendix C opt-in: scheduled connection requests and withdrawal of old invitations
LinkedIn analytics exports (uploaded by Client)
Feature: Core
Reads: Personal and Company Page analytics files Client uploads
Writes or sends: Nothing
Google Analytics (Client's)
Feature: Core Features (Website)
Reads: Website traffic reports
Writes or sends: Nothing
Fathom or Memoket (Client's)
Feature: Conversations Add-On
Reads: Meeting recordings' transcripts and summaries
Writes or sends: Nothing (a Fathom webhook is registered so new recordings arrive)
FreshBooks and a receipts mailbox (Client's)
Feature: Accounting Add-On
Reads: Accounting reports, invoices and expenses; receipt emails (read-only)
Writes or sends: On approval: attaches a receipt to an expense in FreshBooks that has none
Receipt photos (taken or emailed by Client's Authorized Users)
Feature: Accounting Add-On (Receipt Photos)
Reads: Photos taken on the Dashboard's Snap a receipt page or emailed to Client's private receipts address; the vendor, date and amount read from each photo by AI
Writes or sends: On approval: attaches the photo to the matching expense in FreshBooks that has no receipt
E-signature service (Provyn's account)
Feature: Contracts Add-On
Reads: Status of envelopes and signed copies (checked hourly while one is out)
Writes or sends: On a click: sends an agreement for signature (Section 16.5)
GetLeads
Feature: Cold Outreach Add-On
Reads: Prospect lists and counts
Writes or sends: None in GetLeads. The invitations are sent through the LinkedIn Automation Service on a daily schedule, so Appendix C applies
Anthropic
Feature: AI features and the Solution Factory
Reads: Not applicable
Writes or sends: Receives the facts needed for each draft and each receipt photo to be read (Section 7) and, with the Solution Factory, each Request's files and exported data (Section 7A)
Appendix C: LinkedIn Automation Opt-In
To be completed and signed before Provyn turns on any LinkedIn Automated Action (Sections 6.3 and 8.3).
Client legal name: ______________________________
LinkedIn account holder name: ______________________________
LinkedIn profile address: ______________________________
Company Page (if any): ______________________________
Add-On (LinkedIn Outreach or Cold Outreach): ______________________________
Automated Actions Client turns on (tick each):
☐ Scheduled connection requests, up to ______ per ______ (day or week).
☐ A note with each scheduled request: ☐ none ☐ this fixed text approved by Client: ______________________________. AI-written notes are not available on scheduled requests.
☐ Withdrawal of invitations not answered after ______ days.
☐ Other Automated Action, described: ______________________________.
Client and the account holder acknowledge that:
They have read Section 8 of the Provyn Dashboard Terms of Service.
LinkedIn's User Agreement restricts automation, and LinkedIn may warn, restrict, suspend or close the account, without notice, because of these Automated Actions.
Client accepts that risk, and Provyn is not responsible for LinkedIn's actions except as Section 8.5 states.
Client may turn any Automated Action off at any time by emailing support@provyn.com, and Provyn will do so within two business days.
Signed for Client: ____________________ Name: __________ Title: __________ Date: __________
Acknowledged by account holder: ____________________ Name: __________ Date: __________
Countersigned for Provyn: ____________________ Name: __________ Date: __________
Appendix D: Section References for the Consulting Agreement
Where the Master Agreement is Provyn's Consulting Agreement, a reference in these Terms to a section of the MSA means the corresponding section of the Consulting Agreement below. Where the Consulting Agreement has no matching provision, the reference does not apply.
MSA section 2 and 2.3
Subject: Fees, invoices, payment and suspension for non-payment
Consulting Agreement section: 4
MSA section 3.2 and 3.3
Subject: Termination for convenience and for cause
Consulting Agreement section: 13
MSA section 3.4(c)
Subject: Return or destruction of Confidential Information
Consulting Agreement section: 13 (last sentence)
MSA section 4.1
Subject: Client's ownership of its materials
Consulting Agreement section: 5
MSA section 4.2 and 4.3
Subject: Deliverables and Consultant Materials
Consulting Agreement section: 5
MSA section 4.5
Subject: Publicity
Consulting Agreement section: 5
MSA section 5, 5.2 and 5.5
Subject: Confidentiality, service providers and duration
Consulting Agreement section: 11
MSA section 6.4 and 6.5
Subject: Disclaimer; AI and third-party platforms
Consulting Agreement section: 6
MSA section 6.5(d)
Subject: Client's third-party licenses and subscriptions
Consulting Agreement section: 3
MSA section 6.6
Subject: Client Data and data protection
Consulting Agreement section: 3
MSA section 7, 7.1 and 7.2
Subject: Limitation of liability
Consulting Agreement section: 7
MSA section 7.3
Subject: No-charge services
Consulting Agreement section: 8
MSA section 8 and 8.2
Subject: Indemnification
Consulting Agreement section: 12
MSA section 9.3
Subject: Force majeure
Consulting Agreement section: 16
MSA section 9.4
Subject: Notices
Consulting Agreement section: 18.7
MSA section 9.5 and 9.6
Subject: Governing law, venue and jury waiver
Consulting Agreement section: 19
MSA section 9.7
Subject: Entire agreement and precedence
Consulting Agreement section: 18.6