Operator and processing purposes
Before going live, insert the actual controller legal name, jurisdiction and contact details. Describe what RFQ fields are collected, how buyers are verified, the purpose of exporter matching and any lawful grounds relied on for processing.
Recipients and international transfers
Disclose that selected RFQ information may be shared with potential exporters in Russia or other permitted jurisdictions. Assess applicable transfer rules and safeguards; do not imply all cross-border data transfers are permitted automatically.
Retention, security and rights
Set documented retention periods for inquiries, logs, attachments and inactive leads. Identify actual processors, hosting and email providers, cookies and analytics; provide appropriate correction, access and deletion routes. The final policy must match deployed technical behaviour.
Frequently asked questions
Technical and commercial answers below are general sourcing guidance. Actual contracts and current destination rules prevail.
Can buyers withdraw a request?
The final policy must explain the applicable process and its limits.
Are RFQs shared automatically?
The site should disclose actual routing and any consent or other lawful basis before collecting data.
Is this draft a complete legal policy?
No. It is an implementation brief pending jurisdiction-specific legal drafting.