Ask for Aperture library version/context, Mac environment, expected output, and safe non-private diagnostics first.
Customer enquiry readiness · static only
App support questions get a safe route before the form goes live.
This page gets HighCaliberApps.co.uk ready for a future customer enquiry form on the app-catalogue side. It plans product-fit questions, support triage, no-private-file wording, and fulfilment boundaries while keeping live forms, uploads, checkout, analytics, CRM, and customer-data collection disabled.
Disabled by design
No form handler is connected.
Use this page to approve the shape of the future enquiry form before any customer data route is switched on.
Product routing
Each app enquiry should start with fit and safety.
The future app-side form should route questions by product and customer need, not by a generic contact bucket. Recovery questions, MindBridge questions, mobile-preview questions, and product-fit questions each need a slightly different triage path.
Ask for Bento-style database context, target export format, and whether a business migration checklist is needed.
Ask for backup type, device era, expected categories, and whether the issue is contacts, messages, calendar, or inventory.
Ask for mind-map/source format, target workflow, platform, and whether the need is import, edit, outline, or report output.
Future field map
Field plan only — no data collection today.
These are display cards rather than live inputs. They describe what the future app-side enquiry form should collect once approved.
Reply handling only; no identity document request.
Requires final consent and retention wording before live use.
Aperture Library Rescue, Bento Database Rescue, BlackBerry Backup Extractor, MindBridge, Android preview, or general catalogue.
Will this work, install/download, licence/order, export result, support, or business route.
Mac, Windows, Linux, Android, iPhone/iPad, app version, and OS version when useful.
Text-only first contact. Do not attach private libraries, backups, databases, passwords, or payment details.
Customer safety wording
Draft wording for the future app enquiry form.
Draft activation wording: “Please do not send private files, full backups, passwords, payment-card details, or sensitive personal material in this first message. Start with product name, platform, source-file type, and a short description. We will only ask for further diagnostic material if it is needed and a safe reviewed support route has been agreed.”
This wording is a readiness draft only and needs final privacy/legal review before any live app enquiry form is enabled.
Launch gates
Still disabled until the customer-data route is approved.
No form handlerNo file uploadsNo CRM connectionNo email automationNo analytics/trackingNo checkout linkNo customer account collectionNo private-file request
Privacy and retention summary
Draft wording is ready for solicitor review.
Future app enquiry forms should collect only the minimum information needed to reply, route support, and protect the service: name, reply email, enquiry type, product, platform, or route, safe technical context, and a short text message. First contact should not request passwords, payment-card details, private files, full backups, identity documents, or sensitive personal material.
Routine pre-sales enquiries are proposed for deletion or anonymisation after up to 12 months; support enquiries after up to 24 months; order, refund, complaint, dispute, or required business records for longer where legally or operationally needed. The full draft notice remains subject to solicitor review before any live form is enabled.