Founder attestation
Professional credentials you can check.
Damien DeJesus is a licensed CPA in Florida and Connecticut.
You can check both licenses in the Florida and Connecticut public state board records.
Trust Center
Here is what you can check today, what we are building to, and what we cannot show you yet. Missing or outdated evidence stays visible.
Each claim carries the date it was last actually examined. A claim that was not re-examined does not get a new date.
The only form on this site is the contact form, which collects an email address, a message, and a concealed website field used only for spam screening.
Founder attestation
Damien DeJesus is a licensed CPA in Florida and Connecticut.
You can check both licenses in the Florida and Connecticut public state board records.
How to read this page
Designed means a requirement, not proof it is running. Implemented means the stated website feature exists. Unknown means we cannot establish the answer from the available evidence.
Current means the evidence supports that specific claim within its review window. A stale, held, unavailable, or contradicted result is not a passed check. Review dates change only when the evidence is examined again.
Current public posture
These checks cover the website and contact channels. They do not extend to every product or service.
You can send a message through the contact form or book a Google Calendar conversation. Neither starts work or authorizes an action.
Evidence and limitation
Reference: NW-TC-POSTURE-001
The form sends email through the configured contact endpoint. Do not send secrets, credentials, confidential records, or workflow data. Work begins only under a signed engagement.
What we checked
Email and Google Calendar are general conversation channels only; delivery or booking does not create a case, engagement, service agreement, or action authority.
Evidence and limitation
Reference: NW-TC-POSTURE-002
A calendar booking or email is not an acceptance notice. Do not send secrets, credentials, confidential records, or workflow data.
What we checked
Use Log in to reach the sign-in service protected by Cloudflare Access. The link alone does not give you access.
Evidence and limitation
Reference: NW-TC-POSTURE-003
The sign-in service checks whether you are permitted to enter. Following a public link does not bypass that check.
What we checked
The public accessibility statement does not claim full conformance with WCAG, ADA, Section 508, or another standard.
Evidence and limitation
Reference: NW-TC-POSTURE-004
Preferences and automated checks can help visitors and authors, but do not create compliance by themselves.
What we checked
Privacy Policy and Terms of Use are published at /privacy/ and /terms/.
Evidence and limitation
Reference: NW-TC-HELD-001
These pages describe the public Site and conversation channels. They are not a data-processing agreement, acceptable-use policy, security overview, or a statement of good standing.
What we checked
Security observations and preparation gaps are listed at /security/.
Evidence and limitation
Reference: NW-TC-HELD-002
The page reports exact current observations and preparation gaps. No certification, compliance, audit, penetration-test, independent assurance, broad security guarantee, or security incident inbox is claimed.
What we checked
Governed-system design
These are design requirements. Read each limitation to see what has and has not been demonstrated.
Design requirement: your decisions should carry current evidence from the sources permitted for that work.
Evidence and limitation
Reference: NW-TC-DESIGN-001
A design requirement is not evidence that every Nightworks AI capability implements or operates this control.
What we checked
Design requirement: preparing work should never count as permission to act; a person must decide where approval is required.
Evidence and limitation
Reference: NW-TC-DESIGN-002
This is an operating-model requirement, not a claim of active public autonomy or a deployed approval system.
What we checked
Design requirement: an attempted action should count as complete only after an independent check of the destination system.
Evidence and limitation
Reference: NW-TC-DESIGN-003
This requirement does not assert that every external connector or workflow is currently implemented.
What we checked
Design requirement: failed, held, conflicting, outdated, or missing evidence should keep work from being marked complete.
Evidence and limitation
Reference: NW-TC-DESIGN-004
This describes the required behavior; it does not prove every running system meets it.
What we checked
Design requirement: your records and actions should stay separate from those of other customers.
Evidence and limitation
Reference: NW-TC-DESIGN-005
Separation between customers is a requirement here, not an operating, independently assessed, or other higher-assurance public claim.
What we checked
Unavailable or not asserted
Where evidence is missing, you will see what is unavailable. Missing evidence never counts as a passed check.
A data-residency statement, export procedure, legal-hold procedure, and model-provider register are not available from this Trust Center. The providers that operate the Site, and its retention and deletion practices, are stated at /privacy/.
Evidence and limitation
Reference: NW-TC-HELD-003
No residency, export, legal-hold, or training-data posture is asserted.
What we checked
Public uptime, incident history, service levels, backup, restore, recovery-point, and recovery-time evidence are not available from this Trust Center.
Evidence and limitation
Reference: NW-TC-HELD-004
No uptime, incident-free, always-on, service-level, backup, or recovery-performance claim is asserted.
What we checked
Customer results and live-autonomy evidence are not available from this Trust Center.
Evidence and limitation
Reference: NW-TC-HELD-005
No customer outcome, savings, accuracy, scale, or autonomous-action claim is asserted.
What we checked
NW-TC-BOUNDARY-001
For non-sensitive general questions about this public evidence status, email hello@nightworks.ai.
This mailbox is for general questions, not security incidents or starting work. Do not send secrets, credentials, confidential records, or workflow data.
Email hello@nightworks.ai for a non-sensitive general question