Skip to content

Gridsmith

Privacy Policy

How Gridsmith Ltd collects and uses personal data through this website, enquiries, optional analytics and client work: who receives it, where, for how long, and how to exercise your rights.

Version 2.13 | Effective on first publication with the replacement website at gridsmith.uk | Reviewed 2026-11-06 | Adopted by Gridsmith Ltd on 2026-11-06

Contents

1 Who we are

Gridsmith Ltd is the controller of personal data used for our website, enquiries, business administration and client relationships. Our contact details are in section 15. Where we process personal data on a client's behalf for a project, we act under its instructions and agreed data-processing terms; the client remains responsible for its own privacy information.

This policy covers website visitors, people who contact us, clients and their representatives, and people whose personal data remains in historical records.

2 Information we collect

Depending on your dealings with us, we collect:

your name, contact details and organisation;

enquiry details, including the service, budget, timetable, publishing requirements and any links you provide;

correspondence, quotations, contracts, invoices and payment records;

project materials and personal data within them;

technical request information, such as IP address and browser details, processed by our website hosting and content management providers for delivery and security; and

if you allow optional analytics, the information described in section 5.

We receive information from you, people acting for you and project participants. Payment providers supply transaction and reconciliation information. Our Contact and Press enquiry forms collect your name and email, the project details you enter and any optional organisation, telephone number or links you provide. The Contact form can include the service you selected before opening it. The Press form asks questions about your publishing project and may collect links to source material. It does not accept file uploads. We use a submission reference to recognise a retry and avoid duplicate records. The owner or sales department uses enquiries to reply and, where appropriate, prepare a quotation. Contact links also let you send email or WhatsApp messages through your chosen service. Direct enquiries are not currently copied into other systems.

Where you work with us through a freelancing platform such as Freelancer.com, your account, project messages, files and payments are held on that platform under its own terms and privacy notice, and we use them through our account there to provide the work. We do not keep a separate client database. We copy platform records only where the work or the law needs it: for example, files we download to work on, briefs and files shared with delivery agencies (section 6), and invoices and payments in our accounting records. Those copies follow section 8. Records that stay on the platform are kept and deleted under the platform's own rules; we cannot delete them from it.

Please do not send special-category information (such as health, religious or political details), criminal-offence information, passwords or payment-card details through website enquiries or linked files. If agreed work requires sensitive personal data, contact us first so we can agree a suitable secure channel and establish the additional lawful conditions and safeguards. Relevance to a project does not by itself authorise its use.

We assess unsolicited sensitive material and restrict, return or remove it as appropriate.

Historical records include third-party review data previously copied from Freelancer.com: review text, star ratings and, in some cases, a first name or username and the type of work. Removing a name does not necessarily make this information anonymous. Sections 6 and 8 explain where copies remain accessible and how retention is handled.

3 Why we use personal data

We use personal data to answer enquiries, prepare quotations, deliver and support projects, manage payments and business records, handle complaints and rights requests, protect our systems, understand how our website is used where you allow optional analytics, and comply with the law.

4 Lawful bases

Purpose — Lawful basis

Enquiries, quotations and project delivery for an individual — Steps you request before a contract, or performance of our contract with you

Business enquiries and dealings with a client's representatives — Legitimate interests in responding to enquiries and managing client relationships

Accounting and tax records — Legal obligation

Necessary contract and dispute records — Legitimate interests in establishing or defending legal claims

Website security and spam prevention — Legitimate interests in protecting our systems and visitors

Complaints, data-protection rights requests and reviewing or removing historical personal data to meet data-protection duties — Legal obligation

Optional website analytics — Consent

Remembering your cookie choice in the gs_consent cookie on your device; your browser also sends this cookie with requests to our website hosting provider. We do not maintain a separate log of individual cookie choices — Legitimate interests in respecting your choice, including refusals and withdrawals

We consider the impact on individuals when relying on legitimate interests. You need not provide information, but without necessary contact or project details we may be unable to reply, quote or provide the service. We do not make solely automated decisions with legal or similarly significant effects about you.

5 Optional website analytics

Optional analytics run only on a version of our website whose cookie request offers them. If the website shows a cookie notice instead, no analytics service is in use and the rest of this section does not apply.

When they are offered and you allow them, we use Google Analytics 4, provided by Google, and PostHog, provided by PostHog, to count the pages visited and how visitors arrive at the website, as statistics. You can allow or refuse each one separately, and both stay off unless you allow them. The Cookie Policy lists the cookies and browser storage they use and explains how to change your choice.

When a service runs, its provider receives your IP address, which it uses to estimate your approximate location; the address of each page you visit, without any query or fragment; the website you came from; your browser and device type; and a random identifier stored on your device. Google Analytics does not store IP addresses, and we set PostHog to discard them. We use PostHog to record page views. Google Analytics records page views and standard first-visit, session and engagement information. We use neither service for advertising or personalised-advertising features, Google signals, session recording, heatmaps, surveys or automatic capture of what you click, scroll or type. We do not link analytics to your name or contact details. Pseudonymous information is not necessarily anonymous.

