Trust center

Support, corrections, and access problems

Request help with a purchased deliverable, service question, factual correction, privacy concern, payment issue, or accessibility barrier.

Start with the contact form

Choose the review, correction, or support topic and describe the page, deliverable, service, or payment involved. Use the same email address associated with the request when possible.

What to include

Include the page or file name, order or project reference if available, the problem, when it began, the result you expected, and any safe steps already tried. Screenshots are useful only when they do not expose sensitive information.

Keep secrets out of the first message

Do not send passwords, authentication codes, private keys, payment-card data, regulated records, or full incident evidence through the public form. NorthFirn will establish a safer method when the issue requires sensitive material.

How requests are prioritized

Security and privacy concerns, duplicate charges, unavailable purchased deliverables, accessibility barriers, and production-impacting issues receive attention before feature requests or general feedback. Priority does not create emergency coverage outside an agreement.

What support includes

Included revisions, defect correction, monitoring, incident triage, change requests, and third-party responsibilities are defined with each paid offer. Work outside that scope may require a new authorization or estimate.

Availability and emergencies

Ordinary contact, project work, and email receipt do not provide 24/7 support. After-hours response, service levels, and emergency channels apply only when they are included in a written agreement.

Corrections, privacy, and accessibility

A factual challenge is reviewed under the corrections policy. A privacy request should identify the email address or engagement involved. An accessibility report should explain the task and the alternate format or accommodation that would help.