Nabiora documents

Terms of use

Rules for platform access, listing publication, moderation, and user interactions.

Last updated: July 25, 2026

Document status

This document is a product working draft and is not final legal advice.

Nabiora is operating as a beta platform; the operator and official legal details will be published separately when the service is ready for public release.

Current product behavior

Nabiora uses Supabase Auth for sign-in and sessions, PostgreSQL with RLS for data, and Supabase Storage for listing photos.

The project includes profiles, listings, photos, favorites, buyer-seller messages, notifications, reports, manual moderation, and audit logs for administrative actions.

Automatic listing translation runs only when the feature flag and external DeepL provider are configured; quotas and fallback behavior exist, and translations may be unavailable.

A production email provider, analytics, and advertising trackers are not currently wired in the codebase.

Account and access

Posting listings, messages, favorites, and reports requires a Supabase Auth account.

Users are responsible for profile accuracy, account access security, and the legality of their listings.

Administration may restrict accounts for violations, fraud, spam, or attempts to bypass moderation.

Listings and moderation

Listings and edits may be manually reviewed before publication or after reports.

Listing photos are stored in Supabase Storage and must relate to the real item, service, or property.

Translations may be generated automatically through an external provider only when enabled; the author’s original text remains the source.

User-to-user deals

Nabiora provides a classifieds platform and in-app messaging, but is not a party to deals, a payment service, a delivery agent, or a quality guarantor.

Check the item, documents, seller, and payment terms before transferring money.