Before we switch either service on, we accept its provider's data-processing terms and turn off its data-sharing settings, so that Google and PostHog process this information for us under those terms. Google Analytics deletes user-level and event-level data once it is two months old, in Google's monthly deletion process; aggregated statistics that do not identify you are kept longer. PostHog keeps event data for one year under our plan; whether older data is erased or kept in other storage is governed by PostHog's terms, and you can ask us to have your PostHog records deleted (section 10).

Withdrawing consent stops further collection in every open page of our website and removes the services' cookies and browser storage from your device. It does not erase what a provider has already received. Analytics records are held under the random identifier rather than your name, and withdrawing removes that identifier from your device, so if you want to ask about your records, contact us before you withdraw or tell us the dates and pages of your visits.

We may later use AI-assisted analysis of aggregated analytics reports to support human judgement. Before doing so we will update this policy. Analytics consent does not authorise sending raw visitor, enquiry or project data to an external AI service.

6 Who receives information

We share only what is needed for the relevant purpose, with these categories of recipient:

Website and email hosting provider: hosts our website and email, processing website requests, messages and security records.

Messaging services: process the messages you choose to send us. WhatsApp messages are handled by WhatsApp, which also processes them under its own terms. Messages sent this way are separate from enquiries submitted through our website forms.

Analytics providers: Google (Google Analytics 4) and PostHog, only if you allow them, as described in section 5.

Content management provider: manages published content and images. Requests to its content services may disclose technical request information; enquiries are not sent to it. Its document history for our development dataset previously held historical personal data described in section 2 that was retrievable without signing in. Recent checks did not retrieve the known historical records; this does not establish that all copies have been erased. The remaining holdings and retention period have not been verified.

Freelancing platforms you choose to work with us through, such as Freelancer.com: receive our messages, quotations and delivered files for your project, as independent controllers under their own terms, which may involve processing outside the UK.

Supabase processes form requests and stores enquiries for us in our primary database in Ireland. It also processes technical request and security information.

Resend processes internal notification emails for us. A notification contains the enquirer’s name and contact details, any organisation and telephone number supplied, the division, enquiry type, any selected service and a record reference. It omits the enquiry message, Press answers and manuscript links. Our email provider delivers it to our internal enquiries inbox.

Historical database and email delivery records: copies from earlier processing may remain with these providers, in email and in developer-created backups. These may include earlier enquiry and notification records, technical logs and backup copies. The precise remaining holdings and applicable provider retention periods have not yet been verified; this policy does not assert that those records have been erased. Retained personal data remains subject to applicable purpose, confidentiality, security, retention and rights obligations.

Source-code repository provider: historical personal data described in section 2 remains in our repository history and earlier versions. The repository was previously publicly accessible; it is now private, with access restricted through the provider's account controls. This does not establish that copies previously accessed or retained elsewhere have been erased.

Payment providers and our bank: handle customer payments. They receive transaction and billing information and any payment, device or fraud-prevention details they collect directly. We receive payment status and reconciliation records. There is no card checkout on this website.

Our external accountant: receives necessary contact, invoice, payment and supporting financial records, rather than manuscripts or full enquiry messages merely to record a payment.

Delivery agencies: receive the contact details, briefs, communications and project files needed for authorised work, subject to confidentiality, rights and applicable data-processing protections. Gridsmith remains responsible for its agreed services.

Our processors act under data-processing terms. Banks, payment providers and professional advisers may act as independent controllers for their own payment, fraud-prevention, professional or legal duties; their role depends on the service. We can tell you the name of any recipient on request.

We may disclose information where legally required, to protect legal rights, or in a genuine sale or reorganisation of the business. We do not sell personal data to advertisers or data brokers.

7 International transfers

Our website is hosted in the European Economic Area, which is covered by UK adequacy regulations. Company access is restricted to authorised personnel, and the owner reports no current overseas access by company personnel. This does not mean that our email, messaging and other providers and their subprocessors process information only there. Our hosting, content management, analytics and messaging providers and delivery agencies may process or permit access to personal data in other countries. Historical database and email delivery records may also remain subject to international provider processing; their current locations and retention have not yet been verified.

When analytics are switched on, Google may process analytics information in the United States, and PostHog keeps analytics information in its European Union hosting and may permit access from other countries under its data-processing terms. Some of our delivery agencies are in Pakistan, which is not covered by UK adequacy regulations, and some are in the United States, where those regulations cover only organisations certified under the UK Extension to the EU-US Data Privacy Framework. Others are in European countries; not every European country is covered.

The primary enquiries database is in Ireland. Supabase and its subprocessors may process technical information or access data outside the UK and EEA. Resend processes notifications and delivery records in the United States. For transfers outside the UK, including overseas access to project files, we require applicable UK adequacy coverage or appropriate safeguards. For form processing, we require applicable processor terms and transfer safeguards with Supabase and Resend before activating intake. Our hosting provider's data-processing terms set out the transfer safeguards for its services, and our analytics providers' data-processing terms do the same for theirs. A transfer to a US recipient whose certification under the UK Extension to the Data Privacy Framework covers it relies on the UK's adequacy regulations. Transfers involving other recipients, including any continuing processing of historical records, require applicable adequacy coverage or appropriate safeguards. The specific arrangements for relevant email, messaging, content management and historical-data processing require verification; website hosting in the European Economic Area does not by itself establish those arrangements. For agencies without adequacy coverage, the required route is the UK International Data Transfer Agreement or appropriate EU standard contractual clauses with the UK Addendum, supported by the required data protection test and any additional safeguards. We require the applicable arrangements before access begins.

