Back to MMA Camp Georgia
Clear before you enquire

Privacy and enquiry information

This page describes the current website and camp-enquiry flow. It separates an availability request from a confirmed booking and records only commitments supported by the current code.

Reviewed 1 August 2026

1

An enquiry is not a booking

Submitting the form asks the team to check availability. It does not create a confirmed booking, reserve live inventory, sign a contract, or take a payment. A booking exists only after the team confirms the final offer and terms with you in writing.

2

Information the form sends

The form sends the details you enter and the choices needed to answer the enquiry. Required fields are marked on the form.

  • full name, email address, phone number, and country
  • preferred discipline, experience level, module duration, and preferred start date
  • package choice and, for full board, room preference
  • optional additional notes and coupon or referral code
  • system-generated submission and event identifiers used to keep retries consistent
3

Attribution and browser storage

The site records form-start, enquiry-submit, and WhatsApp-click events with site, sport, language, selected package, duration, preferred date, event identifier, and a reporting value of 400 GEL. On submission, normalized first name, email, and phone may be included for enhanced conversion matching.

  • Campaign parameters may include utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid, fbclid, gbraid, and wbraid.
  • The site may also read _fbp and _fbc cookie identifiers and record first-landing, referrer, conversion-page, and guide context.
  • The versioned last-touch attribution record is kept in local browser storage for up to 90 days. A session-only fingerprint and event identifier support safe retries without storing raw contact fields in that session record.
  • A WhatsApp handoff context and token cache may also be kept locally for no longer than 90 days, subject to an earlier server expiry.
4

Where an enquiry goes

The site sends the enquiry through its same-origin proxy to Gymnasia’s public camp-enquiry backend. Current code then uses an operational camp spreadsheet, Camp CRM, internal team notifications, follow-up tooling, and email for the enquiry workflow.

This is a functional description of destinations visible in the current code, not a complete processor register or infrastructure-provider list.

5

Retention, security, and requests

This site does not publish a fixed business retention period for submitted enquiries. Email [email protected] to ask how long a particular enquiry is retained, or to request access, correction, or deletion. Gymnasia will assess the request against the records and obligations that apply.

Do not put passport copies, payment-card data, medical records, or other highly sensitive information in the notes field. Ask the team for an appropriate channel if sensitive information is later required.

6

Commercial terms before payment

Displayed dates, packages, rooms, and prices are planning information and enquiry choices, not live inventory. Before paying, ask for a written final offer confirming availability, dates, package and accommodation, total price and currency, deposit and balance terms, and cancellation and refund terms.

Do not book travel until the camp and the terms have been confirmed in writing.