ADMINEffective date: October 14, 2026. Last updated: October 20, 2026.
Who is responsible for this website#
YAADMIN is authored and developed by Kukhar Bohdan, the person responsible for the YAADMIN website and the account, contact and licensing services described here. Contact info@yaadmin.io for privacy questions or requests, or use Contact — Account & privacy.
This notice covers yaadmin.io, website accounts, newsletters, orders and the website licensing service. Customer-operated YAADMIN Core and Agent installations are separate environments. Their operators determine their own data use and third-party integrations. This notice does not claim that customer files, chat content, credentials or screen captures are automatically uploaded to this website.
Data we collect and why#
| Service | Information processed | Purpose |
|---|---|---|
| Website access | IP address and request information that the web server can record, browser/session identifiers | Deliver pages, maintain sessions and investigate abuse or errors |
| Registration and account | Email, username, display name, password hash, account dates, verification state and preferences | Create and secure your account, verify your email and provide account services |
| Google Login | Google subject identifier, verified email and available name/profile fields | Identify your account or link Google to an existing account |
| Contact and support | Name, email, topic, message, optional order reference, submission time and salted IP hash | Answer requests, maintain correspondence and prevent spam |
| Private support tickets | Account identifier, subject, category, message and reply text, optional owned-order reference, dates, status, staff participation and notification failure state | Verify paid-support eligibility, provide assistance and retain the service conversation |
| Commerce | Billing/contact details entered at checkout, purchased items, amounts, currency, order status, transaction references and order technical data | Administer orders, customer access, support and financial records |
| Licensing | Account email and verification state, associated WordPress user ID, installation ID, supplied app version, status and timestamps, entitlement records and audit context | Verify installations, deliver commercial access and record activation and entitlement changes |
| Email preferences | Email/subscriber identifier, subscription state, consent wording, source, time and confirmation history | Send requested updates and record your communication choices |
Required fields are identified on forms. Without the necessary email or authentication information we cannot provide an account; without contact details we cannot respond to a request. Optional marketing participation is separate from account, Google Login and license access. Do not submit passwords, activation tokens or confidential infrastructure information in public forms.
Passwords are processed by WordPress authentication and stored as hashes, rather than plaintext. Account verification and YAADMIN subscription-confirmation tokens are hashed and time limited. Installation authentication tokens and licensing verification codes are also stored as hashes. These measures do not constitute a guarantee against every security incident.
Application email activation and registration list#
The application activation service checks email syntax and domain mail DNS, then sends a six-digit code valid for 10 minutes. Successful verification proves access to the mailbox and automatically adds the address to the AcyMailing YAADMIN_REG technical registration/service list. Existing unsubscribe and confirmation choices are preserved. This does not enroll the address in the separate marketing list. Activation records include installation/account identifiers, hashed code and session binding, attempt counts, timestamps and synchronization state. Installation credentials are stored as hashes on the server.
Google Login#
Google Login is optional and uses the OpenID Connect scopes openid, email and profile. Google must report a verified email. We store the stable Google identifier and relevant account profile information; we do not receive your Google password or store Google access or refresh tokens after sign-in.
An existing account is not silently linked just because its email matches: sign in first and link Google through Account Settings. You can unlink it using your current WordPress password; Google-only users can set a password using the reset flow. Google processes your interaction with its service under its own Privacy Policy. Google Login does not itself grant a license or subscribe you to marketing.
WooCommerce, payments and licensing#
WooCommerce provides our catalog, cart, checkout and order infrastructure. Checkout is enabled for approved products. The configured payment integrations are Digiseller and PayID19 (cryptocurrency payments); the available method depends on the checkout and regional configuration. Payment providers process information needed to complete a payment under their own terms. Do not enter payment credentials into the contact form.
Order administration retains the relevant billing/contact details, amounts, currency, payment status and transaction references. Visiting a payment provider can disclose your request/network information and the purchase details needed for that provider. This notice does not claim that YAADMIN stores payment-card credentials. No automatic recurring payment is currently enabled.
The website licensing service records installation and entitlement information needed to administer access. Registration alone does not grant paid rights. Website account deletion does not automatically erase the independent licensing, audit, support or order records. These records require separate review when responding to a privacy request.
Email and newsletters#
We use WordPress email through the configured SMTP transport for verification, password resets and other service messages. AcyMailing manages subscriber records and preferences within the website. Technical user/customer/licensing segments serve administration and are separate from the marketing list.
Some registration and checkout forms initially select the optional marketing checkbox. You can uncheck it before continuing; new marketing enrollment requires confirmation. Account verification alone does not subscribe a person who did not select marketing. Newsletter-only enrollment discloses when an account is created and requires a consent choice. Consent and confirmation history can remain after unsubscribing to record your choice.
The optional newsletter welcome offer uses the existing YAADMIN News & Updates list and email confirmation process. After a confirmed subscription, an eligible address can receive one personal 15% coupon for a purchase of packages or paid modules. Coupon records include the permitted email, code, usage limits and delivery status. Support and update renewals are excluded; the coupon cannot be combined with other coupons. Digiseller checkout does not support this discount. Declining the offer does not prevent browsing or buying. Closing the offer stores a browser preference for seven days to avoid repeatedly showing it. Cookie consent does not subscribe a visitor to the newsletter.
You can unsubscribe through a newsletter's unsubscribe link or Account Email Preferences. Withdrawal does not prevent necessary account, security or order messages. Newsletter software can process delivery and campaign interaction information when its tracking features are used; this notice does not represent that a marketing campaign is currently running.
Cookies and browser storage#
Cookies and similar storage support functionality, rather than constituting blanket consent to all processing.
| Cookie or storage | Function | Duration or lifecycle |
|---|---|---|
| WordPress login/session cookies | Authentication and remembered sign-in | WordPress session or selected remembered-login period; logout ends access |
yaadmin_form_nonce | Bind guest forms to a browser and help prevent forged requests | Up to 24 hours |
ya_google_browser | Bind a Google authorization attempt to the initiating browser | Up to 10 minutes; cleared on callback |
| WooCommerce cart/session cookies | Maintain cart and customer session when commerce features are used | Session or WooCommerce-configured expiry |
yaadmin_welcome_dismissed_until (local storage) | Remember that you dismissed the optional newsletter offer | Seven days after dismissal; removable in browser settings |
yaadmin_consent | Remember cookie categories, choice identifier, policy version and choice timestamp | Up to 180 days, or until removed; a changed consent-policy version asks again |
WooCommerce sbjs_* cookies | Optional referral/source attribution: remember how you reached the store | Provider-configured session/attribution lifetime; blocked before marketing-cookie permission and removed where browser-accessible when permission is withdrawn |
| Other WordPress/plugin storage | Browser checks, preferences and features when used | Depends on the feature and browser settings |
Short-lived server-side records also support OAuth state, form verification and rate limits. Their expiry does not mean that the entire associated account is deleted. You can remove cookies or block them in your browser; this can prevent login, Google authorization, form submission or cart operation. Google may use its own cookies when you visit its authorization service. The YAADMIN cookie panel offers Necessary only, Cookie settings and Accept all. Optional categories are off until you choose them. Recognized analytics/advertising scripts, WooCommerce referral attribution and supported third-party embeds are deferred until their category is allowed. Necessary authentication, security, cart and checkout functionality is not conditional on optional-cookie consent.
Use Cookie settings or the persistent Cookie settings button to review or withdraw your choice. When you revoke a previously allowed category, the page reloads to prevent its deferred scripts from starting again. Known browser-accessible tracking cookies are removed; this cannot erase a third party’s historical records, inaccessible cookies or every possible custom tracker. New integrations must be reviewed and categorized before deployment.
Cookie preferences are stored in your browser rather than added to a new server-side consent database. A separate persistent consent log is not created by this panel. The Functional category controls supported optional third-party embeds; YAADMIN’s own video, screenshots and central integration map remain available. No standalone audience-analytics service was identified in the reviewed pages. Marketing currently covers WooCommerce referral/source attribution. Cookie choices do not subscribe or unsubscribe you to email: the existing newsletter/account confirmation process and Email Preferences remain separate and unchanged.
Legal grounds and use of information#
Where GDPR or equivalent rules apply, processing necessary to provide requested account, order or licensing services is based on performance of a contract or steps taken at your request. Protecting the service, preventing abuse and handling correspondence can rely on legitimate interests, subject to applicable balancing and your rights. Marketing enrollment relies on your consent. Records required by applicable tax, accounting or other law may be retained to meet legal obligations. These grounds are limited to the relevant purpose and do not authorize unrelated use of your data.
We do not sell personal information as part of the website functionality reviewed for this notice. No source-verified advertising profiling or solely automated decision process with legal or similarly significant effects was identified. Automated authentication, rate limits and entitlement checks can restrict access; contact us if you believe a restriction is incorrect.
Access, recipients and international processing#
Authorized website administrators can access data needed to operate the service and respond to requests. Hosting, backup and email infrastructure process data necessary for their services. WordPress, WooCommerce and AcyMailing are installed software; using their names here does not imply that all database records are sent to their vendors. Google receives information when you choose Google Login.
The contact inbox is stored on the website; contact email notifications are currently disabled. Contact and sales plugins support Telegram notifications if configured. Telegram credentials for these YAADMIN notification flows are not currently configured, so this notice does not claim active Telegram delivery. If enabled later, recipient configuration and data disclosure must be reviewed before sending customer information.
Information may also be disclosed when legally required or necessary to establish or defend a legal claim. Third-party services such as Google can process information in countries other than yours. The hosting jurisdiction, complete infrastructure-provider list and specific international-transfer arrangements have not been verified for this publication. We do not assert EU-only hosting, an executed transfer agreement or a regulatory certification. Contact us for available information about processing relevant to your request.
Storage and retention#
Website records are stored in the WordPress database and associated infrastructure; backups and mail systems can contain additional copies. Retention depends on the record's purpose, account/service lifecycle, applicable legal duties and outstanding disputes.
Account verification links are valid for 24 hours; YAADMIN subscription-only confirmation links for 48 hours; Google authorization state for 10 minutes. Form-browser cookies last up to 24 hours. Contact abuse counters use short-lived windows, including a 10-minute IP counter. Expired tokens lose their authority, but expiry alone does not prove immediate physical removal of every metadata or backup copy.
No fixed automatic deletion schedule is configured for inactive WooCommerce accounts or pending, failed, cancelled, refunded and completed orders. No verified automatic purge schedule was found for contact messages, licensing/audit records or consent history. These records can remain until manually reviewed and deleted or anonymized. We therefore do not promise deletion after an invented number of days. Account/service records are needed while providing access; order and entitlement history may remain necessary for ownership, support, accounting or claims after access ends.
A deletion request is reviewed across the account, newsletter, contact, order and licensing systems. Some information may need to remain for legal obligations or claims; where applicable we explain the reason. Unsubscribing alone does not delete an account. Deleting an account does not automatically delete its contact messages or independent licensing records. Backup rotation periods and server-log retention have not been verified, so immediate deletion from all backups or logs is not promised.
Your choices and rights#
You can update your display name and request an email change through Account Settings, manage marketing preferences, and unlink Google subject to authentication. For access, a copy of your data, correction, deletion or other privacy requests, email info@yaadmin.io from the relevant account address where possible. We may ask for proportionate information to verify identity and protect another person's data; never email your password.
Depending on applicable law and the processing grounds, rights can include access, rectification, erasure, restriction, objection, portability and withdrawal of consent. Withdrawal does not affect the lawfulness of processing before withdrawal. Rights are subject to applicable conditions; retention required by law can limit erasure. You may complain to the competent data-protection authority where the law provides that right.
WordPress offers administrator-assisted personal-data export and erasure tools. Their coverage depends on registered plugin exporters/erasers. We do not represent that those tools automatically include every custom contact, licensing or consent record; requests may require manual review. Requests are handled under applicable requirements, without promising an unverified service deadline or automatic result.
Security, children and updates#
The site uses HTTPS, WordPress authentication, browser-bound form protections, time-limited authorization records and access-controlled account views. No system provides absolute security. Contact us if you suspect an account or privacy incident.
YAADMIN's administration services are intended for people able to enter the relevant service agreement, rather than services directed at children. If you believe a child has supplied personal information without appropriate authorization, contact us for review.
We update this policy when material website processing changes, including activation of a payment provider or new notification/tracking features. The effective date above identifies this version. Significant changes may also be communicated through the relevant service or account channel.
Contact#
Kukhar Bohdan — author and developer of YAADMIN
Privacy and website inquiries: info@yaadmin.io.
About YAADMIN · Contact · Terms of Use
Private technical-support conversations#
Paid-support tickets are stored in the website’s WordPress posts and comments storage as private service records. Ticket views require account ownership; authorized site administrators and support managers can read and answer them. They are excluded from public search, feeds and ordinary comment listings. Service notification emails link to the authenticated conversation and do not include the full issue or reply text. No ticket attachments or automatic email-reply import are provided.
Ending a support period does not erase its correspondence. Ticket records currently remain until administrator review; no automatic deletion period is configured. For access, export or deletion requests, contact info@yaadmin.io. Standard WordPress privacy tools may not include every ticket and require manual review. Do not submit passwords, private keys or unredacted infrastructure data.