Platform Rules

User Service Rules

What the platform provides

The platform provides requirement and supply information publishing, search, saving, sealed quotes, public questions, permission-based in-platform messaging, bilateral transaction-confirmation records, entity-verification applications, reports and collaboration-issue review. To keep the service safe, it may record business actions, accepted rule versions and necessary audit information.

Current fees and future protected orders

Publishing, search, messages and current collaboration records are free and advertising-free. No protected order fee is collected by this website today. When compliant protected payment is enabled, the proposed service fee is 2.5% of the order amount for the buyer and 2.5% for the seller, separately shown to each party before they agree; applicable coupons can offset only their own platform fee up to that fee. The effective order screen and separately accepted payment terms must state calculation, collection, refunds and settlement before any money is taken. Payment cannot raise a publishing limit or bypass community rules.

Accounts and eligibility

• Users must provide accurate, valid and reachable information and keep their sign-in account secure.
• A person acting for a company or organisation must have authority to represent that entity.
• Accounts may not be impersonated, sold or rented, and the platform may not be used for bulk harassment, fraud or regulatory evasion.
• The platform may request clarification when risks arise and, within current capabilities, close violating posts, reject incomplete verification requests or terminate related confirmation records.

Third-party services

Users independently choose and contract with banks, payment providers, logistics carriers, customs agents, inspectors and insurers. Verify each provider’s identity, qualifications, fees and rules. A platform status does not replace an official payment, logistics, inspection or settlement record issued by that provider.

Responsibility by role

The seller is responsible for truthful supply and lawful provenance, delivery as agreed, and applicable after-sales duties. The buyer is responsible for a genuine requirement, agreed payment, cooperation with inspection and timely acceptance or reasoned objection. The platform is responsible for its own publication, identity-information checks, message and confirmation records, complaint channels, necessary evidence preservation and handling within its control; it does not waive statutory platform duties. Neither a badge nor a platform record guarantees a counterparty’s performance.

Privacy and Data Rules

The platform processes sign-in identifiers, email addresses, display names, contact details users choose to provide, posts, quotes, messages, confirmations, rule-consent records, reports, review records and basic technical logs needed for security.

• A sign-in email is not automatically published as a business contact. It appears in contact details only when the user explicitly enters it there.
• Contact details are masked by default. When a signed-in user deliberately reveals them, the platform records the viewer, related post, viewed account and time for risk control and auditing.
• A public share page displays only information the publisher chose to make public. Anyone with the link may view and forward it without signing in; saving, quoting, commenting, revealing contacts, messaging and transaction confirmations still require sign-in and business permission.
• In-platform messages are visible only to the communicating parties. The current collaboration-issue console does not automatically expose their complete message history to operators.
• The platform records limited product events such as opening a post, starting or completing publishing, submitting an offer, confirming message delivery, using a share action, opening a shared page and returning from that page to the listing. These events use a session identifier and, after sign-in, may be associated with the account to measure reliability and conversion. Share attribution is limited to broad channels such as copy, system share and poster; it does not identify the recipient. Event metadata is allow-listed and does not include message text, contact details, search text, offer notes, listing titles, full URLs or referrers. The online product-event table is checked daily and records older than 90 days are deleted in bounded batches. Encrypted, access-restricted disaster-recovery backups may retain an earlier copy for the separately documented backup lifecycle; they are not used for analytics, and retention cleanup is reapplied after a restore.
• Do not submit passwords, bank verification codes, full identity-document images or sensitive data unrelated to the business purpose.

Business records are retained for as long as reasonably needed to provide the service, audit activity and handle disputes. Access control, minimum disclosure and server-side validation reduce unauthorised access risk, but no online service can promise absolute security.

Publishing and Prohibited Content Rules

Images and a detailed description are optional, but the title, trade direction, source markets, destination, quantity, quantity unit and price mode must be accurate, clear and not intentionally misleading. Users are responsible for lawful product origin, intellectual-property rights, import/export restrictions and their ability to perform.

Live-post limit and listing lifecycle

• Each user may have no more than 10 live posts at the same time. Drafts, paused posts, closed posts and expired posts do not count toward this limit because they are not publicly active.
• A post may remain live for no longer than six calendar months from its publication date. An earlier deadline set by the publisher ends the listing sooner.
• Paused posts are hidden from public discovery and public actions until reopened within their original listing period. Closing a post moves it to history and does not delete its activity record.
• When a post expires, it is removed from public discovery, sharing and new quotes or comments. The publisher may review the old content and create a new post, subject to the same capacity and content checks.
• No payment can increase the 10-post limit or extend a listing beyond six months.

Keep public content contact-free

Do not place phone numbers, email addresses, websites, social-media or messaging accounts, contact links, QR codes or other direct-contact instructions in a post title, description, public comment or uploaded image. Use the platform’s public questions, quote and messaging flows instead. QR codes in JPG and PNG uploads are automatically rejected; ordinary text embedded in an image still depends on reports and human review, and remains prohibited.

Prohibited content

