PermitDesk
PermitDesk › Pilot security review
Pilot security review

Requirements to resolve before a jurisdiction pilot

A jurisdiction must define and independently review its purchasing, security, data-handling, implementation, and staff-approval requirements before any production use.

Proposed scope only. Illustrative proposed pilot only. No working PermitDesk application, public intake portal, production AI workflow, payment connection, third-party integration, or implemented security control is represented as existing. Every production capability requires a separately scoped, buyer-approved implementation.

Discuss a proposed pilot Pilot purchasing guide

What is actually available today

The public website includes a fictional-data, illustrative workflow preview and a published proposed pilot price. No production PermitDesk application, jurisdiction connection, security implementation, customer deployment, or third-party certification is represented.

Potential security controls require verification

Data minimization, access control, encryption, hosting, event logging, retention, incident response, and disposal are proposed discussion topics. Their actual design and implementation must be separately approved and verified before jurisdiction data is processed.

Jurisdiction staff retain all decisions

Any future pilot must keep application review, permit issuance, denial, applicant communications, and purchasing authorization with the jurisdiction's authorized staff.

Agree on data handling and ownership

A future written scope must address data ownership, approved records, access permissions, export needs, retention, model-use restrictions, and disposal. No existing export service or implemented control is represented.

Buyer-directed security and purchasing review

The jurisdiction determines its own required purchasing process, security questionnaire, evidence, documentation, and approvals. No certification, insurance certificate, client reference, purchasing exemption, or guaranteed approval is represented.

About the publisher

PermitDesk is published by JS Technology Solutions, Inc. Questions about the proposed pilot can be sent to hello@trypermitdesk.com.

Review a separately scoped jurisdiction pilot

Discuss the illustrative workflow, your actual requirements, and the purchasing approvals your jurisdiction determines.

Discuss a proposed pilot