Last updated · 24 July 2026
This Policy explains what Truing receives when you use truing.kynth.studio, what happens to a payroll register during an engagement, and how long anything is kept. Truing is a Kynth Studios product. It matters more here than on most sites: a payroll register carries employee names, hours, wages and tips, and it usually belongs to your client rather than to you.
1
The plain-English version
The free checker reads your CSV in the request that carries it and returns a count. The file is not written to disk and not kept. A paid engagement is different: we hold the register until the workpaper is delivered and a retention window has passed, then delete it. We never sell it, never train a model on it, and never use it for anything but your engagement.
2
The free readiness check
The CSV you choose is posted to our own server, scanned in that request, and discarded when the response is sent.
Nothing is written to a database or an object store, there is no account, and we cannot retrieve a file you checked.
The response is a count and the reasons behind it. We do not keep the count, and we do not keep employee names.
We record no code TT or TP figure, because the checker does not compute one.
3
A paid engagement
When you buy a reconstruction, the register you send is held so the workpaper can be produced and defended. In that case:
It is stored on our own infrastructure, not in a third-party AI service;
It is used only to produce your workbook, W-2 import file, method memo, exceptions report and reconciliation;
It is retained for 12 months after delivery so the workpaper can be re-derived if the return is questioned;
It is deleted at the end of that window, or sooner if you ask us in writing;
It is never sold, never shared with another customer, and never used to train any model.
You may ask for deletion, a copy, or a correction at any time by emailing truing@kynth.studio.
We answer deletion requests within 30 days.
If you are a firm sending a register on behalf of a client, you are the controller of that data and we process it on your instructions; tell your client that a processor is involved.
4
Who else touches it
You own your registers and everything we produce from them. The sections below set out who else the data passes through on the way, and for how long we hold it.
Hosting. The site and its API run on Vercel, which processes the request carrying your upload. Vercel does not receive a stored copy, because the checker stores nothing.
Payments. Stripe handles checkout and receives your billing details, your employer or firm name and your payroll system. We never see a card number.
Email. Resend delivers our transactional mail — intake requests, delivery notices and replies. It sees the address we write to and the contents of that message, not your register.
Analytics. PostHog records page views and which sections were used, with inputs masked. It never receives the contents of an uploaded file.
5
What we do not do
We do not sell personal data, and we have not in the preceding twelve months. We do not send marketing email to the employees named in a register — they are not our contacts and never become them. We do not use any AI model in the computation, so no register is ever sent to a model provider. We do not run advertising trackers on this site.
6
Contact & governing law
Questions, deletion requests and data-subject requests go to truing@kynth.studio and are answered within 30 days. Truing is operated from New York, and this Policy is governed by the laws of the State of New York. If we change how a register is handled, the date at the top of this page changes with it.