Customer data processing terms

These terms are incorporated into the customer terms. Our privacy notice describes separate controller activities and retention.

Parties and scope

MJP Tech LTD, company 17018987, 22 Will Meadows, Freystrop, Haverfordwest, Pembrokeshire, Wales, SA62 4AZ, supplies TriggerFlow. The customer identified by the accepted signup or order controls personal data it places in its automations and hosted service. Where the customer is itself a processor, it confirms authority from its controller. MJP Tech processes that customer data to provide the configured service. Account administration, billing and MJP Tech's own security/legal purposes are addressed separately in the privacy notice.

Processing schedule

Item	Agreed scope
Purpose and activities	Operate customer-selected workflows and device management: receive, store, retrieve, display and transmit configured device status, profiles, variables, OCR results, screenshots, diagnostic evidence and integration results; provide requested troubleshooting and delete or return the data.
People and data	Customer staff, account users and people whose information appears in customer-authorised workflows/screens. Data can include names, business contact information, account/device identifiers, activity records, screen/document text and images. The customer selects content and must minimise it. Credentials require the dedicated protected feature.
Duration	The service term and the bounded return/deletion period below. Feature retention settings and the privacy notice's schedule apply during the term.
Excluded default uses	No general authorisation for special-category/criminal-offence data, covert monitoring, children-focused processing or significant automated decisions. A customer requiring such processing must agree a suitable scope and safeguards first.

Responsibilities

The customer determines lawful purposes, gives required notices, manages user/device permissions and provides documented instructions. Instructions include the order, these terms and deliberate feature settings; changes can be recorded through the privacy contact. MJP Tech will process data only on documented customer instructions, including for international transfers, unless UK law requires otherwise. We will immediately flag an instruction we consider contrary to applicable data-protection law and inform the customer before legally compelled processing unless prohibited.

MJP Tech will restrict access to authorised people bound by confidentiality, implement appropriate technical and organisational measures meeting Article 32, support individual-rights requests and assist with security, breach notification, impact assessments and prior regulatory consultation under Articles 32–36, taking account of the processing and information available to us. It will notify the customer of a personal-data breach without undue delay and provide available facts and updates; the customer decides its own regulatory notifications. MJP Tech will provide compliance information and permit proportionate audits/inspections, protecting other customers' data. These terms do not remove either party's statutory responsibilities.

Security measures include encrypted transport, access controls, protected credentials, explicit remote-control permissions, support-message review, restricted background sharing, event retention, recovery protection and supervised erasure. Older installed versions may require an update to apply the current defaults. These measures are not a claim of certification or zero provider access.

Subprocessors and transfers

The customer authorises the listed providers for their stated scope. MJP Tech will impose equivalent Article 28 data-protection obligations on subprocessors, check sufficient guarantees and remain liable to the customer for their performance. We give fourteen days' notice of material additions/replacements and a route to object on data-protection grounds. We will investigate objections before affected processing begins; if unresolved, we will agree an alternative or suspend the affected service.

Provider	Scope / known locations
Microsoft Azure	Hosting, database and monitoring: Canada Central; credential vault: East US. Transactional email: configured Europe, with delivery metadata in Canada Central. Provider support/subprocessor locations can differ.
Cloudflare	Proxy/security for licence and dashboard traffic; global network. Marketing apex/www are DNS-only.
OpenAI	Only customer-instructed AI features using company-managed API access; relevant prompts/images/results. Checked project: Global residency and standard retention; optional sharing disabled. Customer-owned keys/assistant accounts are under their separate arrangements.
GoDaddy / Microsoft 365	Customer-authorised support messages in the support mailbox. Exact tenant residency and provider recovery/holds were not independently verified. No separate archive/backup service is used.

Netlify enquiries, Stripe account billing and public YouTube tutorials are separately described controller activities, not blanket authorisation to send hosted customer content to them. Customer-selected alert destinations receive only the configured content. A restricted international transfer requires an applicable lawful route; a server region alone does not establish one. We maintain a supplier/transfer record and do not promise UK-only processing.

Return and deletion

At termination the customer chooses return or deletion of all customer personal data, with deletion of existing copies unless UK law requires storage. Contact us before closure to arrange a secure return. We offer a secure export and complete active-store removal within thirty days of confirmed scope, subject to a specific legal retention duty. We revoke access and remove associated content through a supervised deletion process, keeping only required accounting/legal records separately. Protected recovery copies remain beyond ordinary use and expire on documented cycles: database fourteen days, app snapshots thirty days and vault recovery ninety days after soft deletion. We reapply deletion decisions after a restore and disclose failures or exceptional retained copies rather than certifying unverified erasure. Customer-held device/export/integration copies remain under the customer's control.

Privacy contact: james@triggerflow.co. The order identifies the customer's authorised contact. These processing terms form part of the accepted customer agreement and bind MJP Tech and the customer for the processing described here. They take priority over conflicting general service terms on data protection.