Data Processing Addendum
1. When this applies
This Addendum applies when you use a migration function — anything where you authorize us to access data held in another service on your behalf. It does not apply to the Drives function, where your files never leave your machine and we are a controller only of the catalogue described in the Privacy Policy.
For migrations you are the controller and Jacked Trade LLC is the processor.
2. What we process, and on whose instructions
We process the data contained in the source you connect, for the purpose and duration of the job you asked for, and on your documented instructions only. Starting a job is such an instruction; so is accepting a quote.
We will tell you if we believe an instruction breaches applicable data-protection law.
3. Confidentiality, security and subprocessors
Everyone with access to your data is bound by confidentiality. Credentials you provide are never stored in this application — there is no field for one — and are destroyed with the workspace.
A job's working copy lives only inside its own workspace on the machine that ran it. We record when each working copy was destroyed, and you can see that date on your own job page.
Each job is isolated in its own workspace, so one client's data is never commingled with another's.
We use subprocessors for hosting, storage and — where the function requires it — AI classification. We remain responsible for their performance, and will tell you before adding one that processes your data.
The subprocessors we use today, and what each one sees:
Railway — hosting for this application and its database, which holds your account, your jobs and your catalogues. Not the contents of your files.
Google — where an archive or a migrated library is delivered, because that is the destination you asked for. For BigQuery loads, records also pass through a staging bucket we control, which is emptied within seven days.
Anthropic — used only by functions that describe your media so it can be searched by what is in it. Those functions send the image; nothing sent is used to train a model. A function that does not tag does not use it, and its statement of work says so.
Stripe — payments. Card details go to Stripe directly and never reach our servers.
Resend — the emails we send you, including quotes and progress. Message contents, not job data.
Adding to this list is a change we will tell you about before it processes your data, and it is a change to this document.
4. Your people's rights, and breaches
We will help you respond to requests from individuals whose data is in a job, and to any regulator's enquiry, so far as the work we did is relevant.
If we become aware of a personal-data breach affecting your data we will tell you without undue delay, with what we know and what we are doing about it.
5. Return and deletion
A workspace can be handed to you or destroyed as one unit, and that is deliberate: it is what makes "give me everything back and delete your copy" a single action rather than a search.
On completion we delete the working copy on request, and by default within 30 days.
6. Audit
On reasonable request we will provide the information needed to demonstrate compliance with this Addendum, and allow an audit where the law requires one, at your cost and on terms that protect other clients' confidentiality.