Producers and Musicians: Seal Your Demos Before Sharing
Published: May 28, 2026 · musica · audio · sellado-de-tiempo · Leer este artículo en español
Sealing a demo means creating technical evidence that this exact audio existed on a specific date, before you share it with anyone. With Veritas UGC you do it free at /certificar: the server computes the file’s SHA-256 hash, applies a server_clock timestamp, and issues a signed certificate with a public verification link.
The real risk of sharing untracked demos
A demo travels far: emails to labels, shared folders with collaborators, messaging groups, USB sticks at gigs. Every send is a copy outside your control, and if a suspiciously similar track surfaces months later, your word counts for little without dated evidence. The problem is not distrust; it is the absence of an orderly record of what you sent and when.
How to seal a demo in minutes
Export the version you plan to share and upload it to /certificar: no account is needed and you can issue up to 10 certificates per hour. You get a signed certificate with the SHA-256 hash, the server_clock timestamp date, and a public link at /verify that anyone can open. If you work from your phone, the native Android app lets you seal a freshly bounced mix without touching a computer. With an account, which you can create with any email, you also keep an organized history of all your versions.
Good habits for sessions and collaborations
Seal the milestones, not just the final master: the hummed idea, the first production pass, and the mix you send to a label tell the story of the work. When you share the demo, paste the verification link into the email itself; it is a graceful way to leave a record without accusing anyone. In collaborations, agree on splits in writing before release. A clear collaboration agreement, combined with seals on every shared version, keeps a good creative friendship from turning into a dispute built on fuzzy memories and missing files.
A timestamp does not replace collecting societies or official copyright registries, and it does not settle disputes on its own. It is a fast, verifiable layer of technical evidence that strengthens your position. For label contracts or authorship conflicts, consult a legal professional.
Frequently asked questions
Which version of a demo should I seal?
At minimum, the one leaving your studio for other hands: that is the copy that could circulate beyond your control. Ideally, also seal intermediate milestones such as the first recorded idea and the advanced mix. Each certificate documents one exact file, so any later change produces a different hash.
Does the certificate prove the song is mine?
It proves that this exact file existed on that date and that you submitted it under a declared identity. It does not verify authorship in a legal sense and does not replace official registries or collecting societies. It is priority and integrity evidence that, combined with your project files and messages, supports your account.
Can I seal stems and the full project?
Yes. You can certify any file, including exported stems or a zip of your DAW project. Many producers seal a package with the full session at key milestones. Keep in mind the limit of 10 certificates per hour in the no-account flow, and always keep the original files: the seal references their exact hash.
Seal your content now
Free, no account required, with a public verification link.
Veritas UGC generates technical evidence (hash, timestamp and traceability). It is not legal advice nor a government IP registry.