Current Version: #1111-2
This Platyform IO Model Agreement (this “Agreement”) is made effective on the date of purchase of a designated “Platyform IO Model and Support Membership” subscription product, by and between the purchaser, identified by the information inputted into “Billing Details” at checkout (ref. section 17 IDENTIFICATION AND ENFORCEMENT for more details), and Platyform LLC (the “Consultancy-as-a-Service” or ” CaaS”), of 2940 N. Prospect #7889, Colorado Springs, CO 80907. In this Agreement the purchaser of the “Platyform IO Model and Membership” subscription product shall be referred to as “Organization” or collectively as “Organizations”, and the CaaS shall be referred to as “Platyform”.
WHEREAS, Platyform possesses technical expertise in the field of digital platform development and, in particular, the creation, development, deployment, training, and support of digital platform technology and integration architectures; and
WHEREAS, the Organization desires to engage Platyform, and Platyform accepts the engagement, to facilitate the deployment, training and support of Platyform’s proprietary resource library including stack templates, component training/support, and technology to the Purchasing Organization (“Organization”) in accordance with the terms and conditions set forth in this Agreement.
NOW, THEREFORE, in consideration of the mutual covenants and agreements set forth herein, the Organization and Platyform agree as follows:
(1) RETENTION OF CaaS. The Organization hereby retains the services of Platyform and its provided system accesses through the establishment of a Platyform IO Model and Support Membership. The Organization’s retention of Platyform services will be retained in monthly periods at varying degrees of availability and scope per the Organization’s available and selected IO service package for that month (ref. Model Overview #1111 for service package details).
(2) DESCRIPTION OF SERVICES. The Organization’s Platyform IO Model system and service access will begin on first received payment of and corresponding activation of the Organization’s dedicated “Platyform IO Model and Support Membership” subscription product.
This Agreement further clarifies the scope, policies, and provision of the services associated with a “Platyform IO Model” product and membership, while the Model Overview document outlines the availability limits of each service per the selected Membership package in an itemized format.
Upon initiation of the Organization’s “Active Subscription” and throughout the course of its successful activation, Platyform will provide the following services and accesses connected with the deployment, training, and support of both the Organization and its sub-client’s Digital Platform initiatives (collectively, the “Services”):
– (2.1) Access to Platyform Organization Portal consisting of agency.platyform.io, learn.platyform.io, and support.platyform.io. The combination of these sites is cornerstone to Platyform’s facilitation of procedural service requests, providing support communication, managing ticket events, providing the Organization’s staff and sub-clients access to Platyform’s Learning and Training library and all other Service initiation and proceeding touch points. The extent to which each of these Services is available to the Organization through these accesses and portal is dependent on the Organization’s selected IO Model Service Package for that month – the live status of which will be actively reflected throughout the Platyform Organization portal.
– (2.2) Organization Services Available to Platyform Organizations – The following services are available on request through the Platyform Organization Services Portal. Each service is facilitated through a combination of tickets that are submitted and reviewable in the Platyform Organization Support and Ticket Manager system.
- (2.2.3) Component Support – Organizations can request Platyform to add support for a new stack component. This can include, but is not limited to new training material, new stack enhancement tools, new stack templates and more. Platyform will review and respond to each request on a case-by-case basis as to the estimated viability and turnaround times. Platyform does not guarantee the addition of any requested non-supported components. If approved and developed, new Stack Components will be made available to all stack deployments through Platyform’s Stack Enhancement Tool plugin’s remote update process with corresponding training and knowledge base material made available in Platyform’s Organization, Learn, and Library channels alongside all other Supported Stack Components.
- (2.2.4) Stack Upgrades – Organizations can request Platyform to add support for a new stack upgrade. This can include, but is not limited to new training material, new stack enhancement tools, new stack templates and more. Platyform will review and respond to each request on a case-by-case basis as to the estimated viability and turnaround times. Platyform does not guarantee the addition of any requested stack upgrades. These Stack Upgrades will be made available to all stack deployments through Platyform’s Stack Enhancement Tool plugin’s remote update process with corresponding training and knowledge base material made available in Platyform’s Organization, Learn, and Library channels alongside all other Supported Stack Components.
- (2.2.5) Custom Development Support – Platyform can support Organizations’ custom development initiatives with submission and approval of a “Custom Development Request Form”. Requests will be fulfilled as Tickets in the Support Ticket Manager and posed against the Organization’s support availability for that month. Simple questions regarding Custom Development can be generally discussed in Platyform’s Organization Support portal and on meetings per the Organization’s monthly service, but these channels are not subject to official review or reports without a submitted Form and Support Ticket.
- (2.2.6) Platform Testing – Organizations can request Platyform to review and test any Digital Platform they represent. This can include, but is not limited to functionality testing, performance testing, best practice implementation review, UX testing, and more. In the case of testing live eCommerce processes, Platyform will use its own payment method for transactions up to $5.00. Test scenario pricing can be accomplished via provided coupon codes or test products. Transactions that must occur above the five dollar (USD) threshold must be facilitated with a provided card or appropriate payment method. Platyform will review and respond to platform testing requests on a case-by-case basis. Platyform will always provide a report post-testing, however, Platyform cannot guarantee a preferential analysis or solution to all issues that are diagnosed and/or addressed through this service. Proposed solutions may also include the need to submit additional Support Tickets.
- (2.2.7) New Stack Deployments – Organizations can request Platyform to deploy and customize IO model versions of its stack templates and associated technologies. The full and current assortment of this library is reviewable at stacks.platyform.io. The available status of these stack technologies will be reflected for logged in Organization users when viewing the library. Organizations are not eligible to deploy Platyform Network models under their Organization’s membership.
Platyform will review and respond to new stack deployment requests on a case-by-case basis. On approval, all stack deployments and transfers will be performed by a Platyform Representative utilizing various combinations of third-party migration plugins licensed to Platyform. The Organization understands and agrees this will require certain site and system accesses that must be provided to Platyform for each request. Once successfully deployed, Platyform will remove its migration plugins and corresponding licensing from the newly deployed site. The Organization will then be provided the appropriate administrator credentials to take over the site and can begin customizing and incorporating the newly deployed site into its support and ticket requests.
- (2.2.8) New “Project Care Plan” and Scope Assistance – Similar to a “Patient Care Plan” in the medical industry, Platyform adopts a Project Care Plan (PCP) approach for effectively retaining and communicating best practice implementation through various organizational layers and customer touch points. Organizations participating at the Advanced Support Membership levels are eligible to request new PCPs for their clients. Project Care Plans will position a series of tickets through the ticket manager that effectively: audit – to identify pros and cons with existing approaches and/or proposals; report – list of issues and proposed solutions; and initiate – approved solutions and workflows. The timeline of facilitating a PCP process is provided on a case-by-case basis. Additionally, the quantity of submitted support tickets necessary to complete the PCP process is variable to the size, scope, and scale of each Project a PCP is requested for.
– (2.3) Access to Platyform Stack Resources will be provided to the Organization and its sites including stack templates, unlimited installations and site licensing for the Platyform Stack Enhancement Tools plugin (w/ associated Organization White Labeling, Custom Support Routing, and Remote Update features w/ active license), training libraries and knowledge base materials, and more. The present availability of this entire library will be made available and navigable at stacks.platyform.io. Platyform is available to deploy, manage, and support these resources across the Organization and their sites at varying capacities depending on the Organization’s monthly selected service package listed in the Model Overview #1111 document and per the terms, policies, and procedures defined in this Agreement.
– (2.4) System and Development Support for all the Organization’s accounts. This support is available to be facilitated through Platyform’s agency service request portal (agency.platyform.io); Platyform’s Support and Ticket Portal (support.platyform.io); and via calls scheduled during the Organization’s agency time slot(s) or on additionally requested calls. the Organization is not restricted in the number of sites it seeks support for in any service package, however, the selected IO Model service package for that month will dictate the extent of Platyform’s scope and availability to manage these requests for the duration of that month’s selected service package.
- (2.4.1) Pre-Scheduled Time Slot Meetings – Platyform provides time slots available in 45-min slots Monday – Friday. The Organization’s selected monthly support level will establish the overall scheduling availability and possible topic and category limits associated with the Organization’s monthly support level (ref. Model Overview #1111).
- (2.4.2) Additional Meeting Requests – Additional Meeting Requests are provided at the availability established in the Organization’s monthly support level and facilitated through the same slot scheduling and calendar policies as the pre-scheduled slots described in sub-section 2.4.1 above. Additional Meeting Requests are subject to topic and category limits associated with the Organization’s monthly support level (ref. Model Overview #1111).
- (2.4.3) Support Portal Turnaround Times – Platyform attempts to review and initially respond to all service and support requests within two business days, however, Platyform is not able to guarantee turnaround times for individual support and/or service requests. All service and ticket requests will be handled on a case-by-case basis with timelines communicated in the appropriate communications channels.
– (2.5) Organization Strategy and Procedural Support including sub-client scope assistance, one-on-one component training (Dedicated Training Assistance), platform testing, Site calls, sales material support, agency suite stack customization, and more will be provided by Platyform to the Organization and facilitated via the agency.platyform.io site. Organization Services will be afforded the same scope of availability allotted to System and Development Support and per the selected monthly service package.
– (2.6) Definition of CaaS Service Scope and Limitations. In fulfillment of its Services, Platyform utilizes a consultancy-as-a-service (CaaS) model that bills agencies on a monthly flat rate basis for the provision of active development, training, and support services along with Accesses to various Platyform training and technology resources according to the Organization’s selected support level for that month. To accomplish this Platyform requires that all Organizations, supported Sites, and development projects utilize “Platyform Stack Approved” plugins, software suites and additionally adopt “Platyform Best Practices” according to the trainings and knowledge base material Platyform curates and provides at learn.platyform.io and through its various support channels.
- (2.6.1) “Stack Supported Component” and “Platyform Best Practice” Policies – Under the CaaS model, Platyform agrees to actively manage and support the Organization and its initiatives that utilize “Stack Supported Components”. the Organization acknowledges and agrees that ticket and service requests Platyform deems do not utilize “Stack Supported Components” and/or do not represent “Platyform Best Practices” are liable to be handled by Platyform at its discretion. This may include but is not limited to dismissal of the request and/or ticket.
- (2.6.2) Custom Development Policies – In the event of requests for new developments and functionality in the Digital Platform, Platyform will provide “proposed development timelines” for each request as it relates to the ability to be rapidly executed via the “Platyform Stack Approved” components list. Any development request that Platyform considers deviating too far from the ability to be accomplished with “Platyform Stack Approved” software solutions and/or abide by “Platyform Best Practices” will be provided a custom-quote and/or timeline for its execution, though Platyform reserves the right to completely decline these requests. Alternatively, the Organization may request a Platyform representative to participate with an external development team to consult on best practice implementations. Services incorporating custom development may all be accessed via their associated requests in the Platyform Organization Services Portal.
– (2.7) IO Model Specific Definitions and Limitations – In relation to Platyform’s other CaaS offering models (Agency, Network, and Exchange) Platyform IO Models are designed for organization-specific, direct-to-customer fulfillment. IO models are offered in direct contrast to Platyform Network models that are designed to facilitate multiple organizations and various layers of fulfillment through a singular digital platform.
Platyform IO Models MAY NOT assume nor represent Platyform Network models under this Agreement. Platyform Network Models are considered “Organizations” in and of themselves and are only available for their singular deployment and on case-specific pricing arrangements. A new Platyform Network Model would need to be agreed to and initiated independently of this Agreement for each new Platyform Network Model. Referral commissions and/or reduced rated are negotiable for each new Platyform Network Model an Organization refers to Platyform.
(3) PAYMENT FOR SERVICES. In consideration of the services to be performed by Platyform, the Organization agrees to compensate Platyform for the services rendered as follows:
The Organization will sign up for its dedicated Platyform IO Model and associated Subscription product on platyform.io (payment options and policies explained in section 3.1 below). The Organization’s specific instance of this digital membership product and corresponding link will have been provided to the Organization by a Platyform Representative.
The Platyform IO Model Plan bills at the rate set in the “Proposal” and displayed on the “Signup” page (paid upfront each month). The Organization’s specific IO Model and Membership will begin on the date of the first received payment and effective activation of its subscription product on platyform.io. After the initial commitment period is met, various options to renew, reduce, or terminate the Platyform IO Model Membership will become available as newly selectable variations inside of the Organization’s subscription product.
It is the member’s responsibility to manage their monthly subscription. Each month Platyform will assume a continuance of last month’s selected service tier unless a change is made to the account on Platyform.io either directly or via communication to a Platyform Representative.
– (3.1) Payment Options, Grace Period and Delinquency – Payments for the Platyform IO Model can be made via mailed check or auto-renewing credit card. Mailed checks must be confirmed mailed by the renewal date of each month or all services and accesses will be subject to immediate postponement and delinquency procedures until confirmed. Confirmations can be done in the support portal via the direct messaging features or communicated via email to the Organization’s Platyform Representative.
- (3.1.1) Grace Periods and Procedures – Starting from the subscription’s renewal date, a fixed seven (7) day grace period with limited services will be afforded the Organization until the check payment is received. After the seven-day period all services and membership accesses will be considered “terminated” and stopped until payment is received. It is best to send check payments at least one week before the upcoming renewal date to ensure service reduction and/or account termination does not occur. Platyform is not responsible for the effectiveness of the Organization’s selected mail carrier, however, will review claimed payment delays on a case-by-case basis.
For auto-billing credit cards, a grace period of three (3) days with limited services and access will be afforded until a successful payment is initiated through the online-support portal. Grace periods for both check and credit card are, ultimately, subject to Platyform’s discretion. If the renewal date and payment period is regularly missed and/or Platyform becomes concerned of misuse, Platyform may choose to revoke that Organization’s grace period entirely. Contrarily, Platyform may choose to extend an Organization’s grace period that has maintained an upstanding history of timely payments.
- (3.1.2) Refund Policies – Completed purchases are non-refundable if any service has been rendered under the payment’s represented term. Otherwise refunds will be offered for 7 days after billing. Any and all processing expenses incurred will be covered by the member and subtracted from the refunded amount.
– (3.2) Referral Commissions and Network Pricing Opportunities – As a Platyform Organization, the Organization is eligible to be paid referral commissions for successful sales it generates across all other Platyform models (Network, Agency, and Licensee) and in accordance with the variable commission rates and terms established in the separate Platyform Referral and Commission Agreement (optional). Organizations enrolled in this program will additionally be offered special pricing opportunities for creating and maintaining Platyform Networks if they agree to “represent” the Network’s development. Platyform Network opportunities are, however, subject to independent negotiations in alignment with existing Platyform Network Models and ultimately made available at Platyform’s discretion.
– (3.3) Rate Renegotiation Policies – A renegotiation of service tier rates is available every 6 months. This is an opportunity for both Platyform and the Organization to assess each other’s performance and utilization of the membership. Either parties may propose an adjustment to the pricing rates, service tickets, and virtual meetings as can be mutually agreed. Changes will be approved or denied at Platyform’s discretion and implemented in the member’s account.
(4) PAYMENT/LIMITATIONS OF THIRD-PARTY SOFTWARE. the Organization understands and agrees they are to purchase and cover the entire costs of any paid third-party platforms and software (including but not limited to third-party platforms, WordPress themes, and accessory plugins) prior to its use towards Platyform’s Services. the Organization further understands and agrees that while Platyform cannot guarantee the compatibility or corresponding effectiveness of software developed by third parties, Platyform only recommends the incorporation of third-party software that Platyform has tested, integrated, and implemented successfully in past experiences and per its detailing in “Platyform Best Practices” and “Support Stack Components” material.
(5) WEB HOSTING. The Organization understands and agrees that any web hosting services require a separate contract with a web hosting service. the Organization agrees to select a web hosting service which allows Platyform all necessary accesses to the digital platforms that are requested to be supported.
– (5.1) Recommendations, Minimum System Requirements, and Limitations – Platyform strongly recommends a combination of Digital Ocean (servers) and SpinupWP (server management interface) for all its models. Platyform is much more ready and able to support Digital Platforms and team member designations that use this foundation. While Platyform will do its best to translate its service offerings to combinations of other hosting platform and service providers, as a bare minimum for full scope services, the Organization understands and agrees that their hosting solution will need to be able to readily provide Platyform with the following:
– SSH Access – For advanced development requests (key files are preferred over passwords)(Team member Sudo Accounts are preferred over any form or shared root access)
– SFTP Access – For basic development (key files are preferred over passwords)(Individualized team member accounts are preferred over shared accesses)
– DB Manager Access – Multiple support, development, and operational scenarios could benefit from this access. (While PHPmyAdmin is a viable solution it is not preferred due to security and performance implications. SSH accesses mentioned above should also allow for easy TablePlus connections, which facilitates faster, more secure development and DB access.)
If the Organization nor Site can provide the full list of accesses above, the Organization understands and agrees that Platyform will be significantly limited to perform any custom assessment or service work per the extent of their hosting provider’s own access and limitations. Furthermore, the Organization understands and agrees that any such limitations posed by their pre-existing and/or non-supported server and hosting combinations will not be translated or equated to any form of reduced rate, payment, or expense.
(6) TERM/TERMINATION. This Agreement will remain effective until the Organization’s associated subscription product and corresponding membership becomes deemed “terminated” (ref. section 6.1.3).
Upon completion of the 4-month commitment the Organization will be provided the following month-to-month options to switch amongst according to the Organization’s desired level of Service for the upcoming month:
1) Continue Advanced Support
2) Intermediate Support
3) Basic Support
4) Plugin Only Support
Detailed breakdowns of the corresponding access and service availability for each continuing support plan can be referenced in the attached Model Overview #1111 document.
– (6.1) Organization Opted Monthly Selection and Termination Procedures – All Platyform CaaS models incorporate upfront monthly billing for the establishment and continuance of the Organization’s membership and corresponding support levels.
- (6.1.1) Initial Commitment Periods – During the duration of the Commitment Period established in this Agreement, the Organization acknowledges that it is only eligible for the Full Support Model detailed in the Model Overview #1111 document.
- (126.96.36.199) Termination Pre-Commitment Period – Any decision by the Organization to terminate an upcoming payment will not obligate Platyform to provide refund or proration opportunities to the Organization for previous payments. The Services and corresponding membership accesses will continue to be provided and fulfilled through the duration of the last paid month, at which point, if the next monthly period’s payment is not made and/or communicated per the “(3.1.1) Grace Period” policies, the Organization will lose all accesses to Services and membership accesses on the due date of that month’s unpaid payment. Additionally, the Organization’s commitment status and agreement will immediately reset and a new commitment period and agreement will become necessary.
- (6.1.2) Monthly Selection Processes Post-Commitment – Once the Commitment Period has been fulfilled, the Organization will become eligible for the selection of monthly options per the Model Overview #1111 document. These monthly options will become selectable in the Organization’s Platyform Organization portal and/or the platyform.io sales site where the original subscription is established. Whether requested to be implemented by a Platyform Representative or self-serviced by the Organization, this change will be reflected as a “subscription switch” to the Organization’s dedicated Subscription product on platyform.io. The selected monthly option and corresponding payment amount will establish Platyform’s availability of Services for the upcoming month, effectively beginning on the Subscription product’s date of renewal for that month. Auto-billing memberships will automatically bill the correct and updated amount. Organization’s utilizing mailed check payments must be sure to update their payment amount totals accordingly.
- (188.8.131.52) Upgrading Mid-Month – the Organization may upgrade their selected Support Membership in the middle of any post-commitment monthly period by paying the prorated amount for the desired upgrade. The upgrade process must be specifically requested in the Support portal, after which the proration calculation and custom membership option will be facilitated by a Platyform Representative. In most cases a one-time catchup invoice will be created and sent for immediate payment. The upgraded Services will begin as soon as the proration payment is received. This will not reset any monthly period, renewal date, or service limits per the last period, it will simply “prorate” all relevant values.
Practical Example: the Organization selected the Intermediate Service package for the month and is two weeks in. The Organization also used its one (1) additional meeting on Monday of that week. The Organization decides to upgrade to Full Support on Tuesday. the Organization would pay a one time upgrade of apx. $1,250 (½ month Intermediate ($1,250) + ½ month Full ($2,500) – $2,500 paid upfront) and would only get 2 new additional meetings for the remainder of that week. All proceedings and Services for the remainder of that month would utilize the Full Support package.
- (6.1.3) Termination Definitions – If the Organization stops making payments against a membership plan, stops communication regarding payments of that plan per the policies set in “section (3.1.1) Grace Periods”, or communicates specifically to Platyform they are terminating their upcoming payments completely, then the Organization’s Membership will be considered “terminated” upon the due date of the first missed renewal payment or appropriate grace period and implemented technically upon the deactivation of the Organization’s membership subscription on platyform.io.
- (184.108.40.206) Termination Procedures –When an Organization’s Membership is designated to be terminated, Platyform systems will automatically remove all accesses of that Organization’s members, including their staff and Site accounts, from Platyform’s comprehensive collection of resource libraries, service portals, request forms, training materials, Organization sales material, and all other access opportunities that had be provided through the Organization’s Membership.
- (220.127.116.11.1) Platyform Stack Enhancement Tool Deployments – All Platyform Stack Enhancement Tool Plugins that had either been licensed under the Organization’s terminated Membership will fall back to states of “Platyform Default Branding and General Support”. In this state all of the Organization’s white labeled branding and custom support routing links will effectively revert to Platyform’s default branding and support options to a single link to Platyform general support respectively. “Inactive and unlicensed Platyform Stack Enhancer” nags will be displayed in the admin dashboard, while available access to new plugin updates will become unavailable for all deactivated deployments on the Organization’s own and Sites’ Digital Platforms. HOWEVER, all plugin features and Digital Platform processing functionalities unrelated to Organization White-Labeling, Remote Updates, and Custom Support Routing will continue to work at full operational and functional capabilities. This process is additionally detailed in the Model Overview #1111 document.
- (18.104.22.168.2) Reactivation Policies – Organizations that have successfully completed their commitment period will have 6 months from their last missed payment to reactivate their membership and subscription without requiring a new commitment period and Agreement. Terminated Organizations that go beyond 6 months without activated Platyform services, will be required to start a new commitment period and Agreement.
Reactivation of all Services and Accesses described in this Agreement will be provided to Organizations that Platyform deems eligible and occur immediately upon payment and corresponding reactivation of the terminated Membership. Platyform reserves the right to offer special use case and lifetime license opportunities at its discretion, but these offers will be provided on a case-by-case basis and subject to their own independent agreements and contracts.
- (22.214.171.124.3) Suspension Hardship Request – If a customer is experiencing a personal emergency that interferes with their ability to effectively engage in their membership and subscription at any level or period in their initial commitment, they can request a “Suspension Hardship Request Form” be filled out (either by them or a Platyform Representative can fill it out on their behalf). If the Suspension Hardship Request is approved, Platyform will provide an appropriate timeline, unique to that customer’s situation.
Practical Example: An Organization is 2 months complete with its four month commitment when the lead project manager encounters a personal emergency. The Organization submits a Suspension Hardship Request Form detailing the situation, Platyform reviews, and agrees to postpone Services and the remaining 2 month commitment until the Organization’s lead project manager is back which is estimated to take 3 months. However, despite direct communication from Platyform, the Organization does not respond to Platyform for 4 months. Platyform informs the Organization that it must restart its 4 month commitment from the beginning.
(7) RELATIONSHIP OF PARTIES. It is understood by the parties that Platyform and its employees are independent contractors in respect to the Organization, and not employees of the Organization. the Organization will not provide fringe benefits, including health insurance benefits, paid vacation, or any other employee benefit, for the benefit of Platyform.
– (7.1) Platyform Representative Policies – Though Platyform has no “introduction requirement” or visual branding prerequisite for its Representatives regarding Organization and Site communication, Platyform and its personnel will not be misrepresented nor improperly introduced under any entity other than those represented in Platyform’s official branding. Offenses to this policy either flagrant or reported are subject to review.
- (7.1.1) Call and Meeting Policies – On calls and during meetings, Platyform representatives may only pose marketing concepts as potential solutions to technical problems. While the viability of custom solutions can be posed and discussed per Platyform policies, Platyform representatives will NOT promise or guarantee custom solutions on phone calls in any form. Custom solutions and service requests posed from calls must go through the appropriate review and ticket approval channels on the Platyform Organization Services Portal for either New Stack Components, New Stack Upgrades, or Custom Development Support.
– (7.2) Organization Policies – All Platyform Organizations are independent entities from Platyform and solely responsible for establishing and maintaining their own business processes as it relates to branding, marketing, internal policies, business procedures, pricing, and clientele. Platyform holds no interest in these decisions, however, Platyform does enforce a series of ethical standards with the brands and messaging that it will work with and represent. At Platyform’s discretion it will not work with Organizations that frequently depict and/or highlight mature content and sexual themes; incorporate excessive and/or extreme use of violence and/or profanity; participate in business malpractice and/or illegal activity; consistently disregard payment schedules and/or make scheduled payments frequently difficult; or solicit/retain high levels of personal information, such as social security numbers, medical records, and other records that come with high additional risk layers of security and compliance. If Platyform suspects any of these policies have been violated, Platyform will review the violation on a case-by-case basis with the possibility that the respective Organization will be terminated from the Organization’s monthly service immediately with no available proration or refund for the remainder of that month’s membership or associated ticket dismissal(s).
– (7.3) “Project Care Plan” Policies – When a new Project Care Plan (PCP) is requested, the requesting Organization understands and agrees that Platyform is not assuming nor establishing any form of contractual responsibility. Platyform approaches all PCP projects as an independent stack technology consultant in direct relation to the Organization. Platyform will assist the Organization with the project’s overall audit/assessment, diagnosis, development timelines, and ongoing maintenance procedures, however, the Organization acknowledges that no promise nor binding agreement is being established between Platyform and the Organization when Platyform provides Project Care Plan services to the Organization under the guidelines of this service and Agreement.
– (7.4) “Against Platform Advice” Policies – Each Organization’s initiatives as they relate to service requests, support communication and ticket events will be logged and monitored. Platyform reserves the right to deny any request on the basis of “Against Platform Advice”. In this situation the Organization will be provided with an “Against Platform Advice (APA)” report that details the specific concern along with appropriate resolution steps to resolve the issue.
– (7.5) Work Delegation and Organization Responsibility – Platyform will provide all necessary resources to facilitate its own service offerings and membership product accesses to the Organization per the terms established in this Agreement.
- (7.5.1) Content – Platyform is not responsible for the creation or population of any kind of content beyond its dependency or requirement for technical review, development, and/or execution as necessitated by Platyform’s Organization and Support services. Content services and assistance provided by Platyform for purposes outside of technical execution is completely up to Platyform’s discretion.
- (7.5.2) Third-Party and Affiliate Licenses – Platyform Organizations are responsible for procuring and managing their own premium plugins, third party platforms, and corresponding licenses as they are deemed necessary for stack initiatives by Platyform. Platyform provides trainings on and directly supports procurement processes and basic-to-advanced operations for most all supported stack components and platforms. However, these third-party tools and interfaces are not controlled nor represented by Platyform in any way and liable to change at any time per each third-party’s own discretion. It is each Organization’s own responsibility to maintain good standing with Platyform’s affiliates, third-party providers, and to seek support with third-party developers if Platyform is unable to support the situation directly through its own platforms and support resources for any reason. Platyform will assist with third-party support per the Organization’s monthly support model and/or Platyform’s own discretion in the situation’s additional implications for Platyform’s suite of trainings and stack technologies.
- (7.5.3) Resources – Platyform is not responsible for the procurement and/or direction of resources beyond the provision of Platyform’s own services to the Organization as detailed in this Agreement. The Organization maintains its own distinct responsibilities to communicate, provide, and manage appropriate resources for its own initiatives outside of this Agreement and agrees to not knowingly submit requests to Platyform that disregard either party’s obligatory positions in this regard. Platyform is, however, responsible for accurately assessing and providing its services in alignment with the assessed capability and resource availability levels of the Organization and its operations.
- (7.5.4) Marketing and Campaign Execution – It is the Organization’s responsibility to manage, retain, and communicate all elements of its own marketing strategy to Platyform. Throughout its Services, Platyform will only pose marketing concepts as they relate to technical solutions and/or as best practice opportunities for defined initiatives. Platyform and its Representatives will only pushback to marketing concepts if they fall out of best practice and/or ethical standards. It is the Organization’s responsibility to ultimately manage and oversee that its marketing initiatives are being fulfilled according to its own interests.
- (7.5.5) Custom Development Initiatives – Platyform can be requested to perform custom developments that will be facilitated as either Stack Upgrade or New Stack Component Organization Services and ticket requests. Platyform will manage these requests on a case-by-case basis and provide timeline estimates according to Platyform’s own resource availability. However, if an Organization would like to engage a custom developer for any reason, Platyform can be requested as a development resource in accordance with the Custom Development Support request service, per the Scheduled Calls and Additional Meetings services, and through posing new questions in the Support portal. All custom developments facilitated and directed by the Platyform team are considered exclusively owned by Platyform. Platyform holds no ownership or controlling interest in custom developments completed by other developers and teams, however. Custom developments the Platyform team assisted with via the Custom Development Support service will additionally be expedited through the Platyform Community Resource Library and made available for sale commissions according to the Terms of Service and commission rates established in the Platyform Community Resource Library at the time of the sale.
– (7.6) Designated Internal Point Person – To help ensure effective communication Platyform requests that an “internal point person(s)” be designated from within the organization’s staff. Platyform will identify the point person as the “account liaison” and ask for their direct accountability and availability ensuring Platyform information is being effectively understood and disseminated throughout the organization’s internal operations.
(8) INTELLECTUAL PROPERTY & WORK PRODUCT OWNERSHIP. Except for Organization Content (defined in section 8.2 below) and in accordance with its CaaS model, Platyform retains rights to all content on Platyform’s platforms and technologies including text, software, scripts, code, designs, graphics, photos, sounds, music, videos, interactive features, articles, sketches, charts, models, animations, and other content that Platyform does not expressly license already (“Content”).
Additionally, Platyform retains full rights and ownership for all Platyform’s self-produced and independently published works that originate in Platyform’s comprehensive “Stack Technology Resources” and are externally deployed/facilitated to the Organization, including but not limited to: Stack Templates, Stack Tools, Stack Enhancements, Training and Learning material, Platyform Representatives’ Support communication, and all other Platyform-produced works not expressly described in these Terms.
– (8.1) Organization Access to Platyform Stack Technology – Platyform’s entire collection of IO stack enhancement technology, trainings, and other “Platyform Stack Technology and Components” is made available to the Organization through its active IO Model membership and development/support plan(s). This Access is variable to the monthly support package selected and as outlined in the Model Overview #1111.
- (8.1.1) Limitations and Usage Policies – All Platyform Services will be facilitated through Platyform’s own designated procedures and channels. Outside of specific usage rights granted to the Organization by Platyform, the Organization agrees to not use, copy, edit, translate, display, distribute, download, transmit, sell, create derivative works of (further defined in section 126.96.36.199), or in any way exploit any Content, including Organization Content (unless it is the Organization’s own Organization Content that has been appropriately submitted and posted on its own platforms), without Platyform’s prior written consent. Unauthorized use of the Content may constitute a breach of copyright, trademark, or other intellectual property laws and may subject you to criminal or civil charges and penalties.
- (188.8.131.52) Derivative Works Definition & Policies – Platyform acknowledges that many Organizations will use Platyform trainings, constructs, and concepts to base and formalize their own training, offerings, and developments to their Sites. Platyform does not consider any form of training material, Stack Enhancement, or conceptual model an Organization uses as the basis for training or direct fulfillment of its Site or otherwise related Platyform Stack initiative to be a “derivative work”.
Derivative Works considered a breach of this Agreement include unapproved Content that is repositioned by the Organization for commercial sale and/or directed marketing and in what Platyform feels is in competitive alignment and/or “Against Best Practice” with Platyform’s existing trainings, published concepts, and product offerings.
– (8.2) Organization Content – Any copyrightable works, ideas, discoveries, inventions, patents, products, or other information developed and/or directed by the Organization outside of Platyform services (see 8.2.1 Origination Policies below) and in direct connection with its own Digital Platform shall be considered by Platyform to be the exclusive property of the Organization/ Upon request, Platyform shall sign all documents necessary to confirm or perfect the exclusive ownership of the Organization to its own collection of work and/or proprietary organizational information, to Platyform’s best understanding of the work in question’s ownership.
- (8.2.1) Origination Policies – If the Organization provides the resources necessary to direct and compose the development of a new Stack Enhancement, that Stack Enhancement is considered to have originated with the Organization. All developments, tools, content, and specialized customizations the Organization originates are effectively considered Organization Content. All Stack Tools, Enhancements, and other technologies Platyform originates are considered to be exclusively Platyform’s.
- (184.108.40.206) Platyform Custom Development Support Service Requests – Platyform is available to assist and consult on the creation of custom developments through the opportunities and procedures described in “Custom Development Initiatives”. Assistance provided by Platyform through the specified processes will not imply any form of ownership position. However, a “Custom Development Request Form” will be made available by Platyform to the Organization for appropriate tracking and Support Ticket management. Custom Development Assistance services can be terminated at Platyform’s discretion, of which an “Against Platform Advice (APA)” will be filed and made available to the Organization’s account.
- (8.2.2) Publishing on Platyform Community Libraries – Any custom stack development that originates with the Organization can be submitted for publishing and associated sale on Platyform Community sites. However, all interests and policies thereof are guided by Platyform Community’s own separate Terms and Agreements.
– (8.3) White Labeling Opportunities – Platyform retains full discretion over all opportunities afforded Organizations to “white label” Platyform’s Content and Intellectual Property not defined as Organization Content and/or directly afforded through the Platyform Stack Enhancement Tool’s Relay Licensing System© (ref. 8.3.1 below). The Organization understands and agrees that no expressly labeled and/or branded “Platyform” Content will be re-labeled or re-branded in its deployment on either the Organization’s own sites. While the Organization may opt to author its own custom plugins and stack developments that Platyform holds no interest in when directly deployed, the Organization understands and agrees that seeking to publish custom works on Platyform Community systems will be subject to formatting, crediting, and labeling guidelines separately detailed in the Platyform Community Terms of Service Agreement.
- (8.3.1) Platyform Stack Enhancement Tool White Labeling and Support Routing – Organizations that maintain an active membership of any status in regard to their dedicated subscription product on platyform.io will be provided the opportunity to white label any instance of the Stack Enhancement Tool’s deployment that is successfully licensed under the directions provided in the plugin’s interface. When white-labeled the plugin’s name as it appears in the WordPress Sidebar will be replaced with the Organization’s (i.e., “Platyform” appears as “the Organization”), and all brand imagery as it relates to the Support pages inside of the plugin will be replaced with the Organization’s own brand imagery (more information in the Model Overview #1111 document). Additionally, when successfully licensed, all sub-licensed sites under the Organization’s license will further facilitate custom support options and link routing to the Organization’s dedicated Organization Suite, instead of Platyform’s default support channels.The Organization understands and agrees that all Organization White Labeling and Support Routing functionality is dependent on successful license activation of their Organization Membership through the Relay Licensing System© and subject to “fallback behavior” as specified in the “Termination Procedures sub-section 220.127.116.11 of this Agreement when a deployment becomes effectively unlicensed.
Practical Example: the Organization submits a Stack Upgrade Request to build a new Gamipress to Memberium integration. Platyform approves the request and builds the integration in 3 days time. The integration is officially announced and made available to all licensed Platyform Stack Deployments via a remote update procedure in each site’s WordPress admin backend. In this scenario, Platyform LLC exclusively owns the new “Stack Enhancement” and can market, offer, and deploy it as an available “Stack Enhancement Tool” to its entire CaaS base for use in their own Digital Platforms. However, Platyform cannot offer nor present the “new Gamipress Stack Enhancement” as anything more than an available, generic, technical functionality. All marketing agenda, performance metrics, and industry-coinage regarding the Organization’s own deployment of that function would be considered a part of the Organization’s own proprietary intellectual property and Organization Content.
(9) CONFIDENTIALITY. Platyform will not at any time or in any manner, either directly or indirectly, use for the personal benefit of Platyform, or divulge, disclose, or communicate in any manner any information that is proprietary to the Organization. Platyform will protect such information and treat it as strictly confidential. This provision shall continue to be effective after the termination of this Agreement.
(10) EMPLOYEES. Platyform’s employees, if any, who perform services for the Organization under this Agreement shall also be bound by the provisions of this Agreement. At the request of the Organization, Platyform shall provide adequate evidence that such persons are Platyform’s employees.
However, Platyform and its employees, if any, are allowed to use in their respective portfolios, the Organization’s branding as well as services performed for the Organization that do not infringe upon said proprietary information above both during and after the duration of this Agreement.
(11) ASSIGNMENT. Platyform’s obligations under this Agreement may not be assigned or transferred to any other person, firm, or corporation without the prior written consent of both the Organization and Platyform.
(12) ENTIRE AGREEMENT. This Agreement (#1111) and Model Overview #1111 contains the entire agreement of the parties, and there are no other promises or conditions in any other agreement whether oral or written. Any additional agreements that are mentioned in this Agreement are understood to be unique and independent agreements requiring their own direct approval and initiation: Platyform Community Terms and Conditions for submitting new Stack Templates, Enhancements, and Tools to the Platyform Community site and corresponding payouts; Platyform Referral and Commission Agreement for establishing commission payouts and standards when the Organization refers business to Platyform; and additional independent Agreements for managing case-by-case opportunities and promotional scenarios as they relate to Platyform, the Organization, and other involved parties in those independent scenarios.
(13) SEVERABILITY. If any provision of this Agreement shall be held to be invalid or unenforceable for any reason, the remaining provisions shall continue to be valid and enforceable. If a court finds that any provision of this Agreement is invalid or unenforceable, but that by limiting such provision it would become valid and enforceable, then such provision shall be deemed to be written, construed, and enforced as so limited.
(14) AMENDMENT. Platyform is free to make amendments, waivers, and/or discharges of any provision of this Agreement that shall be effective against all Organizations per the terms further detailed in this section. Organizations will be appropriately notified of any and all changes through the policies and procedures outlined below.
– (14.1) Amendment Procedures and Organization Protections – All updates to this Agreement will be logged and maintained for historical reference in section (18) REVISIONS of this Agreement. Platyform will not make any amendment to this Agreement that is in any way exclusive to or directed at a specific Organization or segment of Organizations. Any such initiative by Platyform to establish an agency-specific, or otherwise exclusive agreement is allowable via its own specific arrangement and independent agreement at Platyform’s discretion.
- (14.1.1) “Update To Agreement” Notices – Any and all updates to the Agreement will be communicated to all Organizations via emails delivered to account owners with included information detailing the change(s). Updates deemed by Platyform to pose significant change(s) to the current version of the Agreement will be additionally communicated via notices and action-required prompts in the Platyform Organization Services and/or Support portals, and/or other communication channels as Platyform deems appropriate.
- (14.1.2) Timelines and Proceedings – Every update to the Agreement will be communicated 30 days before taking effect. This allows every Organization an opportunity to retain services under the Agreement version for the month they had last paid, while providing adequate time to discuss any concerns and/or feedback regarding the updated Agreement. When the next month’s renewal order is paid by the Organization, any and all new terms and revisions established in the new Agreement version will be considered acknowledged and agreed to per the Organization’s continued use of services and/or dismissal of action-required prompts.
(15) NOTICES. Any notice required to be given pursuant to this Agreement shall be provided in email, actively embedded in the Platyform Portals, and/or in writing and mailed by certified or registered mail, to the Organization membership’s billing address and/or portal account as Platyform deems appropriate.
(16) APPLICABLE LAW. This Agreement shall be governed by the laws of the State of Colorado.
(17) IDENTIFICATION AND ENFORCEMENT. This Agreement is considered binding and enforceable to the individual and any associated business entity entered into the “Billing Details” fields of the Organization’s dedicated “Platyform IO Model and Support Membership” subscription product. This is the first name, last name, signature, organization name, address, email, and phone information initially submitted at checkout.
– (17.1) Policies and Update Procedures – Each monthly renewal the individual represented in the Organization’s “Billing Details” will be recognized as the responsible and enforceable individual for that monthly period. If this information needs to change at any time the Organization agrees to communicate this change to Platyform appropriately, in a timely manner, and with accurate information. If Platyform becomes aware that the individual and/or business entered in the membership’s “Billing Details” is no longer accurate or relevant to the entity being serviced, Platyform reserves the right to suspend any and all services and/or access at that time until correct information can be provided and appropriately updated with a relevant and enforceable individual and/or business entity in fulfillment with the establishments of this Agreement.
(18) REVISIONS. This Agreement maintains a version log and revision history, updated as appropriate with each revision, and made available in the section below.
#1111-2 (Released: June 16, 2022) –
- Removed “Non-Compete” section as irrelevant
#1111-1 (Released: May. 20, 2022) –
– Initial Version