Controller and scope
- Operator
- Sibidz LLC
- Privacy contact
- hello@sibidz.io
- Postal address
- Postal address pending
The operator determines how Sibidz uses personal data to run the service. This notice covers its searchable Floor, lot pages, auction rooms, accounts, bidding tools and platform payment services. Your chosen AI assistant and payment provider have their own notices and responsibilities. UK GDPR and EU GDPR rights apply where the relevant law covers the processing; a Wyoming location does not remove those rights.
Information we use and where it comes from
You, your authorized agent and other auction participants supply account names, handles, email addresses and optional contact details; private principal names, countries and representatives; seller applications and review decisions; lot revisions, auction attempts, descriptions, photos, origin and delivery or fulfilment regions; bids, withdrawals and agreement acceptances; and seller receiving instructions, including a PayPal business email where offered. We also generate account identifiers, credential hashes, verification records, service transactions and timestamps. Platform payment records also include public wallet addresses, transaction identifiers and Bitcoin outpoints, asset amounts, signed payment payloads, operation and refund authority, financial-terms acceptances, address-screening outcomes, and identity-to-account relationships, account purposes and policy references, promotional awards, per-account balances and holds, exact source and destination allocations, fee waivers and linked corrections. These platform records are distinct from the buyer and seller’s direct auction payment.
Requests expose connection information, including IP addresses, to the hosting service. Sibidz uses a keyed hash of the source address for abuse limits rather than storing it as a public identifier. We retain keyed fingerprints of supplied PayPal emails and principal details to flag matching accounts for operator review. Matches are signals, not proof of misconduct. Rate-limit counts and matching-detail signals are summarized to the operator by email; the messages omit raw addresses, names, payment details and credentials. Tokens and private settlement records are never intended for public pages. Do not include private addresses, credentials, sensitive personal data or unrelated people’s information in public lot text or photos.
Purposes and legal bases
- Contract
- Provide requested accounts and auctions, verify email, publish authorized lots and bids, record accepted terms, calculate results, communicate outcomes and supply the seller and winner with their contract and receiving details.
- Legitimate interests
- Protect accounts, prevent abuse, keep reliable auction evidence, provide factual evidence and operate and secure the service. These interests must be balanced against your rights. For a business representative or other person who is not personally a contracting party, these interests may support necessary service records.
- Legal obligations
- Meet applicable recordkeeping, disclosure and rights-handling duties where a specific law requires them.
- Consent
- If a separate optional use requires consent, ask separately. Agreement acceptance is not consent to marketing, advertising or unrelated processing. You may withdraw a consent-based permission for the future without affecting earlier lawful use.
Email and necessary account and contracting details are required for authenticated participation; without them Sibidz cannot verify an account or accept a bid or listing. You may search and browse the Floor, read lot pages and watch auction rooms without registering, accepting an agreement or authorizing a bid. Optional profile contacts are not required.
Public records and other recipients
Approved published lot pages, photographs, origin and fulfilment regions, public account identifiers and handles, bids, withdrawals and auction results are public. Unpublished and rejected lot content and review reasons are available only to the relevant account and authorized operator; records remain retained for audit. Auction rooms stream the same public bid history, handles, per-lot closing times, extensions and results to spectators without accounts. A website link is public only when its owner supplies website_url for publication on their profile; other contact fields remain private. Public material may be copied or indexed by others. Historical handles identify the account at the time of an event. Sale entries retain the bidding account, accepted terms and timestamp. Public bidder counts reflect participating accounts; private acceptance details are not published. Sealed reserve amounts remain private, including after closing. Private principal names, emails, contacts and receiving details are restricted to the relevant parties and authorized operator access; after a committed sale, only the actual seller and winner receive the necessary counterparty contract details and their expressly consented, frozen verified emails in one shared handover. First bids and seller submissions require separate explicit sale-contact authority. Changing or withdrawing consent prevents reuse for future actions; existing validly accepted obligations and necessary records remain governed by frozen terms.
The service uses DigitalOcean hosting, managed database and object storage, and AgentMail for verification messages, auction-result emails and the hello@sibidz.io inbox. AgentMail processes the email address, message content and delivery information; replies sent to that inbox are also held there. Authorized service providers process necessary data to host, secure, store and deliver the service. When configured for live review, Sibidz sends bounded listing or auction snapshots, associated account and content identifiers, declared origin and fulfilment regions, and supplied image data to its configured AI review provider, currently Grok. Decisions retain the model, policy, evidence references and reasons for review. Explicit development auto-approvals are simulated and do not call that provider. Blockchain observers receive the public addresses and transaction identifiers needed to check payments; for x402 payments, Sibidz verifies the authorized signed transaction and submits it through its configured Algorand node provider. Customer signing keys and recovery phrases are not required. Confirmed blockchain transactions are public, and their public history cannot be erased by deleting an application record. The operator must confirm the processor list and agreements before live launch. Information may also be disclosed where law requires it, or to advisers handling an actual dispute subject to appropriate confidentiality.
Sibidz does not send a purchase payment to PayPal. The buyer and seller provide information to their chosen payment provider themselves. Your AI client may send authorized tool requests and receive responses under its own privacy terms.
Location and international transfers
The configured operator and its hosting, database, storage, email and AI providers can involve different countries. Their actual processing regions and contractual arrangements must be confirmed before live launch. Where UK or EU transfer rules apply, the operator must use an applicable adequacy decision or appropriate safeguards, such as relevant contractual clauses and any necessary additional measures, and make information about the safeguards available on request. This draft does not claim a particular certification, adequacy route or signed transfer agreement.
Search and pageviews
Search filters select matching public lots, including category, location, status, event membership and closing time. The application does not store a personal search history. Successful lot-page views increment aggregate popularity totals without visitor identifiers. Hosting logs may include requested URLs and connection information. Search and public viewing do not create agreement acceptance or bidding authority.
How long information is kept
Account and contact information is needed while an account is active and for resolving outstanding auctions, requests or disputes. Auction, agreement and service-credit records are retained as evidence of actions and obligations. The operator must set and review a proportionate schedule based on those purposes, applicable legal requirements, dispute periods and rights requests; they are not retained forever merely because a database record is immutable.
Verification codes expire after 10 minutes and their hashes are cleared by the cleanup worker after expiry. Temporary unattached photo uploads expire after 24 hours. Email payloads are cleared when completed, superseded or expired; outbox metadata is removed by cleanup seven days after its expiry. Photos retained with saved seller listings, published lots and other historical records currently remain with the auction history. Backup retention and broader account/history deletion periods still need operator confirmation.
There is currently no self-service account deletion. A request needs operator review, including whether erasure, restriction or redaction is required and whether any lawful retention exception applies. Public copies made by others may remain outside the operator’s control.
Your rights, including the right to object
Where applicable, you can request access, correction, erasure, restriction and a portable copy of information, and withdraw consent where it is the basis for a use. You can object to processing based on legitimate interests on grounds relating to your situation. Any direct-marketing objection must be honored. These rights have conditions and lawful exceptions; the operator must explain any refusal and the available complaint route.
Use the privacy contact above once confirmed. The operator should verify identity proportionately, avoid requesting unnecessary documents and respond within the applicable statutory period, normally one month under UK/EU rules, explaining any permitted extension. No public data correction should silently falsify a recorded auction event.
You may complain to the UK Information Commissioner’s Office or your relevant EU supervisory authority, including where you live or work or where an alleged infringement occurred. You do not have to waive that right or first resolve the matter with Sibidz.
Automated rules and human review
Software validates bids against the public opening price, tick, closing time, registration and frozen rules, and checks the sealed reserve when determining whether a sale completes. The standing valid highest bid wins only when the closing result is recorded; a retraction may leave no standing bid. Automated limits can reject requests or restrict account actions to prevent abuse. These decisions can affect your ability to participate or create a purchase obligation in a live auction. Automated listing checks evaluate the supplied content, photos and declared regions; they do not certify identity, ownership, authenticity or legal compliance. A current approved lot check is required for publication, and changed or expired evidence can require a new check. Uncertain or challenged decisions may require an authorized operator’s review. Payment-address screening is a separate process that can hold a financial operation; a clear result is not legal clearance.
If applicable data-protection law gives you rights concerning a solely automated decision with legal or similarly significant effects, you may request human intervention, explain your position and contest the decision through the operator. The operator must assess the applicable basis and safeguards before live operation; this notice does not promise that a recorded sale can simply be reversed.
Children, security and website storage
Participation is restricted to people aged 18 or older. Sibidz does not request dates of birth; an explicit age declaration is required when accepting an agreement. Contact the operator if a minor’s account or information is identified.
Credentials are hashed and sensitive agreement and receiving details are encrypted. Access is limited by account role and participation. These measures do not make a public HTTP connection private; use a secure connection for real personal or payment information. Public pages do not currently set analytics or advertising cookies or load third-party trackers. Your browser, hosting provider and connected AI client may process connection data separately.
Changes
Notice versions carry a date. Material changes should be communicated before any new use where required. A privacy-notice update does not rewrite frozen auction terms or remove existing rights.
Referrals and invitations
A signed first-party cookie retains the first valid referral link for up to 30 days. If your agent creates an account during that period, we record the referral, its qualifying first bid and any reward or review decision. Existing accounts are not attributed. We use existing verified mailbox and account signals to prevent duplicate rewards; referrers see aggregate counts, not recipients’ email addresses.
Invitation email content is encrypted while queued. A keyed address fingerprint prevents repeat invitations and records opt-outs. An agent can provide a private, read-only referral view. Its limited cookie expires with the agent-provided link, which is removed from the address bar when opened. Registration and invitations are handled through your connected agent.