YOUR INFORMATION
Privacy policy.
How this website handles your information, why it is used and how to get in touch about it.
Last updated: 27 October 2026.
Who is responsible
Paul Loyanich (legal name: Pavlo Loianych) operates loyanich.com and is responsible for the personal information processed for this website and the enquiries described here. Contact [email protected] for privacy questions and requests.
Business details: Pavlo Loianych, ul. Tadeusza Jasińskiego 26A lok. B2, 05-270 Marki, Poland. VAT ID: PL1251733723 (NIP 1251733723). REGON: 522232315.
This is a personal professional website. References to Tarkmote describe collaboration and delivery capacity; they do not make every enquiry a contract with a Tarkmote company. Where an engagement is handled by a separate contracting entity, its identity and any relevant processing arrangements are agreed for that engagement.
Information and purposes
Project enquiries and correspondence
When you submit an enquiry or send an email, I receive the information you provide, such as your name, email address, phone number, company, subject and message. Website enquiries are stored in Odoo CRM. I use this information to respond, understand the project and discuss a possible engagement.
For steps you request before a contract with you personally, the legal basis is those pre-contractual steps. For business enquiries on behalf of an organisation, it is the legitimate interest in responding and developing relevant professional relationships. Sending an enquiry does not subscribe you to marketing.
Required fields are marked on the form. Without sufficient information and contact details, I may be unable to respond. Please do not send passwords, access tokens, payment-card details, sensitive personal information or confidential datasets through the form.
News and Forum placeholders
The News and Forum links currently serve as placeholders. News email subscriptions and visitor Forum registration/posting have not been opened. These links do not enrol you in a mailing list. This notice will be reviewed before those features are opened.
Invited customer accounts
Public account registration is closed. Customer portal access is granted manually by invitation. If you accept an invitation or use an existing account, Odoo processes your account identifiers, contact information, authentication and session information, and the records you are authorised to access, such as your orders or invoices.
This information is used to provide the requested customer access, administer the relevant business relationship and, on the basis of legitimate interests, protect accounts and investigate misuse. Portal access does not grant access to the internal administration system. Keep your password private and contact [email protected] if you suspect unauthorised access or want to close your account.
Closing an account does not necessarily remove order, invoice or contractual records that must be retained separately. The unsuccessful-enquiry retention period does not automatically apply to customer accounts or business records.
Shop and transaction records
The Shop seller is Pavlo Loianych, operating a Polish sole proprietorship (jednoosobowa działalność gospodarcza). The personal professional name Paul Loyanich refers to the same person; the seller is separate from Tarkmote OÜ and Tarkmote LLC.
If you use the Shop, Odoo may process the contact, billing, order and other information required for the selected service or transaction. This supports steps before a contract, performance of the relevant agreement and applicable legal obligations. The seller and commercial terms shown for the transaction govern the purchase. Payment-related information is handled through the payment methods offered at checkout; do not send card details by email or in an enquiry.
Orders, invoices and contractual records are handled separately from unsuccessful enquiries. The retention schedule below explains the accounting baseline, continuing obligations and review of inactive customer records.
Website operation and security
Technical requests can include your IP address, requested address, time, browser/device information and error or security information. These are used to operate the website, diagnose faults and prevent abuse, on the basis of legitimate interests in a reliable and secure service.
Contact and sign-in protection (Google reCAPTCHA)
The contact and sign-in pages use Google reCAPTCHA to help distinguish legitimate requests from automated spam, fraud and abuse. This involves sending technical information to Google, which may include your IP address, browser and device information, and interaction signals used to assess the request. The service may use a security cookie or browser storage. This is separate from optional audience analytics.
I use this protection on the basis of legitimate interests in protecting accounts and communications. If the check cannot run or a request is rejected, the protected action may not complete. For an enquiry or help accessing your account, email [email protected]; do not send your password. See the Accessibility notice if a security check creates a barrier.
Providers, access and locations
The website, Odoo database and filestore use shared self-hosted infrastructure in Poland. Access is limited to people who need it to handle requests, support the systems or meet legal responsibilities. Authorised technical administrators may access the shared infrastructure for operation and support.
- Cloudflare: website delivery, DNS and security, including technical connection and request information. See Cloudflare’s privacy information and processing terms.
- Brevo: transactional email delivery from Odoo. Information needed to deliver messages may include recipient information and message content. See Brevo’s privacy information.
- Google Analytics: optional visit measurement after acceptance. See Google Analytics privacy information and Google’s processing terms. International processing may occur under the safeguards described below.
- Google reCAPTCHA: security checks for contact and sign-in requests. Google processes reCAPTCHA customer data under its Cloud Data Processing Addendum and applicable service terms. Its Cloud Privacy Notice explains the separate processing of service data. See Google’s reCAPTCHA information.
- Google Workspace: email correspondence through [email protected]. See Google Workspace processing terms.
- Stripe: payment processing when offered and selected at checkout, including payment, billing, transaction and technical information needed to process the payment, prevent fraud and handle refunds or disputes. Stripe also processes some information for its own purposes as explained in Stripe’s privacy policy. See its data processing agreement.
Necessary information may also be disclosed to professional advisers or authorities where required by law or needed to protect legal rights.
Processing outside the European Economic Area
External providers may process information outside the EEA, including through support or subprocessors. The applicable safeguards depend on the service and recipient and may include an adequacy decision or Standard Contractual Clauses with additional safeguards where required. Contact [email protected] for information about the arrangements applicable to your information.
Retention
The approved retention periods for this website are:
- Unsuccessful enquiries: 90 days after the enquiry is marked unsuccessful and closed, unless a legal obligation or specific legal claim requires longer retention.
- Routine access, application and error logs: 90 days.
- Security events and administrative audit records: one year.
- Regular backups: up to one year from creation.
- Accounting and tax records: the normal baseline is five years from the end of the calendar year in which the relevant tax payment was due, rather than from project completion. Longer retention applies where required by law, including an extension of the relevant tax limitation period.
Contracts, orders and supporting records are also kept where necessary for ongoing performance, support, warranties, payment recovery or specific legal claims. An applicable continuing obligation or legal hold can require retention beyond the normal accounting baseline; the continuing need is reviewed. Unrelated personal information is not retained merely because an accounting document must be kept.
The approved process is an annual review of inactive customer records. For active relationships, information needed for current projects, support and transactions is retained. When there is no continuing relationship, obligation or legal hold and the applicable retention periods have expired, personal information is deleted or properly anonymised, including relevant correspondence and attachments. Truly anonymised sales statistics may be retained indefinitely.
Portal access is reviewed separately and can be revoked when no longer needed. Closing an account does not erase records that must still be retained. Archiving a contact in Odoo only hides it from normal lists; it is not deletion or anonymisation.
This schedule is being implemented. Daily backups are in place; automated backup expiry and routine log and enquiry cleanup are not yet enabled. The annual inactive-customer review and related deletion/anonymisation workflow are approved policy and have not yet been established as a scheduled operational process. Contact me about a specific retention or deletion request while this work is completed.
Information removed from active records may remain in restricted recovery copies until they expire. Restoring a backup requires review and reapplication of applicable deletion and restriction decisions.
Your choices and rights
Depending on the circumstances and applicable law, you may request access, correction, deletion, restriction and portability of your personal data. You may object to processing based on legitimate interests on grounds relating to your situation. If processing relies on consent, you may withdraw it without affecting processing that took place before withdrawal.
Email [email protected] with your request. I may ask for proportionate information to confirm your identity and normally respond within one month, explaining any lawful extension. Rights can be subject to legal exceptions.
You may complain to the competent data-protection authority where you live or work or where you believe an infringement occurred. You do not have to contact me first. The European Commission’s information for individuals explains these rights and complaint options.
Cookies and analytics
Google reCAPTCHA may use security cookies or storage as described above. Odoo uses cookies or browser storage for functions such as sessions, language preferences, accounts and shopping-cart operation. Cloudflare security services may use cookies for request checks or remembering a completed challenge. Blocking these technologies can affect website features. See Cloudflare’s cookie information.
Google Analytics 4 is optional and is used to understand visits and improve this website. The Analytics script is loaded only after you choose Accept analytics. Reject analytics leaves it off. You can reopen Cookie settings at any time and choose Reject analytics to withdraw your choice; this disables further tracking in the page, clears accessible first-party Analytics cookies and reloads the page if Analytics was running. Withdrawal does not undo earlier processing.
Your accept/reject choice is stored on this device for 180 days. Analytics cookies created by this implementation are configured to expire after 180 days without extending that expiry on activity. Google Analytics user/event retention is set to 14 months with reset on new activity off; this is separate from browser cookies and does not set retention for standard aggregate reports. These settings do not govern server logs or backups.
Analytics may process online identifiers, device/browser information and page-interaction data on the basis of your consent. This implementation disables Google signals and advertising-personalisation signals and removes query strings and fragments from the page and referrer URLs supplied in its initial configuration. This integration does not intentionally submit enquiry contents, names or email addresses to Analytics. Plausible tracking remains disabled. For privacy requests concerning earlier Analytics data, contact me.
Updates and questions
This policy may be updated as the website and processing arrangements change. The date above identifies the latest revision. For questions or requests, contact [email protected].