Terms and Conditions
These Terms and Conditions govern paid Apple app development services and related native iPhone and iOS work supplied by CRADERO LIMITED. They apply when a statement of work incorporates them. Contact: admin@cradero.technology, +44 7411 525634, 25 Belhaven Park, Muirhead, Glasgow, Scotland, G69 9FA.
1. Parties, language and commercial setting
These Terms and Conditions (“Conditions”) govern the supply of professional services by CRADERO LIMITED, a company operating from 25 Belhaven Park, Muirhead, Glasgow, Scotland, G69 9FA (“we”, “us”, “our” or the “Company”) to the person or organisation that accepts them (“you” or the “Client”). The public website at https://cradero.technology is an invitation to treat. A binding services contract is formed only when we issue a written statement of work, proposal, engagement letter or order acknowledgement that incorporates these Conditions and you accept that document in writing, including by a confirming email from an authorised address. The governing language is English. The commercial subject is Apple app development services and related native work described on the site, including iPhone software development, iOS mobile solutions, Swift application development, iOS UI development, App Store application development, native Apple app solutions, iOS product development, custom iPhone software and Apple mobile technology. Nothing in these Conditions appoints us as Apple, as an App Store, or as your internal IT department.
Notices under these Conditions must be in writing and sent to admin@cradero.technology or to the Muirhead postal address. Telephone +44 7411 525634 may be used for operational discussion but does not, by itself, vary the contract. If you are contracting as a consumer, mandatory United Kingdom consumer law prevails to the extent it conflicts with a clause. Most clients are businesses. If you are unsure of your status, say so before we start the first exposure bath.
2. Definitions used throughout these Conditions
“Apple Platforms” means iOS, iPadOS and related Apple operating environments named in the statement of work. “Deliverable” means software, documentation, listings copy, design files or other materials we are required to deliver. “Exposure Mask” means the written scope that identifies users, devices, constraints, non-goals and acceptance tests. “Negative Input” means materials you supply, including briefs, credentials, designs, copy, certificates, TestFlight lists and third-party access. “Print-Ready Result” means a Deliverable that has passed the agreed acceptance tests, not a poetic standard of beauty. “Working Day” means Monday to Friday excluding Scottish bank holidays, 09:00 to 17:30 United Kingdom time unless the statement of work says otherwise. “App Store Rules” means Apple’s developer agreements, review guidelines, Human Interface Guidelines and related policies as updated by Apple. Headings are for reading, not for limiting interpretation. References to statutes include amendments. Words in the singular include the plural.
A person includes a company. “Including” is illustrative. A reference to writing includes email but does not include a social-media direct message unless we agree. A reference to software includes source, binaries, provisioning profiles and associated scripts that we actually create under the engagement. Open-source components are identified as such and are licensed by their own terms, not by a silent assignment.
3. Order of documents and entire agreement
If there is a conflict, the statement of work prevails over these Conditions for the conflicting point, then any data-processing addendum, then these Conditions, then the website Terms of Service, Privacy Policy and Cookie Policy. Pre-contract marketing on cradero.technology, including darkroom metaphor copy, is not a specification. These Conditions together with the statement of work and any addenda form the entire agreement and supersede prior negotiations, except that fraud and fraudulent misrepresentation remain actionable. You acknowledge that you have not relied on any representation that is not set out in the contract documents. Our employees are not authorised to make oral warranties that survive unless confirmed in the statement of work.
A variation must be in writing and expressly stated to vary the contract. A series of informal chat messages does not vary scope merely because they are numerous. If you issue a purchase order with extra terms, those extra terms do not apply unless we sign them. Silence is not acceptance of your additional terms. This clause is intended to keep exposure controlled so that hidden side letters do not stain the print.
4. Our status and your status
We are an independent contractor. Nothing creates a partnership, joint venture or employment relationship. You warrant that you have power to contract, that the signatory is authorised, and that you are not asking us to perform unlawful work. You will obtain internal approvals, works-council notices if any, and budget. If you are buying as an agent, you must name the principal. We may request evidence of incorporation. We contract with the named Client, not with a crowd of informal stakeholders. Multiple stakeholders may attend workshops, but instructions that change scope must come from the person named in the statement of work or their written delegate.
We may decline to start until anti-money-laundering or sanctions questions that a reasonable Scottish supplier would ask have been answered. We do not provide banking secrecy. We do not accept cash for Apple app development services. Invoices are payable as stated in the fees section.
5. Nature of the services — controlled exposure
We will provide the services with reasonable skill and care, consistent with a competent United Kingdom supplier of native Apple work of similar complexity. We do not guarantee App Store approval, because Apple is independent. We do not guarantee commercial success, download volume, or that users will like the product. We do not guarantee that a third-party API will remain available. We do not guarantee that Apple will not change APIs. We will, however, control scope, reveal hidden technical structure, and develop a Print-Ready Result against the Exposure Mask. The metaphor used on the website is a method of talking about quality, not a separate set of mystical obligations.
Unless the statement of work says otherwise, services are supplied on a time-and-materials or fixed-price basis as priced, not as an unlimited bath. Unused hours in a prepaid block expire as stated. If not stated, they expire twelve months after purchase. We may pause work if you fail to supply Negative Input after a written reminder.
6. Apple app development services
Where the statement of work includes Apple app development services, we will plan, build and iterate native software for the named Apple Platforms, including the baths described as Expose, Submerge, Watch, Fix, Rinse and Dry when those labels are used in project notes. The service includes reasonable clarification of unclear briefs, but it does not include inventing your business model. You remain responsible for product legality in your sector, including financial promotion, health claims, gambling, and children’s products. We may refuse a feature that would likely violate App Store Rules or United Kingdom law. Refusal is not a breach. It is highlight control.
Unless listed, Apple app development services do not include hardware procurement, Apple Developer Programme enrolment in your name without your action, 24-hour operations support, paid media, or rewriting your organisation. They do include, when specified, coordination of TestFlight groups you provide and preparation of store-listing materials you approve.
7. iPhone software development
iPhone software development focuses on handheld use: performance on devices named in the Exposure Mask, interruption by calls, background constraints, camera and file access only where justified, and layout that remains readable. You must name minimum iOS versions. If you do not, we will propose a version line based on Apple’s current support posture and your user base. Supporting antique versions may increase fees. Device lab access is limited to devices we reasonably hold or that you supply. We are not required to buy every new iPhone on launch night unless the statement of work funds that purchase.
Field conditions such as gloves, sunlight, and poor network must be described if they matter. We cannot protect shadow detail we were not told exists. If your workers operate in Faraday-cage buildings, offline behaviour must be in the mask. Otherwise it is a change.
8. iOS mobile solutions
iOS mobile solutions may include iPhone and iPad surfaces, shared services, and role-based access as specified. They do not automatically include a web application, Android, or a desktop companion. If you later want those, that is a new exposure. Integration with your existing systems requires documented APIs, non-production credentials first, and a client-side owner who can answer questions on a Working Day. We will not guess at undocumented SOAP ghosts. If your backend is not ready, the mobile print will wait in the rinse or we will stub, as you choose in writing.
Push notifications, widgets, watch companions, live activities and app clips are included only if named. Each has extra App Store and design implications. Naming them in a meeting after sprint two is a change request.
9. Swift application development
Swift application development means we write and structure Swift (and agreed associated languages) in a repository you control or that you authorise. We will apply reasonable engineering hygiene: readable modules, attention to concurrency, and tests where the statement of work includes them. One hundred percent coverage is not implied. We will not introduce a secret dependency that phones home to CRADERO LIMITED. Residual snippets of generic technique remain ours to reuse, as described in the intellectual property section. Project-specific business logic that you paid to have written is treated under the assignment clause.
If you mandate a particular architecture religion, put it in the mask before Submerge. Converting a finished print from one architecture church to another is a new bath and a new fee. We may refuse architectures that would make App Store application development unreasonably fragile.
10. iOS UI development
iOS UI development is the making of interfaces that hold contrast: hierarchy, Dynamic Type where reasonably practicable, colour choices that remain readable, and motion that does not leak attention. It is not a promise of a custom illustration library, a full brand rewrite, or cinematic animation. Apple Human Interface Guidelines are a reference, not a statute, but we will not knowingly ship a parody of them. If your brand guidelines conflict with accessibility, we will tell you and ask you to choose. Your choice, once written, is the Exposure Mask on that point.
Copy is your responsibility unless copywriting is purchased. Lorem text in an intermediate build is a process artefact, not a Deliverable. Final strings must be supplied or approved. Localisation into languages other than English is included only if priced. The site language is English; that does not force every application to be English-only, but extra locales are extra work.
11. App Store application development
App Store application development includes preparing the binary path, privacy answers based on information you confirm, screenshot sets from builds you approve, and responses to review questions we can answer as implementers. You must hold, or promptly create, the Apple Developer account that will own the listing. We will not hold your account as if it were ours. If Apple rejects a build, we will analyse the rejection and propose a fix within scope. If the rejection arises from your business model, your content, or your missing legal basis, extra work is chargeable. Apple’s timelines are not our breach.
Paid applications, in-app purchases, subscriptions and StoreKit features are included only when specified. Taxation of digital supplies is your concern, including any need for a specialist. We are not your tax agent. Age ratings, content descriptors and kids-category decisions are yours, with our technical advice.
12. Native Apple app solutions and iOS product development
Native Apple app solutions means we prefer first-party frameworks and native UI unless the statement of work selects another approach. A wrapper around a website is not native merely because it is installed. If you insist on a wrapper, we will say so in the mask so that later disappointment is not a dispute. iOS product development includes sequencing features, advising on cuts, and protecting the main subject from feature flare. It does not include hiring your staff, running your company, or sitting in your board as a director.
Discovery workshops, if purchased, produce notes and a recommended mask. They do not produce a finished application. If you stop after discovery, you pay for discovery. You do not acquire a right to demand the unbuilt print.
13. Custom iPhone software and Apple mobile technology
Custom iPhone software is built for your mask, not sold as a shrink-wrap product with a public licence. We do not grant a right to resell the software as a competing toolkit unless a distribution licence is priced. Apple mobile technology in these Conditions means the practical stack used to deliver on Apple Platforms, including tooling, signing and distribution, not a licence to Apple’s intellectual property. You must accept Apple’s terms yourself. We are not a party to your contract with Apple and cannot vary it.
If you require a white-label engine to sell to your own customers, say so. That is a different print, with support, versioning and liability implications that a single internal app does not have.
14. Exclusions and non-goals
Unless expressly included we do not supply Android, web, Windows, game-engine ports, hardware design, plastic tooling, photography studios, printing presses, chemical manufacture, legal opinions, penetration tests by a CREST firm, 24/7 incident response, paid user acquisition, or content moderation teams. We do not impersonate a camera shop or a film production company. We do not store customer card data on this website. We do not accept instructions to circumvent digital rights, to spoof App Store reviews, to seed fake accounts, or to hide tracking from users in a manner contrary to Apple rules or PECR.
If a desired integration is legally or technically closed, we will say we cannot develop that detail. An impossibility is not a delay. It is a blocked shadow that must be redesigned or abandoned.
15. Client obligations and Negative Input
You will supply, in a timely manner, truthful Negative Input, including access, copy, credentials that you are allowed to share, decision-makers, and test devices if required. You will not send live production secrets in chat. You will rotate anything that was overexposed. You will ensure that TestFlight testers have consented to receive builds. You will obtain licences for fonts, stock, and third-party SDKs you insist we use. You will not instruct us to infringe. You will review test strips promptly. Silence for more than ten Working Days after a review request may be treated as deemed acceptance of that increment if we warned you of that consequence in the request.
You remain responsible for your staff’s use of any staging build, including personal data they type into it. You will not use staging as production. You will maintain your own backups of business data. We are not your disaster-recovery vendor unless that is purchased.
16. Exposure Mask, changes and estimates
Work proceeds against the Exposure Mask. A change is anything that alters users, platforms, integrations, compliance duties, languages, design system, or acceptance tests. We will quote or estimate the change. We need not start the change until you approve. Estimates are not caps unless labelled fixed. If we learn that the negative was denser than disclosed, we will stop and re-expose the plan. Continuing without a revised mask is not a gift of free hours.
Emergency changes requested by telephone must be confirmed in writing the same Working Day. If two of your stakeholders contradict each other, we will follow the named instruction owner and charge for the fog.
17. Timetable, dependencies and delay
Dates are targets unless the statement of work uses the words “time is of the essence”, which we will rarely accept for App Store dates we do not control. Dependencies include your feedback, third-party vendors, Apple review, certificate expiry, and backend readiness. Delay caused by those dependencies moves the Dry date. We will not pay liquidated damages unless a separate clause, rarely offered, is signed. We may reallocate people if you pause for a long period, and restart may need a re-entry fee to recover context.
If Apple announces a deprecation that forces extra work, that extra work is a change unless it is a small adjustment we can absorb within the unused contingency, if any, named in the statement of work.
18. Acceptance, rejection and latent defects
Acceptance tests will be written or, if not written, will be reasonable fitness for the mask on named devices. You may reject a Deliverable only for material non-conformity. Cosmetic opinions after you approved a design direction are not material. After acceptance, or deemed acceptance, further edits are maintenance or a new exposure. Latent defects that existed at acceptance and that we caused will be repaired at no extra fee if reported within thirty days, unless the statement of work sets another warranty window. Defects caused by your changes, third-party outages, or new OS versions after Dry are not latent defects of ours.
A Print-Ready Result may still be improved. Improvement is optional work. Do not confuse a living product with a failed acceptance.
19. Personnel, subcontracting and non-solicitation
We decide who performs the work. You may not select individuals as if they were your employees. We may subcontract under confidentiality and data-protection constraints, remaining responsible for our subcontractors. You will not, for twelve months after the last supply, solicit for employment any person of ours who materially performed the services, except through a public advertisement not aimed at them. A breach of this clause is compensated by a fee equal to three months of that person’s last applicable rate, which the parties agree is a genuine pre-estimate of replacement cost, not a penalty.
We will not solicit your employees either, on the same terms, so the tray stays stable. This does not stop anyone from applying to a genuine open advert.
20. Fees, invoices, expenses and tax
Fees are as stated in the statement of work, exclusive of VAT where applicable. We invoice as scheduled, or monthly in arrears for time-and-materials. Payment is due within fourteen days unless otherwise stated. Late sums may bear interest at the statutory rate under the Late Payment of Commercial Debts (Interest) Act 1998 if it applies, or otherwise at 4% above the Bank of England base rate. You will pay reasonable expenses that were pre-agreed, including devices purchased for you, which then belong to you. Withholding tax, if any, is your problem to structure; net sums received must equal the invoice unless a treaty mechanism is agreed in writing.
We may suspend services for non-payment after notice. We may recover reasonable collection costs. Disputed lines must be identified in writing within ten Working Days; undisputed lines remain payable. Set-off against our invoices is not allowed except for sums that are due, liquidated and undisputed.
21. Intellectual property assignment and licences
Upon full payment, we assign to you the copyright in Deliverables created specifically for you under the engagement, excluding our pre-existing tools, templates, internal scripts, generic components, and know-how. We grant you a non-exclusive licence to use those excluded materials as embedded in the Deliverables for your internal operation of the application. You do not receive a right to extract our internal toolkit and sell it. Third-party and open-source components are licensed by their own terms. Apple’s software remains Apple’s. Your Negative Input remains yours. We may use anonymised non-identifying descriptions of the project as a print on our portfolio unless you forbid that in the statement of work.
Until payment, we reserve all rights in unpaid Deliverables and may disable staging. We will not ransom production keys that are already in your account; those are in your Apple Developer account. We will not withhold your repository access if the repository was always yours. We may withhold our private forks of unpaid work.
22. Confidentiality
Each party will keep the other’s confidential information secret, using at least reasonable care, and use it only to perform the contract. Exceptions: information that is public other than by breach, independently developed, already known, or required to be disclosed by law or a competent authority. A disclosure required by law should, where legal, be notified to the other party. Confidentiality lasts for five years after Dry, and indefinitely for trade secrets that remain secret. Source code you mark as confidential is confidential. These Conditions are not confidential. Pricing in a statement of work is confidential.
We will not use your confidential product idea to build a competing public app while confidentiality lasts. You will not use our internal method notes to brand yourself as CRADERO LIMITED.
23. Data protection and security
Each party will comply with United Kingdom data protection law. Roles will be as stated in the Privacy Policy and any processor addendum. You will not send us special category data or children’s data unless the mask says so and a lawful basis is documented. We will apply measures proportionate to a small professional firm. We are not responsible for your production cloud. Signing keys will be handled with care. You will enable two-factor authentication on Apple accounts. If a security incident affects data we process, we will notify you without undue delay after we confirm it. You will notify us if your side is breached in a way that affects the project.
Penetration tests, if required, are a purchased extra performed by an agreed tester. We will remediate in-scope findings that are our defects. Findings that are your infrastructure remain yours.
24. Warranties and disclaimers
We warrant that we will provide the services with reasonable skill and care and that, to our knowledge, Deliverables created by us will not knowingly infringe a third party’s United Kingdom copyright. We do not warrant uninterrupted operation, error-free software, fitness for a purpose you did not disclose, compatibility with future Apple systems not yet released, or that users will not misuse the application. Implied terms that can be excluded in a business-to-business contract are excluded to the fullest extent permitted. Nothing excludes fraud, or death or personal injury caused by negligence, or other non-excludable liability.
Sample screens on cradero.technology are metaphor and portfolio, not a warranty that your print will look like a safelight tray. Demo devices in meetings may run unfinished chemistry.
25. Limitation of liability
Subject to non-excludable liabilities, our total aggregate liability arising out of or in connection with an engagement, whether in contract, delict, negligence, statutory duty or otherwise, is limited to the fees paid by you to us under that engagement in the twelve months before the claim arose, or five thousand pounds sterling, whichever is higher. We are not liable for loss of profit, revenue, goodwill, data (except to the extent we are required to restore data we were contracted to host, which we ordinarily are not), indirect or consequential loss, or App Store ranking. We are not liable for Apple’s acts. We are not liable for your users. A claim must be notified in reasonable detail within twelve months of the facts arising, failing which it is barred, except for fraud.
The parties agree that fees reflect this allocation of risk. If you need a higher cap, we may quote a different rate and insurance arrangement. Until that is signed, this cap applies.
26. Indemnities
You will indemnify us against losses, including reasonable legal costs, arising from your Negative Input, your content, your breach of App Store Rules that you insisted on, your unlawful processing of personal data, and third-party claims that your product idea infringes, except to the extent caused by our proven infringement in original code we wrote without following your instruction. We will indemnify you against proven United Kingdom copyright infringement in original code we wrote, subject to the liability cap, provided you give prompt notice, sole control of defence, and reasonable assistance. We may replace or modify infringing code. Open-source licence conflicts caused by a library you required are your indemnity, not ours.
An indemnity does not apply to the extent a party failed to mitigate. Settlements require consent not to be unreasonably withheld where money would be paid.
27. Term, termination and consequences
The engagement starts on acceptance and continues until Dry plus any purchased support, or until terminated. Either party may terminate for material breach not remedied within fourteen days of notice, or immediately if the other becomes insolvent in the Scottish or wider United Kingdom sense. We may terminate if you instruct illegal work. You may terminate for convenience if the statement of work allows, paying for work done plus committed non-cancellable costs. On termination you will pay outstanding invoices. We will deliver paid-for materials in our possession in a reasonable form. Confidentiality, IP in paid work, liability, governing law and this survival list survive.
We are not required to keep building after termination. Access we created in your systems should be revoked by you. We will return or delete your confidential data on request except for copies we must keep for law or disputes, which will be locked.
28. Force majeure
Neither party is liable for delay caused by events beyond reasonable control, including Apple outages, widespread cloud failure, epidemic, fire, flood, strike (except of that party’s own staff where it is a targeted action they could reasonably settle), war, terrorism, and changes of law that make performance illegal. The affected party must notify and mitigate. If force majeure lasts more than sixty days, either party may terminate without fault, paying for work done. App Store queues that are merely slow are not force majeure unless Apple is substantially offline.
29. Compliance: bribery, slavery, tax evasion, sanctions, export
Each party will comply with the Bribery Act 2010, the Modern Slavery Act 2015 as applicable, the Criminal Finances Act 2017 facilitation-of-tax-evasion rules, and applicable UK sanctions. You warrant that the application will not be supplied to a sanctioned person where that would be unlawful. Export of encryption software may require attention; you will tell us if you intend to distribute outside the United Kingdom in a regulated way. We will not pay bribes. Gifts of trivial stationery are not bribes. We may refuse a jurisdiction. You will not ask us to hide a payment.
We expect you to have a similar ethic in your supply chain. We are a small company; our due diligence is proportionate. We still do not work around sanctions as a clever trick.
30. Publicity, portfolio and naming
We may list your organisation name and a non-confidential description on the print wall unless you opt out in the statement of work. We will not disclose secret features. You may say publicly that CRADERO LIMITED performed Apple app development services. You may not imply that Apple endorses you, or that we endorse your politics. Trademarks remain the owners’. Darkroom photographs on our site are our assets.
31. Assignment, notices, waiver, severance, third parties
You may not assign the contract without our consent, not to be unreasonably withheld for a solvent affiliate. We may assign to a purchaser of our business. Notices are effective when actually received, or two Working Days after first-class post to the Muirhead address or your registered office. Failure to enforce is not a waiver. If a clause is invalid, the rest remains, modified as little as required. A person who is not a party has no right under the Contract (Third Party Rights) (Scotland) Act 2017 to enforce these Conditions, except that our subcontractors may benefit from liability limits. Apple is not a third-party beneficiary.
Further assurance: each party will sign documents reasonably required to perfect the IP assignment after payment. Counterparts and electronic signatures are valid. The contract may be executed in counterparts.
32. Dispute resolution and governing law
The contract is governed by the laws of Scotland. The courts of Scotland have exclusive jurisdiction, except that we may seek interim protection in any court. Before issuing a claim, senior representatives will meet in good faith within fourteen days of a written dispute notice, including by video. Mediation in Glasgow may be suggested but is not a condition to litigation except where a protocol requires it. Nothing stops a party seeking urgent interdict. The UN Convention on Contracts for the International Sale of Goods does not apply. These Conditions are not an arbitration clause unless a separate arbitration agreement is signed.
Complaints about the website are not disputes under this section unless they concern a paid engagement. Website terms have their own jurisdiction clause, also Scots law.
33. Support, maintenance and service levels
After Dry, support is not included unless purchased. Purchased support is provided during Working Days, not as a 24-hour operations centre. Response targets, if any, are aims, not warranties, unless labelled as a service level with a service credit, which we rarely offer. OS updates by Apple may require a new exposure. We are not obliged to keep a retired engineer on a pager. Critical defects in in-scope warranty windows are handled under acceptance, not under a separate SLA.
Documentation we supply will be sufficient for a competent iOS engineer to continue, not a novel for a novice. Training sessions are extra if not listed.
34. Accessibility, performance and quality records
We will take reasonable steps toward accessibility on Apple Platforms, including Dynamic Type and VoiceOver basics where the UI is under our control. Full WCAG certification, user testing with disabled people, and legal opinions on the Equality Act 2010 are extras or your counsel’s work. Performance budgets, if unnamed, will be reasonable for the device class. We keep project records for the retention periods in the Privacy Policy. You may request a copy of your project artefacts that we still hold, at a reasonable copying fee if the volume is large.
Quality is judged against the mask, not against a competitor’s marketing. A denser application is not automatically a better print.
35. Insurance, records, audit and TUPE
We maintain insurance that is reasonable for a small Scottish software firm. Certificates may be provided on request. You may not dictate our insurer. Audit rights, if any, are limited to data-protection and fee records for your engagement, on reasonable notice, no more than once a year, at your cost, and not in a way that exposes other clients. TUPE is not expected to apply to these services. If a regulator later says it does, the parties will discuss in good faith; we do not intend to supply an organised grouping of employees to you.
Health and safety on your premises follows your site rules if we visit. Remote work follows our own. We are not your occupier.
36. Beta software, prototypes and experiments
Prototypes may be thrown away. They are not production. If you put a prototype in public TestFlight, you accept the risk. Beta OS versions from Apple may break builds; waiting for a stable OS is not our delay. Experimental APIs may vanish. We will warn when we use them. You must confirm in writing if you accept that risk. A prototype can be beautiful and still not be a Print-Ready Result.
37. Keys, certificates, accounts and escrow
You will own the Apple Developer account. We will use invitation-based access. You will revoke our access when the engagement ends. We will not be your recovery contact unless you appoint us and we agree. Source escrow with a third party is an extra. We do not offer informal escrow by keeping a secret copy as leverage. Unpaid work may remain in our private systems as the IP clause allows. Production certificates in your account remain yours.
If you lose your account through your own mismanagement, rebuilding signing is chargeable. If Apple disables an account for your policy breach, that is not our breach.
38. Open source and third-party packages
We may use open-source components under licences that are compatible with App Store distribution. Copyleft that would force you to publish your proprietary logic will not be introduced without your written approval. You must approve paid SDKs. Licence scans, if required by your counsel, are an extra. We are not liable for a vulnerability in a third-party package except to apply a reasonable update when we are still engaged and the update is in scope. After Dry, updates are maintenance.
39. Consumer clients, distance selling and cancellation
If you are a consumer and the Consumer Contracts Regulations apply to a distance contract, we will provide the required information. If you ask us to start digital services within a cancellation period, you may lose the right to cancel for work performed, as the regulations allow when you make that request. Custom software tailored to you may be excepted as the law provides. This section does not convert a business client into a consumer. If you are a consumer, non-excludable rights under the Consumer Rights Act 2015 remain.
40. Interpretation against overexposure
These Conditions should be read to give reasonable commercial effect. They should not be read to require us to perform miracles, to replace Apple, or to absorb your entire enterprise risk for a modest fee. They should not be read to allow you to withhold payment for taste after acceptance. They should not be read to allow us to abandon a half-built print without the termination mechanics. Ambiguity will not automatically be construed against the drafter where both parties are commercial. The analog darkroom language on the public site is branding. In these Conditions, ordinary legal English controls. Where both appear, the legal English wins.
Questions about these Conditions before signature should be sent to admin@cradero.technology. Do not assume a website FAQ overrides them. The company is CRADERO LIMITED. The work is Apple-native. The address is 25 Belhaven Park, Muirhead, Glasgow, Scotland, G69 9FA. The phone is +44 7411 525634. The domain is cradero.technology. That is the identification print.
41. Workshops, travel to Glasgow and remote collaboration
Workshops may be held by video or, if agreed, at 25 Belhaven Park, Muirhead, Glasgow, Scotland, G69 9FA or at your premises. Travel outside the Glasgow area is chargeable at reasonable cost plus time unless bundled. We do not provide hospitality as a contractual deliverable. Remote tools will be agreed; we may refuse a tool that cannot hold confidentiality. Recordings are off by default. If you record, you are the controller of the recording. Time spent waiting for your late attendees is still time. A workshop is not a substitute for a written mask. Decisions must be written down the same Working Day or they may dissolve like an unfixed print.
If weather, rail or public health measures prevent a Muirhead visit, video is a reasonable substitute and not a downgrade of the contract. We will not refund a cancelled visit that you cancelled late except for our unspent travel disbursements.
42. Design files, brand assets and illustration
You must supply brand assets in usable formats. We are not obliged to recreate a lost brand book from a screenshot. Custom illustration, 3D, photography direction, and motion-design beyond modest iOS transitions are extras. If you supply assets you do not own, your indemnity applies. We may reject assets that would fail App Store review for deception or for prohibited content. Darkroom imagery on our marketing site is not a template you may copy into your application as if it were your identity. Your application should look like your organisation, not like CRADERO LIMITED’s safelight room, unless you separately licence that look.
Icon production for App Store and home screen is included when iOS UI development is in scope, at a reasonable number of iterations named in the statement of work. Endless icon taste cycles are changes.
43. Copywriting, localisation and transcreation
English interface copy may be drafted by us when purchased, but legal, medical and financial claims remain yours to approve. Localisation, including right-to-left languages, plural rules, and transcreation of tone, is a separate bath. Machine translation without review is not a Print-Ready Result. You must tell us if a locale has regulatory wording. We do not translate your privacy policy unless hired to draft software strings that match it. Inconsistency between store listing language and in-app language is often a review risk; we will point it out if we see it, and you will decide.
44. Analytics, crash reporting and third-party SDKs
Analytics and crash tools are included only if named. You must complete Apple privacy answers honestly. We will not hide an SDK. We will not sideload a tracker to dodge App Tracking Transparency. If an SDK vendor changes its behaviour, you may need a new build. We are not the SDK vendor’s support desk. Data from analytics in your production app is yours. Do not send us exports full of end-user content unless a processor addendum covers it. If you insist on a particular SDK that is hostile to privacy, we may refuse.
Consent prompts, if required, will be implemented as specified. Their legal adequacy is a matter for your counsel. We implement the switch, not the opinion.
45. Payments, StoreKit, subscriptions and commerce
If the application sells digital goods, Apple’s commission and rules apply. You will comply with them. Physical goods, bookings and services paid outside Apple may have different rules; you will not instruct us to route digital content in a way that knowingly breaches App Store Rules. Receipt validation, tax invoices to consumers, and refund policy text are your commercial duties. We can implement technical hooks. We cannot make Apple pay you faster. Chargebacks and fraud in your merchant account are yours. We do not hold customer funds. We do not operate a payment institution.
46. Notifications, messaging and communications features
Push, email gateways, SMS and in-app chat are extras unless named. You are the controller of message content. You will comply with PECR and with any Ofcom rules that apply to your messaging. We will not build spam cannon features. Quiet hours, unsubscribe, and preference centres should be specified if they matter. Delivery of a push is not guaranteed by Apple or by carriers. Failed delivery is not our material breach. If a message feature handles special category data, say so before Submerge.
47. Maps, camera, microphone, health and other sensitive APIs
Sensitive Apple APIs require purpose strings and, often, extra review. You will supply truthful purpose text. We will not implement covert background recording. Health, fitness, home, and similar frameworks are excluded unless named, because they change the privacy print entirely. Camera access will be limited to the feature. Photo library access will use the limited picker where reasonable. Location will be as coarse as the feature allows. If you want constant tracking, expect a harder review and a harder privacy discussion. We may refuse stalking-capable designs.
48. Offline, sync and conflict resolution
Offline modes must be specified, including what happens when two devices edit the same record. If unspecified, last-write-wins may be used as a simple default, which can destroy shadow detail. That default, if accepted in the mask, is not a defect. True conflict UI is extra. Sync is only as good as your backend. We will not invent a distributed database under a small fixed fee. If your field staff work for days without signal, tell us the longest dark period.
49. Identity, authentication and credentials
Sign in with Apple, organisational SSO, magic links, and passwords have different costs and review profiles. You will choose. We will not store passwords in our marketing site form. In an application, we will follow reasonable current practice, not a 2008 pattern, unless you insist in writing on a worse pattern against our advice, in which case your indemnity widens. Account recovery is your operational process. We are not your identity provider. Session length should be in the mask. Biometrics stay on device.
50. Hosting, backends and shared responsibility
Unless we expressly host, you or your cloud vendor host. We develop the Apple client. Outages of your API are not our outages. CORS, certificates, and DNS are yours if you run them. If we recommend a backend pattern, it is advice, not a hosting contract. Data residency in the United Kingdom must be requested. Default cloud regions chosen by you may be outside the UK; that is a transfer you must assess. We will not silently move your data to a novelty region.
51. Environments, branches and release trains
We typically use development, test and release branches as suited to the team size. You will not commit secrets. You will not force-push shared history without agreement. Release trains that you interrupt with last-minute legal copy still count as interruptions. Hotfixes after Dry are chargeable unless under warranty. We may freeze a branch before App Store submission. Unfreezing for a non-critical colour tweak is a change. Version numbers follow a scheme we will propose if you have none.
52. Testing duties of both parties
We test against the mask on named devices. You test against your business reality. UAT is your bath. If you do not UAT, you accept the technical tests only. Automated tests, if purchased, cover what they cover. They do not cover taste. Beta testers you recruit must be real. Fake reviews are forbidden. Device fragmentation should be discussed; we cannot hold thirty historic iPhones unless you fund them. Simulator tests are useful and insufficient. We will say when a bug is only in the simulator.
53. Accessibility beyond the baseline
If you need conformance evidence, commission an audit. We will fix in-scope findings that are engineering defects. We will not certify. Captions, audio description, and Easy Read are extras. Colour-only information will be avoided where we control the UI. Reduce Motion will be respected where feasible. Custom fonts that break Dynamic Type should be avoided; if you insist, you accept the accessibility cost. Equality Act duties for your public service are yours as the service provider.
54. Security testing and responsible disclosure
If a researcher writes to admin@cradero.technology about an application we built, we will pass the report to you if you operate it. We are not obliged to pay bounties. We will not perform hostile testing on your production systems without a written authorisation. You will not perform hostile testing on our marketing host. A password on a sticky note in your office is not our vulnerability. A leaked TestFlight link that you forwarded is not our leak.
55. Content moderation, user-generated content and children
If users can post content, you need rules, reporting, and a human process. We can build buttons. We do not staff a moderation room. Applications directed at children require extra Apple and ICO attention. We will not disguise a child-directed product. Age gates that are merely cosmetic may fail. You will take counsel. We may refuse.
56. Sector rules: finance, health, education, transport, public sector
If you are regulated, say so in the mask. We are not authorised by the FCA. We are not a clinic. We are not a school. Public-sector procurement terms apply only if we sign them. Frameworks with unlimited liability, uncapped indemnities, or broad audit of unrelated clients will be rejected or repriced. Freedom of information, if you are a public body, may expose contract documents; you will tell us what you must publish. We will mark genuine trade secrets.
57. Insurance claims, evidence and expert witness
If a dispute with a third party requires our testimony, time is chargeable at then-current rates unless we are the opposing party. We will not alter records. We keep ordinary project notes, not a forensic archive, unless you purchase that discipline. Logs rotate. Do not assume we still have a chat from years ago.
58. TUPE, IR35 and status of individuals
People we send are our people. You will not supervise them as employees. You will not integrate them into your holiday rota. IR35 status assessments, if you are a public authority or otherwise required, should be discussed before start; we operate as a genuine business with multiple clients and our own method. We do not provide substitute labour desks. If you need a contractor inside IR35, hire differently. These Conditions are for a company-to-company services print.
59. Ethical limits and prohibited instructions
We will not build tools whose primary purpose is unlawful covert surveillance, stalking, non-consensual image abuse, fraud, or evasion of sanctions. We will not clone a third-party app so closely that it is a passing-off risk we can already see. We will not hide malware. We will not backdoor your users. If a request is ambiguous, we will ask. If it remains a stain, we will stop. Fees for work already lawfully done remain payable. Fees for refused unlawful work are not payable, and we may report as law requires.
60. Marketing site, metaphor and no-reliance
You acknowledge you have read that cradero.technology uses analog darkroom language as brand. You do not expect chemical trays to appear in the repository. You do not expect us to be photographers. You do not expect a cinema. Case prints may be masked. Keywords such as Apple app development services describe the trade. They are not a warranty of a particular architecture. Reliance is on the statement of work. This clause is intended to stop a later argument that a headline on the homepage created a collateral contract.
61. Change of Apple rules during an engagement
Apple may change review guidelines, entitlement usage, account enrolment, and technical requirements while we work. We will adapt within remaining unused contingency if the adaptation is small. Material new duties are a change. We will not freeze Apple’s world. If Apple retires a feature your product needed, we will propose a redesign. The cost of the redesign is a change unless we caused a needless dependency against an already announced deprecation that we should have seen at Expose.
62. Documentation standards
We supply README-level and handover notes sufficient for a competent successor. We do not supply a textbook. Comments in code will be used where the why is not obvious. We do not comment for the sake of decoration, matching the cleanliness of our public site. Architecture decision records, if purchased, will be short. Diagrams, if purchased, will be as agreed, not a full enterprise-architecture practice.
63. Training, pair sessions and knowledge transfer
Knowledge transfer is scheduled, not ambient. Pairing all day is a different commercial model. Your staff must attend if transfer is to work. We will not be blamed if they do not. Recordings of training, if you make them, stay inside your confidentiality. We may refuse to be recorded if the session includes another client’s secret, which it should not.
64. Warranties on third-party materials you provide
You warrant that fonts, icons, music, photos, and datasets you provide are licensed for App Store distribution in your territories. You warrant that personal data in those datasets can be used. You warrant that you will refresh licences that expire. We may request copies of licences. We are not your licence docket clerk, but we are entitled to pause if a risk is obvious.
65. Territories, languages of law and stores
Unless stated, we prepare for distribution on the App Store territories you name, defaulting to the United Kingdom. Other stores, enterprise distribution, and unlisted apps have different paths. Legal localisation of terms inside the app is your counsel’s work. We can insert URLs to your policies. We will not invent eleven-thousand-word terms for your product unless you hire a lawyer; our legal pages on cradero.technology are our notices, not yours.
66. Records of processing inside a shipped application
If we help you draft privacy answers, you confirm the facts. If your SDK list changes after Dry, you must update answers. We do not watch your account forever. A processor addendum, if we handle live personal data, will list categories, purposes, and deletion. Without that addendum we try not to handle live personal data. Staging should use fictionals. Your staff sometimes paste real data; you will train them.
67. Backup of work product during the engagement
Repositories should be in your organisation account. If, exceptionally, they start in ours, we will transfer after payment. You should keep your own copies. A disk failure in a laptop is mitigated by remote git, not by mythology. We are not liable for your failure to accept a transfer. After transfer, deletion from our laptops follows our retention, with legal-hold exceptions.
68. Meetings, reporting cadence and quiet periods
A weekly written note is typical unless you buy more. Daily stand-ups with a large audience are often overexposure; we may recommend fewer voices. Quiet periods around submission are healthy. You will not add twelve stakeholders in the last week without expecting delay. Reports will be plain. They will not be theatrical dashboards unless you purchase theatre, which we generally will not sell.
69. Rates review and continuation
Time-and-materials rates may be reviewed with thirty days’ notice after the first twelve months of a continuing engagement. Fixed-price remaining work does not change mid-print unless a change is agreed. Continuation after Dry is a new mask or a support plan. Silence after Dry is not a retainer. A retainer, if any, must say what hours it buys and what happens to unused hours.
70. Set-off, netting and payment mechanics
You will pay in pounds sterling unless we agree another currency. Bank charges for international transfers are yours if you insist on paying from abroad. We may provide account details on invoices. We will not publish those details on the public website. You will verify a change of bank details by a second channel because fraudsters overexpose fake invoices. We are not liable if you pay a criminal after ignoring that check. We do not accept crypto-assets.
71. Entire remaining boilerplate with Scottish emphasis
Rights are cumulative. Nothing restricts a remedy that cannot be restricted. Time is not of the essence except where stated. A delay in payment is of the essence after the cure period. The parties submit to the non-exclusive ability of Scottish courts to grant interim remedies even if a jurisdiction clause is exclusive for substantive claims, to the extent a court accepts that. The contra proferentem rule is moderated as already stated. A reference to a regulator includes a successor. A reference to Apple includes its affiliates who operate the relevant programme. A reference to iPhone includes successor handhelds running the named OS if the mask uses that reading.
These Conditions bind permitted successors. They do not bind Apple. They do not bind your users. They do not bind Companies House. They do bind CRADERO LIMITED and the Client named on the statement of work.
72. Schedule-like detail: Expose bath
Expose includes interviews, review of existing negatives, identification of users, devices, integrations, and risks, and the writing of the Exposure Mask. It may include a short technical spike. It does not include production coding of all features. You will make people available. If your organisation cannot describe its own process, the mask will take longer. We will not invent a process you will not follow. Output is a document you can reject. Rejection means we rework within the purchased Expose hours, then stop for a change if still rejected.
73. Schedule-like detail: Submerge bath
Submerge is implementation against the mask. You will not constantly re-aim the enlarger. A weekly re-aim is a change culture, not a method. We will show test strips. You will comment on them. Code will live in the agreed repository. Secrets will live in a manager, not in screenshots. If you demand a feature that blows the highlights of performance, we will say so and wait for your written choice.
74. Schedule-like detail: Watch bath
Watch is structured review: design, code, and product. We stop when midtones are readable. You may ask to continue polishing; that is extra. Watch includes TestFlight where specified. Feedback must be consolidated by your instruction owner. Fifty contradictory comments are fog. We will charge to de-fog.
75. Schedule-like detail: Fix bath
Fix locks architecture, signing, privacy answers, and store metadata. Changing the architecture after Fix is expensive. You will complete questionnaires truthfully. We will not guess your data collection. If you refuse to answer, we cannot submit. That pause is yours.
76. Schedule-like detail: Rinse bath
Rinse removes unused screens, debug flags, test accounts, and overexposed copy. You will confirm what must remain. If you want to keep a hidden debug menu in production, you accept the risk. We advise against it. Rinse is not a full rewrite. If Rinse reveals that the subject was wrong, that is a new Expose, not a free gift.
77. Schedule-like detail: Dry bath
Dry is handover: paid IP assignment mechanics, access revocation plan, listing live or ready, and a short note on how to rebuild. Dry is not eternal care. If Apple’s review extends past Dry, we will remain available for review questions for a reasonable window stated in the statement of work, after which availability is support. Celebration is optional and not billable unless it consumes a Working Day of our people at your request.
78. Examples of changes that are not defects
New iOS version mid-project. New brand colours after UI freeze. Extra language. Extra user role. Extra integration. A legal opinion that rewrites consent. A board member who appears at week ten with a new product. A desire to copy a competitor’s unique screen. A backend that is late. These are changes or your delays. They are not evidence that CRADERO LIMITED failed to use reasonable skill. A genuine coding error that misses the mask is a defect. Learn the difference; it keeps the commercial print clean.
79. Contact block for legal notices
Legal notices to CRADERO LIMITED must be sent to 25 Belhaven Park, Muirhead, Glasgow, Scotland, G69 9FA and may be copied to admin@cradero.technology. Telephone +44 7411 525634 is not sufficient for a termination notice. Notices to you will be sent to the address on the statement of work or your registered office. You will keep those addresses current. A bounced email you caused does not stop deemed delivery if we also posted. Website publication of new marketing terms does not vary a signed engagement. Only a written variation does.
80. Closing acknowledgement
By accepting a statement of work that incorporates these Terms and Conditions, you acknowledge that unclear material becomes valuable when the exposure is controlled and the hidden structure is developed correctly, that Apple remains independent, that fees reflect the liability cap, that Muirhead is the working address of CRADERO LIMITED, and that the services are native Apple software services rather than photography, cinema, laboratory chemistry, or a generic template house. You acknowledge the Privacy Policy and Cookie Policy exist on cradero.technology and apply to personal data. You acknowledge that these Conditions were written for this company and this trade in the United Kingdom.
81. Annex A — glossary of project labels
The following labels may appear in project tools without creating extra legal duties beyond these Conditions: EXP for an exposure reference; TRAY for a workstream; PRINT READY for a candidate build; NEGATIVE for source material; MASK for scope; FIXER for a freeze; RINSE for cleanup; DRY for handover. If a label is used loosely in chat, the statement of work still controls. A person nicknamed enlarger is not a defined role. Emoji are not notices. A green tick in a chat is not acceptance unless the instruction owner also writes that the increment is accepted. This glossary exists so that brand language does not accidentally rewrite liability.
82. Annex B — device matrix defaults
If the statement of work is silent, we target the current iOS version and the two previous major versions, on iPhone sizes reasonably common in the United Kingdom at Expose. iPad is off by default. Mac Catalyst is off. visionOS is off. watchOS is off. tvOS is off. Adding any of those is a change. Notch, Dynamic Island, and safe-area handling on included iPhones is in scope for iOS UI development. We do not promise pixel identity with a design file that ignored safe areas. You will supply at least one physical device or accept simulator-plus-your-UAT as the path.
83. Annex C — store listing duties
You will supply subtitle, description, keywords, screenshots or approval of screenshots, privacy policy URL for the application (which is not this website’s Privacy Policy unless you deliberately reuse it, which we do not recommend), support URL, and age information. We will not invent medical claims. We will not stuff keywords deceptively. Localised listings are extras. You will respond to App Store questions that only you can answer, such as login credentials for a demo account. A missing demo account is a common rejection; it is your delay if you did not provide one after we asked.
84. Annex D — source hygiene
Commit messages should be intelligible. Binary secrets should not be committed. Licence headers, if your counsel requires, must be supplied as text. We will not paste a novel into every file. Code formatting will follow an agreed Swift formatter. Arguments about tabs after acceptance are not defects. Large generated assets should not choke the repository. If you insist on storing gigabytes of video in git, you accept the cost.
85. Annex E — meetings with Apple, legal and other advisers
If Apple seeks a call, we can attend as implementer if you purchase the time. We do not speak as your solicitor. If your solicitor seeks a call, the same applies. We will not waive privilege you may have with your solicitor by careless copying. You should keep legal advice in a separate tray. We will not pretend to be in-house counsel. If a regulator writes, you will tell us what we must preserve.
86. Annex F — handover checklist
A typical Dry checklist includes: repository access confirmed in your organisation; Apple account access revoked or reduced as you direct; TestFlight groups noted; listing state noted; known issues list; rebuild instructions; contact for a short warranty window. Items not on the purchased checklist are not implied. Hardware we bought for you will be delivered or collected as agreed. Hardware we own stays with us. Paper notes in Muirhead will be destroyed or returned according to the Privacy Policy.
87. Annex G — examples of reasonable skill
Reasonable skill for CRADERO LIMITED means: reading current Apple documentation at Expose, not shipping obviously deprecated APIs without a reason, not storing passwords in plaintext in code we write, not ignoring an entitlement we enabled, and not leaving a staging URL hardcoded after Rinse if Rinse is in scope. It does not mean omniscience about an unpublished Apple bug. It does not mean a zero-defect eternity. It does not mean matching a billion-pound competitor’s polish on a modest fee. Courts should read this annex as commercial context, not as an extra warranty schedule that expands the warranties section.
88. Annex H — fees worked example
If a statement of work is fixed at a named sum for a named mask, extra roles, extra locales, and extra integrations are extra. If time-and-materials, weekly notes will show hours at the named rate. Rounding may be to the nearest quarter hour. Travel is separate. Devices are separate if purchased. Apple’s developer fee is yours to pay to Apple. App Store commission is yours. Our invoice is for our services only. This example does not price your project; it shows how numbers relate so that later fog is less likely.
89. Annex I — data processing outline when we are processor
Subject matter: technical operations on personal data in staging or limited production support if purchased. Duration: the engagement plus deletion period. Nature: development, testing, limited debugging. Purpose: to deliver the services. Types: as you supply, ideally pseudonymous. Data subjects: as you determine. Obligations: UK GDPR processor terms summarised in the Privacy Policy and, where signed, a full addendum that prevails. Sub-processors: hosting and email as needed, plus named tools in the addendum. This outline is not itself an addendum. If you need the addendum, ask before Submerge.
90. Annex J — final identification
Contracting entity: CRADERO LIMITED. Trade: Apple app development services and the related native iPhone and iOS work described in these Conditions. Address: 25 Belhaven Park, Muirhead, Glasgow, Scotland, G69 9FA. Email: admin@cradero.technology. Telephone: +44 7411 525634. Website: https://cradero.technology. Law: Scotland, United Kingdom. These Terms and Conditions, including annexes A to J, form part of each engagement that incorporates them. They should be printed or saved by you at signature so that a later website edit does not confuse the historical print.
91. Additional provision on concurrent engagements
CRADERO LIMITED may serve more than one client at a time. We will not place the same person in a conflict where confidential information of two rivals would reasonably mix in a single head on the same Working Day without information barriers that we consider adequate. We do not operate a large chambers system. If you require exclusivity in a sector, that exclusivity must be purchased and time-limited. Absence of an exclusivity clause means we may develop iOS mobile solutions for another organisation, including one that competes with you, provided we do not use your confidential Negative Input. General Swift skill is not your property. Your product idea, if confidential, is.
92. Additional provision on staff absence and substitution
Illness, leave and resignation happen. We may substitute personnel of comparable competence. You may object on reasonable confidentiality grounds. You may not object merely because you preferred a personality. If a named person was a contractual assumption, which is rare, we will discuss a pause or a fee adjustment. We do not guarantee celebrity engineers. We guarantee the company’s method. If substitution would materially delay Dry, we will tell you. A short flu is not force majeure. A long incapacity of a sole specialist on an obscure API might be, if we cannot substitute in time.
93. Additional provision on comments, issues and ticket hygiene
Tickets should contain one subject. Screenshots should be cropped. Reproduction steps should be written. “It feels off” is not a defect report unless attached to a mask criterion. We may close tickets that are duplicates, obsolete, or wishes. Reopening requires new evidence. Priority labels you apply are requests; we may re-label according to risk. A blocker that is actually a change will be moved to the change tray. Ticket tools are not the contract. If the ticket system disagrees with the statement of work, the statement of work wins.
94. Additional provision on demo data and fiction
Demos should use fictional people. Names of film characters are still sometimes real people’s names; prefer obviously synthetic data. Photographs of staff should be licensed. Faces of strangers from the street should not appear. We will not scrape the web for faces. If your demo needs a map, we will use a sandbox key. If your demo needs payments, we will use a test merchant. Live keys in a conference demo are overexposure. If you insist, the risk is yours.
95. Additional provision on accessibility statements and public sector buy
If you must publish an accessibility statement, you write it. We can supply technical notes about what the application does. We will not sign your statement as if we were the public authority. If a buy is under a framework that contradicts these Conditions, we will either sign a negotiated instrument or decline. Silence after you send a 90-page framework is not assent. We need time to read. Time spent reading hostile paper may be chargeable if you asked us to consider it after engagement start.
96. Additional provision on comments to the press
Neither party will disparage the other in the press in a way that is false. Honest reviews of a product by users are not your or our disparagement. We will not leak your unreleased app. You will not claim we missed a date that Apple actually held. If a journalist calls, we will refer them to you unless the story is about us. We may correct factual errors about our address or our name. Muirhead is not a fictional town. G69 9FA is the postcode. Use it correctly.
97. Additional provision on electronic communications evidence
Email from admin@cradero.technology or from named company addresses may evidence instructions. Chat tools may evidence operational detail but are a poor place for acceptance. You should assume chats are discoverable in a dispute. Do not write things in chat you would not write on a print. We may export chats if a dispute begins. We will not secretly record voice calls. If a call is to be recorded, we will say so. Scottish intercept law is not a toy.
98. Additional provision on partial invalidity of App Store related promises
If a court holds that a promise about Apple’s behaviour is unenforceable because Apple is independent, the rest of the contract continues. The parties agree that any implied term that we control Apple is excluded. If a court holds the liability cap too low for a particular loss that cannot be limited, only that loss is affected, not the remainder of the cap for other losses. If a court holds a non-solicitation fee to be a penalty, the clause converts to a duty to pay proven recruitment cost instead.
99. Additional provision on survival of annexes
Annexes A to J and sections 91 to 100 survive to the extent they describe interpretation, identification, IP, confidentiality, liability, data, and notices. Operational annexes about baths cease to require future performance after Dry except for purchased support and warranty. Survival is not an excuse to keep working unpaid. Survival is an excuse to keep the legal print readable after the trays are washed.
100. Execution and counterpart
A statement of work may be signed by wet ink or by a recognised electronic signature. Counterparts may be exchanged by email as PDF. The contract is made when the last required signature is placed or when an authorised email states acceptance of a named version, whichever the statement of work allows. Pre-printed purchaser terms on the back of a purchase order are ineffectual unless we countersign those exact terms. You should initial these Conditions or incorporate them by URL plus version date. The version is the date shown at the top of the Terms and Conditions page on cradero.technology at the moment of incorporation, which you should save. End of Terms and Conditions.