Home/Checker/How building details and contact data are handled
Official references0Last source checkcurrent
How building details and contact data are handled
Share only the building facts needed to clarify the next LL152 step. Keep DOB credentials, payment data, government IDs, and emergency reports out of this intake.
What this page covers
What the intake stores
The intake stores the name, email, phone, building address or identifier, page path, scenario context, and the message you submit.
The current phase-one workflow keeps that data in CSV files so the page context and the follow-up note stay together.
Name, email, and optional phone number
Building address or identifier
Page path, intent, and scenario context
A short message about what still blocks the next step
What this page covers
Retention, correction, and deletion
The intake is meant for lightweight case handling, not for long-form document storage.
If you need a correction or deletion request, email [email protected] from the same address you used in the intake.
Keep submissions limited to what changes the answer
Use email for deletion or correction requests
Do not send large attachments or portal credentials through the intake
What this page covers
What to leave out
Do not send DOB NOW credentials, payment details, government IDs, or unrelated tenant information through this form.
The intake is for routing context, not for account takeover, billing, or emergency gas reporting.
No DOB passwords or login screenshots
No credit card or bank data
No Social Security or tax identification data
No emergency condition reports that should go directly to 911, your gas utility, or DOB emergency channels
Decision basis
Why this page matters
Use this page to understand what the intake asks for, where the current CSV workflow stores it, how long it is kept, and how to request deletion or correction.
Official references0 city sources
Last source checkcurrent
Best used whenYou need policy, privacy, or contact boundaries.
The checker is designed around official-source-first guidance, phase-one launch constraints, and language that stays specific without pretending to give legal certainty.
The intake keeps the likely next step, blocker, and contact details together so the next reply can start from the current case context.
Operator
LL152 Guidance Desk
A virtual team maintaining a narrow, source-checked routing surface for NYC Local Law 152. Use it to narrow the next filing step before you act in DOB NOW.