Skip to main content
Order confirmed

Thanks — here's what happens next

One email from you and the work starts. There is nothing to schedule and nobody to talk to.

What to do next

  1. 1

    Sanitise your script

    Replace real usernames, passwords, tokens and CSV rows with synthetic values. I need the structure, not your data — the values are of no use to me, and this is what keeps your production data out of the job entirely.

  2. 2

    Put it somewhere you control

    SharePoint, Google Drive, S3, anywhere you can share a link from — expiring if you can. Not an email attachment: that leaves copies in both mailboxes, both sent folders and both providers’ backups. A link means you can revoke my access the moment the work is delivered.

  3. 3

    Send me the link and your order number

    That is the whole handover. Your turnaround starts when a complete submission arrives — not at purchase — so a missing data file never eats a deadline.

  4. 4

    I send the finished script back

    With notes on everything I changed and the manual-work list marked off. Questions afterwards are included, and your files are deleted 30 days later.

Your order number is in your receipt email. Include it so I can match the job to the tier you bought.

Send my script link

Opens an email to sales@martkos-it.co.uk with the fields pre-filled.

A reminder of how your script is handled

The same terms you saw before buying — repeated here because this is the point where they actually apply.

Send sanitised scripts only
Replace real usernames, passwords, tokens and CSV data with synthetic values before sending. I need the structure of your script, not your data — the values are of no use to me. If a script cannot be sanitised without destroying what makes it worth migrating, tell me and we will find another way.
No production data, in any form
That includes raw HAR captures, database dumps and screenshots of live traffic. If you send something containing production data, I will delete it and ask for a sanitised version rather than work from it.
Share a link from your own file store
Not an email attachment: email leaves copies in your mailbox, my mailbox, both sent folders and both providers’ backups — retention nobody can honestly promise to control. Send a link from your own SharePoint, Drive or S3 instead, expiring if you can. The file stays under your control and you can revoke my access the moment the work is delivered.
Deleted 30 days after delivery
Your files and everything derived from them are deleted 30 days after I hand the work back. The 30 days exist so you can come back with a question. Ask and I will delete sooner.
Handled by me, in the UK
Your files are stored and worked on by me personally, on my own equipment, in the United Kingdom. They are never shared with another client, another customer, or anyone else.
I use AI tooling, and you can opt out
The software itself contains no AI: the converter is compiled Rust running inside your own browser, and nothing about it calls out anywhere. The manual work is different. When I complete the parts a converter cannot do, I use Claude (Anthropic) as a working tool, so sanitised script content may be processed by it outside the UK. That is exactly why sanitised input is a requirement here and not a preference — there should be nothing personal left in what reaches it. If you would rather no AI tooling touched your script at all, say so with your order and I will do the work without it, at no extra cost.
A written agreement if you need one
For work in a regulated environment I will sign a data processing agreement under UK GDPR Article 28 before anything is sent. Ask for it with your enquiry and it will come back with the quote.