01
Information we may collect
We may collect your name, company, email, phone number, project requirements, business location, preferred service, messages, meeting notes, support requests, billing details and technical information needed to plan or support a project.
02
Project and technical data
Clients may provide website content, product data, workflows, hosting details, domain records, API keys, app store information, screenshots, error logs or sample records. We use this information for communication, planning, development, testing, deployment and support.
A delivered application may process account profiles, authentication records, role assignments, business transactions, uploaded files, device information, notification tokens and realtime activity needed for its agreed features. The specific data model, access rules and retention needs are defined for each client system.
03
Application accounts and managed data
Where a project includes user accounts, information may be stored in a managed PostgreSQL database and associated object storage. Authentication services may process identifiers, password verification data, session tokens, one-time-code events and recovery activity. Passwords should not be available to application administrators in readable form.
Realtime features may transmit record changes and presence or channel events to authorised users. Access should be restricted through database policies, server-side permission checks and the roles agreed for the product.
04
How we use information
Information helps us respond to enquiries, prepare quotations, understand requirements, provide services, configure systems, process payments, deliver support, maintain security and communicate relevant project updates.
05
Global providers
Digital services may involve trusted hosting, cloud, domain, email, payment, analytics, messaging and app-store providers operating in different countries under their own privacy and security terms.
06
Data minimisation and access
We aim to collect only what is needed. Access is limited to people and providers who require the information to perform agreed work. Clients should avoid sending unnecessary sensitive information and should share credentials only through approved secure channels.
07
Security
We use reasonable technical and organisational measures, including encrypted connections, database access policies, protected sessions, careful credential handling, environment separation and responsible project storage. Sensitive secrets are kept outside application source where the delivery environment supports it.
No online service can be guaranteed completely secure. Clients should maintain strong authentication, review staff access, protect administrative accounts and devices, and report suspected misuse promptly.
08
Cookies and technical data
Hosting and security systems may process browser type, device information, visited pages, referral source and approximate location to operate, protect and improve the site. See our Cookie Notice for more detail.
09
Retention
We keep information only as long as reasonably needed for enquiries, projects, support, accounting, legal obligations, maintenance or legitimate business records. Information may then be deleted, anonymised or securely archived where practical.
10
Client ownership and confidentiality
Client project data remains confidential and is not sold. Public-facing work may be showcased only when appropriate and without exposing private records, credentials or non-public system details.
11
Your choices
You may request access, correction, update or deletion of personal information, subject to identity verification, active project needs, backups, legal obligations and records we must retain for legitimate business purposes.
12
Updates
We may update this policy as our services, providers, security practices or legal requirements change. The latest version will appear on this page with its revision date.