OSINTverseDocs

Privacy and the recipient's choices

Display modes, unlisted pages, search-engine indexing, the public profile, what the issuer and the public see, and what account deletion does to a certificate.

Markdown version

OSINT Certificates is built for people who often work under a handle. The recipient controls what the public page shows; the issuer controls what is recorded; OSINTverse signs the record and publishes the keys.

Display modes

A certificate records a name and, optionally, a handle. The public page shows one of:

ModePage showsWhen
Name onlyThe nameAlways available.
Handle onlyThe handle, with a note that the name is withheldWhen the type allows it and the recipient has a handle on record.
Name and handleBothWhen the type allows it and there is a handle.

The issuer chooses which modes a type allows; the recipient picks among them after claiming, on Dashboard → Certificates. Before the claim, the page shows the first mode the type allows that the data supports.

Switching modes never changes the signed record. The record holds a salted commitment to each field; the public JSON discloses the value and salt of the shown field only, so a withheld name cannot be confirmed by guessing. Details are on How verification works.

Unlisted pages

Every verification page is reachable by link only until the recipient turns on Let search engines index the page for that certificate. Until then the page and its JSON twin answer with noindex, and the page is not in the sitemap. Issuers cannot override this.

The page has no third-party scripts and no tracking pixels. The only measurement is a view counter the issuer sees; no visitor logs are kept for a page.

The PDF, the PNG, and the JSON and Markdown twins are checked with OSINTverse before every use (see Caching), so a copy made while your name was shown is not served after you withhold it. A file someone already saved to their own disk is theirs; switching modes cannot reach it.

The email, the claim, and reminders

The certificate email comes from OSINTverse on the issuer's behalf, with one link that claims the certificate. It has no open or click tracking.

  • Claiming needs the address it was sent to. Sign in with that address from the link, or sign in first: a certificate sent to the address on your account waits on Dashboard → Certificates and claims in one click, without the link. That shortcut needs a confirmed address (a sign-in link or a provider that verifies email), so registering someone else's address collects nothing.
  • The claim page hides most of the address. Before you sign in it shows only a hint such as j•••@e•••.com, enough to tell which of your addresses to use and not enough to hand the address to whoever holds the link.
  • Reminders are few and you can stop them. While a certificate stays unclaimed, OSINTverse sends the reminders listed in the limits table and then none. Each reminder says which one it is, and the claim page has a Stop reminder emails button that works without signing in. Reporting the email as spam stops them too.
  • Only the newest link works. A resend or a reminder brings a new link; the earlier one stops working once the new email has been accepted, not before, so a failed send never leaves you without a working link.
  • Nothing becomes public by claiming. Listing on your profile and search indexing are both off until you turn them on.

The public profile

A recipient can list a certificate on their public profile at /u/{username}. The profile exists only once at least one certificate is listed; an account that lists nothing has no public page. It shows:

  • the name as the newest listed certificate that shows a name prints it, otherwise the username only. The name on the account itself is never used: the profile must not reveal more than its certificates do,
  • the account picture, only when a listed certificate shows the name. A picture from a Google or GitHub sign-in often shows a face, so while every listed certificate withholds the name the profile shows initials instead,
  • the social links from the profile settings,
  • the listed certificates, each with its own display mode, status, issuer, and link to the verification page.

Revoked and superseded certificates never appear on a profile, and cannot be listed. An expired certificate can stay, labelled as expired, but is no longer offered to search engines. The profile is noindex unless at least one listed certificate is valid and set to be indexable.

What the public sees, and what it never sees

Public page and JSONIssuer console and REST APINobody
Title, description, issuer name and trust level, recipient as disclosed, dates, fields, skills, evidence link, status, public revocation reason, signatories, record, hash, signatureEverything public, plus the recipient's email and handle, the display mode, the listed and indexable flags, the personal message, the private revocation reason, the email delivery status, how many reminders went out and whether the recipient stopped them or reported the email as spam, the view count, the event logClaim tokens (hashed at rest), salts of withheld fields, the signing key, who filed a report

Searches, cases, wallets, and API keys are never linked to a certificate in either direction.

Data roles

The issuer decides who receives a certificate and what it says; OSINTverse processes recipient data (name, email, optional handle, the issuer's fields) on the issuer's behalf to sign, deliver, and display it. Field keys and labels that look like personal data (birth dates, ID numbers, addresses, phone numbers, and similar) are refused in the type editor.

An issuer can register a webhook: a URL of its own that receives each certificate event (issued, claimed, bounced, revoked, and so on) with the same recipient data the issuer already sees in its ledger, signed so the receiver can check it came from OSINTverse. That data goes to the issuer's system, under the issuer's responsibility; it never includes a claim link, and OSINTverse keeps a delivery record (event, outcome, HTTP status) for the issuer's console.

Name corrections

A recipient who asks for a corrected name sends the issuer the requested name (and handle, where the type allows one) and an optional note. The issuer sees them in the console and decides; an approval reissues the certificate, so the corrected name goes into a new signed record and the old one is marked replaced. The request, the decision, and the issuer's note are kept with the certificate's history for the issuer and the recipient; they are never on the public page.

Reporting a certificate

Every verification page has a Report this certificate button, and it needs no account, because the person a certificate names may not have one. Use it when a certificate names you without your consent, looks forged, was issued by someone pretending to be an organisation, or carries wrong details.

  • You pick a reason and may add a few lines and an email address for a reply. Both are optional.
  • A person at OSINTverse reads every report. The issuer is not told who filed it, and your email, if you gave one, is shown to OSINTverse staff only.
  • A report changes nothing by itself. After reading it, OSINTverse can revoke the certificate or suspend the issuer; a suspended issuer's certificates keep their real status and say so.
  • If the details are simply wrong and the certificate is yours, a name correction reaches the issuer directly and is usually faster.

Reports are limited per visitor (the number is in the limits table). The same endpoint is open to tools: see API.

Account deletion

Deleting your OSINTverse account (Settings → Delete account, with its recovery window) does this to your certificates:

  • the certificate is unlinked from your account,
  • it is removed from your profile and set to noindex,
  • the verification page keeps working by id, with the display mode you last chose,
  • the issuer keeps its record, including your email, as the controller of that data.

The record is not revoked, because a revoked-by-deletion certificate would misrepresent what the issuer awarded. To have a certificate withdrawn, ask the issuer to revoke it, or report it.

Deleting the issuer's team

A team that has issued at least one certificate cannot be deleted. Deleting a team would remove the issuer, its credential types, and every certificate it issued, and their verification pages would stop resolving; the deletion request is refused with that explanation. The way out is a suspension: a team owner asks an OSINTverse admin to suspend the issuer, issuing stops, and every certificate stays verifiable with its real status. Revoke what should no longer stand first; a revoked certificate keeps its page and says so.

A team whose issuer never issued anything can still be deleted; the empty issuer goes with it.

On this page