Payment and professional providers may also process internationally under their applicable terms and duties. Contact us for details or a copy of relevant safeguards, with confidential information redacted where necessary.

8 Retention

We keep information only as long as needed for its purpose. The owner manages retention, deletion, backups and privacy requests. The following documented retention schedule remains the basis for those duties; its current applicability to particular historical holdings and providers requires confirmation:

Records — Retention

Enquiries that do not become projects, including form records, email and messaging correspondence and retained internal notification emails — 12 months from receipt or last contact, whichever is later

Identified spam — 30 days

Necessary project and contract records, including the final delivered set — Six years after the end of the financial year in which the project ends

Accounting and tax records — Six years after the end of the relevant financial year, or longer where tax law requires

Signed rights transfers and waivers — While the rights are relied on, then six years

Complaints — With the project record, or two years after closure if there is no project

Project working files — Return or deletion within 90 days after the project ends unless otherwise agreed

Optional analytics records, when switched on — Google Analytics: user-level and event-level data deleted once two months old, in Google's monthly deletion process; aggregated statistics that do not identify you are kept longer. PostHog: event data kept for one year under our plan. Cookies and browser storage on your device: as set out in the Cookie Policy

Our documented schedule calls for monthly enquiry and spam deletion reviews, annual reviews of long-term records after their periods end, and quarterly working-file clearance checks. These are review duties, not a statement that review cycles or deletions have been completed; deletion is not represented as automated. Agreed client data-processing instructions also apply. A documented legal hold may extend retention of relevant records, with restricted access and further review.

We retain only proportionate evidence of rights requests and preferences for accountability, disputes and respecting objections. We do not keep records of individual cookie choices; we keep dated versions of our cookie request and policies to show how consent is asked for. The historical third-party data described in section 2 has been removed from our current website source code and deleted from the active development content dataset. Copies remain in repository history and earlier versions and a development backup; remaining copies in Sanity document history have not been verified. The repository is now private; this does not establish that copies previously accessed or retained elsewhere have been erased. Their remaining retention periods have not been verified. The documented schedule requires monthly review and review when a removal request or source change requires it, with removal when no longer needed or lawful. Continued retention needs an applicable lawful basis; the existence of a historical copy does not itself establish one. This is not a claim that every copy has been erased.

Providers may retain technical, security and backup records under their own operational and legal retention rules. We have not verified the currently applicable periods for historical database and email delivery records, other provider logs or backups, or developer-created backup copies. The owner has not established a new company backup system; this does not mean that provider-managed backups are absent, and no tested backup/restore system is claimed. Deleting a main record does not immediately erase every backup; copies awaiting expiry must remain protected and unavailable for ordinary use, and applicable deletions must be reapplied after restoration. Contact us about a particular record or retention period.

9 Security

We use appropriate technical and organisational measures, including access controls and confidentiality requirements. The forms use encrypted connections. The intake checks submissions, limits repeated requests and restricts database and queue access to authorised systems and personnel. We keep the full enquiry in the enquiry store and limit the information included in internal notification emails. No internet service can guarantee absolute security. We assess personal-data breaches and notify the regulator and affected people where the law requires.

10 Your rights

Subject to the law, you can request access, correction, erasure, restriction and portability of personal data, object to processing based on legitimate interests, and withdraw consent. You can object to direct marketing at any time, and we will stop.

Contact us using section 15. We may need to confirm your identity. We respond without undue delay and normally within one month, explaining any lawful extension or pause. Erasure is subject to exceptions, including necessary legal duties or claims; we explain any refusal and your complaint rights. Requests may involve our processors as well as our own records, including historical copies. Removing a copy we hold does not remove the original record on an independent third-party platform. Withdrawal stops future consent-based processing without affecting its previous lawfulness; retaining existing personal data still requires a lawful basis.

11 Marketing

We do not currently send marketing messages. An enquiry does not subscribe you. If we introduce electronic marketing, we will use consent or an applicable lawful exception, identify us and provide a simple way to stop further messages.

12 Cookies

See our Cookie Policy for the cookies we use and your choices.

13 Data-protection complaints

Complain by email or post using section 15; no special form or wording is required. We acknowledge complaints within 30 days, investigate, keep you informed and explain the outcome without undue delay.

You can also complain to the Information Commission, the UK data protection regulator, at ico.org.uk (opens in a new tab). The regulator usually expects you to contact the organisation first, but you do not have to.

14 Changes

We update this policy when our processing or legal obligations change, with further information or consent where required. A later policy does not retrospectively authorise earlier processing.

15 Contact

Gridsmith Ltd

30 Briarfield Road, Farnworth, Bolton, BL4 0HD

contact@gridsmith.uk