Affective TechnologiesIHNYC Service Docs

Patron feedback

Planned2 min read

Table of Contents

The patron feedback page is not currently available. When enabled, it is designed as a one-way suggestion box: a patron can send a message and may add a rating, name, or contact method. It is not a public review, live chat, or emergency channel.

For patrons

  1. Write the feedback you want the Pub team to receive.
  2. Add a rating or contact information only if you choose.
  3. Submit once and wait for the confirmation message.

The page may be unavailable when the Pub is not accepting new submissions. If something presents an immediate safety concern, contact on-site staff directly instead of relying on the form.

Before you send

Feedback is read by authorized Pub operators. Do not include passwords, payment details, medical information, or anything that should not be part of an operational record.

What operators see

Authorized operators receive a private queue. They can mark a note as new, read, or archived so the team can separate unreviewed feedback from completed triage. A submission does not create a public post and the system does not promise a direct reply.

flowchart LR
  PATRON["Patron submits a note"] --> CHECK["Input and abuse checks"]
  CHECK --> QUEUE["Protected feedback queue"]
  QUEUE --> REVIEW["Authorized operator reviews it"]
  REVIEW --> ARCHIVE["Archive or follow up outside the form"]

Privacy and safety

  • Name, rating, and contact information are optional.
  • Message text is visible only to roles allowed to review feedback.
  • Limited technical metadata is used to detect repeated abuse and troubleshoot delivery; it is not shown as patron-facing content.
  • Patron text is treated as untrusted input and displayed as text, not executable page content.
  • Operators should archive or remove records according to the Pub’s retention policy and avoid copying personal details into unrelated tools.

Technical boundary

The public form accepts a narrow, validated submission. Abuse controls limit repeated automated use without publishing the thresholds or decision logic. Reading, changing status, and removing feedback are separate protected actions enforced by the Pub service.

The intentionally public submission contract is summarized in Public API reference.

Related: Admin access · Architecture