Prygenix SignOff / Setup / Security

Security and data handling for Autodesk Forma

Prygenix SignOff works inside your Autodesk Construction Cloud account with each person's own Autodesk permissions. It keeps the least it needs to do that: encrypted Autodesk sign-in tokens and a few names and IDs, never your project files.

Last updated 23 October 2026. For ACC account admins, IT and security reviewers. It adds to the Prygenix PDF Studio privacy notice and the Prygenix security overview.

How it connects

Permissions it asks for

Each person's sign-in
3-legged OAuth
data:read data:write data:create: list hubs, projects and folders, open a PDF, save a signed PDF as a new version or file, read submittals, add the signed PDFs to a submittal and record the review response. Always with that person's own Forma permissions. We also read their Autodesk profile (name and verified e-mail address) to sign them in.
The app itself
2-legged, account:read
Read only. Used to check that the app is authorized in an account and that the person setting it up is an account admin (Account Admin API user search), and to turn the people, companies and roles a submittal is assigned to into e-mail addresses for notifications (project users, companies, roles). Nothing is changed with this token.

What we store

Autodesk tokensPer person who signs in: the access and refresh token Autodesk issued, encrypted (AES-256-GCM), and their Autodesk display name. Deleted when they click Disconnect, when Autodesk stops accepting them, or when the account is removed (below).
Account set-upPer ACC account set up: its hub ID, name and region, who set it up and when, the plan, and whether Autodesk currently authorizes the app. The seats are licence records: e-mail address and name of each person with a seat.
Project e-mailsFor projects where someone turned on e-mails: the project ID and name, who turned it on, and for each submittal a short state marker (its ID, workflow state, when it arrived and who has it) so that only changes are e-mailed. No submittal contents, files or comments.
E-mails we sendContain the submittal number, title, spec section, project name, due date and, when closed, the response, plus a link that opens it in SignOff. Sent only to the people Forma assigns the submittal to, and to people who turned on alerts for themselves.
Sign-in sessionsA session per sign-in, stored only as a hash, valid for 30 days or until sign-out.
Documents sent for signatureOnly if someone uses Send to others to sign: the PDF is stored encrypted until the deletion date the sender chose, then deleted; the signing record (who signed, when) is kept. See the privacy notice.

What we never store

How it is protected

Who can do what

Pausing and removing it

Other services involved

AutodeskAutodesk Platform Services: sign-in, Data Management, Submittals and Account Admin APIs.
HostingOur server at a hosting provider (virtual private server) runs pdf.prygenix.com and the licence server.
E-mail deliveryOur e-mail provider delivers sign-in codes and submittal e-mails.
DigiCertOnly for DSC signing with a trusted timestamp: receives a hash of the signature, never the document.

Questions and reporting a problem

Security questionnaires, a data processing agreement, or a suspected vulnerability: support@prygenix.com. Confirmed security issues are fixed first. Prygenix Innovations Private Limited, Bengaluru, India.