Rolando Andrade
Back to Content

DEVLog - July

Discover what happened in July 2026. SignatureAPI started on qualified signatures and Brazilian attestations, ParentSignature for Schools began, and Privacy Policy Review got real checkout.

· 2 min read
DEVLog - July

July had 380 commits across 10 repositories. Two of them were about trust: making signatures stronger in the eyes of the law, and making a school product people can depend on.

I wrote this devlog later, from my GitHub history, to fill a gap in the series.

Stronger signatures

SignatureAPI got 263 commits from me this month, and much of it was about the legal strength of a signature.

First, I added a new attestation strategy for Brazil. An attestation is proof, from a trusted third party, that a document existed in a certain form at a certain time. In Brazil the trusted system is called ICP-Brasil, and we get the timestamp from BRy, a provider in that system.

Second, I made document timestamps LTV enabled. LTV means Long Term Validation. It keeps a signature verifiable years later, even after the certificates behind it expire.

Third, I laid the groundwork for qualified electronic signatures, or QES. In the European Union, a QES has the same legal weight as a handwritten signature. For now this is only the first step: a test signer and an account setting to turn the feature on.

I also added the radio group as a new field type, and a “sign all” button that fills every signature field at once. Each account can turn it on or off. Both are in the public docs and the changelog.

SignatureAPI Electronic signature API for workflows, applications and platforms. signatureapi.com

I also published a public demo: SignatureAPI web integration demo. It shows how to embed a signing ceremony inside your own web page.

A sample agreement signed inside the web demo page.
A sample agreement signed inside the web demo page.

ParentSignature for Schools

ParentSignature already had a landing page for schools. In July I started the product behind it, a new app: ParentSignature for Schools. It took 35 commits.

The base is a workspace. Each school is one workspace, and all its rules live in one place. On top of that I built two features:

  1. Rosters. You paste a spreadsheet of students and families. The app shows you what will change before it saves anything.
  2. Forms. You upload a PDF and place the fields where parents should sign. Every form has versions from day one. When you send a version, it is locked, and any new edit creates a new version.

That second rule matters. A parent should always sign exactly the form the school sent.

ParentSignature A free tool that lets teachers collect parent signatures on school forms digitally. parentsignature.com

Privacy Policy Review checkout

Privacy Policy Review now uses a live Stripe price, with branded checkout and promotion codes. I made the record of the attorney’s review stronger, with a stable completion date. I also switched the AI review to the gemini-3.5-flash-lite model.

The Privacy Policy Review homepage, with a sample Record of Attorney Review.
The Privacy Policy Review homepage, with a sample Record of Attorney Review.
Privacy Policy Review Automated Privacy Policy Review by Attorneys. privacypolicyreview.com

Smaller things

On this blog, I rebuilt how my CV is generated, updated my career pages and linked each role in the CV to its career page. I also started a few personal projects that I am keeping private for now.

What comes next

  • SignatureAPI: keep building qualified signatures.
  • ParentSignature for Schools: sending forms and tracking who signed.

Thank you for reading. If you build software that needs signatures, try the demo!

Interested in working together? Check out my services and pricing to see how we can collaborate on your next project. Let's Build