Legal & licensing.
Draft documents — qualified legal review required before publication.
REVIEW REQUIRED: These drafts are not approved commercial agreements. Checkout remains blocked until the applicable legal versions have been reviewed and approved. No purchase acceptance is collected in this preview.
General Terms and Conditions
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. TFAST Digital Agency proposes to supply the software, licence and services described in a written order. A software licence, support entitlement, hosting service and custom development engagement are separate commitments. The order should identify the customer organization, product, licence, permitted deployment, currency, taxes and deliverables. No licence or download entitlement arises from an unverified payment or browser success screen. Third-party services require their own accounts and terms. Before publication, legal review must settle the contracting entity, applicable law, dispute procedure, mandatory consumer rights and the relationship between these terms and each product agreement.
Regular License Agreement
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. The proposed FinCore Regular licence costs USD 199 once for one licensed organization operating its own FinCore system. The customer may customize the purchased source and use its own branding and domain within the agreed licence. The order must identify the organization and permitted production deployment; appropriate development and staging environments are permitted. Installation documentation, a licence certificate and eligible downloads are included once the release is supplied. Installation, hosting, migration and custom development may be charged separately. Unauthorized source resale, redistribution, sublicensing or sale of modified standalone copies is prohibited. Ordinary SACCO, lending and financial-service charges are not software-access charges. Support and update periods must be specified separately from perpetual usage rights. Third-party and open-source licences remain applicable.
Extended License Agreement
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. The proposed FinCore Extended licence costs USD 799 once and includes the Regular capabilities plus permission to charge third parties for access to one licensed hosted end product. It permits customer branding, a customer-owned domain and source customization within that product. It does not grant unlimited installations, source redistribution, sublicensing or sale of modified standalone software copies. Identify the licensed organization and production deployment in the order; appropriate development and staging environments are permitted. Technical documentation, licence management and eligible releases are included when available. Define the Extended support and update periods in the final agreement; their expiry must not automatically terminate perpetual usage rights. Ordinary financial-service charges are distinct from charging for software access.
Custom Development Agreement
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. The Custom plan is a quoted implementation and development service rather than an instant source-code purchase. An approved statement of work must identify modules, workflows, reports, integrations, branding, domain/server/database configuration, installation, testing and deployment. Migration, training and third-party charges require explicit scope. Record milestones, acceptance criteria, customer responsibilities and production handover. Include twelve months of technical maintenance starting on the agreed production handover date. This covers corrective maintenance, applicable security fixes and compatibility work within the agreed scope. New modules, unrelated features, major redesigns, hosting and third-party fees are not automatically included. Offer a maintenance renewal after that period; maintenance expiry must not automatically disable a perpetual licence.
Refund Policy
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. A refund policy must be approved before commercial checkout opens. Product descriptions, delivery method, installation requirements and licence scope should be clear before payment. Customers should report payment duplication, missing delivery or a material software issue with the order reference and relevant details. Staff must investigate against the accepted agreement and applicable mandatory rights. Do not delete invoices, payment events or customer financial records when processing a refund or chargeback. Any entitlement revocation must be justified and audited under the final policy. No blanket no-refund rule, fixed deadline or eligibility promise is established by this draft; legal review and the owner must determine these terms.
Privacy Policy
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. The proposed marketplace processes account/contact information, billing and order records, legal acceptance, licence and download activity, support messages and quotation details. Payment details should be handled by the selected provider; do not store card credentials in this application. Access should be limited to authorized personnel and necessary service providers. Define the actual hosting locations, processors, lawful grounds, retention periods, international transfers, rights request process and incident contact before publication. Minimize sensitive information in support attachments and audit logs. This local preview is not a statement that production processing or compliance registration has been completed. Refer questions to the published TFAST business contact while the final notice is prepared.
Data Processing Terms
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. A software download alone does not establish that TFAST hosts or processes the customer institution’s operational financial data. For a hosted or managed engagement, a signed processing schedule should identify the parties’ roles, purposes, data categories, data subjects, duration, hosting locations and approved subprocessors. Establish documented instructions, access controls, confidentiality, incident coordination, assistance with rights requests, deletion/return obligations and audit arrangements. The customer must authorize any migration or production access. Do not upload live member financial records to an illustrative demo or local marketplace support ticket. Applicable legal requirements and the actual service architecture need qualified review before this document is approved.
Software Support Policy
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. Product support is linked to the actual purchased licence and published support entitlement. Tickets should identify the product, order, affected version and a reproducible issue without disclosing secrets or unrelated personal data. Support may cover installation guidance, licensing, downloads, bugs and documented features according to the agreed plan. It does not automatically include unlimited custom development, unrelated integrations or a guaranteed response time. Regular and Extended support duration, channels, working hours and escalation targets remain to be approved. A Custom engagement includes twelve months of scoped maintenance from production handover. Staff should record eligibility and resolution history; expired support must not itself destroy customer data or disable a perpetual licence.
Software Updates Policy
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. Each published release should identify its version, date, compatibility, changes, package checksum, signature and eligible customers. Security fixes and major feature upgrades may have different entitlements. Customers must review requirements, back up their deployment and plan database migrations before installing updates. Do not blindly overwrite customized files. Releases should include a rollback or recovery plan, and support must clarify how customizations affect installation. Define applicable security-update access and upgrade periods in the final product terms; no unlimited future-feature entitlement is created by this draft. Deprecation and discontinued product notices should explain the effect on support and updates separately from perpetual usage rights.
Intellectual Property Policy
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. TFAST and applicable third-party licensors retain rights in software and materials except as expressly granted by a licence or signed project agreement. A customer may use its own name, branding and domain and customize source within the purchased licence. These permissions do not authorize source resale, redistribution, sublicensing or marketing modified copies as a separate standalone product. Preserve third-party copyright notices and comply with open-source obligations. A Custom project must define ownership and permitted use of newly developed work, pre-existing components and customer materials in writing. Publishing a customer project or testimonial requires permission. A signed licence is evidence of entitlement, not a claim that editable source can be made impossible to copy.
Acceptable Use Policy
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. Do not use marketplace accounts, hosted services, demos or downloads to access another customer’s records, bypass payment or authorization, redistribute restricted packages, upload malicious content or interfere with availability. Public demos must contain only appropriate test data; do not upload real financial, patient or student records. Security reports should avoid disclosure of other users’ private information. Any response to abuse must be proportionate and documented under the final agreement. A licence dispute must never trigger deletion, encryption, corruption or alteration of customer financial data. The owner and legal reviewer must define notice, appeal and service-restriction procedures before publication.
Disclaimer and Limitation of Liability
Version 1 · draft · Review required
REVIEW DRAFT — NOT AN ACCEPTED CONTRACT. Software suitability depends on verified features, supported versions, deployment configuration and the customer’s requirements. Documentation descriptions do not establish regulatory certification, a security guarantee, uninterrupted operation or a guaranteed commercial result. Customers should test financial calculations, access controls, backups and integrations before production use. Responsibilities for hosting, infrastructure, third-party services and operational data must be allocated in the final agreement. Any warranty, limitation, exclusion, indemnity or liability cap must be expressly drafted and reviewed for the applicable transaction and mandatory law. This draft sets no monetary liability cap and does not attempt to exclude rights that cannot lawfully be excluded.