Reporting a shared page, and taking one down

What it is

One-line: Every page published to Omniscio Shares carries a small Report this page link for anyone who opens it, and the product owner has one switch that takes a page off the public web — hiding it everywhere, deleting nothing, and reversible.

Where to find it

One place per reader. The Report this page link sits at the bottom of every published share, and it needs no account — anyone who can open the page can use it. A report reaches the publisher as a normal inbox card. The owner works from their own console, where each reported page carries a single Take this page down button.

Who can do what

Who	What they can do
Any visitor, signed in or not	Report a page they are looking at, and nothing else
The publisher	See that their page was reported (an inbox card); they cannot resolve it themselves
The product owner	Read every open report, take a page down, and put it back

How it behaves

Nothing here is automatic: no page is ever scanned, and nothing is removed on its own. Every step below is either a person reporting something or the owner deciding what to do about it. The sections that follow are who may do what, what a report contains, what a takedown actually changes, and what this deliberately does not do.

Reporting a page

The link sits at the bottom of every shared page. It opens a short form: you pick a reason from a fixed list — phishing or a scam, malware, impersonation, harassment or hate, explicit content, or something else — and you can add a sentence of detail if you want to.

• You do not need an account, the app, or even JavaScript. It is a plain form.
• You are not asked who you are. No name, no email, no sign-in. Nothing that identifies you is stored with the report.
• What you type is never shown back to you or to anyone else on a page. The confirmation is a fixed thank-you; your words go to a person reviewing the report.
• The page you reported does not see your report. Nothing is sent to the publisher except the fact that a report exists and the reason given.

If a page has already been taken down, revoked, or expired, its report form is not available — there is nothing left to report.

What happens to a report

A report does not trigger anything automatic. Omniscio never scans the page, never classifies it, and never sends its contents to an AI. A person reads the report and decides.

The person who published the page gets an inbox card saying their page was reported and the reason given, coalesced to one card per page. The card asks them to do nothing, because there is nothing they can do — the decision is not theirs.

The product owner sees every open report in the admin console, newest first, with the page's current state beside it.

Taking a page down

The owner's console has one button per reported page: Take this page down.

• It removes the page from the public web immediately, everywhere the content could be fetched — the page itself, its interactive form, the version embedded in other sites, the video, and the thumbnail.
• It deletes nothing. The publisher's file, their record of it, and their existing link are all untouched.
• It is reversible with one click. Putting the page back restores the very same address; the publisher does not need to re-publish or change anything.
• It cannot be undone by the publisher. Editing or re-publishing a share cannot clear a takedown — only the owner can.
• Anyone opening a removed link sees a plain page saying it was removed. They see none of the original content.
• Every takedown is recorded in the owner-only audit trail: who did it, when, and why.

Reporting abuse of the form itself

Reporting is limited per visitor and per page, and every field is size-capped, so the form cannot be used to flood a publisher or to run up cost. A limit is never reported to you as an error about the page — it is simply "too many reports from here today".

What this does not do

• No automatic scanning or blocking. Nothing is judged by a machine.
• No content leaves Omniscio. A report is a message, not a copy of the page.
• The publisher's own controls are separate. Withdrawing or deleting your own share is the normal revoke/delete flow in the Shares panel; it is not a takedown.

Related

What a share is and how one is published at all is on Share artifacts, and the panel you manage your own shares from is on Shares view. The comment thread a reader can leave on a shared page is on Share comments.