Privacy & Cookies.
How your data is handled on this site
Who I am
I'm Vladimir Vishar, a self-employed tattoo artist accepting enquiries for future London appointments. This site, vishartattoo.com, is my portfolio and enquiry point. You can contact me directly at [email protected].
What I collect, and why
When you use an enquiry form on this site, you may be asked for your name, email, phone or WhatsApp number, Instagram username, preferred reply method, location, tattoo idea, placement, size, preferred timing, cover-up details and reference images. The book waitlist asks only for a name and email address.
That information is sent to a private backend I run on Cloudflare, which forwards it to me so I can reply. It's used to respond to you and handle the tattoo request. It is not sold or used for unrelated marketing. It may be processed by the site's technical providers where needed to deliver the message, and if you proceed with booking, may be used where needed to handle the enquiry or booking.
Tattoo enquiries and reference images are sent directly to me through a private Cloudflare Worker and my private Telegram chat. Sending a form does not reserve an appointment. If the project proceeds, I will explain the deposit, confirmed studio, dates and booking terms before payment.
Enquiry assistance and email drafts
Before you submit a tattoo enquiry, the form may run an optional clarity check on the project description. This check sends only the project type, placement, approximate size, tattoo idea, cover-up status and the number of reference images to a decision-model provider so the form can suggest a small number of pre-written clarification prompts. Your name, email address, phone number, Instagram handle and the reference images themselves are not sent to that provider.
The clarity check is processed through OpenRouter and TypeSafe's Jev model with zero-data-retention and data-collection-disabled controls requested on every call. If you leave the form without submitting it, the draft enquiry itself is not saved as an enquiry, client or project. The CRM keeps only limited technical preflight telemetry such as the event id, outcome, categories, provider result and latency; it does not store the draft tattoo text in that telemetry.
After you submit a tattoo enquiry, Cloudflare Workers AI may process the saved enquiry text to extract the details you provided, identify missing information, prepare a short internal summary and create a suggested reply. The result is kept with the correct private client and enquiry record.
When authorised studio staff view Gmail correspondence already linked to an existing client and enquiry, a new relevant incoming email may be processed in the same limited way. Gmail access remains restricted to authorised staff and the linked client context.
The assistant cannot accept or decline an enquiry, set a price, promise a date, confirm a booking, mark a payment, or send a message. A person reviews and can edit every reply draft before anything is sent.
Reference images are not sent to or analysed by the AI in this version.
Cookies & analytics
No optional analytics or advertising-measurement cookies are set unless you accept them. Advertising measurement uses separate consent choices, so an older analytics-only choice does not automatically enable OpenAI Ads or Meta advertising measurement.
If you accept analytics cookies, this site loads Google Analytics, Google's website analytics service, to see which pages are visited and how the site is used overall. I use this to understand what's helpful and improve the site — it does not identify you personally. Google Analytics only runs after you accept it; if you decline or do not respond, it is never loaded and no Google Analytics cookies are set. This analytics data is not used for advertising or remarketing: I do not run Google Ads, and Google Analytics is not linked to any ad platform.
On the tattoo enquiry page, you may separately accept OpenAI Ads measurement so I can measure whether a ChatGPT ad click resulted in a successfully submitted enquiry. That measurement uses the OpenAI Ads Measurement Pixel and may also send the same confirmed conversion server-to-server through the OpenAI Ads Conversions API. For a fresh visitor, the enquiry page can present optional analytics and advertising-measurement purposes in one consent banner. The Pixel can store the OpenAI click reference (oppref) in a first-party __oppref cookie and an opaque browser reference in a first-party __obref cookie so a later conversion can be associated with the original ad interaction.
If you accept Meta advertising measurement on the tattoo enquiry page, the Meta Pixel loads from Meta and records a PageView. After an enquiry has been successfully saved, it records the standard Lead event. Meta may set or read advertising-measurement identifiers such as _fbp and, where an ad click identifier is available, _fbc. During migration, the existing advertising Pixel and the replacement company-owned Pixel may each record a separate PageView and Lead for the same confirmed enquiry; both are governed by the same optional Meta consent. The existing advertising Pixel stays in use for active campaigns until a separately verified transition. The Meta Pixel is not loaded before the relevant consent. With renewed, explicit consent to the expanded Meta measurement purpose, my backend may also send a confirmed enquiry through Meta Conversions API using the same event ID for deduplication, and later send limited CRM conversion-status events (qualified enquiry or booked client). Email and phone number, where available, are normalized and SHA-256 hashed before being sent for attribution/matching. The raw contact values, reference images and tattoo details are not sent to Meta for ad measurement. Previously saved Pixel-only consent does not authorize this expanded processing; a new acceptance is requested.
The OpenAI Ads and Meta lead events are sent only after the enquiry has been successfully saved. OpenAI Ads measurement does not manually transmit your contact details. Meta's optional, separately consented Conversions API may use SHA-256-hashed email and phone number for attribution/matching. Neither advertising integration receives your tattoo description, reference images, private notes or unrelated CRM conversations.
Your consent choices are stored in your browser's localStorage so the prompts do not keep reappearing.
You can reset your choices at any time:
Third parties
This site is hosted on Cloudflare, which provides security and delivery for every visit. Cloudflare also provides the private backend and Workers AI used for the limited enquiry assistance described above. Site fonts are self-hosted. Telegram processes enquiry messages and reference images so they can reach me. Google provides Gmail for authorised correspondence linked to existing client and enquiry records. If you accept optional measurement, Google Analytics may process aggregate site-usage data, OpenAI may process the advertising-measurement event and click-reference data described above, and Meta may process PageView, Lead, limited CRM conversion-status events and consented hashed contact identifiers described above. No optional measurement event is sent before the relevant consent.
How long I keep things
Enquiry messages are kept only for as long as needed to reply and, if you go ahead, arrange the work. If you'd like your enquiry data deleted sooner, email me and I'll remove it.
Your rights
Under UK GDPR you can ask to access, correct, or delete the personal data I hold about you. To do so, email [email protected]. If you're not satisfied with how a request is handled, you can complain to the UK's Information Commissioner's Office at ico.org.uk.
Last updated: 9 September 2026.