Useful guidance needs visible sources and visible interests.
SilentProof guides are researched and maintained by the Borealbit Editorial Team at Borealbit Technology Limited. The same company develops and publishes the SilentProof app, so our product interest is part of the record—not hidden behind an apparently independent publication.
Editorial policy reviewed: 2026-08-13
Authorship
Who writes and reviews the guides
Articles are published under “Borealbit Editorial Team” because they combine product knowledge, source review, and editorial maintenance by the company rather than the opinion of an unnamed independent expert. Borealbit is responsible for the final wording, links, dates, and corrections.
We do not present the team as a law firm, government agency, acoustic laboratory, certified sound-level-meter manufacturer, landlord association, or tenant-advocacy organization.
Commercial disclosure
Borealbit benefits when the app succeeds
Borealbit Technology Limited owns, develops, publishes, and monetizes SilentProof. Articles may explain a problem that the app is designed to help document and may link to its App Store page. Borealbit may benefit from downloads and one-time Pro purchases generated by those links.
Product recommendations are therefore not independent endorsements. We try to make them useful by stating what SilentProof does, what it does not do, and when an official form, certified instrument, lawyer, landlord, or public agency is the appropriate next step.
Research method
How we build a source-based guide
1. Define the user task
We identify whether the reader needs to document an incident, understand a measurement, prepare a message, or use an official complaint channel.
2. Find the controlling source
For city workflows and legal rules, we look first for current agency pages, statutes, regulations, and official code libraries rather than copying another blog.
3. Separate fact from product guidance
Official requirements are attributed to their source. SilentProof checklists and workflow suggestions are labelled as supplemental documentation rather than government requirements.
4. State the limits near the claim
Phone readings are described as reference levels. The app does not certify compliance, identify a source, file a complaint, provide legal advice, or guarantee an outcome.
Source policy
Primary sources first
We prefer city and agency service pages for complaint procedures; current statutes, regulations, and official code libraries for legal thresholds; and first-party product documentation, App Store listings, test code, and actual app screens for SilentProof claims.
Secondary sources may help identify terminology or locate primary material, but they should not replace the controlling source when one is available. We place links near material claims and include a reviewed date on topics that can change.
We avoid unsupported claims that a complaint “will be taken seriously,” that an agency “must act,” or that an app-generated report is “legal evidence.” A clear record may make a pattern easier to review; acceptance and outcomes remain with the recipient and applicable process.
Updates
Dates reflect meaningful review
Blog pages show their original publication date and, when applicable, the date of the latest substantive review. We update a date when sources, product facts, conclusions, or materially useful instructions were checked or changed—not for cosmetic edits alone.
Corrections
Errors should be easy to report
Send a source link and the page URL to support@borealbit.com. We check the primary source, correct material inaccuracies, update the review date when appropriate, and remove claims that cannot be supported.
Product and content boundaries
Documentation is one step in a larger process.
SilentProof keeps incident context together and can export a selected PDF. It does not replace an official complaint form, a government inspection, a certified acoustic measurement, professional legal advice, emergency services, or the decision of a landlord, agency, insurer, mediator, or court.