FAQ

A Redtail record is a structured digital entry created by an organisation, describing a physical object or document. It contains the information the issuing organisation provides — title, description, attributes, media — and, where applicable, a reference to a public anchor transaction on a public ledger. Each record has a public verification page.

The issuing organisation creates the record through its Redtail account. Redtail does not create records on behalf of issuers and does not validate the substance of a record before publication. The issuer is responsible for the accuracy and lawfulness of the information published.

No. Records are not legal proof of authenticity, ownership, custody, condition, value, legality, or regulatory compliance. They are a structured digital record of the information provided by the issuing organisation.

Verification means confirming that a published record's data and media match what was committed to a public anchor at the time the record was created. It does not prove that the underlying claims about the physical object — authenticity, ownership, condition, value, custody, or legality — are true.

Today, the issuer of a record is identified by the information provided by the account that created it (the organisation's name and details, recorded inside the record). Issuer identity is not currently independently verified by Redtail and is not cryptographically bound to the wallet that submitted the anchor transaction. See the verification specification for details.

Creating records requires a Redtail account. Public verification pages can be viewed without an account.

Records are published with a public verification page at a URL of the form redtail.id/v/<...>. Anyone with the link can view that page without an account.

The on-chain anchor transaction is immutable and cannot be deleted. The structured record data and media on the verification page may be edited by the issuer through their Redtail account; the integrity check on the public verification page is computed against the anchored content, so subsequent silent substitution of the anchored fields is detectable.

Redtail uses subscription plans for authenticated Record publishing. Each account gets one free test Record. After that allowance is used, publishing additional Records requires an active Subscription Plan, unless the account has an administrative or sponsored exemption.

Current plans, limits, billing intervals, and prices are shown on the pricing page before checkout. Public overage is not currently offered; if you reach your plan limit, you may need to wait for the next billing period or choose a higher plan.

Subscription payments are processed through Stripe at checkout and renew automatically on the selected monthly or annual interval until cancelled. You can manage cancellation from the Redtail billing dashboard.

Yes. Billing details may be collected during Stripe Checkout or stored in your account and reused for future billing documents.

Stripe may generate subscription invoices, Stripe invoices, or payment documents for subscription payments. Redtail may also keep its own billing records and invoice archive for accounting, support, and legal retention purposes. These documents should not be described as Polish VAT or KSeF invoices unless and until that treatment is confirmed and implemented.

PLN (Polish zloty) is the binding transaction currency unless a checkout page or written agreement clearly states otherwise. If you see an EUR amount anywhere on the site, it is an approximate equivalent for informational purposes only.

If a subscription payment fails, your subscription may become past due or inactive. While there is no active subscription entitlement, you may be unable to publish additional Records. Your existing Records remain accessible, subject to the Terms of Use and our moderation and security rules.

Historical one-off charges from the previous per-record billing model may remain visible in billing history and may still need to be paid if they were validly incurred before the subscription model was introduced. New authenticated Record publishing is handled by subscription entitlement, not by the old per-record postpaid model.

You can cancel a subscription from the Redtail billing dashboard. Unless stated otherwise during cancellation, the plan remains active until the end of the already paid billing period and then stops renewing.

Refunds are not automatic. However, this does not affect your statutory rights. Refunds or billing adjustments may be granted in justified cases, such as technical errors, duplicate charges, payments collected in error, or other exceptional situations reviewed case by case.

If you believe the service was not delivered as described, you may submit a complaint — see our Terms of Use for details.

If you are a consumer, you generally have a 14-day right of withdrawal for distance contracts. For subscription services and digital services, the exact withdrawal rules depend on when the service begins, what has already been performed, and applicable consumer law. Details are described in our Terms of Use.

The person submitting the content is responsible for it. You should upload only content you own or have permission to use (photos, PDFs, descriptions, and attributes).

Yes, if you have the right to use and display that record and its contents. If the third-party document includes personal data or confidential information, make sure you have a lawful basis to process it and that you do not exceed what is necessary.

Please do not upload sensitive personal data, confidential materials, trade secrets, or anything you would not want stored or potentially shared via a link.

We process your uploads (photos/PDFs), the information you enter for the record, account data (if registered), billing data, invoice-related billing details (if provided), and basic technical logs needed for security and reliability. Details are described in our Privacy Policy.

Yes. We use a third-party AI service to analyse your upload and generate a structured draft. The draft is always presented for your review and editing before a record is created. Uploads processed for draft generation are not used to train AI models, in line with our applicable provider terms. This automated analysis does not make decisions that produce legal effects concerning you.

Yes. If the interface provides a delete option (for example in "My Records"), you can remove your records there. If you run into issues, use the contact/feedback form and we'll help.

Deleting removes off-chain data (such as the record page and uploads) where technically feasible. On-chain transaction references (tx hashes) cannot be deleted because blockchains are immutable.

No. Redtail is not a notified body, regulatory authority, auditor, or qualified trust service provider under eIDAS. We do not issue certificates of authenticity, conformity assessments, or other official compliance certifications. We provide infrastructure for organisations to publish and verify their own records.

No. Redtail records are not conformity records. Redtail does not claim alignment or compliance with any specific regulatory framework, including the EU Digital Product Passport (ESPR). Records must not be presented as such.

You may link to or display the public verification page on your website. We recommend referring to it as a "digital record" or "verification page" rather than a "certificate", and including a short note clarifying that the record is a digital attestation by you (the issuer) and not a third-party certification.

Yes. Each record is anchored on the Base network. The only element committed on-chain is the record's content hash, embedded in the calldata of an anchor transaction. Your uploads, record content, and personal data are not written to the blockchain. You can copy the transaction hash from the verification page and open it on BaseScan to check transaction status. A "Success" status confirms the transaction was executed on-chain — it does not authenticate the physical item.

BaseScan is a third-party explorer. Opening it may share your IP address and standard browser data with BaseScan.

QR codes and NFC tags may be used to open a record's public verification page where supported. Behaviour and availability may change as the product develops.

Any printed label can be copied. That is why label scanning opens a public verification page where the record content and anchor reference can be reviewed; the verification page, not the label itself, is what carries the integrity check.

A record published through Redtail can be verified directly against public ledger data, given the record's structured data, the on-chain transaction hash, and the hashing algorithm. The verification specification describes the data needed to do this independently.

Use the feedback/contact option on the site. Share the record link and a short description of the issue. We review reports and take reasonable steps to address them.

Please refer to our Privacy Policy and Terms of Use.