Privacy policy · Cookie policy · Terms of service · Terms and conditions · Capture desk
Part A. Parties, interpretation and field of contract
A1. Contracting entity
These terms and conditions (“Conditions”) govern the supply of services by AVA INTERACTIVE LTD (“the Company”, “we”, “us”) of 61 Bridge Street, Kington, United Kingdom, HR5 3DJ, to the business customer identified in a statement of work, purchase order accepted by the Company, or other written engagement (“the Client”). Together the Company and the Client are the parties. The public website at avainteractive.mobi and the telephone number +44 7411 526199 are contact channels, not additional contracting entities. Notices in writing may be sent to network@avainteractive.mobi and to the Kington postal address. These Conditions apply to messaging platform development, communication app development, group chat software, instant communication platform work, private messaging application design and build, video chat app development, voice communication software, team messaging platform work, social messaging application work, and other communication technology solutions described in the statement of work. They apply to discovery, design, engineering, documentation, deployment assistance, training and support to the extent purchased. They do not apply to consumer retail of a mass-market chat application sold by the Company to the general public, because that is not the Company’s ordinary model.
A2. Hierarchy of documents
If there is a conflict, the following order of precedence applies: (1) a deed or variation signed by both parties; (2) the statement of work including any data processing schedule, security schedule and acceptance scenes; (3) these Conditions; (4) the website terms of service; (5) marketing pages on avainteractive.mobi. A purchase order issued by the Client is a request to contract on these Conditions. Additional terms printed on a purchase order do not apply unless the Company expressly accepts them in writing. Headings are for convenience. References to statutes include amendments. “Including” means including without limitation. “Business day” means a day other than Saturday, Sunday or a public holiday in England when banks in London are open. Time is GMT or BST as applicable in the United Kingdom. “Writing” includes email to the addresses nominated in the statement of work.
A3. Definitions used throughout
“Capture note” means the documented understanding of weak signals, noise to be filtered and patterns to be made visible, including workshop records. “Deliverable” means software, configuration, documentation, designs or other work product identified as a deliverable. “Background IP” means intellectual property owned or licensed by a party independently of the engagement. “Foreground IP” means intellectual property created by the Company in the course of the services, excluding Background IP and excluding third-party components. “Platform” means the messaging or communication system to be developed or adapted. “End users” means individuals who use the Platform other than the Client’s project staff. “Personal data”, “controller”, “processor”, “processing” and “personal data breach” have the meanings in UK GDPR. “Online Safety Duties” means duties under the Online Safety Act 2023 and related Ofcom codes to the extent they apply to the Client as a provider of a regulated service. “Field lock” means a recorded decision that is treated as stable for the purpose of estimating and building. “Wing trace” means a secondary outcome or module identified in the pattern sheet. “Statement of work” includes any proposal accepted by both parties that identifies scope, fees and timetable.
A4. Entire agreement and reliance
These Conditions and the statement of work constitute the entire agreement and supersede prior discussions, including conversations at the Kington desk, website copy about nocturnal signal capture, and illustrative portfolio traces. Each party acknowledges it has not relied on any representation not set out in the contractual documents, except that this does not exclude liability for fraud. The Client acknowledges that messaging products are socio-technical systems: adoption depends on the Client’s culture, moderation, legal basis and operational discipline as much as on software. The Company does not warrant that any Platform will achieve a particular volume of messages, a particular app-store ranking, or a particular reduction in email. Those are hoped-for patterns, not guaranteed captures.
Part B. Scope of communication technology services
B1. Messaging platform development
Where the statement of work includes messaging platform development, the Company shall design and build, to the contracted scope, facilities for conversations between authorised users, which may include one-to-one threads, rooms, presence, delivery states, attachments, search, and administration. The Company shall document the room model, identity model and delivery semantics as field notes. Unless expressly purchased, the following are excluded: global content moderation as an ongoing managed service, twenty-four-hour live operations, interconnection with every third-party chat network, and migration of unlawful archives. The Client shall supply identity sources, branding, legal bases for processing, and a named product owner with authority to pin field locks. Instant communication platform work is a subset in which delivery latency targets are stated numerically in the statement of work; if they are not stated, the Company shall build to a professional standard for ordinary organisational chat, not to a high-frequency trading standard.
B2. Communication app development
Where communication app development is purchased, the Company shall produce client software for the platforms named, typically iOS, Android and or web. Store listings, privacy nutrition labels, screenshots and review-response labour are included only if listed. The Client is the developer of record on store accounts unless otherwise agreed. The Client shall provide certificates, merchant details and responses to store questions within a reasonable time. Rejection by an app store is not a breach by the Company if the rejection arises from the Client’s content, legal posture, or failure to supply materials, or from a change in store rules after a field lock. The Company shall make reasonable adjustments to meet documented store requirements that existed at the date of the field lock, within a change budget if the adjustment is material.
B3. Group chat software
Group chat software includes membership, roles, notifications and, where purchased, moderation tools. The Company shall implement the gravity model described in the capture notes so that working rooms can be distinguished from public squares to the extent specified. The Client remains responsible for community standards, staff training, and decisions to suspend users. Mention storms, spam and coordinated abuse cannot be engineered out of existence; they can be made more observable and more controllable. The Company does not warrant the absence of harmful user-generated content.
B4. Private messaging application
Private messaging application work includes a written key and retention story. Marketing language such as “unbreakable privacy” shall not be used unless the statement of work defines the threat model, device assumptions, backup behaviour, screenshot limitations and metadata that remains visible. The Company shall implement the contracted cryptographic posture. The Client shall not represent the product as providing protections that the threat model excludes. If the Client later requests a silent administrative back door that contradicts the documented threat model, the Company may refuse and treat the request as a change that may require re-pricing, delay, and legal review. Lawful interception support, if any, is only implemented where the statement of work and applicable law require it and is documented.
B5. Video chat app development and voice communication software
Video and voice modules are specified with codecs, participant limits, recording rules and a close behaviour. Bandwidth, device performance and third-party media infrastructure affect quality. The Company warrants professional implementation of the contracted media path, not studio-grade quality on every network. Recording is off unless purchased and legally based. The Client shall obtain notices and consents for recording. Emergency calling, like a regulated public safety answering point, is excluded unless expressly designed and licensed. Timed sessions and honest close behaviour, where specified, are part of the Deliverable; circumventing them by the Client after handover is not the Company’s breach.
B6. Team messaging platform and social messaging application
A team messaging platform emphasises organisational memory, search, files and administrative control. A social messaging application emphasises bounded circles and a closeable night if those field locks are pinned. Mixing the two without a documented pattern is a common source of noise. The Company shall build the model purchased, not both unless both are in scope. The Client shall not later demand a public infinite feed as included within a team platform fee.
B7. Related services
Discovery workshops, interface design, protocol selection, infrastructure as code, observability, accessibility remediation, documentation, training, and warranty support are included only as listed. Hosting accounts, domain registration, SMS fees, media-relay fees, certificate fees and store fees are Client costs unless the statement of work says the Company will pass them through at cost plus any agreed handling.
Part C. Formation, change and Client duties
C1. Formation
A contract is formed when the Company accepts a statement of work in writing, or begins work after written instruction that refers to these Conditions, whichever is earlier. Website capture notes are invitations to begin a conversation. Quotations are valid for the period stated or, if none, twenty business days, and assume the facts then known. If a weak signal later reveals a larger pattern, the Company may revise estimates through change control rather than absorb an unbounded scope.
C2. Client duties
The Client shall provide timely decisions, access to stakeholders, lawful sample data, environment credentials, and feedback during agreed windows. Delay in pinning a field lock entitles the Company to adjust timetable and, where staff are held idle, to charge reasonably for the idle window or to reassign staff and restart with a new slot. The Client shall ensure it has a lawful basis for any personal data it supplies, including existing chat archives. The Client shall not require the Company to scrape a third-party private messaging application in breach of that service’s terms or of law. The Client shall nominate a product owner reachable on business days.
C3. Change control
Changes to scope, acceptance scenes, threat model, platforms, languages, integrations or non-functional targets shall be raised in writing. The Company shall describe impact on fee, timetable and risks. Work on the change does not begin until the Client accepts, except that the Company may refuse a change that is unlawful or that would destroy the documented meaning of a privacy promise already made to end users. Minor clarifications that do not alter effort are not changes. A series of minor clarifications that together alter effort may be bundled as a change.
C4. Acceptance
Deliverables are accepted when the Client confirms in writing, or when the acceptance scenes in the statement of work are met, or five business days after delivery if the Client does not reject with specific defects, whichever occurs first. Cosmetic preferences are not defects. A defect is a failure to meet a documented field lock. Partial acceptance of modules is permitted. Use of a Deliverable in production is deemed acceptance of that Deliverable, without prejudice to latent defects notified promptly.
Part D. Fees, tax and payment
Fees are as stated in the statement of work, whether fixed, capped time and materials, or retainer. Unless stated otherwise, fees are exclusive of VAT, which shall be added at the prevailing United Kingdom rate where applicable. Expenses such as travel to a site other than Kington, device purchases requested by the Client, and third-party cloud usage may be billed at cost with evidence. Invoices are payable within fourteen days of the invoice date unless the statement of work states another period. Time is of the essence for payment. Late sums bear interest under the Late Payment of Commercial Debts (Interest) Act 1998 if that Act applies, otherwise at four percent above the Bank of England base rate, together with reasonable recovery costs. The Company may suspend services for overdue sums after written notice of seven days. Suspension is not termination. The Client may not set off disputed sums against unrelated invoices except as English law requires. Milestone fees are earned when the milestone criteria are met, not when the Client’s internal politics delay a launch. If the Client cancels a scheduled workshop inside five business days, the Company may charge a reasonable preparation fee.
Estimates given before a capture sequence is complete are indicative. Fixed prices assume the Client’s existing systems behave as described. Hidden complexity in identity providers, undocumented legacy chat, or app-store policy shifts may trigger change control. The Company does not work on a pure contingency of app-store success. Refunds are not available for time already properly expended. Deposits are non-refundable to the extent of work commenced and costs committed, and otherwise as the statement of work states. Currency is pounds sterling unless stated. International Clients bear their own bank charges. The Company is not a credit provider.
Part E. Intellectual property, open source and residuals
Each party retains its Background IP. Upon payment in full of fees due for a Deliverable, the Company assigns to the Client the Foreground IP in that Deliverable, excluding Background IP, tools, generators, internal field-note templates, and snippets the Company uses across engagements. The Company grants the Client a non-exclusive, perpetual licence to use Company Background IP that is embedded in a paid Deliverable, solely as embedded, not as a standalone toolkit for building unrelated products. The Client grants the Company a licence to use Client materials for the purpose of performing the services. The Company may reuse non-confidential residuals: general skills, generalised architecture patterns for messaging platform development, and anonymised knowledge of what noise looks like in group chat. The Company shall not reuse the Client’s unique business logic, trademarks, or identifiable message content. Third-party and open-source components are licensed on their own terms. The Client shall comply with those terms, including notice files. The Company shall provide a bill of materials of significant components on request at acceptance. Warranty of non-infringement is limited to the Company’s original authorship and does not extend to combinations the Client later makes, to open-source licences chosen jointly, or to protocols the Client mandates.
Until payment in full, Foreground IP remains with the Company and the Client has a limited evaluation licence. If the Client uses unpaid work in production, fees are immediately due. Portfolio use: the Company may describe the type of pattern captured, in anonymised form, unless the statement of work requires silence. Named case studies require the Client’s written permission. Source escrow is not included unless purchased.
Part F. Data protection, security and Online Safety
F1. Roles
For the public website and for the Company’s own sales and accounts, the Company is controller as described in privacy-policy.html. For End-user data inside a Client Platform, the Client is controller and the Company is processor only to the extent the data processing schedule says so. Each party shall comply with UK GDPR and the Data Protection Act 2018 in its role. The processor schedule shall set out subject matter, duration, nature, purpose, types of personal data, categories of data subjects, and the Client’s documented instructions. The Company shall not process End-user content for its own analytics or model training.
F2. Security
The Company shall implement technical and organisational measures appropriate to the risk of the contracted work, taking account of encryption posture, access control, logging, separation of staging and production, and staff confidentiality. Absolute security is not warranted. The Client shall protect credentials issued to it, shall apply updates the Company provides under a support plan, and shall not disable logging required to investigate incidents. Personal data breaches in Company-controlled systems shall be notified to the Client without undue delay if the Company is processor, and to the ICO by the responsible controller as the law requires.
F3. International transfers
If processing involves a transfer from the United Kingdom, the parties shall use a lawful mechanism. The Client is responsible for choosing hosting regions consistent with its promises to End users. The Company shall not quietly relocate production data to another country.
F4. Online Safety Act and illegal content
If the Platform is a regulated user-to-user service, the Client is ordinarily the provider with Online Safety Duties. The Company shall implement safety features that are specified and paid for, such as reporting flows, hashing against known illegal image databases where contracted, age-assurance hooks, or terms-acceptance gates. The Company is not the Client’s nominated safety officer. The Company does not monitor live user content as a managed service unless a separate operations contract is signed. The Client shall not instruct the Company to design a service whose primary purpose is the facilitation of illegal activity. The Company may terminate for unlawful purpose.
F5. Children’s data and age
If the Platform is likely to be accessed by children, the statement of work shall address age-appropriate design, default privacy, and parental tools as required by law and by the Client’s risk appetite. Additional fees apply. The Company does not accept undocumented last-minute conversion of an adult team tool into a children’s social messaging application without change control.
Part G. Warranties, support, third parties and app stores
The Company warrants that services will be performed with reasonable care and skill, consistent with a competent United Kingdom messaging platform development practice. Software Deliverables will, for thirty days after acceptance unless a longer warranty is purchased, materially conform to the field locks. The remedy is re-performance or repair within a reasonable time, or a proportionate refund of the defective portion if repair is impracticable. This warranty does not cover defects caused by Client changes, third-party outages, misuse, unsupported browsers, or End-user devices that fail contracted minimums. Implied terms as to quality and fitness are excluded to the extent permitted, except that nothing affects statutory rights that cannot be excluded in a business-to-business contract under English law.
Support after warranty is only as purchased. Severity definitions, response targets and maintenance windows shall appear in a support schedule if bought. Out-of-hours cover is not implied by the nocturnal visual metaphor of the Company’s brand. Third-party media relays, push gateways, SMS, maps, fonts, stores and identity providers have their own service levels. The Company is not liable for their outages. App-store taxes, review delays and policy changes are third-party risks. The Company shall reasonably assist with a resubmission if a rejection relates to an implementation error by the Company.
Part H. Liability, indemnity and insurance
Nothing in these Conditions limits liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or any other liability which cannot be limited under English law. Subject to that, the Company shall not be liable for loss of profit, revenue, anticipated savings, goodwill, data (except the cost of commercially reasonable restoration from backups the Client ought to have kept), or indirect or consequential loss. The Company’s total aggregate liability arising out of an engagement, whether in contract, tort, misrepresentation or otherwise, shall not exceed the fees paid by the Client to the Company under that engagement in the twelve months preceding the claim, or ten thousand pounds, whichever is greater. The Client shall indemnify the Company against claims by End users, regulators or third parties arising from the Client’s content, moderation decisions, legal bases, representations about encryption, or operation of the Platform after handover, except to the extent caused by the Company’s proven breach of these Conditions. Each party shall maintain insurance appropriate to its business. The Company maintains professional indemnity and public liability at levels it considers proportionate to a Kington studio; certificates may be provided on request. The Client is recommended to maintain cyber insurance if it operates a communication platform.
Part I. Confidentiality, publicity and non-solicitation
Each party shall keep the other’s confidential information secret, using at least reasonable care, and use it only for the engagement, for five years from disclosure or longer for trade secrets. Exceptions: information that is public other than by breach, independently developed, already known, or required to be disclosed by law or court, in which case the disclosing party shall if lawful give notice. Capture notes about the Client’s weak signals are confidential. The Company’s pricing models and internal tools are confidential. Staff introductions do not waive confidentiality. Neither party shall reverse engineer the other’s confidential software except as permitted by law. For twelve months after the engagement, neither party shall solicit the other’s employees who worked directly on the project, except through general advertising not targeted at them. This does not prevent hiring after an unsolicited application. Publicity is limited as in Part E.
Part J. Term, termination and consequences
The engagement continues until completion of the services or until terminated. Either party may terminate for material breach not remedied within thirty days of notice, or immediately if the other becomes insolvent, enters administration, or ceases business. The Company may terminate if the Client insists on an unlawful instruction, fails to pay after suspension notice, or harasses staff. The Client may terminate for convenience on thirty days’ notice if the statement of work allows, paying for work done, committed third-party costs, and a reasonable wind-down. On termination the Company shall deliver paid-for work in its then state, delete or return personal data as processor subject to law, and may retain copies required for legal defence. Licences to unpaid work end. Survival: fees, IP, confidentiality, liability, indemnity, data protection, and governing law.
Part K. Force majeure, assignment, subcontracting
Neither party is liable for delay caused by circumstances beyond reasonable control, including infrastructure failure of a major cloud region, epidemic, change of law that makes performance illegal, or app-store outage, provided the affected party gives notice and mitigates. Payment obligations for work already done are not excused. The Company may subcontract specialist tasks, remaining responsible for the subcontractor’s performance as if its own, and shall impose confidentiality. The Client may not assign the contract without consent, except to an affiliate or as part of a bona fide sale of the business, with notice. The Company may assign to a successor of its practice. These Conditions do not confer rights on third parties under the Contracts (Rights of Third Parties) Act 1999. End users are not third-party beneficiaries.
Part L. Dispute resolution and law
The parties shall attempt in good faith to resolve disputes through the product owner and the Company’s director, then through mediation in England if both agree. Nothing prevents seeking interim injunctive relief to protect intellectual property or confidential information. Subject to that, the courts of England and Wales have exclusive jurisdiction. These Conditions are governed by the law of England and Wales. The United Nations Convention on Contracts for the International Sale of Goods is excluded. If a Client is in Scotland or Northern Ireland, the parties still choose English law and English courts for commercial certainty, unless a mandatory local rule applies to a particular statutory claim.
Part M. General
If a provision is invalid, the remainder continues. Failure to enforce is not a waiver. Variations must be in writing. Counterparts and electronic signatures are valid. Notices are effective on receipt if sent to the nominated email or two business days after posting by first class to 61 Bridge Street, Kington, United Kingdom, HR5 3DJ or the Client’s registered office. Relationship of the parties is independent contractor, not partnership or employment. The Company may work for other clients in communication technology solutions, including those in adjacent sectors, provided confidential information is not misused. Export control and sanctions: the Client warrants it is not a prohibited party and that the Platform will not be supplied in breach of United Kingdom sanctions. Anti-bribery: each party shall comply with the Bribery Act 2010. Modern slavery: each party shall comply with applicable duties. Equality: the Company shall not discriminate in the provision of services contrary to the Equality Act 2010. Accessibility: where the Client requires WCAG conformance to a named level, that is a field lock and is tested against the scenes specified, not against every possible assistive combination in the world. Language of the contract is English. The visual metaphor of ultraviolet capture used in marketing has no legal meaning beyond these Conditions.
Part N. Discovery and capture sequence in contractual form
The Company’s method of Darken, Attract, Observe, Pin, Read and Translate is a professional process, not a mystical rite and not a substitute for the Client’s governance. Darken means reducing the glare of existing tools so that the real conversational thread can be seen; the Client shall permit observation of current tools under confidentiality. Attract means identifying where useful conversation already gathers; the Client shall not insist that a dead channel is the centre of gravity without evidence. Observe means the Company may witness delivery failures, mention weather and device habit; it does not mean covert surveillance of staff beyond what the Client has authority to permit. Pin means field locks are written; the Client shall not treat pins as optional decorations. Read means architecture and threat notes; the Client shall cause its security and legal reviewers to comment within the window. Translate means build and handover. Skipping steps to “just start coding” is a change that increases defect risk and may be refused if it would make acceptance untestable. Workshops may be recorded if both parties agree. Recordings are confidential. The Company may produce a capture note as a Deliverable. If the Client disagrees with the capture note, it shall mark objections promptly; silence followed by a demand to reopen fundamentals during late engineering is change control.
Part O. Identity, directories and federation
Many communication failures begin in identity. The statement of work shall state whether users sign in with passwords, single sign-on, magic links, device credentials, or a mix. The Company is not responsible for the Client’s identity provider outages. Directory synchronisation, deprovisioning on staff exit, and guest access are included only if specified. Federation with external messaging networks is a specialist integration with protocol and policy risk; it is never implied. Presence leakage, last-seen timestamps and read receipts have privacy consequences; their defaults are field locks. The Client shall not later claim that a presence feature was “obviously required” if it was not pinned. Account recovery for a private messaging application can conflict with a high threat model; the chosen recovery story shall be written, including what happens if a device is lost.
Part P. Moderation, trust and safety engineering
Where purchased, the Company shall build reporting buttons, block lists, audit logs for moderator actions, and rate limits. Policies, human moderators, appeals, and relations with law enforcement remain the Client’s. The Company shall not be named as the service’s safety contact unless a separate operations agreement is signed. Hash-matching, classifiers and automated filters have error rates; the Client accepts false positives and false negatives as inherent. The Company does not warrant that illegal content cannot be posted. Rate limits may be tuned after launch as a support task. Moderator tools can themselves process special category data if users report it; the Client must have a basis. Staff of the Company who encounter apparently illegal content during debugging shall be entitled to stop, to preserve evidence as required by law, and to notify the Client. The Client shall not require the Company to operate a bulk interception capability disguised as debugging.
Part Q. Records, retention, deletion and legal hold
Retention timers, export, and deletion are features if specified. Default retention, if unspecified, shall be documented as “indefinite until the Client configures otherwise” or another explicit default; ambiguity is to be avoided because it destroys meaning. Legal hold that freezes deletion for litigation is a Client operational process; the Company shall implement a freeze flag only if purchased. Backups may outlive live deletion for a rotation period; the statement of work shall say so. End-user requests for erasure of messages that also sit in another person’s inbox raise complex balancing; the product behaviour shall be specified rather than left to improvisation by engineers at launch night. The Company is not the Client’s records manager under the Freedom of Information Act unless the Client is a public authority and purchases a specific records module.
Part R. Hosting, environments and handover
The Company may deploy to Client-owned cloud accounts, which is the preferred pattern for a serious Platform, or to Company-managed tenancy if purchased. Access keys shall be rotated at handover. Documentation shall include build instructions, environment variables, and operational runbooks proportionate to the fee. Handover is complete when the Client can deploy or when the Company remains operator under a hosting schedule. The Company is not obliged to provide oral knowledge that was already written. If the Client’s staff decline training that was offered, later dependence on the Company is a support contract, not a defect in the original build. Domain names, TLS, DNS and email authentication records for notifications are Client assets unless registered by the Company as agent.
Part S. Testing, accessibility and performance
Testing includes the acceptance scenes. Automated tests are included to the extent specified. Load testing to a named concurrent-user figure is included only if purchased, with the Client providing realistic fixtures. Accessibility testing against a named WCAG level uses agreed assistive samples; it is not a certification by a third-party auditor unless that auditor is hired. Performance on a congested mobile network cannot be guaranteed globally. The Company shall test on the device matrix listed. Additional devices are change. Internationalisation and right-to-left layout are included only if listed. Time zones in timestamps shall be specified. The Client shall supply translations if multilingual copy is required.
Part T. Employees, contractors and IR35
Personnel supplied by the Company are not Client employees. If legislation on off-payroll working is relevant to a particular individual placed inside the Client’s organisation, the parties shall cooperate on status determination. The default model is that work is done as a contracted service from the Company’s practice, not as a disguised employment. The Client shall not supervise Company staff as if they were employees except for reasonable site rules when on Client premises. Offensive conduct toward Company staff entitles the Company to remove personnel and, if not remedied, to terminate.
Part U. Sector overlays
If the Client is in a regulated sector such as financial services, healthcare, education or public service, additional overlays may apply: records, encryption, residency, and inspection. Those overlays are not included by silence. The Company can implement technical controls that are specified. It does not provide the Client’s regulatory permissions. Clinical safety officers, senior managers under SMCR, or Caldicott guardians remain Client roles. The Company shall not be cited as having “signed off” a clinical or financial risk merely because it wrote software.
Part V. Exit, portability and death of a protocol
On exit, the Client is entitled to paid-for source and data export as specified. Formats shall be reasonable, such as standard database dumps and object storage, not a bespoke eternal schema warranty. If a third-party protocol or library becomes obsolete, replacement is a new engagement. The Company is not obliged to maintain a Platform in perpetuity without a support fee. Escrow, if purchased, shall name the trigger events. Staff who leave the Company are not individually obliged to answer the Client except through surviving corporate support arrangements.
Part W. Ethical use and prohibited purposes
The Company may refuse work whose primary purpose is stalking, non-consensual interception, fraud, or the operation of a service designed to evade United Kingdom criminal law. Dual-use tools such as encrypted private messaging have legitimate uses; refusal is a matter of the Company’s judgement about purpose and Client representations. Misrepresentation of purpose is a material breach. The nocturnal signal metaphor shall not be interpreted as a promise to hide the Client from lawful process.
Part X. Notices to End users and app disclosures
The Client shall publish accurate privacy notices, cookie information, and, where required, store disclosures. The Company may draft technical descriptions as a Deliverable. Legal conclusions are the Client’s. If the Client publishes claims that contradict the threat model, the Company may require correction as a condition of continued support, because such claims create indemnity risk and destroy the meaning of the capture.
Part Y. Benchmarks, references and audits
The Client may audit the Company’s processor controls not more than once per year on reasonable notice, during business hours, subject to confidentiality, and at the Client’s cost, unless a breach has occurred. Audits shall not include fishing through other clients’ field notes. Penetration tests of production require coordination. Public benchmark wars using the Platform as a comparative advertisement against named competitors are not authorised without the Company’s consent if they imply the Company endorses a claim.
Part Z. Miscellaneous commercial realism
Software estimates are professional judgements under uncertainty. Messaging systems touch identity, networks, human behaviour and law. The Company will document assumptions. The Client shall read them. A cheap fee with an unbounded dream of replacing every communication tool in an enterprise is not a field lock. Phasing is encouraged. The address 61 Bridge Street, Kington, United Kingdom, HR5 3DJ is a correspondence address; meetings may be remote. Site visits are scheduled. The brand’s ultraviolet cloth is a visual system, not a physical laboratory to which the Client is entitled access. These Conditions may be updated for new engagements; live engagements keep the version incorporated unless varied. Questions: network@avainteractive.mobi, +44 7411 526199.
AA. Push notifications in legal detail
Push notifications are a frequent source of PECR and product-noise problems. The statement of work shall state whether notifications are transactional, whether marketing pushes will ever be sent, and whether a user can silence a room without leaving it. The Company shall implement permission prompts consistent with the contracted platforms. The Client shall not later convert transactional infrastructure into a marketing cannon without a lawful basis and a product change. Badge counts, lock-screen previews and mention sounds can leak message meaning in physical space; those leakages are to be documented in the threat model of a private messaging application. Delivery of a push is not the same as delivery of a message inside the Platform; semantics shall be written so support staff do not contradict one another. Third-party push gateways process device tokens; their locations shall be listed in the processing schedule. The Company is not liable for a gateway outage. Quiet hours, if purchased, are a product feature, not a legal curfew imposed on End users by the Company. The Client remains responsible for any nuisance claims arising from aggressive default notification settings that the Client insisted upon against the Company’s capture note. Documentation shall include how to rotate certificates before they expire, because expired push certificates are a common operational failure that the Client may misread as a defect in messaging platform development. If the Client’s marketing team demands rich media pushes that expand the threat surface, that demand is change control. The Company shall not hide a marketing SDK inside a team messaging platform under a generic “analytics” label. Signal attracted is timely notice of a human conversation; noise separated is notification frost; pattern documented is a permission and channel model a successor can still read. Fees for designing that model, if not in the original statement of work, are additional. Acceptance scenes shall include a test of mute, a test of mention, and a test of token invalidation. The Client shall supply Apple and Google account access with least privilege. Compromised store credentials are a Client security incident. The Company shall be notified if those credentials may have affected build pipelines. Push is not a substitute for in-app inbox reliability; both paths, if purchased, shall be tested. International roaming, device battery optimisation and user-installed blockers can drop pushes; such drops are not defects. The Company shall document those limitations in the handover cloth so that visible direction is not destroyed by mythical uptime claims.
Further particularisation for Push notifications in legal detail follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
BB. Media handling, codecs and infrastructure costs
Images, voice and video create cost, law and quality problems that text chat does not. The statement of work shall state maximum file sizes, transcoding, thumbnail policy, virus scanning, and whether media lives in the same store as message bodies. The Company shall implement the contracted pipeline. Bandwidth and storage fees from cloud vendors fluctuate; unless a hosting schedule says otherwise, the Client pays them. The Company is not a reseller of infinite media. Voice communication software may use a media relay; geographic placement affects latency and data-protection analysis. Video chat app development may use simulcast or other techniques; those choices are engineering field locks. Recording archives can become a shadow messaging system; if recording is on, retention and access control must be pinned. The Client shall not store illegal content knowingly. If automated scanning is purchased, its limits shall be written. Thumbnails can reveal message content on shared screens; a private messaging application may disable them as a field lock. EXIF stripping, if purchased, is a privacy-preserving pattern. The Company does not warrant that End users cannot circumvent stripping with external cameras. Live location sharing, if requested, is a high-risk feature requiring explicit scope, because it can be misused for harm; the Company may refuse. Stickers, animated media and custom emoji packs are not included unless listed; they expand moderation surface. The Client shall budget for content delivery. Sudden viral load on a social messaging application is not a defect in ordinary team platform sizing. Capacity planning is a purchased activity. The Company’s nocturnal visual references to dust and cloth are not a description of media quality. Quality metrics, if any, shall be numeric. MOS scores are not implied. Echo cancellation on cheap hardware varies. The Client shall specify a device matrix. Additional codecs after a field lock are change. Music streaming rights are not implied by a voice room. The Platform is not a broadcast licence. If the Client wishes to host public events, a different pattern is required. Handover shall include how to rotate media keys if such keys exist. Lost keys can mean lost archives; that consequence shall be explained to the Client before a high-secrecy design is chosen, so meaning is not destroyed by a romantic encryption story.
Further particularisation for Media handling, codecs and infrastructure costs follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
CC. Search, memory and organisational records
Team messaging platforms are often sold as organisational memory. Search quality depends on indexing, permissions and retention. The Company shall implement the contracted search. It does not warrant that every informal joke will be findable years later, nor that search will replace a proper records system. Permissioned search that leaks across rooms is a defect if it violates a field lock; search that is slower than a consumer web engine is not a defect unless a numeric target was pinned. Export for subject-access requests may require a different query path; if the Client is a controller with such duties, the feature must be purchased. eDiscovery holds are not implied. The Client’s administrators can, in many designs, read staff messages; that fact must not be hidden in marketing. If a private corridor is promised inside an otherwise administrative platform, the exception shall be technically real and documented. Deleting a message for myself versus for everyone is a classic ambiguity; the product language shall match the implementation. Quoted replies, threads and forwarded traces can resurrect deleted meaning; the pattern shall be documented. The Company shall not be asked to silently alter historical messages to rewrite a workplace dispute. Integrity of logs may matter in grievances; if so, auditability is a field lock with a fee. Search across voice transcripts requires a transcription vendor; that vendor is a processor to be named. Transcript error rates are accepted. Language support is as listed. The Client shall not assume that slang in a particular United Kingdom region will be perfectly indexed. Emoji and images are often poorly searchable unless additional work is bought. These limitations are part of honest capture, not a failure of care.
Further particularisation for Search, memory and organisational records follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
DD. Accessibility, inclusion and interface language
Communication products that cannot be used by disabled people are incomplete captures of the organisation’s actual staff. Where WCAG is named, the Company shall design against it for the listed scenes. Custom ultraviolet visual systems can harm contrast if misapplied; the product interface, unlike the marketing site, shall meet the contracted contrast. Keyboard access for room lists, focus management for new messages, and captions for video are included only if specified. Captions are not implied by video chat. The Client shall supply a plain-language content style if it wishes to avoid jargon. The Company may use the Client’s brand colours in the product; if those colours fail contrast, the Company shall propose a field lock that preserves brand without destroying readability. Localisation is more than translation; date formats, name order and collation shall be specified for the markets listed. The Company is not liable for offensive translations supplied by the Client. Right-to-left layout is a material change if requested late. Voiceover and talkback testing uses sample devices. Assistive-technology users among End users may still need the Client’s support processes. Inclusion also concerns harassment tools; those are moderation features, not CSS. The marketing site’s nocturnal aesthetic does not dictate that the product must be unreadable dark mode; product theming is a separate Deliverable.
Further particularisation for Accessibility, inclusion and interface language follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
EE. Commercial agents, introductions and non-circumvention
If an introducer brings a Client to AVA INTERACTIVE LTD, any introducer fee is a separate contract. These Conditions do not make the introducer a party to the development contract. The Client shall not use materials supplied in a paid discovery to solicit a competitor to reproduce the same unique business logic at a lower fee while representing it as independent invention, without prejudice to the competitor’s right to build generic chat. Generic patterns of messaging platform development are residuals. Unique workflow that was documented as Foreground remains protected as IP and confidential information. The Company shall not poach the Client’s named End-user community. Non-circumvention as to a named third-party vendor introduced by the Company, if desired, must be written; otherwise ordinary competition law applies. Bribes and kickbacks are prohibited. Hospitality shall be modest and recorded if required by the Client’s policy. The Kington desk is not a venue for concealed commission. If the Client requests a disguised below-cost bid to harm a competitor, the Company may refuse.
Further particularisation for Commercial agents, introductions and non-circumvention follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
FF. Training, documentation quality and knowledge transfer
Documentation is proportionate to the fee. A modest engagement receives a concise field-note pack: architecture, credentials location, acceptance evidence, and operational caveats. A large engagement may include user guides. The Company writes in English. Screenshots are of the contracted build, not of every future theme. Training sessions are time-boxed. Additional sessions are charged. Recording of training requires agreement. The Client shall identify trainees. Knowledge transfer does not include making the Client’s junior staff into a replica studio capable of all future communication technology solutions without further hire; it includes enabling operation of the delivered Platform. If the Client declines to read the documentation, later questions that are answered there may be billed as support. The Company may use its own templates. The Client may rebrand user-facing help if licence allows. Internal capture notes that contain other clients’ confidential traces will not be handed over. Source comments, if any, are not a substitute for runbooks. The absence of comments in public website code of the Company’s brochure is irrelevant to product documentation duties.
Further particularisation for Training, documentation quality and knowledge transfer follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
GG. Warranty exclusions specific to conversation products
The Company does not warrant that End users will be polite, that rumours will not spread, that a leaked screenshot will not occur, that a group will not fragment, or that a competitor will not launch a similar app. It does not warrant compatibility with every future operating-system version beyond a reasonable period specified in support. It does not warrant that encryption makes the Client immune to compulsion, malware on a device, or physical observation. It does not warrant uptime of the public internet. It does not warrant that a social messaging application will become a cultural habit. It does not warrant legal compliance of the Client’s use in jurisdictions not listed. It does not warrant that Ofcom, the ICO, or an app store will agree with the Client’s interpretations. It warrants care and skill and material conformance to field locks, as in Part G. This exclusion section exists so that faint, useful signals in the contract are not destroyed by implied romance about software. The Client is buying a captured pattern implemented as software, not a guarantee about human history.
Further particularisation for Warranty exclusions specific to conversation products follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
HH. Invoicing mechanics, purchase orders and public bodies
If the Client is a public body, it shall issue a purchase order in time. Payment in thirty or sixty days, if required by the Client’s standing orders, must be in the statement of work; otherwise fourteen days applies. Framework agreements do not silently replace these Conditions unless signed. Freedom of information requests that would reveal Company pricing may be resisted to the extent the law allows for commercial confidentiality; the Client shall consult the Company before disclosure where lawful. For private Clients, missing purchase-order numbers are not a reason to delay payment if the work was instructed. Billing contacts shall be named. Disputed lines shall be particularised within ten business days; undisputed lines remain payable. The Company may send invoices by email as PDF. E-invoicing networks are used only if purchased as a process. Credit terms are not extended to Clients who repeatedly pay late. The Company may require payment in advance for third-party media spend. The address for billing remains 61 Bridge Street, Kington, United Kingdom, HR5 3DJ unless a finance portal is agreed. VAT invoices shall contain the particulars required by United Kingdom law. If the Client’s finance system destroys the meaning of a description by truncating it, the Client shall still pay against the attached statement of work reference.
Further particularisation for Invoicing mechanics, purchase orders and public bodies follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
II. Sub-processors, toolchains and software bills of materials
The Company uses ordinary professional tools: source control, issue tracking, design files, and cloud consoles. Named sub-processors for End-user data are listed in the processing schedule. Tooling that does not receive End-user content is not a sub-processor of that content. The Client shall not demand that the Company abandon its toolchain without paying for equivalent isolation. A software bill of materials shall identify significant libraries. It is not a warranty that a volunteer maintainer will remain alive. Critical vulnerabilities in dependencies shall be addressed under support if a support plan exists, or as a paid change if not. The Company shall not be required to dual-license the Client’s product as open source unless that is the contracted pattern. Copyleft obligations, if triggered by a Client-mandated component, are the Client’s risk if the Client insisted after advice. The Company shall give advice in the capture notes; ignoring advice is not a Company breach. Build reproducibility is a best effort unless a higher standard is purchased. Supply-chain attacks are a shared internet risk; the Company applies reasonable pinning and review, not omniscience.
Further particularisation for Sub-processors, toolchains and software bills of materials follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
JJ. Ending remarks on governing commercial purpose
AVA INTERACTIVE LTD exists to capture weak conversation signals and translate them into platforms that organisations can operate. These Conditions allocate risk in a way that allows a small United Kingdom studio to work with Clients without accepting unbounded liability for the social life of those Clients’ users. They require both parties to pin meaning: about privacy, about groups, about voice, about money, and about law. They should be read with the privacy policy, cookie policy and terms of service, but they prevail for paid work. For a new capture, write to network@avainteractive.mobi, telephone +44 7411 526199, or send a note from avainteractive.mobi. The Company will darken noise, attract the useful thread, and, if the signal is one it can hold, translate it into visible direction without destroying its meaning. That sentence is a brand metaphor and also a fair summary of the standard of care: do not crush the brief under a generic catalogue; do not promise a carnival; document the pattern; hand over luminous proof. These Conditions are intended to be enforceable, readable, and specific to communication technology solutions rather than to an unrelated trade. They have been prepared for use under English law from Kington in the United Kingdom. They are not a substitute for independent legal advice. The Client should obtain such advice if the Platform is high risk. The Company may update this text for future engagements. The version incorporated is the one referenced in the statement of work. If none is referenced, the version published on the date of acceptance applies. Page titles on the website shall not be read as limiting a clause. Internal cross-references to Parts A to Z and AA to JJ are for navigation. The parties may add schedules: service description, fees, processing, security, support, and acceptance. Schedules win on their subject if they expressly vary a named clause. Silent schedules do not. This is the end of the operative commercial field lock.
Further particularisation for Ending remarks on governing commercial purpose follows so that the field is not left as a slogan. The Client and the Company shall treat the statement of work as the place where numeric targets, named vendors, named platforms and named dates live. These Conditions supply the background law and the default risk allocation. Where a topic in this Part could be read as expanding scope, it does not: it expands explanation. Scope remains what was purchased. The Kington practice will not perform unbounded labour because a clause is long. Length is for clarity in communication technology solutions, where silence has historically caused disputes about encryption, moderation, stores and fees. Each party should keep a copy of the accepted version. Electronic copies are sufficient. Translation of these Conditions into another language is not authoritative. If a court must construe a clause, it shall do so in commercial context: a specialist messaging platform development studio and a business Client, not a consumer downloading a free social app. Nothing here creates a fiduciary duty beyond English law. Nothing here requires the Company to give evidence in the Client’s internal disciplinary hearings except under compulsion or a paid expert engagement. Nothing here requires the Client to adopt the Company’s marketing aesthetic in the product. The ultraviolet moth-sheet interface is a brochure universe. The product may be calm, accessible and ordinary if that is the capture. Ordinary can still be precise. Precision is the point.
KK. Schedules, signatures and version control of the commercial pack
A complete commercial pack for a messaging platform development engagement typically includes the statement of work, these Conditions, a processing schedule if End-user data will be processed by the Company, a security schedule if the Client’s sector requires it, a support schedule if operations are purchased, and an acceptance schedule listing scenes. Each schedule shall bear the same engagement reference. Signatures may be wet ink or electronic. It is enough that the accepting email from an authorised Client address attaches or links the pack and says that it is accepted. The Company shall keep the accepted pack. If the Client’s procurement portal generates a different PDF with truncated clauses, the fuller pack identified in the accepting mail prevails. Version numbers, if used, shall be monotonic. Marketing pages on avainteractive.mobi are not schedules. Capture notes become schedules only if they are attached and marked as such. The parties shall not hide a fee change inside a caption on a design file. Fee changes need a written change order. This Part exists because communication projects generate many artefacts; only some of them are contractual. Distinguishing them is part of not destroying meaning.
LL. Closing field lock
These terms and conditions are the commercial field lock of AVA INTERACTIVE LTD. They are written for English law, for a Kington correspondence address, and for work in instant communication platforms and related software. They should be read slowly. They allocate duties about privacy promises, group gravity, voice and video, stores, fees, and handover. They allow a small studio to capture faint briefs without accepting the entire social risk of a Client’s user base. They require the Client to pin what it actually wants. Correspondence: AVA INTERACTIVE LTD, 61 Bridge Street, Kington, United Kingdom, HR5 3DJ. network@avainteractive.mobi. +44 7411 526199. Public site: avainteractive.mobi. Related public notes: privacy-policy.html, cookie-policy.html, terms-of-service.html, contact.html. The operative metaphor remains: the most useful signals are often faint; the right system brings them into the light without destroying their meaning. In contract, that means write the threat model, write the room model, write the fee, write the acceptance scenes, and do not later pretend a carnival was included.
MM. Interpretation examples that do not expand scope
If a statement of work says “team messaging platform” and the Client later points to a social feed on a competitor’s consumer app, these Conditions treat that pointing as a change request, not as an implied term. If a statement of work says “private messaging application” without a threat model, the Company shall propose a written model before claiming encryption adjectives in any store listing it drafts. If a statement of work is silent on video, video is out of scope even if the brochure site mentions video chat app development as a capture point the studio can offer. If a statement of work includes voice communication software, it does not include a radio licence. If the Client’s staff paste production data into a ticket, that act is the Client’s processing, and the Company shall minimise and may refuse to keep the paste. If the Client asks for “whatever Slack does”, that phrase is not a specification; the Company shall require field locks. If two Client stakeholders contradict each other, the product owner’s written pin prevails, or work pauses. These examples are interpretive aids. They do not add features. They exist so that a dispute about meaning can be resolved without theatre.