SaqrBridge
Sign inCreate an account
Method

Register of consent statements

Nine binding acts, nine distinct texts. Each is displayed at the precise moment of the act, in an identified version, with a checkbox never pre-ticked. This register publishes all of them, in full, before registration even opens.

Why these texts are versioned

A single blanket acceptance of general terms at sign-up protects against nothing. It is signed once, often unread, and says nothing about the precise act a party performs six weeks later when filing an export permit or confirming a delivery. That is why consent here is granular and replayed at every step.

Each text carries a code, a version and a fingerprint, a digital signature computed on its exact content. When a user ticks a box, we record their identity, the date and time, the IP address, the version of the text and this fingerprint.

The consequence is simple, and it is the whole point of the system: it is the version accepted by the user that is binding, not the one shown on this page today. If a text is amended, the previous version stays archived unchanged and remains enforceable for acts performed under it. Rewriting a text never rewrites what was accepted before.

Register map

When each text appears, who signs it, and what it covers.

CodeMoment of the actSignatorySubject
A1RegistrationThe registrantAccuracy of the information provided, acceptance of the general terms in their current version, right to refuse or suspend the account.
A2Publishing a listing or a Saqr IDThe sellerLegal possession of the bird, captive origin, closed ring and transponder, permits held, and a reminder that publishing does not amount to verification.
A3Opening a case fileBoth partiesAcknowledgement that SaqrBridge is not a party to the sale contract concluded between them.
A4Filing each documentThe party filing itAuthenticity and currency of the document filed, and the consequences accepted for a false or expired document.
A5Ordering a verificationThe payerExact scope of the service, identity of the third-party verifier, limits of its opinion, cap on liability.
A6Completing each milestoneThe party responsible for the milestoneConfirmation of having completed the step for which it bears legal responsibility, on the stated date.
A7Off-platform paymentBoth partiesAcknowledgement that SaqrBridge does not hold the funds, provides no escrow and guarantees no payment.
A8Handover of the birdSeller and buyerDelivery completed, receipt in conformity, and any reservations recorded where applicable.
A9Closing the case fileBoth partiesMutual release regarding performance of the contract, without effect on either party's legal obligations.

Current texts

Current version of each consent statement, as it will be displayed at the time of the act.

What a consent statement proves, and what it does notA recorded consent statement proves that an identified person declared something, on a given date, in a given version of the text. It does not prove that what was declared is true. That is exactly the purpose of the verification layers, and it is also why responsibility for each declaration stays with its author. See the four layers.
Draft versionThese texts are a working draft. They will be validated by a lawyer before the service actually goes live, and their final version may differ from the one published here. We would rather say so than let anyone believe they are already final.