Privacy policy

Information received by the website

An enquiry requires your name, country, at least one contact method — phone or email, selected crops, quantities and units, and a consent check. Company, comments, variety, calibre and shipment month are provided where relevant. Delivery terms are sent with the enquiry. The form cannot accept an enquiry without the required information.

The enquiry record includes language, website domain and page path, supplied UTM campaign tags, enquiry ID, receipt time and consent version. Duplicate prevention data and manager delivery attempts are also stored. Do not include payment details, identity documents or other information unnecessary for a supply enquiry in your comment.

How information is used

Enquiry details are used to review your request, prepare an offer, clarify delivery terms and respond through the contact provided. Technical records help prevent spam and duplicates, track delivery and recover data after failures.

The form requires a separate consent check; analytics consent is selected separately. The controller must determine the final legal grounds for enquiry processing, website protection and retention before public launch. This draft does not replace that decision.

Storage and recipients

Enquiries are stored in the application database. Once live channels are connected, they are sent to authorised company managers through Telegram and email; delivery failures may lead to repeated notifications. Staff with server access can export enquiries as CSV files. These copies also contain enquiry data.

The public version is intended to use hosting, Telegram, an email provider and Cloudflare Turnstile to protect the form. Google Analytics and Yandex Metrica are added if analytics is enabled. Actual providers, processing locations, access arrangements and international transfers must be identified before launch. Storage exclusively in Georgia has not been confirmed.

In the current development preview, notifications and Turnstile checks are simulated; live delivery to recipients is disabled. Test enquiries are still saved in the database.

Technical information and form protection

The API uses your IP address for rate limiting and stores a keyed cryptographic representation in its rate-limit table. Old entries are cleared during subsequent rate checks after one day. The IP is not added to the enquiry payload, but may appear in web server and infrastructure logs; their retention periods remain to be defined.

If a local country lookup database is connected, the server processes the IP to suggest a country without contacting an external GeoIP service. With live Turnstile, the browser connects to Cloudflare and the server verifies its token. These processing arrangements must be covered by the final policy.

Requests about your information

For requests concerning access, correction, deletion or withdrawal of consent, contact info@janilife.com. Include the enquiry ID if known and the contact used for submission. Do not attach an identity document unless separately requested with a justification.

Request verification, applicable response periods and exceptions must be defined before public launch. Analytics consent can be withdrawn in cookie settings. The final text must describe applicable rights and the route to the competent supervisory authority.

Analytics and browser settings

External analytics is disabled in development. In the public version, Google Analytics and Yandex Metrica are intended to load only after you select “Allow analytics” and configured counters are available. Refusing analytics does not prevent an enquiry. Cookie settings let you change your choice and withdraw consent.

The analytics choice is kept in browser local storage and treated as valid for 180 days. Each website domain stores its choice separately. This period applies to your choice, not to retention by analytics providers.

Application events contain the page path and language, without enquiry field values. Form fields are excluded from Yandex Metrica session replay. Replay may be enabled on pages without URL parameters, a fragment or a referring address. Provider retention periods and data settings still require agreement.