Privacy
This privacy notice reflects the current production workflow. Public Trade Requests, Deal Room requests, Compliance submissions, Contact messages, support tickets, email queue entries, AI usage records where configured, rate-limit events, and Admin workflow records are handled through server-side Supabase routes when submitted.
Information collected
Submitted workflows may include role, commodity or project details, route, quantity, contact details, company or counterparty information, message content, document status notes, department routing, locale, reference identifiers, and technical request metadata used for rate limiting and audit.
How information is used
Information is used to route requests, support human review, queue contact or email responses, operate Admin workflows, maintain audit records, diagnose platform health, and improve public guidance.
Storage and browser data
Operational records are stored in Supabase through server-side access. Public clients do not receive service-role credentials. Language preference and AI session history may be stored in the user's browser localStorage.
Sensitive documents
Do not submit private keys, wallet recovery data, bank credentials, or confidential shipment documents through public forms. Admin-only upload URL generation exists for controlled private document workflows; public document upload is not open.
Third-party processing
Where configured and used, email may be processed through Microsoft Graph or SMTP, AI questions may be sent to server-side OpenAI, and Pi flows may process Pi identifiers. No public analytics or tracking script is present in the repository.
Data rights and legal gaps
Users may contact support@persiangulf.app for privacy requests. Fulfillment depends on applicable law, requester verification, operational retention needs, and legal details still requiring owner or lawyer confirmation.