Legal
Privacy
What we collect, where it is kept, who else sees it, and how to get it removed.
Last updated
Trady is new, and this page describes what the software does today rather than what we plan for it. Where something is not automated yet, it says so instead of promising a schedule.
This page will change as the product does. Questions go to CONTACT EMAIL.
What we collect
Only what the product needs to run. There is no analytics service, no advertising code and no third party tracker on this site.
Your account
- An email address, which is how you sign in and the only way we can reach you.
- A password. We never store it. What is stored is a scrypt digest with a random salt per account, which cannot be turned back into the password you typed.
- Sessions. When you sign in, your browser gets a random token in one cookie. The server keeps only a SHA-256 digest of that token, so a copy of the database does not let anyone sign in as you. A session lasts 14 days, and signing out revokes it immediately.
What you upload and what we make from it
- The video files you submit.
- The transcript we derive from each video, including the timing of individual words, because that is what word by word captions are made of.
- The moments we select, with their scores and categories, and the vertical clips we render from them.
Running the account
- A credit ledger. Every charge, release and top up is an entry with a timestamp, so your balance can always be explained line by line.
- An audit record of privileged actions, such as creating or deleting a project: who did it, when, and what changed.
- Ordinary server logs, which include IP addresses and request paths, kept for debugging and abuse handling.
Where it is stored
Trady runs on a single server. Account data, projects, transcripts, clip metadata and the credit ledger live in one PostgreSQL database. Video files and rendered clips live in MinIO object storage on the same machine.
Every table that holds workspace data carries a workspace id and is protected by Postgres row level security, so a query made on behalf of one workspace cannot read another workspace’s rows even if the application code asks it to. Traffic to the site is served over HTTPS.
Who else sees it
One company outside our server processes your content, and you should know exactly what leaves the machine.
OpenRouter. We send the audio of your video to a speech to text model through OpenRouter to produce the transcript, and we send the resulting transcript text through OpenRouter to a language model to pick the moments worth cutting. That means your audio and the words spoken in your video leave our server and are processed by OpenRouter and by the model provider behind the model in use.
We do not control how OpenRouter or its upstream providers handle what they receive. Their own terms and privacy policies govern that, and if the content of a video makes this a problem, do not upload it.
Beyond that: nobody. We do not sell your data, we do not share it with advertisers, and we do not use your videos, transcripts or clips to train any model of our own.
How long we keep it
The honest answer is that deletion is manual today, and we would rather say that than publish a retention schedule no code enforces.
- Deleting a project marks it as deleted and removes it from your workspace. The source video and the rendered clips stay in object storage until someone removes them by hand. There is no automatic purge yet.
- Expired and revoked sessions stay as rows until they are cleared manually. They cannot be used to sign in once expired or revoked.
- Credit ledger entries and audit records are kept for as long as the account exists, because they are the record of what you were charged and what happened.
- If you want your videos, clips and account erased, write to CONTACT EMAIL and we will do it by hand and confirm when it is done.
Cookies
One cookie, set when you sign in, holding the session token described above. It is marked http only so page scripts cannot read it. There are no analytics or advertising cookies, which is why this site has no cookie banner.
Payments
There is no payment processing in the product yet, so no card or payment details have ever reached it. When checkout ships we intend to use Mayar for Indonesian rupiah and NOWPayments for crypto, both of which handle payment details on their own systems. This page will be updated before either goes live.
Your choices
You can delete a project from the dashboard at any time. For a copy of your data, or for erasure of an account and everything in it, write to CONTACT EMAIL. We will answer as a person, not a ticket system.
Trady is not built for children and we do not knowingly collect anything from them.
Changes to this page
When what the software does changes, this page changes with it, and the date at the top moves. If a change is significant, such as a new company processing your content, we will email account holders rather than quietly editing the text.
The operator of Trady is LEGAL ENTITY NAME, at REGISTERED ADDRESS.