Responsibility & contact
- Legal name
- Dariia Hrinchenko
- Country
- Ukraine
- Legal address
- Pending. Not supplied for publication.
- Privacy contact
- Pending. No public email or other legal contact is approved.
The business status and complete identification of the person or entity responsible for this processing must be confirmed. Ukraine is the confirmed country; it does not by itself establish the law or court for every visitor or service.
This notice covers website browsing and the initial application. Arrangements for sessions, session notes, calls, payments and any later correspondence need their own confirmed details before those activities begin.
Application information
The reviewed local form requires an email address. Phone or messenger details, name, timezone and a brief request are optional. The form also records the phone-country selection or default, messenger service and any supplied service name, session format and language selections, the required acknowledgements, a consent version, a random request reference and submission time.
Please keep a request brief. You can leave the request field blank. Do not include medical records, detailed sexual or health history, or another person's identifying information. For a couples request, avoid sharing a partner's private details.
The application is intended for people aged 18 or over. The form asks for an adulthood acknowledgement; it does not collect identity documents or verify age independently.
Purpose & permission
The application flow is designed to save a request for review and follow-up about a possible session, prevent repeated or abusive submissions, and notify reviewers that a request arrived. There is no marketing subscription or automated suitability decision in this flow.
The form currently requires separate acknowledgements about the process and application data use. A checkbox alone does not resolve every legal requirement. Health or sex-life information can need additional protection even when a visitor volunteers it.
Before publication: confirm the applicable legal grounds and any specific consent needed for sensitive information, plus a working way to withdraw consent. GDPR applicability remains to be assessed; this draft does not claim it applies universally.
Storage & recipients
In the connected local application, submissions pass through the website's server endpoint into a dedicated private area of a shared Supabase project. Its configured database region is London, United Kingdom. Application records are not available through a public visitor-facing read endpoint.
With the permission shown on the form, new submissions are also sent to Dariia’s configured Telegram review group. The notification includes the request reference and the information you supply: contact details and, for the full application, name, session and language preferences, time zone and request text. Group members and Telegram process this information; Telegram is separate from the private database. Please keep the initial request brief and do not send medical records or another person’s private information. Earlier submissions made under the reference-only notice are not resent with their details.
Administrators of the shared database can have access beyond this application's private area. A private schema is not a separate administrator or backup boundary. The website host also handles the network requests needed to serve the site and its application endpoint.
Before publication: confirm authorised reviewers and administrators, hosting and processor arrangements, provider access and subprocessors, follow-up email or messenger providers, and safeguards for international transfers. A London database region does not establish that all processing stays in London.
Technical information
Serving a page involves network information such as an IP address and request headers. The application endpoint uses a keyed hash derived from the network source to limit submissions. The application record stores that hash, rather than the raw IP address. This does not describe all hosting or provider logs.
The editable phone-country default can be suggested from your browser language or, when available, a country code supplied by the host from the network request. This does not request your device's precise location.
Site code keeps the form's retry reference and unsent text in page memory. It does not save application drafts in cookies or local storage. A separate local-storage preference records only your analytics choice. Browser autofill, session restoration and caching are separate browser features. See Cookies & storage.
Optional analytics
Only after you allow it, the local candidate counts a page visit, the first Apply click and a signal that an application was successfully saved. It records campaign labels from explicitly tagged links, the referring website's hostname, coarse device/browser categories and a host-supplied country code where available. Full referring URLs, arbitrary query strings, search terms and precise location are not stored.
A random visit reference stays in page memory, with no persistent visitor ID. It does not identify a person or count unique people across visits or devices. Analytics records contain no application reference, name, email, phone, messenger detail or request text; they are not joined to application records. Source attribution can be missing when another service suppresses its referrer or a visitor declines analytics.
The password-protected owner view contains aggregate statistics. Records use dedicated private tables in the same shared Supabase project, with no public read endpoint. An expiring keyed network-source hash is used separately for abuse protection, not as a visitor identifier. The normal analytics window is 90 days; old analytics records are removed during subsequent analytics operations, not by a guaranteed scheduled purge while the site is idle. The application retention policy remains separately unresolved.
You can refuse or withdraw analytics using Privacy choices in the footer without affecting an application. Browser privacy signals keep it off. These safeguards are an implementation choice, not a general certification of legal compliance or approval to open public applications.
Retention & deletion
No retention period or deletion schedule has been approved. The reviewed application has no scheduled automatic deletion. This draft promises neither a fixed storage period nor immediate or automatic erasure.
Before launch, the owner must approve and implement retention criteria for requests, consent records, the abuse-prevention hash, follow-up correspondence, logs, notifications and backups. The final notice must explain those criteria and any limits on deletion.
Your rights
Ukraine's personal-data law provides rights to information and access, to challenge processing, to seek correction or destruction in the circumstances set out by law, to withdraw consent and to complain to the Ukrainian Parliament Commissioner for Human Rights or a court. Other rights may apply depending on your location and the processing.
A public route for privacy requests is still missing. The final notice must identify it and explain how requests are handled. Do not submit sensitive information through the application form to exercise a privacy right.
You can find official information on the Ukrainian Commissioner's data-protection page.