Frequently Asked Questions

SBIX has two products:

• Check — analyzes your content and finds similar or copied versions
• Certify — creates a timestamped proof you can keep and verify

Use Check to understand your exposure. Use Certify to create proof of priority.

Use Check to understand your exposure. Use Certify to protect your content.

Yes. Without certification, you have no timestamped proof that you published first. If a dispute arises, establishing priority becomes much harder. Certification creates a verifiable record before any conflict occurs.

No. Your files are never stored.

Your original files are not stored. SBIX works from cryptographic fingerprints.

A score from 0 to 100 indicating how original your content appears based on SBIX analysis. It reflects uniqueness, history, and presence across platforms. It is an analytical signal, not a legal proof.

The Check result also includes a decision (SAFE / REVIEW / BLOCK), a verdict (e.g. ORIGINAL_LIKELY, POSSIBLE_COPY), and a decision_reason — a human-readable audit trail explaining the result.

SBIX Check is designed primarily for images. Support for other file types depends on the workflow and plan.

Not necessarily. It means copies or visually similar content exist in the index. The original may still be yours. Check gives you data to investigate — it doesn't render a verdict.

Yes. SBIX can certify videos. The certification is based on a cryptographic fingerprint of the file. The result is the same: a verifiable proof with timestamp and anchoring.

The Evidence Pack is a standalone ZIP containing 8 files. It works offline, without an account, forever:

• certificate.pdf — digitally signed, human-readable proof
• proof.json — machine-readable, all proof metadata
• timestamp.tsr — raw RFC-3161 timestamp token
• anchors.json — Tezos and Aleph blockchain references
• verify.sh — shell verification script
• verify.py — Python verification script
• verify.md — step-by-step verification instructions
• sha256sums.txt — integrity checksums for all files

Available on Pro and Legal plans.

The proof hash is anchored on public networks (Tezos, Aleph). This ensures integrity and tamper resistance. Only the hash is stored — never your file.

Yes. Every proof has a public verification URL at verify.sbix.io/verify/{proof_id} — no account or API key required. Share it with auditors, lawyers, or any third party.

The Evidence Pack also includes offline verification scripts (verify.sh, verify.py) that confirm authenticity using only standard cryptographic tools and public blockchain explorers — no internet connection to SBIX needed.

A certificate provides timestamped proof of existence: the content existed, in this exact form, at this exact time. It includes a cryptographic hash, a timestamp, and blockchain anchoring.

The Legal plan adds an eIDAS-qualified timestamp (EU Regulation 910/2014, Article 41), which carries a legal presumption of accuracy across all EU member states. This is designed for use in EU legal contexts.

We do not guarantee admissibility in every jurisdiction. Consult legal counsel for your specific situation.

SBIX is operated by GLABTECH SARL, incorporated in Saint-Barthélemy (FR), under EU jurisdiction. Infrastructure runs on EU-based servers (ASN AS30077). The eIDAS timestamps are issued by QTSA.eu (AlfaTrust Certification S.A.), a Qualified Trust Service Provider on the official EU Trusted List.

SBIX certificates can support evidence outside the EU, but legal treatment depends on the jurisdiction and the court.

For EU-specific legal use, the Legal plan adds an eIDAS-qualified timestamp.

Admissibility depends on the court and specific circumstances. Consult local legal counsel for cases outside the EU.

• SHA-256 for fingerprinting
• RFC-3161 for timestamping
• eIDAS qualified timestamp on Legal plan
• Public blockchain anchoring (Tezos, Aleph)

Yes. The SBIX API provides programmatic access to Check and Certify endpoints. Available on Pro and higher plans. Documentation is available in your dashboard after sign-up.

Large files are processed using a hash-based method. The file is fingerprinted locally or streamed to generate a SHA-256 hash. That hash — not the file — is what gets timestamped and anchored. The resulting proof is identical in structure and legal value to any other certificate.