• Fraud, money laundering, unlawful fundraising, phishing links, fake supply, fabricated demand or illegal payment instructions;
• Prohibited or controlled goods, infringing or counterfeit products, and forged credentials, documents or proofs of origin;
• Sanctions evasion, customs or tax evasion, unlawful personal-data trading, or any other illegal content;
• Claims made in the name of the platform, a bank or payment provider that promise escrow, refunds, fund release or absolute transaction safety;
• Duplicate or repeatedly reposted spam, bulk harassment, threats, discrimination, insults, malicious traffic diversion or interference with another user’s normal participation.

Posts should describe a genuine, current and relevant need or supply. Publishers should update or close content when availability changes, answer good-faith questions truthfully and avoid duplicate posts intended only to dominate discovery.

Based on reports and current capabilities, the platform may close violating posts, preserve handling records and cooperate with competent authorities as required by law. Results are delivered through in-platform notices. The current version does not provide account restrictions, proactive operator revocation of an existing verification badge, or a separate appeals process.

Transaction Collaboration Rules

Communicate on the platform

Users are encouraged to keep product questions, quotes, images, videos and transaction details in the platform so that both parties retain one coherent collaboration record. Questions that do not contain private or contact information may remain public for the benefit of other participants. A private conversation can be started only after the publisher accepts the other participant’s valid quote or the two users follow each other. This permission does not imply endorsement or transaction protection.

Creation and confirmation

• A confirmation must relate to a real post and real counterparty. A user may not create one with their own account.
• It must record at least the product, quantity, quantity unit, currency, total amount, and inspection and performance terms.
• Buyer and seller confirm the same content version separately. Until both have confirmed, the terms are not a final bilateral agreement.
• After confirmation, the platform records the account, time and content snapshot. Later edits to the original post do not rewrite that snapshot.
• If terms change, cancel the old confirmation and create a new record for both parties to confirm again.

External payment and fulfilment

Each party must choose reliable banking, payment, logistics, customs or inspection services, verify that the payee and trading entity correspond, and confirm status directly with the relevant provider. A platform confirmation must not be presented as proof of payment, frozen funds, inspection or settlement.

Cancellation

Cancellation means only that the record no longer represents an intention to cooperate on the current terms. Saved confirmations and action history remain. External payments, logistics, contracts or other services are not automatically reversed; contact the relevant provider separately.

Future protected-payment capability

A corporate bank account alone does not activate order-level fund custody. Before enabling protected orders, the platform must publish the compliant collection/settlement route, counterparty identities, per-party 2.5% fee, staged payments, release conditions, evidence, refunds and complaint handling, and obtain separate agreement. Do not pay based on a chat claim or a bank-account screenshot; rely on the official order payment state and verifiable bank/payment-provider records.

Entity Verification Rules

A verification badge means only that the platform reviewed specified entity information. It does not verify products, inventory, creditworthiness or ability to perform, and is not a credit rating, product certification or transaction guarantee.

• Company verification requires a registered legal name matching the public company name, registration number and jurisdiction. Once verified, the public company name cannot be changed directly. A company-name change requires new registration evidence.
• The platform may cross-check submitted information against public registries and record entity type, legal name, country and verification time.
• A jurisdiction change removes an existing badge and requires a new application. A verified company name is locked; changing contact details does not remove the badge.
• Text recognition from a license image is only data extraction. Automatic approval requires authoritative registry or electronic-license verification and proof that the applicant is authorised for that company; this is not yet connected. Uploading an arbitrary image must not automatically create a verified badge.
• Incomplete, unverifiable or inconsistent applications may be rejected with an explanation of what is needed. The current version does not let operators proactively revoke an existing badge.

Reports and Collaboration-Issue Rules

Community conduct

Treat other participants respectfully. Do not harass, threaten, discriminate against, shame or mobilise others to attack a user. Disagree with a price or claim using relevant facts, and use the report function for suspected abuse instead of escalating it publicly. Reports made in good faith are welcome; knowingly false or retaliatory reports are prohibited.

Content reports

Users may report suspected fraud, unlawful content, harassment, infringement or duplicate advertising. A report should explain the facts; duplicate reports do not accelerate review. The platform limits unrelated people’s access to reporter information where practical.

Handling outcomes

Operators decide whether to close a post or reject a report based on the report and the reported content, and record their basis. Complete submissions receive an initial handling response within 1–3 business days; this is not a guaranteed final resolution deadline. There is no separate appeals channel in the current version. If an appeals capability is introduced, submission, review and notification procedures will be published first.

Transaction collaboration issues

The current console shows operators only the submitter’s issue description and related confirmation record. Operator handling is limited to recording a basis, terminating or restoring the in-platform confirmation status and notifying both parties. It does not establish the complete facts or decide ownership of funds, breach liability or another legal dispute.

The platform cannot stop or refund a payment or seize funds, and cannot replace a bank, payment provider, carrier, arbitrator, court or law-enforcement body. If fraud, threats or illegal conduct are suspected, contact the relevant institutions as well. The platform does not promise recovery of funds or resolution of an external dispute within a fixed time.

Operator and Contact Details

This site is currently in trial operation. The public marketplace, post details, public comments and public profiles can be browsed without signing in. Registration and sign-in are required only for publishing, quoting, saving, commenting, contact, following, private messaging, alerts, reports and transaction collaboration. Anyone with a share link may view and forward its page. The page is excluded from search-engine indexing, but that is not a confidentiality measure. Do not put passwords, document numbers or other non-shareable sensitive data in public fields. Use the in-platform report entry or operator console for issues.