Privacy Policy

Controller identity

The controller for the processing described in this policy is Thai-Russian Chamber of Commerce (TRCC), หอการค้าไทย-รัสเซีย. Its public office address is shown in the contact details below.

Information we may collect

Depending on the service used, TRCC may collect:

• names, contact details, position, and representative information;
• company, organization, professional, registration, residence, and business-classification information used in a membership application;
• event registration choices, attendance information, and related communications;
• inquiry subjects and messages;
• supporting documents, including a passport or national ID, representative photo, registration documents, or payment proof where the relevant workflow requests them;
• independent publication choices for member-directory or representative information;
• technical and security information such as request time, requested path, network address, user agent, form-protection events, and server logs.

Membership applications

TRCC uses membership application information to receive and review an application, verify applicant and supporter details, communicate about the application, make membership decisions, request or review supporting documents and payment proof where applicable, and create membership records after approval.

Submitting an application does not itself create a public profile. Public directory fields and a representative photo may be shown only after the relevant independent permission, membership conversion, TRCC review, and public eligibility checks.

Event registration

TRCC uses event registration information to administer attendance, capacity and waitlists, communicate registration decisions and event details, manage event operations, and review payment proof where a selected registration option requires it.

Registration data and payment proof are private operational records. They are not public event content unless a separate, clearly identified publication permission and review process applies.

Contact and inquiry forms

TRCC uses information submitted through contact and inquiry forms to review the message, route it to the responsible operator, respond to the sender, protect the form from abuse, and keep an appropriate communication record.

General inquiry forms are not intended for unnecessary identity documents, financial data, or other sensitive information.

Required and optional information

Required fields are identified in the relevant form. If required information, an acknowledgement, or a required supporting file is not supplied, TRCC may be unable to accept, evaluate, or complete the requested application, registration, inquiry, or payment-review step.

Optional fields and separate publication choices may be left blank or unselected. A publication choice does not approve an application or make information public by itself.

Purposes and processing grounds

TRCC processes personal data for the service requested by the person, for administration of membership and events, for communications, for record keeping, and for website security and abuse prevention.

Depending on the interaction and applicable law, processing may be necessary to take requested pre-contractual steps or administer a relationship with TRCC, to meet an applicable obligation, or for legitimate operational and security interests that do not override the person's rights. TRCC relies on consent where the website asks for a separate choice, including an applicable public-directory or representative-publication choice; that choice can be withdrawn for future publication by contacting TRCC.

Uploaded and sensitive documents

Passport or national ID files, registration documents, representative photos, and payment proof are used only for the workflow in which they are requested. Access is limited to authorized operators or representatives who need the information for review, verification, payment administration, or the related decision.

These files are not intended for public display. A representative photo may be published only under the separate permission and public-review conditions described above. Users should submit only the document pages and details requested for the relevant workflow.

Recipients and service providers

Personal data may be available to authorized TRCC staff, operators, committee or Chamber representatives, and event personnel where their role requires it for the relevant purpose.

TRCC may also use categories of service providers needed to operate the service, such as website hosting and infrastructure, email delivery, private file storage or backup, security and maintenance, and event or payment administration where applicable. This policy does not name a provider unless its current role has been independently confirmed.

TRCC does not sell personal data.

International processing

Website, communications, event, or infrastructure providers may process data in jurisdictions in which they operate when this is necessary for the relevant service. TRCC does not list specific transfer countries in this policy without confirmed operational evidence.

Where an international transfer occurs, TRCC will address it according to the applicable requirements and the actual service arrangement.

Cookies, embeds, and analytics

The website uses technical functions needed for normal operation, including session and security cookies where a service requires them, form-protection state, and server logs.

At publication of version 1.0, analytics counters are disabled. Google and Yandex site-verification meta tags may be present; those text-only verification tags do not themselves load an analytics tracker. If analytics is enabled later, this policy and any required choice mechanism must be reviewed before the tracker is loaded.

Some pages may link to or embed third-party content, including privacy-enhanced YouTube content. Loading or activating that content may connect the browser to the external provider, whose own terms and privacy information apply.

Retention

TRCC keeps information only for as long as reasonably needed for the relevant application, membership, event, inquiry, payment, record-keeping, dispute, security, or applicable legal purpose.

Periods differ by record and workflow. This policy does not state a fixed period where no confirmed retention schedule exists. Information may be archived, restricted, corrected, or deleted through the applicable operator process.

Security and operational logs

TRCC uses access controls, private storage boundaries, validation, form-abuse protection, backups, and operational logging appropriate to the website workflow. Access to private submissions, documents, payment proof, and internal notes is restricted to authorized roles.

No website or online transmission can be guaranteed to be completely secure. Users should avoid submitting information not requested by the relevant workflow.

Your data-subject rights

Subject to applicable law, a person may ask about access to personal data, correction, deletion, restriction or objection, portability where applicable, withdrawal of a consent for future processing, or how to raise a concern with the competent authority.

Send a request to the privacy contact shown below and describe the relevant TRCC interaction and requested action. To protect the person concerned, TRCC may request proportionate information to verify identity before disclosing or changing a private record. A representative may be asked to show authority to act. Do not send passport or national ID material unless TRCC specifically requests it through an appropriate channel.

Updates to this policy

TRCC may update this policy when website functions, forms, providers, or operational practices change. The current version and effective date are displayed on this page.

An update does not rewrite the policy version captured with an earlier form submission.

Contact

For questions about this policy or to make a data-subject request, email the dedicated privacy contact shown below. The contact is a TRCC privacy channel and is not described as a Data Protection Officer. TRCC does not state in this policy that a DPO has been formally appointed.