Your data should have a clear job.

Marlo is operated by Built by James Ltd, company number 11337649, registered in England and Wales. Our registered office is One Eastwood Harry Weston Road, Binley Business Park, Coventry, England, CV3 2UB.

For questions or data-protection requests, email hello@builtbyjames.co.uk. Our ICO registration reference is ZB095666. Built by James Ltd is the controller for account, billing, security and service-administration data. When a customer imports Shopify Partner data for reporting, we generally process that data on the customer's instructions under our Data Processing Addendum.

• Account and team data: name, email address, profile details, authentication identifiers, organization membership and role. If you choose Google sign-in, Google supplies the identity details you approve to Clerk.
• Billing data: billing name, address, tax identifiers, Stripe customer and subscription identifiers, invoices and payment status. Stripe receives and stores complete payment-card details; Marlo does not.
• Shopify Partner data: Partner organization and app identifiers, app and shop names, shop domains and countries, subscription and lifecycle events, transaction and payout records, uninstall reasons and reporting notes entered by your team.
• Connection and security data: encrypted Partner access tokens, short token hints, API-key hashes, audit events, webhook identifiers, request metadata, IP address, browser or device information and error logs.
• Website journey data: page path, selected campaign parameters, signup call-to-action and a random visit identifier created in memory for the active page session. If you choose signup, that identifier is handed to the Marlo app so aggregate signup, trial, activation and paid outcomes can be measured. Marketing event records do not include your email address, raw referrer, IP address or user-agent, although hosting providers may process request-level data in operational logs.
• Communications: messages and information you send when requesting support, exercising a right or discussing the service.

Please do not place unnecessary sensitive or special-category personal data in customer notes, uninstall reasons or support messages.

• Contract: to create accounts and teams, authenticate users, connect the Shopify Partner API, produce reports, provide support, operate subscriptions and deliver the service you request.
• Legitimate interests: to secure Marlo, prevent abuse and fraud, maintain audit trails, diagnose failures, measure whether core product workflows function and improve reliability. We balance these interests against your rights.
• Legitimate interests: to measure, in aggregate, which first-party pages and signup calls-to-action lead to a functioning Marlo workspace, trial, activation and paid subscription. This measurement uses a random first-party visit identifier rather than advertising profiles or third-party trackers.
• Legal obligation: to maintain tax and accounting records, respond to lawful requests and meet regulatory obligations.
• Consent: where we introduce an optional use that legally requires consent. You may withdraw consent without affecting earlier lawful processing.

We do not sell personal data, use it for third-party advertising or make solely automated decisions that produce legal or similarly significant effects.

We receive data directly from you and your team, from Clerk and an optional Google sign-in connection, from Stripe when you manage billing, and from Shopify when an authorized team administrator connects a Partner organization. We also generate service, security and audit records as Marlo is used.

• Clerk: authentication, organizations and member identity.
• Convex: application database, backend functions and scheduled processing.
• Vercel: application hosting, delivery and request-level operational logs.
• Stripe: checkout, subscriptions, invoices, tax calculation and the customer billing portal.
• Google: optional identity provider when you choose Google sign-in.
• Shopify: the customer-authorized source of Partner reporting data.

We may also disclose information to professional advisers, regulators, courts, law enforcement or a purchaser of the business where the law permits and appropriate safeguards apply. Team administrators can access information belonging to their organization.

Some providers may process information outside the UK. Where a restricted transfer applies, we rely on an applicable UK adequacy regulation or contractual safeguards such as the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, together with the provider's security commitments.

• Account, team and imported Shopify reporting data is kept while the service is active. Following closure, we aim to delete or anonymise it within 90 days unless it must be retained for a dispute, security investigation or legal obligation.
• Billing, invoice and tax records may be kept for up to six years after the relevant accounting period.
• Support correspondence and security records are retained only for as long as reasonably needed for the issue, audit trail or legal claim.
• First-party marketing event records are deleted after 180 days. The marketing site does not persist its random visit identifier in a cookie or browser storage. If you choose signup, the acquisition record passed to the app is valid for up to 30 days and is removed from browser storage after it is attached to a workspace.
• Residual encrypted backups are removed through provider rotation rather than being restored for ordinary business use.

Marlo uses authentication cookies and similar storage required to sign you in, secure a session, carry the first-party source you chose into the workspace and remember the plan and billing interval selected while completing signup. The marketing site's random visit identifier exists only in memory and is not placed in a cookie or browser storage. We do not place advertising or cross-site behavioural-analytics cookies. If we add non-essential persistent device storage, we will provide an appropriate consent control before using it.

You can block cookies through your browser, but required authentication or checkout features may stop working. The current inventory and durations are on our Cookies and Device Storage page.

Measures include encrypted Partner credentials, transport encryption, signed webhooks, organization-scoped authorization, role checks for administrative actions, hashed API credentials, restricted production keys and audit logging. No online service is risk-free; please report suspected misuse to hello@builtbyjames.co.uk. See our security page for the current product controls.

Depending on the circumstances, you may ask for access, correction, deletion, restriction, portability or an objection to processing. You may also withdraw consent and complain to the UK Information Commissioner's Office. We may need to verify your identity and, for customer-controlled Shopify data, coordinate with the relevant customer administrator.

Email hello@builtbyjames.co.uk to exercise a right. You can also contact the ICO.

Send a complaint to hello@builtbyjames.co.uk with the subject “Data protection complaint”, or write to our registered office. We will acknowledge it within 30 days, investigate it, keep you informed without undue delay and communicate the outcome. This process does not prevent you from complaining to the ICO at any time.

We will update this notice when Marlo's data practices materially change and will show the revision date at the top. Where a change significantly affects your rights, we will provide an additional notice through the service or by email where appropriate.