Privacy policy.

Who runs this site

DUXA LIFE and Duxastr Studio are operated by Andrii Danchuk, based in Warsaw, Poland. I handle the personal information described in this notice. You can reach me through the contact page or @ContactDuxaBot on Telegram.

This notice covers the main website, public posts and pages, contact enquiries and the Studio features described below. Some connected services have their own privacy information, linked in the other services section.

Browsing and visitor counts

The server and network or security providers handling a page request receive technical connection information, such as your IP address, requested address, request time and browser information. This supports page delivery, troubleshooting and protection against abuse.

Public pages that include the site's visitor counter create a random browser identifier in local storage. While the page is visible, it sends a periodic heartbeat to this website. The counter keeps a keyed hash of that identifier, first and last activity times, and daily visit records. It counts browsers, rather than identifying you by name. These records are pseudonymous, not a guarantee of anonymity.

The status page shows aggregate visitor counts and server health. The counter does not send your name or the contents of contact forms as part of its heartbeat. Clearing browser site data removes the identifier from your browser; it does not automatically delete records already held on the server.

Journal articles may adapt my public Mint Mode channel notes and link to the original Telegram posts. New channel records are held as editorial drafts and become website posts only after my approval.

Cookies and local storage

Browser storage is used for features you use on this site:

• Visitor counter: a random identifier stored as duxa-visitor on pages where the counter is enabled.
• Preferences: some pages remember your chosen language. Studio remembers your selected services and display currency on your device.
• Studio form protection: a studio_session cookie helps protect submissions against forged requests. Its configured lifetime is up to 24 hours.

Local-storage preferences and the visitor identifier have no fixed browser expiry and remain until cleared by you or your browser. You can remove them in your browser's site-data settings. If you return to a page with the visitor counter, it may create a new identifier.

Studio can put selected services and the display currency into the page address so you can share a project configuration. Anyone who receives that link can see those selections. Contact fields are not intentionally added to that configuration link.

Messages and Telegram

When you send the main contact form, the website receives the name or company, reply contact, topic and message you enter. The message is sent through the website's contact service to me through Telegram so I can respond to your enquiry. The notification also includes the IP address associated with the submission for spam prevention. Supplying a reply address does not subscribe you to a newsletter.

If you start @ContactDuxaBot, Telegram provides the public profile information available to the bot, including your displayed name, numeric Telegram ID, username if you have one, language and messages you send. A phone number is available only if you choose to share it. Messages can be relayed between you and me through the bot. Telegram processes this communication under its own policies.

Some links to the Community Archive Google Form also notify me when the link is opened. That notification contains the source page, button label and destination, rather than the answers you later enter into the external form. The external form has its own data handling.

Please avoid sending passwords, payment-card details or unnecessary sensitive information in a general enquiry.

Studio projects and reviews

Studio project requests contain the services you selected, quantities, estimates, display currency and the contact and project details you submit. They are saved on the server and sent to the owner through Telegram notifications to review the request and discuss the work. A request is not an automatic payment.

Studio reviews are saved for moderation. Your submitted name, rating, review text, positives and negatives become public only after approval. Approved reviews are visible to other visitors, and public content may be copied or indexed by others.

To enforce one review per IP address, the reviews database retains a keyed hash of the submitting IP. The review system does not put the raw IP into the review database or public response. The keyed duplicate-prevention record remains even when non-public review text is removed. This protection is separate from technical logs at the server or network provider.

The Studio request-data notice is available in these languages:

• English
• Polski
• Українська
• Русский

Other services

Service enquiries use the PC Help enquiry system and its privacy notice. A services-directory form collects your name, reply contact and message so the relevant provider and site administrator can handle the enquiry. Computer-help work can involve additional device, transport and order details, described in the same notice and the PC Help service terms.

Private chat, shared drawings, notes and other tools may process content you create or share. Read the information shown in the relevant service before submitting private information, and treat shared access links as confidential. A public website page and a private tool are not the same sharing context.

Providers and Google

Hosting and network providers process connection information needed to run and protect the website. Telegram processes messages and notifications sent through its service. Opening another website, such as a Google Form, Steam or a social profile, is also subject to that provider's privacy information. Their processing may take place outside your country.

Google AdSense: Google ad serving on the main pages is disabled during the site's review and consent setup. The site retains an AdSense account-verification meta tag and an ads.txt seller record. Those verification records do not themselves load Google's advertising script.

If Google advertising is enabled, Google and its partners may collect or receive information, including IP addresses and other identifiers, and may place or read cookies, use web beacons or use local storage for ad delivery and measurement. Personalised advertising can also use data to tailor ads. Any required consent choices must be provided before the relevant processing is enabled.

Read Google's Privacy Policy and how Google uses information from sites and apps that use its services.

How long information is kept

• Studio requests: application records are automatically cleaned up after 180 days. Contact-bot profiles are cleaned up after 180 days without further contact.
• Studio bot records: local inbox, relay and sent-notification records are cleaned up after 30 days. These are application-storage periods; they do not automatically remove copies already delivered through Telegram.
• Studio reviews: pending or rejected personal review content is removed after 180 days from creation or the latest moderation. Approved reviews remain public until withdrawn. The keyed duplicate-prevention reservation has no automatic expiry.
• Visitor counter: the current server-side browser and daily-visit records have no automatic expiry. They support historical aggregate counts.
• Other correspondence and infrastructure logs: retention depends on the operational purpose, provider and any applicable obligations. No fixed deletion period is specified here for these records. Contact me about a particular message or record if you need more information.

Different service notices may give additional periods for agreed work or billing records. A deletion request may need to be assessed against any applicable obligation to retain a record.

Your choices and requests

You can ask about your information or request access, correction, deletion or restriction through the contact page or @ContactDuxaBot. You may also ask to withdraw a published Studio review. Include a request or review reference if you have one, and do not send passwords.

Requests are assessed under applicable data-protection law. Where processing relies on consent, you can withdraw it; this does not change processing that took place before withdrawal. I may need enough information to identify the relevant record and check that the request is yours.

I will update this page when the described features or data handling change. The update date above is separate from the site's original creation date in the footer.