Draft dated 27 October 2026. Unconfirmed facts are marked below. Read our Terms.
Who operates this service
Mirabal Imports is an industry-agnostic B2B connection platform and independent commercial intermediary and sourcing brokerage. [OPERATING LEGAL ENTITY AND ABN/ACN IF APPLICABLE — OWNER TO CONFIRM]. [MONITORED PRIVACY EMAIL AND POSTAL ADDRESS — OWNER TO CONFIRM]. This local-development draft requires legal review before public deployment, including Australian Privacy Principles applicability and requirements in other markets. It is not a compliance certification.
Information we collect and why
Registration collects company name, contact name, business email, international phone, country, Buyer/Seller/Both role and sign-in credentials. Website, registration number, categories and description are optional. Required fields enable account access, verification, matching and communication; without them an account cannot be created. Passwords are hashed locally. We also process commercial requests/offers, search descriptions, messages, read status, notifications, consent records and security events. Owner enquiries may include documents and correspondence. Provide only information you are authorised to share, without unnecessary sensitive information.
Matching and disclosure choices
Matching compares requirements with eligible opportunities. Authorised company names and opportunity summaries can be shown under matching-sharing permission; contact fields are not automatically public. Matching is not a guarantee of reliability, suitability or a transaction. Email verification is not business verification. Owner-managed commercial introductions remain a separate reviewed workflow. Internal notes, credentials and private documents are not public marketplace content.
Optional AI processing
With per-query external-processing consent, enabled marketplace extraction sends your search description and buyer/seller kind to OpenAI. Separate profile/contact fields, other private records and attachments are not sent with extraction. Your typed text may itself contain personal information: avoid including it. Manual entry remains available. Check AI interpretation before relying on it. Separate authorised owner tools can send selected inbound correspondence for reply drafting or limited commercial descriptions for semantic comparison under their own processing and review controls. This does not authorise blanket AI monitoring of marketplace messages. Provider terms and countries must be confirmed before deployment; an API storage setting alone does not establish zero retention.
Messages and exceptional review
Conversations are private between authorised business participants in ordinary operation. Exceptional review for reported abuse, fraud, security or legal requirements must be restricted, purpose-recorded and audited. That production review workflow is not yet implemented. There is no general administrator conversation viewer. Local filesystem operators can nevertheless access development storage; this is not end-to-end encryption. Ordinary administrators must not have unrestricted browsing. A case-scoped Report Conversation process is proposed, not available yet.
Contact sharing and revocation
Contact sharing is off by default. You select available fields from your own profile, review them and explicitly confirm sharing with one conversation counterpart. This is separate from matching consent and does not expose the other party’s contacts. Revocation stops further in-platform display but cannot erase information already viewed, copied or communicated elsewhere. Minimal private consent/audit records may remain. Participant message history can remain after matching consent changes; contact visibility is checked separately.
Storage, providers and overseas processing
The development version uses local files and restricted server routes. Managed production hosting, database/authentication, backups and secret storage remain proposed integrations, not verified production safeguards. Supabase staging was created in Sydney according to the owner; this does not establish all processing, support or backup locations. OpenAI and separately authorised Gmail workflows involve external providers. Counterpart businesses may be overseas. [PROVIDER LEGAL ENTITIES, CONTRACTS, RECIPIENT COUNTRIES AND CROSS-BORDER SAFEGUARDS — TO CONFIRM]. Do not assume Australian-only processing.
Security and cookies
Local controls include password hashing, expiring sessions, server-side ownership/participant checks, same-origin mutation checks and restricted application routes. Message/contact responses use no-store handling. Local persistence uses locking and atomic replacement. These do not guarantee security or substitute for managed access policies, monitoring and tested recovery. Session cookies support sign-in. This version does not introduce advertising trackers. Security/audit records support abuse prevention and investigation and must remain purpose-restricted. Before public launch, establish an incident-response process to contain suspected breaches, assess affected information and risks, preserve limited evidence, and notify affected people and regulators where required by applicable law. [INCIDENT CONTACT, RESPONSIBLE TEAM AND APPLICABLE NOTIFICATION DUTIES — TO CONFIRM]. This is a required operational process, not a claim that a managed incident-response service is already in place.
Retention and deletion
[CATEGORY-SPECIFIC PERIODS, DELETION TRIGGERS, BACKUP EXPIRY AND LEGAL-HOLD RULES — TO CONFIRM]. The prototype has no complete account-erasure or retention scheduler. Proposed production practice is deletion or de-identification when information is no longer needed, subject to justified legal obligations and holds. Messages, consent evidence and transaction records may require different treatment. Requests require identity/authority checks, a scoped response and an explanation of limits, including retained backups and counterpart copies.
Access, correction and complaints
Edit your company profile in your account. For access, correction, deletion or a complaint, use the monitored privacy contact once confirmed above; never send credentials. Proposed procedure: verify identity proportionately, acknowledge and assess the request, explain the outcome and lawful limits, and provide escalation. [RESPONSIBLE PERSON, RESPONSE TIMEFRAMES AND COMPLAINT ESCALATION — TO CONFIRM]. Where applicable, unresolved complaints may be taken to the OAIC or relevant regulator. The prototype contact form is not evidence of an operational privacy-request service.
Legal requests and marketing
Legally required disclosures must be assessed for authority and scope, limited to necessary information and privately documented; notify affected people where lawful and appropriate. Registration is service processing, not optional marketing consent. No marketing opt-in is collected by this form. Future marketing requires separate choices and effective opt-out. Accepting Terms does not replace other necessary consents. Review and update this draft before materially different processing.