1. Controller identity and geographic scope
STARLIGHT PORTER LTD is the controller of personal data processed through https://starlightporter.wiki and in connection with AI software development, machine learning software solutions, intelligent mobile applications, generative AI app development, AI automation software, computer vision applications, natural language processing apps, recommendation engine development, deep learning solutions and intelligent data processing. The company operates from 911 Green Lanes, London, United Kingdom, N21 2QP. Operational correspondence on privacy matters should be directed to tech@starlightporter.wiki or +44 7411 527869.
This policy applies to visitors, prospective clients, contracting clients, suppliers, job applicants and any other natural person whose information reaches the London yard in the course of a commercial or pre-commercial relationship. It is written for the laws of the United Kingdom, including the UK GDPR and the Data Protection Act 2018, and for the Information Commissioner’s Office as the relevant supervisory authority. Where a project involves a controller established in the European Economic Area, additional transfer and processor terms are documented in the relevant statement of work rather than implied by website use alone.
The registered operating address is used as the establishment for determining the lead supervisory logic inside the United Kingdom. Remote delivery to other UK nations does not relocate the controller. If a client requires a named data protection officer under Article 37 UK GDPR, that appointment will be confirmed in writing; otherwise privacy queries are handled by the intake desk and escalated to instructed counsel where the risk grade requires it.
2. Categories of personal data
Identity and contact data include names, job titles, employer names, email addresses, telephone numbers, postal addresses and the content of intake tickets submitted through the load form. Technical data include internet protocol addresses, approximate location derived from IP, browser type, device class, referral path, pages viewed, and timestamps. Commercial data include contract references, load identifiers, invoicing contacts, bank details used only for payment of fees, and records of services scoped or refused.
Project data may include personal data contained inside client materials: customer lists, staff identifiers in logs, images for computer vision application work, voice or text samples for natural language processing apps, behavioural events for recommendation engine development, and labels used in machine learning software solutions. Such material is processed as a processor or as a controller depending on the written allocation in the contract. Website use alone does not grant a licence to upload special category data.
Special category data and criminal offence data are not sought through the public website. If a deep learning solution or intelligent data processing engagement would require health, biometric, trade union or similar data, a separate legitimate assessment, additional lawful basis and heightened security grade are required before any such material is accepted onto the belt.
3. Sources of data
Data is collected directly when a person submits the intake form, writes to the published email, telephones the yard, attends a scheduled meeting, or signs a statement of work. Data is collected indirectly when a browser loads pages on this domain, when a professional intermediary introduces a prospect, when a payment provider confirms a transaction, or when public corporate registers are checked to verify a contracting entity.
We do not purchase marketing lists of private individuals. We may review publicly available professional profiles to confirm that an enquiry is genuine and that the organisation named on a ticket exists. Automated scraping of social networks for profiling is not part of the yard method.
4. Purposes and lawful bases
Responding to enquiries and preparing proposals is processed under legitimate interests in operating an AI software development practice and, where steps are taken at the request of the data subject prior to entering a contract, under the contract basis. Performing a paid engagement, issuing invoices, and keeping delivery records is processed under contract and under legal obligation for tax and accounting.
Operating, securing and improving the website is processed under legitimate interests in keeping a reliable public yard and under consent where a non-essential cookie is used. Defending legal claims, screening fraudulent intake, and maintaining information security is processed under legitimate interests and, where applicable, legal obligation.
Direct electronic marketing to a sole trader or to a named person at a corporate subscriber follows the Privacy and Electronic Communications Regulations. Where consent is required it is recorded. Where the soft opt-in conditions are met, a simple opt-out is honoured. Marketing is never a condition of receiving a grade note on a genuine load.
Training of our own internal tools on a client’s personal data is not a default purpose. If a statement of work expressly permits use of anonymised or aggregated residuals, that permission is construed narrowly and does not extend to republishing identifiable records.
5. Legitimate interests assessment
The yard’s legitimate interests include conducting a professional services business, preventing misuse of intake channels, keeping evidence of what was agreed, and improving the screening method using non-identifying operational metrics such as time-to-first-grade and fraction mix. Those interests are balanced against the right of a visitor not to be profiled in a surprising way, the right of a client employee not to have their correspondence treated as marketing fuel, and the right of data subjects inside a client dataset not to be used for unrelated model experiments.
Where the balance is close, we minimise: fewer fields on the public form, no silent third-party advertising pixels as a default, and contractual bans on using production personal data as a casual training corpus. A person may object to legitimate interests processing by writing to the published email. An objection to all processing required to perform a live contract cannot usually be honoured without terminating the load, which will be explained in the reply.
6. Cookies and similar technology
Short-term storage required to keep the site stable may be set without a marketing overlay. Any non-essential cookie, local storage key or tracking pixel is described in the cookie policy at cookie-policy.html and is not treated as consent merely because a person continued to scroll. Consent, where used, is specific, informed and as easy to withdraw as to give. Queries about cookies may be sent to tech@starlightporter.wiki.
7. Recipients and processors
Personal data may be disclosed to professional advisers, insurers, banks, accountants, hosting and email infrastructure providers, analytics tools that have been approved after a processor review, and subcontractors named in a statement of work for a specific fraction such as specialised labelling for a computer vision application. Each processor is bound by written terms requiring confidentiality, security, deletion or return, and a ban on independent commercial exploitation of the data.
We do not sell personal data. We do not trade enquiry lists. A request from a competent United Kingdom authority is assessed for legality before disclosure. International recipients are used only with an appropriate transfer tool as described below.
8. International transfers
The controller is established in the United Kingdom. Some infrastructure or specialist subprocessors may be located in the European Economic Area, the United States, or another country. Where the destination is not covered by a UK adequacy regulation, we use the UK International Data Transfer Agreement or the UK Addendum to the EU Commission standard contractual clauses, plus supplementary technical measures such as encryption in transit and at rest, access logging, and minimised fields.
Client project data is not moved to a new country merely for convenience. If a generative AI app development component relies on a model hosted outside the United Kingdom, that location is disclosed in the technical design so the client can decide whether the grade is acceptable. Website visitors should assume that basic hosting logs may be processed in the region of the content delivery node that served the page.
9. Retention
Unsuccessful enquiries are retained for up to twenty-four months so that a repeated ticket can be recognised and so that the yard can defend a complaint about what was said at intake. Contracts, invoices and tax records are retained for at least six years from the end of the relevant accounting period. Project archives follow the deletion or return timetable in the statement of work, with a short additional period for backup expiry.
Security logs are kept for a rolling period sufficient to investigate incidents, typically ninety days unless an investigation is open. Recruitment records for unsuccessful applicants are kept for twelve months unless a longer period is agreed. When retention ends, data is deleted or irreversibly anonymised so that it can no longer be attributed to a living person.
10. Security measures
The yard applies access control, unique credentials, encryption in transit for the public site and for remote administration, least-privilege accounts, and a requirement that client datasets for machine learning software solutions sit in segregated workspaces. Staff and contractors handling personal data are bound by confidentiality. Portable media are avoided. Production secrets are not placed in public repositories.
No method is perfect. A person who suspects unauthorised access should write immediately to the published email with the time, the system, and any ticket reference. Incidents meeting the legal threshold are notified to the Information Commissioner’s Office and to affected individuals in accordance with UK GDPR Articles 33 and 34.
11. Automated decision-making
The public website does not make solely automated decisions that produce legal or similarly significant effects about a visitor. Recommendation engine development and other model-based systems built for clients may include automated scoring inside the client’s own environment. In those cases the client remains responsible for fairness, explainability and human review unless the contract expressly assigns those duties to us for a defined component.
We do not use website behaviour to assign a secret credit, insurance or employment score. Intake tickets are read by people.
12. Children’s data
The site and the commercial services are directed at organisations and adult professionals. We do not knowingly collect personal data from children through the public forms. If a computer vision application or intelligent mobile application for a client would process children’s data, additional design constraints, parental or guardian logic where required, and a documented data protection impact assessment are preconditions to accepting the load.
13. Data subject rights
Under UK GDPR a person may request access, rectification, erasure, restriction, objection, and data portability where the legal conditions are met. A person may also withdraw consent where consent was the basis, without affecting the lawfulness of prior processing. Rights are not absolute. We may refuse a request that is manifestly unfounded or excessive, or where disclosure would adversely affect the rights of others, including trade secrets in a model that cannot be extracted without exposing third-party data.
Requests should be sent to tech@starlightporter.wiki from an address we can reasonably associate with the record, or with enough identity evidence to prevent disclosure to the wrong person. We respond within one month, with a possible extension of two further months for complex or multiple requests, in which case we explain the delay.
14. Processor engagements
When we process client-supplied personal data to deliver AI automation software or intelligent data processing, we act on documented instructions, assist with data subject requests to a reasonable professional standard, and delete or return the data at the end of the engagement unless United Kingdom law requires storage. Subprocessor changes that are material to risk are notified according to the contract. Audits are accommodated in a form that does not endanger other clients’ confidentiality.
15. Data protection impact assessments
Systematic evaluation of individuals, large-scale special category processing, or novel biometric identification inside a computer vision application will trigger an impact assessment before the load is crushed. The assessment records necessity, proportionality, residual risk, and consultation with the client as controller. If residual risk remains high, the Information Commissioner’s Office is consulted where the law requires it.
16. Marketing and professional updates
We may send factual service notices to contracting contacts as part of performing the contract. We may send occasional professional notes about screening methods to people who asked for them. Every marketing message includes a working stop method. We do not use purchased consumer lists. We do not append telephone numbers harvested from unrelated forms.
17. Third-party sites and models
Links to other sites, map tiles, font delivery networks and model providers are outside our controller perimeter once the browser or the runtime has left this domain. Those parties publish their own notices. Using a third-party large language model inside a generative AI app development project is described in the technical design so that personal data is not sent to an unexpected endpoint.
18. Changes to this policy
This policy may be updated to reflect legal change, a new fraction of services, or a change of infrastructure. The updated text is published on this page with a revised date. Material changes that affect a live contract are also notified to the contracting email on file. Continued use of the public site after publication constitutes notice of the new text for visitors. Contracting parties remain governed by the version incorporated into their agreement until that agreement is varied.
19. Complaints
A person who is dissatisfied with our response may complain to the Information Commissioner’s Office, the United Kingdom supervisory authority for data protection. We ask that the yard is given a fair chance to grade the issue first by writing to tech@starlightporter.wiki. The ICO’s contact details are published by the ICO and are not reproduced here as a substitute for checking the current official source.
20. Company details and contact
STARLIGHT PORTER LTD operates the website https://starlightporter.wiki from 911 Green Lanes, London, United Kingdom, N21 2QP. Telephone +44 7411 527869. Privacy correspondence: tech@starlightporter.wiki. This notice should be read with the cookie policy, the terms of service and the terms and conditions. It does not create rights beyond those granted by law and by any signed agreement. Last updated 18 August 2026.
For the avoidance of doubt, submitting an intake ticket is a request for a commercial conversation, not consent to unrestricted processing of any file attached without asking. Do not send passwords, full payment card numbers, or special category archives through the public form. Use a channel agreed after the first grade note.
21. Detailed processing records for service fractions
AI software development typically processes business contact data and, later, user identifiers inside software that we build and the client operates. The purpose is delivery of a working system. The lawful basis for our own staff contacts is contract or legitimate interests. The lawful basis for end-user data inside the built system is determined by the client as controller unless we host a managed environment under a processor addendum.
Machine learning software solutions may process labelled examples, feature tables and evaluation scores. Personal data in those tables is minimised. Direct identifiers are removed or hashed where the model can still be weighed. Training on special category data is excluded unless a written impact assessment and additional basis exist.
Intelligent mobile applications may process device identifiers, location if strictly required for the field job, photographs taken by the operator, and crash diagnostics. Location is off by default unless the graded output cannot function without it. Photographs are retained according to the client’s retention schedule, not ours, when we act as processor.
Generative AI app development may process prompts, retrieved passages and generated drafts. Prompts can contain personal data accidentally. We design logging so that operators can audit, and we advise clients not to paste unnecessary identifiers. Provider subprocessors are listed in the design pack.
Computer vision applications process images and derived bounding records. Faces are not enrolled for biometric identification unless the client has a documented lawful basis and the yard has accepted that grade of risk. Default vision work is object, document or scene grading, not identity.
Natural language processing apps process text. We discourage uploading medical notes, children’s records or criminal allegations into evaluation sets without a dedicated legal review. Recommendation engine development processes interaction events. Profiling of end users for the client’s product is the client’s responsibility unless we operate the ranking service under processor terms.
Intelligent data processing may involve matching, deduplication and survivorship. This can significantly affect individuals if done carelessly. We document match rules, keep an exceptions chute, and do not silently merge records that the client has marked as legally distinct.
22. Sharing inside the United Kingdom group of recipients
Counsel, accountants and insurers receive only what they need to advise or to underwrite. They are not licensed to use yard data to train their own public models. Hosting providers receive encrypted disks and keys managed so that casual administrator browsing is not the operating pattern. If a specialist labelling house is used for a vision fraction, samples are sampled, not the entire production archive, unless the weigh requires full coverage and the client instructs it.
23. Records of processing
We maintain an internal record of processing activities covering the purposes, categories, recipients, transfers, retention and security measures summarised in this policy. That record is not a public dashboard. A supervisory authority may inspect it. Clients acting as controllers receive the processor descriptions needed for their own Article 30 records.
24. Accuracy and client duty
We keep our own contact records accurate when a person tells us they have moved. We do not audit the accuracy of a client’s entire customer database as a hidden extra inside a software build. If intelligent data processing is scoped to include survivorship and cleansing, accuracy work is priced and scheduled as its own fraction.
25. Closure of the public form
Abuse of the intake form, including automated posting, injection attempts, or uploading of apparently stolen datasets, may result in blocking of addresses, preservation of evidence, and referral to law enforcement. Such processing is a legitimate interest in protecting the yard and other clients.
26. Job applicants and contractors
If you apply to work with STARLIGHT PORTER LTD, we process your CV, covering note, interview notes, right-to-work information, and any references you authorise. The purpose is recruitment. The lawful basis is legitimate interests in hiring, and contract steps at your request. Special category data is not requested on the public site. If an applicant volunteers health information to request an adjustment, we process it to consider that adjustment. Unsuccessful applications are kept for twelve months unless you ask us to delete sooner and no legal hold applies. We do not sell applicant lists. Automated scoring of CVs is not used as a sole decision. A contractor’s company details and insurance certificates are processed to engage them. Bank details for paying a contractor are used only for payment and statutory records.
References are taken only with your knowledge. We may verify professional claims that are material to an AI software development role, such as claimed delivery of a production machine learning software solution, using publicly available information and the referees you name. Criminal record checks are not a default for website visitors and would only arise for a role that lawfully requires them, with a separate notice.
27. Visitors to 911 Green Lanes
The operating address is 911 Green Lanes, London, United Kingdom, N21 2QP. Scheduled visitors may sign a visitor record showing name, organisation, time, and who they met. The purpose is security and fire safety. The basis is legitimate interests. Records are kept for a short period unless an incident requires longer holding. We do not operate a public walk-in gallery. Unscheduled visitors may be turned away. If CCTV is operated by a building manager rather than by us, that manager is the controller of the footage and should be asked for their notice. We will tell you if we become the controller of any camera covering the yard desk.
28. Detailed retention schedule in prose
Website server logs: typically ninety days, unless needed for security investigation. Cookie consent records: up to twenty-four months or until withdrawn. Intake tickets that do not become contracts: up to twenty-four months. Statements of work and variations: life of the contract plus six years. Invoices and tax: six years from the end of the accounting period. Project repositories we host temporarily: until handover plus backup expiry, usually not more than ninety days after confirmed dispatch unless the contract says otherwise. Model evaluation sheets containing personal data: as the processor clause and the statement of work specify, often deleted after the evaluation is documented in aggregate. Warranty correspondence: warranty period plus twelve months. Litigation holds override deletion until released. Anonymised operational metrics, such as counts of fractions dispatched, may be kept indefinitely because they are no longer personal data.
When two retention rules apply, the longer rule wins if a legal obligation is involved; otherwise we take the shorter rule that still lets us grade a complaint fairly. Backups expire on a rolling cycle and are not used as a hidden live archive. A deletion request that arrives during backup life will be honoured in the live system immediately and in backups at the next cycle unless a hold applies.
29. How to exercise rights in practice
Write to tech@starlightporter.wiki with “data rights” in the subject if you can. Say which right you mean. If you want access, say whether you want website enquiry records, a recruitment file, or something else. We may ask you to confirm an email address or to provide a document if the risk of disclosure to the wrong person is high. We do not charge a fee for a reasonable request. If you ask for the same material repeatedly without a reason, we may charge a reasonable administrative fee or refuse. We will not disclose another person’s data, our complete security configuration, or another client’s confidential load in answering you. Portability applies to data you provided to us by automated means under consent or contract, not to every internal note we typed while screening a ticket.
Objections to direct marketing are honoured quickly. Objections to processing that is required to perform a live contract will be discussed; often the practical result is to pause or end the load. Restriction means we store but do not actively use the data while a dispute is graded. Erasure is refused where we must keep invoices, where claims may still arise, or where freedom of expression in a limited professional record is not the issue but statutory retention is.
30. Processors in categories
Hosting and content delivery: organisations that store files and serve pages for starlightporter.wiki. Electronic mail: organisations that route mail to and from tech@starlightporter.wiki. Accounting: firms or platforms that store invoices. Bank: the institution that processes fees. Professional counsel: solicitors or counsel instructed on a matter. Cloud compute used on a client load: named in the statement of work because it varies. Labelling specialists: used only when a computer vision application or language pile needs extra hands, under confidentiality. Analytics: only if consented on the public site. Mapping: Google if you load the contact iframe. We do not list every possible future vendor in this policy because that list would go stale; a current list for a live project is in the design pack, and a current list for the website can be requested.
31. Data minimisation examples for each keyword load
For AI software development, we need a product owner and a description of systems, not an entire staff directory. For machine learning software solutions, we need a sample that can be weighed, not every historical row on day one. For intelligent mobile applications, we need the jobs the field worker actually performs, not a dump of every GPS point the organisation ever stored. For generative AI app development, we need policy documents that the model is allowed to see, not private HR files that happened to sit in the same drive. For AI automation software, we need the systems of record and the exception types, not every password in a shared spreadsheet. For a computer vision application, we need representative images with lawful capture, not covert recordings. For a natural language processing app, we need a labelled sample of tickets, not a live mailbox forwarded in bulk. For recommendation engine development, we need interaction events that the client may lawfully use, not purchased lists of people who never touched the service. For deep learning solutions, we need confirmation that compute and labels exist, not a fashion request for a network style. For intelligent data processing, we need the survivorship rules the business will actually stand behind, not a hope that the yard will invent a legal identity model.
32. Joint controllers and introductions
If an intermediary introduces a prospect, that intermediary is not automatically our joint controller. We become a controller of the prospect’s business contact details when we receive them for our own response. If we and a client jointly determine purposes for a public-facing tool, a joint controller arrangement will be written; we do not assume joint control merely because we wrote software the client operates. Introductions from other professionals should be made with the prospect’s knowledge. We do not pay for stealth lists of private individuals.
33. Security incident narrative
If we confirm a personal data breach likely to result in a risk to individuals, we notify the ICO without undue delay and within seventy-two hours where feasible, and we notify individuals when the law requires it. Our internal steps are: contain, assess, record, notify, repair, and learn. We do not publish a theatrical live blog of incidents. Clients who are controllers of the affected data will be told what we know about our systems so they can meet their own duties. A suspected incident should be sent to tech@starlightporter.wiki with times and ticket numbers. Do not send exploit instructions to that inbox as a public trophy; send enough fact for us to close a hole.
34. Automated tools inside the yard
We may use ordinary business software, including email filtering, spam screens, and internal search. Those tools can be statistically assisted. They are not used to make solely automated decisions about a visitor’s legal rights. If we use a generative tool internally to draft a first reply, a person still sends the grade. Client confidential material is not pasted into a consumer model endpoint that the provider may train on, unless the client has accepted that provider in the design and an enterprise control is in place. This is both a confidentiality practice and a privacy practice.
35. Transfers from the United Kingdom in more detail
Adequacy regulations issued by the United Kingdom government are the first tool when they apply. Where they do not, the UK IDTA or the UK Addendum to EU standard contractual clauses is used, plus encryption, access control, and a vendor review. A transfer impact assessment is recorded for novel or high-risk destinations. United States recipients may sit under a UK-US data bridge if that mechanism is valid and the recipient is certified at the time of transfer; otherwise contractual clauses remain. We do not treat a browser loading a font file as a “restricted transfer” in the same way as exporting a client’s customer database; both are disclosed here so the distinction is clear. Project data exports are controlled. Website CDN nodes may be global.
36. Contacting the controller again
STARLIGHT PORTER LTD, 911 Green Lanes, London, United Kingdom, N21 2QP. Telephone +44 7411 527869. Email tech@starlightporter.wiki as plain text. Website https://starlightporter.wiki. This policy is the privacy notice for the public site and for ordinary commercial correspondence. A statement of work may add processor particulars without replacing this notice for our own controller activities. If you have read this far, you already know the yard prefers a long accurate notice to a short decorative one. That is consistent with heavy clarity: the usable fraction of a privacy notice is the part a person can actually rely on when they need to exercise a right or understand a purpose.